Looks like there's a similar PreValue problem for the id for a RTE stylesheet; for example, the config file for a datatype we've created looks like this;
Note the "1732" parameter, which is the local node id of the associated stylesheet - but that's different on the target server, so I get errors logged in the UmbracoTraceLog;
2013-08-16 15:55:07,343 [58] ERROR umbraco.editorControls.tinyMCE3.TinyMCE - [Thread 38] Error adding stylesheet to tinymce Id:1732 System.NullReferenceException: Object reference not set to an instance of an object. at umbraco.editorControls.tinyMCE3.TinyMCE..ctor(IData Data, String Configuration)
I'm probably going to port soft of the stuff i've done for the Content Version that does map these id's back over to uSync so it can workout IDs between versions.
Thanks for uSync, it is a really cool product and it allows us to do some really cool automations. I was wondering whether you got around to providing a workaround for this RTE prevalue issue?
We are currently facing this as an issue and I'm not sure how to handle this. We could remove the RTE definition from our source control and have it as the ONLY data type that we have to manually service during deployments to each environment. But it would be really cool if you had a fix for this.
Richtext Editor Stylesheet node ID
Looks like there's a similar PreValue problem for the id for a RTE stylesheet; for example, the config file for a datatype we've created looks like this;
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
Note the "1732" parameter, which is the local node id of the associated stylesheet - but that's different on the target server, so I get errors logged in the UmbracoTraceLog;
Yes, i am looking at that at the moment
I'm probably going to port soft of the stuff i've done for the Content Version that does map these id's back over to uSync so it can workout IDs between versions.
Hey Kevin,
Thanks for uSync, it is a really cool product and it allows us to do some really cool automations. I was wondering whether you got around to providing a workaround for this RTE prevalue issue?
We are currently facing this as an issue and I'm not sure how to handle this. We could remove the RTE definition from our source control and have it as the ONLY data type that we have to manually service during deployments to each environment. But it would be really cool if you had a fix for this.
Thanks!
is working on a reply...