Using 4.1, if I right-click on the root XSLT directory to "Create" a new XSLT and then, without ANY modifications to the XSLT file, click to save the new XSLT, I get an error message that the file can not be saved.
I had the web host open permissions for Network Service to all directories off root, including the XSLT directory.
Do you also get an error when trying to view the created XSLT file? If that is the case you should probably try to checkout if there is missing a reference to a custom extension if you're using such one in the xsltExtenstions.config.
Jan: well, I can save the XSLT when I turn the error-checking off. THEN, yes, I can view the created XSLT. I just had the web host change permissions for all directories off of root for full permissions to "Network Service" should I do the same for IUSR account? That seems like a security vulnerability?
Ove, I think the answer is yes, i.e., the "front" or default page for the site redirects to another page inside the content tree.
So XSLTs that existed before I redirected the home page continue to work (and they do) is that consistent with this? I suppose I could also temporarily disable redirection, make the XSLT/Macro and then re-enable it? (I'm going to check out the uComments package, but I'm just curious)
Anyways, the uComponents Permanent Redirect is better for SEO, as the umbracoRedirect is a temporary redirect which Google doesn't index.
I.e. if you use it on your home page and redirect to another page, Google will see those pages as two different pages and they will therefore "steal" ranking from each other.
Using umbracoPermanentRedirect and uComponents solves this problem.
Can not save new, unmodified XSLT in 4.1
Using 4.1, if I right-click on the root XSLT directory to "Create" a new XSLT and then, without ANY modifications to the XSLT file, click to save the new XSLT, I get an error message that the file can not be saved.
I had the web host open permissions for Network Service to all directories off root, including the XSLT directory.
I do not see any errors in the UmbracoLog
What to do?
Hi Kyle
Do you also get an error when trying to view the created XSLT file? If that is the case you should probably try to checkout if there is missing a reference to a custom extension if you're using such one in the xsltExtenstions.config.
What permissions are set for the IUSR?
/Jan
Do you use umbracoRedirect on the container node for your site?
Jan: well, I can save the XSLT when I turn the error-checking off. THEN, yes, I can view the created XSLT. I just had the web host change permissions for all directories off of root for full permissions to "Network Service" should I do the same for IUSR account? That seems like a security vulnerability?
Ove, I think the answer is yes, i.e., the "front" or default page for the site redirects to another page inside the content tree.
Then that is your problem. When having an umbracoRedirect on your default page, saving XSLT from the webinterface doesn't work.
You can try to use uComponents umbracoPermanentRedirect instead.
Ove, very interesting.
So XSLTs that existed before I redirected the home page continue to work (and they do) is that consistent with this? I suppose I could also temporarily disable redirection, make the XSLT/Macro and then re-enable it? (I'm going to check out the uComments package, but I'm just curious)
Thanks!
Kyle
Yeah. It only affects saving XSLT files.
Anyways, the uComponents Permanent Redirect is better for SEO, as the umbracoRedirect is a temporary redirect which Google doesn't index.
I.e. if you use it on your home page and redirect to another page, Google will see those pages as two different pages and they will therefore "steal" ranking from each other.
Using umbracoPermanentRedirect and uComponents solves this problem.
Ah yes, the good ol' umbracoRedirect bug...spot on Ove - you rock! :-)
/Jan
is working on a reply...