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 ...
14
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 ...
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 ...
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'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 ...
10
I would add one more possible cause to the list
Also check (any of) it's grand-parent Structure group properties:
if it is set to Publishable=false.
Although it doesn't seem a logical place to look for, but I have seen this behavior before.
10
These are specified in the Security section of the Business Process Type (for each Purpose).
The Business Process type is then included in the Publishing section of the Publication Properties.
9
It is because that you can not publish a Keyword but the Category. If you meant to say that even for Category the publish button is disable, then explore its properties and see if the Checkbox - "Publishable" is marked or not as shown below:
9
That link you refer to has nothing to do with publishing, but with uploading files into the CM
I assume you use the http(s) deploy method for publishing files. In that case, you should go to the web.config of your website where your httpupload.aspx file is hosted (that file is responsible for receiving the publish packages from your CM).
The web.config ...
9
This error seems to be quite common to newer Tridion devs, so it has been covered already in quite detail. Basically what happens is that you have already published another Multimedia Component to the same presentation folder under the same file name.
Please check the resources below:
https://stackoverflow.com/questions/12458609/attempting-to-deploy-a-...
9
The correct answer would be: "any way you like".
But to give you a hint in the right direction, for a survey you need forms, and something handling their responses. Both can be found in for instance Wufoo.
And there just happens to be a nice ECL provider for that, available for free on SDL Tridion World
9
You can't disable it, but you can make it a really bad choice. Depending on your environment, let's say you have 3 publishers, you could configure 2 out of the 3 machines, to only work on medium and low priority jobs, meaning that all high-priority jobs would be processed by a single server instead of all 3.
You can also configure your publishers to not ...
9
As mentioned for TBBs to be able to make changes to CM items, you need to set allowWriteOperationsInTemplates = true in the Tridion.ContentManager.config on all machines that are rendering for you, so this means all CM servers and all Publisher servers.
Please note that as documented, SDL strongly recommends against this practice as it compromises your ...
9
The reason behind Target Types is abstraction.
In principle, for most implementations, all you need is 2 target types:
Staging
Live
On a true global deployment model, "Staging" for your vietnamese editors might be a site running somewhere in APAC, while "Staging" for your French editors could be a site hosted in Amazon Ireland (Dublin).
Here you have 2 ...
9
Clear-TcmPublicationTarget doesn't delete the target - it "decommissions the specified Publication Target". Meaning the system forgets that anything was ever published to that target.
Step two is to actually delete the Publication Target and its associated Target Types, which you can do using the API or the UI.
If you wish to do it through the UI, you'll ...
9
For #1 publishing priority is the way to go. Maybe changing the default priority to "low" will give you enough of an override to push things through quickly. Using publishing priorities in conjunction with the information I share in the blog post on keeping threads available.
Item #2 might need event system, but you should be careful of performance impacts. ...
8
The 'Throttled' state means that the Transport Service is unable to move the transport package (a zip file) from the Publishing server (often the same machine as the CM server) to the Deployer server.
This is normally because the Deployer is too busy to handle any more 'Incoming' packages. We can increase the 'Window size' on the Deployer server, to allow ...
8
I agree with John that it would be based on the clients needs, but also in relation to what development and deployment model you have chosen.
When looking at the different implementation options, I like the simplicity of having HTML in your (DWT) Templates and then often will go for Publishing CSS and JS as Pages (personally hate the idea of using ...
8
Here is the logic that I use with clients (and chiming in with what Alvin said):
C# is code, therefore belongs in a code repository (e.g. SVN).
Java is code, therefore belongs is a code repository.
SQL scripts is code, therefore belongs is a code repository.
.... should I go on?
So what makes JavaScript or CSS any different? It is code that also needs to ...
8
It's the same event as publishing 'now'.
The difference is simply that the PublishInstruction will have the StartAt property set to the date/time selected for rendering, and the DeployAt property set to the date/time selected for placing the content online.
8
Content Delivery
In your cd_deployer_conf.xml, modify the "Cleanup" attribute of the Queue Location element to be "false":
<Queue>
<Location Path="c:\tridion\staging\incoming" WindowSize="20" Workers="10" Cleanup="false" Interval="2s"/>
</Queue>
Restart your deployer for these changes to take effect.
Content Manager
Modify your ...
8
Indeed, the installer should not force you to create a new CM Environment in Topology Manager. If it does, that should be reported as a defect.
As a work-around, you could create a dummy CM Environment (like you did), then change the TRIDION_CM_ENVIRONMENT_ID environment variable and use Remove-TtmCmEnvironment cmdlet to get rid of the dummy thing again.
8
As Nuno explained in this question: its main reason is abstraction.
What you can set on Target Type and not on Publication Type is security. For second, you have have multiple target types that point (publish) to same Publication Target which gives you more flexibility with it.
8
In a DAO, you can try to fish out the Deployer Action like so:
LocalThreadTransaction.get().getDeployerTransaction().getDeployerAction()
Only top voted, non community-wiki answers of a minimum length are eligible