Well, code sample for publish is:
I added a screenshot on purpose so that you will need to retype it and see what IntelliSense does and what overload methods do. :) What is more important is that you know what each of the parameter means.
So to publish an item you need following:
you need an array of items you want to publish. Here you need to provide an ...
This is because most probably you reference Microsoft.OData.Client library in some event system, but you have not merged it with current DLL. Exception is self-explanatory. Some piece of your code cannot reference Microsoft.OData.Client library. By MSDN, it's not part of .NET framework, so you need to deploy it reference it additionally (either by merging it ...
If you want publishing dissabled, I would just stop publishers service. No need to remove targets and other stuf. You can even push notifications about maintenace. You can check how to achieve this by looking into Atila's Sos last year Tridion Developers Summit lightning talk
There is no out of the box option for this. It is either all, or some. There is no option to customize the existing GUI window to modify information during selection what needs to be done because the information about in which publications item should be published is done in Resolver after clicking on the button publish.
Now you can always construct your ...
I would use a custom resolver to achieve this. This is a class which is executed after an item has been put in the publish queue, but before it is rendered and transported to the deployer. They are easy to do and very flexible.
The following example might get you started (with the usual 'works on my machine' caveat):
I'm assuming you are altering the Page Package item and not the Output JSON... but in any case, what you are trying to achieve is not possible using templating.
You can however override the Page publish url using a Deployer extension, but why do you want to do that in the first place? I have the feeling that that's asking for trouble, ie. you will be ...
Based on your comment that "the network team did some changes on server where we have deployer setup" the most likely issues will be:
Deployer not running (is it a service or an HTTP upload web application?
Firewall blocking the Deployer port from other servers (if the Deployer server is a Windows Server most likely it is the Windows Firewall blocking it)
Please check following:
restart transport service
connectivity between CM and broker DB
connectivity between CM and Deployer server [if CM and Deployer servers are different]
Check incoming folder in deployer server. is it receiving any package. in current situation it should not be. but it's worth to check.
revisit all ...
As Marko mentioned, if you want to suspend publishing altogether, you could just stop all Publisher Services.
If you are using Topology Manager, you can also mark individual CD Environments as "offline". This will suspend publishing to those CD Environments only.
Maybe a reason to migrate to Topology Manager based publishing? :-)
I would try to accomplish this at the template level, rather than event system. In order for Tridion to deploy an image (binary) it needs to call Engine.AddBinary(...) and if you are using your own templates you are doing that already for any binary you are publishing. If you are using other frameworks, such as DD4T or DXA, there's also a common place for ...
maybe first check DB configuration in CD Discovery Service, and test DB is accessible from CD with port number and user account.
also verify the CD Discovery Service endpoint is accessible https://prod-discoverysvc.ccccc.com/discovery.svc. username/password is correct with topology setup. if not please provide test and maybe try other checks.
Looks like the issue is having communication issue from CMS to discovery service. Please register the keystore on CM for discovery service and enable keystore entry on cd_transport_conf.xml
Example : Under sender type: DiscoveryService
Keystore : <Ketstore Path=“jrepath\lib\security\cacerts” Secret=changeit”
Hope this helps .
A page does usually not contain any direct reference to an image (it could, through page metadata).
A page does contain a list of component presentations, and a component presentation contains a component which may contain a field linking to an image.
So, what you could do is
- go through all fields of the page metadata to check if a field is a multimedia ...
Looking at the SDL Tridion 2013 SP1 Product Prerequisites PDF document that's available from the Product prerequisites page in the Tridion 2013 SP1 documentation, neither Windows Server 2016 nor SQL Server 2016 are listed as supported.
However, that does not mean that the definitely won't work! If you have the software and some time then you could try it (...
Maximum Window Size exceeded is triggered when the amount of in transit transactions has reached the WindowSize value, this is mainly to protect the Deployer from getting too many zip packages at once. You have not provided the exact version of Tridion 2013 and hot fix applied, (is it SP1 HR-1?) but you may need to look if you have the latest fix applied as ...