Hello Amir,Can you copy your schema extension here ? It's difficult to help without more elements. It can come from your extension, but to be sure we have so see it.Also, when you go to the nms:recipient schema edition, even if you can't edit it, you can see the generated schema (with its extensions...

Here what the console send to the server to get the HTML content :<Transform xmlns='urn:ncm:publishing'> <strPublishingId xsi:type='xsd:string'>cus:Content1</strPublishingId> <strModelName xsi:type='xsd:string'>HTML</strModelName> <elemContent xsi:type='ns:Element'> <Content1 ....... xt...

hello @bryceh57660644, Is the solution of Manoj ok for you ? I think this should work. When I go to your web site, I see you followed his recommandations, but there is a code problem (you declare a function 'saveTrackingTag' without the 'function' instruction and it throws an error).

Hello,I know the situation : you use the embeded content into the delivery (with publishing model linked). Users edit directly the content (ncm:content) with the delivery form.I just did some test, and yes, the embeded content cannot be modified with standard method '.save()' (or maybe needs somethi...

Hi, Did you try the last solution I gave (the one with xtk:session:Write instead of save() ?). This is exactly the purpose : you can't save as this the delivery embeded content. Maybe you didn't see it, I copy it as a new solution.

Hello,Do you have access to the server ? I mean, not through the console, but with FTP access or a distant desktop ?If so, you can create subfolders in the 'res' folder. These subfolders are accessible with the HTTP access to the 'res' folder. Another way should be to upload a zip file of your folde...

Hello,I know the situation : you use the embeded content into the delivery (with publishing model linked)I just did some test, and yes, the embeded content cannot be modified with standard method (or maybe needs something more). Unfortunately you can't just use the load method, modify the xml part o...

Ho sorry Laurent ! I didn't notice your answer bellow ! Very Sorry !

Hi, after another test, I confirm that the installation lang is linked with the instance locale (<userInfo instanceLocale="xx-YY"/>). It's defined into the config-instanceName.xml(serverconf > shared > datastore@lang value), so if you "force" the lang into the registry and that corresponds to the in...

Also, @Ken_Qrious, Is there some lines in the delivery logs ? What are the dates for each lines ? It could be usefull to follow the differents steps, and see if the end of the delivery is long time before the post processing call, or if the problem is in the delivery itself ? Cedric