24

You may have to create a web.config file in the root of the HTTPUpload web application. Here is an example web.config that I've used in the past: PLEASE NOTE: One of these values is in kilobytes, and the other in bytes - Pesky Microsoft! <?xml version="1.0"?> <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> ...


21

The Publisher machine is basically a CM machine that users don't have access to. All communication to the publisher service (even if it is running on the same machine) is done via some database tables (exposed in the UI as the Publishing Queue, but obviously this is a simplified view of it). Basically the publisher service, on startup, starts "listening" to ...


20

Try to explain this to the Business User: It shows success because it processed correctly every item that this publishing transaction was resolved to. It is unfortunately not as easy to change this behavior as one would think (without performance impacts, which we all know is not what the Publishing Queue needs right now). You send ItemX to the queue. ...


17

Via core service you can retrieve PublishTransactionData object, which contains all info about transaction itself: PublishTransactionData transaction = (PublishTransactionData)Client.Read(transactionID, new ReadOptions()); PublishTransactionState transactionState = transaction.State; DateTime transactionStateChange = transaction.StateChangeDateTime; string ...


16

This behaviour is normal. Tridion keeps a list of all published multimedia components and their actual files on the file system. If you would change the name of a file in the multimedia component and republish it, it will update this record, and remove any old files, and put the new file in place. If this wouldn't happen, the server you publish to would be ...


16

Actually there is a better and far safer solution than the one @Nuno proposes. What you can do is "mock unpublish process". You can capture undeploy transport package on CD side of some other page, then change it to have id of your page (change XML that contains inpublish instructions), and copy it into incoming folder of deployer. Deployer will pick it up ...


15

Looks like you need to add a resolve instruction object to your publishing. I did something similar when I wrote the PagePublish Power tool (you can view the full code here: https://code.google.com/p/tridion-2011-power-tools/source/browse/trunk/PowerTools.Model/Services/PagePublisher.svc.cs) The main bits you need are: The call to publish : coreService....


15

Was Java version 7 recently installed on that machine? I've recently seen the same error when a sys admin removed Java 6 and installed Java 7. Also check if all the necessary Jar files are present in the \lib directory. It seems that the javax.xml.xpath Factory class can't be loaded.


14

The biggest "gotchas" I've had with an R5.3 to 2011 upgrade were mostly on the Content Manager side. Definitely follow the other answers for ways to confirm your final presentation-side markup, but be sure to test and synchronize your CMS-side components manually or with code. Issues the community's helped me with: CM-side: Image References change, mainly ...


14

Be careful here - you are seriously changing the default behaviour of Tridion - the ability to republish all pages where a component is used by publishing the component is very useful for editors who may not know where a component is used, but want to make sure that it is up to date all over their website. Why is it that you do not want the pages to be ...


13

The publishing queue is designed to be a queue, not a logging mechanism. Restricting users from deleting publish transactions has it's disadvantages. I.e. it refrains users from deleting big transactions in a busy publishing queue. Why not implement an alternative logging on who published what at what time? This could be done with an event system by ...


13

Yes - the core service supports publishing. Have a look at: ICoreService2011.Publish you can call it with the following signature: IEnumerable<PublishTransactionData> Publish( IEnumerable<string> ids, PublishInstructionData publishInstruction, IEnumerable<string> targets, Nullable<PublishPriority> priority, ...


13

This could be one of two things: 1> The Structure Group is marked as unpublishable, as is detailed in this question Why does publishing a page in a non-publishable structure group give a publishing success status? 2> The pages in the Structure Group have not yet been published to the target you are using. In the case of two you can uncheck the checkbox ...


13

From my experience I have seen this happen a lot when the WindowSize you configure in cd_deployer_conf.xml is larger than the Workers, also configured in cd_deployer_conf.xml. Items get transported to the Deployer and are simply waiting to be deployed. But if mass publishing is going on you will see a lot of files in the Deployer's incoming directory ...


13

The problem here is that it is an unpublish operation and no templates are executed and we cannot use the AddInstructions method available in the RenderedItem class. As an alternative there is a non documented extension point called a TransportHandler, you need to implement the ITransportHandler interface that is located in a GAC assmebly Tridion....


13

What you propose is definitely the approach I would take... Remove the "publish to SmartTarget" TBB from the Component Templates to make sure items don't end up there again... Create a set of "delete" operations for Fredhopper (probably scripted to make sure I don't copy/paste the wrong URIs) Drop this file in the "incoming" folder of Fredhopper I was ...


13

You'll need LoadFlags.Expanded, and then you can get the items from the PublishContexts. I've just done a little POC with the following code and a published Structure Group and both resolvedItems and processedItems arrays have four items in them. void Main() { ReadOptions opt = new ReadOptions() { LoadFlags = LoadFlags.Expanded}; string ...


12

There's multiple ways in which something like this could be handled... Unresolve the resolving The Tridion Publisher Resolving process is the one determining that there is nothing to be unpublished, because item x is not published to target y. One could potentially write a custom resolver that would change this behavior, so that the unpublish instruction ...


12

As always, there's multiple ways to skin this cat... You could always write an event that would catch the DELETE action on a PublishTransaction object and cancel it - though this may have other repercussions I have not researched (will the purge tool still work for instance) You could disable the delete button for non-Admins via a GUI extension as mentioned ...


12

1) No, but see my answer to 3 2) the license file is validated, minimally, on initialization, which for the deployer is on start up (for other use cases it might be per session/request) 3) the deployer supports deployment to the file system as a default (legacy support), hence with a faulty key it worked. As this is intended behavior you did not see an ...


