I created an extension that I load the new way with [XsltExtension] attribute without registering in xsltextension.config. It loads fine on my localhost (Windows 7) and is available in Extension dropdown in xslt editor. However it will not load on my public server (Windows Server 2008 R2), and I get no error in the Applicationlog
Are you sure that the proper permissions have been set? I supose you don't have any problems if you add the extension manually in the config file, right?
My apppool user has modify rights to all files at the moment, but I don't see how that should be nessesary. Either it reads the dll file or it reads the config file (I updated the config file manually). Or is there another reason why it should have write rights?
I think I have misunderstood the problem - I thought some package or something had been installed and failed because it could not write to the xsltExtensions.config file :-)
But nevermind me being confused since it seems I provided the correct solution anyway, eh? ;-)
xsltextension not registering in 4.6.1
Hi
I created an extension that I load the new way with [XsltExtension] attribute without registering in xsltextension.config. It loads fine on my localhost (Windows 7) and is available in Extension dropdown in xslt editor. However it will not load on my public server (Windows Server 2008 R2), and I get no error in the Applicationlog
Anyone got an answer to that?
/Bo Kingo
Hi Bo
Are you sure that the proper permissions have been set? I supose you don't have any problems if you add the extension manually in the config file, right?
/Jan
Hi Jan
The "manuel" method works, but how is that related to permission settings? The dll file containing the extension has modify rights
/Bo
Hi Bo
Well I think it makes sense that if network service or iusr does not have write permissions to the file then the changes can't be written.
Try giving full access to see if that works and then narrow it down afterwards for instance.
Hope this helps.
/Jan
Hi Jan
My apppool user has modify rights to all files at the moment, but I don't see how that should be nessesary. Either it reads the dll file or it reads the config file (I updated the config file manually). Or is there another reason why it should have write rights?
/Bo
Hi Bo
I think I have misunderstood the problem - I thought some package or something had been installed and failed because it could not write to the xsltExtensions.config file :-)
But nevermind me being confused since it seems I provided the correct solution anyway, eh? ;-)
/Jan
Hi.
I have the same problem. Extensions not showing up in Umbraco when only using [XsltExtension] in DLL. Any ideas?
----
Christopher
Not really. Its seems to solved in 4.7 beta. Haven't testet in 4.7 RC
/Bo Kingo
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.