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
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
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
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
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
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
Thanks for your valuable responses and i figured this issue myself by activating the tcmpublisherlog which gave me a clue giving an error saying about a connection failure regarding MSDTC process and firewalls .
The issue is i have CME configured in one server and the db server in another so we need to have the host entries in both the servers for each ...
11
There could be a few problems here, try the following:
It could be a permissions problem, check the permissions for the account doing the deployment.
You could try changing the storage configuration to not publish to the broker, helping you better determine where the problem lies.
Try unpublishing/republishing from the CMS.
Ensure that the license file is ...
11
Check your storage configuration (cd_storage_conf.xml or cd_broker_conf.xml for older systems), specifically the storage location for ComponentPresentation items with item extension ".ascx"
You need to ensure that you are publishing your ASCX web controls to the file system and to somewhere within your web application in order that .Net will execute them.
...
11
In the UnPublishEventArgs there is a member UnPublishInstruction.
This will have a property - StartAt - If StartAt property is set to DateTime.MinValue that means the Unpublishing is scheduled for Immediate unpublish and if it is set to a particular datetime, that means it is schedule to unpublish at some other time.
11
This is most certainly by design, it should be impossible to move a page if the page is published to a specific location.
You have three options - the third one I wouldn't do, but it's there:
1) Unpublish the pages and then move them to the desired location, then republish
2) Create copies of the pages and publish them - then simply unpublish and delete ...
11
You may want to consider using the Child Publications Only Resolver eXtension from the SDL Tridion World site that was developed by Bart: http://sdltridionworld.com/community/2011_extensions/childpublicationsonlyresolver.aspx
You still enable the Publishing Target for the parent, but the parent's items are removed using a Custom Resolver.
11
Sounds like you haven't added a mapping for that Publication to an environment.
You do that using Add-TtmMapping. For more information, see the following documentation page: Mapping a Publication to a Web Application
11
It is actually a windows path limitations and error comes from it
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath
10
I was missing the requestLimits element as in:
<system.webServer>
<security>
<requestFiltering>
<!-- This is the value in **bytes** -->
<!-- 524288000 bytes = 500MB -->
<!-- The maximum for this is 4,294,967,295 (3.99GB) - http://stackoverflow.com/questions/4022434/-->
<...
10
You can, indeed, configure queue filtering so that your scale-out publisher only processes some items. For the most common use-cases, you probably don't want to do this - mostly it makes sense just to have an extra publisher picking up items in the normal order and generally helping to improve throughput.
If you don't mind having an under-utilised ...
10
You can use the Event System and Subscribe to the PublishTransaction SaveEvent and then add a handler to check the State. Here's an example code below:
// Ties into the PublishTransaction for save event
private void InitializeEvent()
{
EventSystem.Subscribe<PublishTransaction, SaveEventArgs>(HandlerForTransactionSaved,
EventPhases....
10
The protocol of deployment is setup in the Publication Target on the CMS, this is done under Destinations in the General tab of the Publication Target.
The configuration of the Deployer is just specifying where to pick the transport packages up from, unless it is a HTTP/HTTPS Deployer, then the protocol is depending on the setup of the website (either HTTP ...
10
By changing the settings in cd_storage_conf.xml so that the default storage area my local file store I found an ascx file corresponding to my component presentation. Once this was present my page was correctly rendered.
<Storage Type="filesystem" Class="com.tridion.storage.filesystem.FSDAOFactory" Id="defaultFile" defaultFilesystem="false"...
10
I'm not sure there is a correct answer here... i think it's based on the client needs.
Here's an opinion...
It's now possible to store binaries in the broker database, it makes a great case for managing them in the CMS, so that external 'consumers' (development teams, partner websites, load balanced machines, etc) can consume / store these files and ...
10
There is not a way, out of the box, to see all publish history. By default only the last published date is available.
You could trawl the deployer log files for the publish transaction, but that would not tell you who published it.
If you require this functionality / audit trail, you would have to implement Tridion Events system and record each publish to ...
Only top voted, non community-wiki answers of a minimum length are eligible