12

You have default option for SFTP not FTPS in Tridion. but Tridion allows custom implementation also. you can also check following sdllivecontent url http://goo.gl/BGZb2 (Requires login) Its says: A default installation of SDL Tridion does not support the following protocols: SCP (Secure Copy), which uses SSH1 (Secure Shell version 1) FTPS,also known as FTP/...


12

Verify first that there is a valid reason for use a protocol that is not offered Out of the Box In case you are interested in using a protocol that is not available in the product, here are some steps so you can get started: Create a new protocol schema and add the required fields (The name of the schema has to match with the Type attribute you use in the ...


12

The exception - java.lang.ExceptionInInitializerError - suggest that you JRE/JDK is not functioning correctly and you may need to un-install and re-install the JRE on your CMS and/or on your CDA servers. Follow below steps to verify: Go to Command prompt Navigate to the installation bin path of your JRE - by default for 32-bit it will be something like - C:...


12

The problem is with the Java Development Kit installation. Looking back at the prerequisites for the Tridion 2013 I decided to check the Java installation. Even though I had just done a fresh installation of Java, when I tried java -version in a command prompt I received the error message Error occurred during initialization of VM. java/lang/...


11

There is no out of the box tool from SDL which allows you to compare two sites. I would say you best bet is to use a tool like HTTrack to download a copy of the new and old sites, and then use a file/folder comparison tool like WinMerge to identify any delta between the two data sets. Some similar suggestions have been made in this Drupal related post: ...


11

Just to add a little extra To Bart's answer: If you expand the 'See items to be published' in the Publish dialog box, you'll see there are no items to be published. It would be nice if the publish dialog did have a message to let you know that zero items will be published.


11

The Publish Status is related to the Publish Transaction and everything in it, if that does not raise any warnings or errors, it ends up as successful. The funny (and sometimes annoying) result of this is that an empty Publish Transaction, will always return successful instantly. When publishing a Page in a non publishable Structure Group, the Publish ...


11

I actually think it's a pretty good idea not to upgrade the broker databases. Broker databases are in their nature ephemeral, and publishing afresh from the CM is the right thing to do. Regarding the comparison of pages, I don't see why you would expect Tridion to have a tool for this when there are any number of excellent web testing tools. So for example,...


11

Generating a big XML on publish time is the easiest option but can be a time consuming action, specially as you will need to trigger republish on every page publish/unpublish. I have seen some sitemap publish taking minutes. There are many options, but my favorite approach consists on 2 steps: publishing small XML fragments with every page publish/...


11

What we implement most of the times (for .NET front-end apps): a table on the front-end DB to store the sitemap information create a custom deployer to store sitemap information at publishing time create a custom .NET sitemap provider using this custom table. This way has (imo) following advantages: sitemap is always up to date (each publish/unpublish ...


Only top voted, non community-wiki answers of a minimum length are eligible