I think the problem lies in the fact that your event handler is asynchronous (and you're subscribing to the TransactionCommitted phase).
A Save action normally happens on the dynamic version (v0) of an item. So, the -v0 in the TCM URI is no surprise.
However, if you do a typical save-and-close/checkin transaction, the check-in action typically results in ...
No, not out of the box.
There were several extensions floating about.
http://yabolka.com/gui-extension-readonly-and-hidden-fields-in-tridion-2011-and-up/ was an original from 2011, with a couple of TREX questions you should be able to get this working (e.g. Readonly fields in Tridion 2013 SP1)
To cut a long story short, you could write an extension that
As posted in this announcement, SDL Tridion 2013 SP1 became out of Standard Support as of December 31, 2019. Any issues encountered for the year following would be addressed on a best-effort basis and only if your organization has an agreement in place with SDL.
Refer to the SDL Product Lifecycle for the support policy, which explains Extended Support with ...
I don't think anything specific to Webbdav url is changed in Web 8.5.
Probably underlying framework is handling url encoding a bit differently.
If you do Url decoding of both Webbdav paths, you would see two identical strings.
I'll answer the second question first
how we can reuse the Tridion search functionality in a Custom Page.
Take a look at Core Service, and GetSearchResults (and other related methods for retrieving the results of a search). For filtering take a look at SearchQueryData which is passed in the previous method.
As for the first question,
Is the same ...
If you create the page in the root SG, the sitemap.xml will be available in your rootURL/sitemap.xml. The crawler should be able to browse the site to pick it up, without any modifications or customization.
If for some reason, you need the file to be physically available on the root on the project (on the filesystem), you have a few options.
Use a ...
I've written a script using the CoreService to traverse every folder and structure group across the whole BluePrint.
This includes the expected settings in the system to get the same authorization setup (or perhaps Security Access Profile, if you will).
However, it doesn't gather the information ...
Sadly, I don’t think that is possible - you’re going to need to write a Core Service script to traverse every folder and structure group (across the whole Blueprint) and build up you’re own list.
Once you have this info, you could write an Events System tool to record any permission changes in these items to prevent you having to run the report again.
Agree with both Alvin and Mark, it's a very broad topic and depends on what exactly you need/want "Know Your Needs" and on that note, here is a quick link which might interest you..
After doing a lot of trial and error, I was finally able to cache my object. Here are my findings for anyone trying to implement caching in DXA. These are not specific to DXA but common for Springs+EHCache.
@EnableCaching annotation on your context configuration class,
provide appropriate cache manager beans,
separate service bean into interface and ...
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 ...
well, that's a pretty open question and depends very much on the requirements/expectations of the client (business and technical).
Perhaps it would be best for you check a few of the many blogs out there and then to write a blog proposing your thoughts - then any technical questions can be posited in this forum?
You will need to reach out directly to SDL Support. As of Jan 1st 2020, SDL Tridion 2013 SP1 HR1 entered in the "extended support phase" as per the notification at https://community.sdl.com/product-groups/sdl-tridion-dx/tridion-sites/b/product-announcements/posts/sdl-tridion-2013-sp1-hr1-standard-support-extended-to-december-31-2019.
I'm not sure if SDL ...
Since, you are using DXA, I will say the approach of generating the sitemap might not makes sense (unless there are other fine prints which we are not aware about).
The correct approach could be similar to the one mentioned here:
Generate Sitemap XML File using default functions of DXA 1.5/1.7 in Web 8/8.5
You can use the Compress output TBB. you can enable compression by setting the parameter CompressionEnabled to 'yes'.
I am not sure about the TBB location for DXA 1.7 but for DXA 2.2 the location is "\100 Master\Building Blocks\Framework\Developer\Templates\DXA.Legacy".
It turns out that in the web.config of the topology manager the old domain name was still used for the user credentials after encrypting the config and changing the setting things work like a charm. the documentation is a bit confusing on doing this encryption, so for those who want to know the below lines work:
aspnet_regiis.exe -pdf "database" "C:\Program ...
You cannot prevent an exception or error being thrown by the application for pages or items that does not exist. However, you can customize the error message or throw errors differently to create a better user experience.
You can look through the example for DXA 1.4. It should be pretty similar to the DXA version that you are using, though.
The other way ...
You will need to do a SystemWideList with a TargetTypesFilterData filter, with the ForRepository property set.
Here is an example in PowerShell:
$client = Get-TridionCoreServiceClient
$filter = New-Object Tridion.ContentManager.CoreService.Client.TargetTypesFilterData
$linkToPublication = New-Object Tridion.ContentManager.CoreService.Client....
The encoding is determined by Chilkat based on the content. It is, unfortunately, a bit of a black box. Sometimes that detection fails and it picks the wrong encoding. That appears to be the case for you.
Luckily, we built in an override for just such a situation. You can set the FixedEncoding element in OutboundEmail.xml to an encoding that will work for ...
I see these encoded in my test system also. From what I understand of WebDAV, encoding these shouldn't cause an issue. I presume both values function the same?
I understand that parenthesis' are classified as sub-delimiters (W3C) so I wonder if they need to be treated differently as part of a URL as with being part of a set of URL Parameters. ...
You can conditionally execute the XPM filters per environment by defining your own custom filter which implement a FilterChain with the chain.doFilter() command executed conditionally based on your environment configuration.
You're essentially replacing the XPM filters in the web.xml with your own custom ones that conditionally execute a FilterChain.
I faced the similar issue when porting from current environment (DXA working) to new environment. Copying the DXA Application Data Definition.xml to [tridion home]\config\ImportExport\ApplicationData solved the issue.
In general, you need to have CD (incl. ADF) somewhere in your architecture to make Session Preview work.
In the architecture you describe, you do have CD (underneath DD4T), but the challenge is that it is not directly in the Web App itself, but in a (custom) REST service.
With Session Preview, the XPM front-end will send a cookie containing a Preview ...