When saving a Stylesheet that is too big, we get a permission Error in the back office
Hello,
We have a stylesheet of over 6000 lines (not rules, lines of code).
This renders well on the front end, but when editing it via the Umbraco Back Office we get a "Stylesheet not saved: Please make sure that you have permissions set correctly" warning. When we cut it down to less than 3967 lines, it saves as expected.
Did you ever figure out what was causing this issue? I am currently having the same issue and I was interested in finding out if you were able to solve it.
What browser are you using when trying to save the stylesheets? And are there any particular reason that you're editing it through the stylesheet editor in Umbraco? Usually that's not a best practice and should be done using a proper editor outside the Umbraco environment in my humble opinion. That will keep you out of these weird trouble as well :)
When saving a Stylesheet that is too big, we get a permission Error in the back office
Hello,
We have a stylesheet of over 6000 lines (not rules, lines of code).
This renders well on the front end, but when editing it via the Umbraco Back Office we get a "Stylesheet not saved: Please make sure that you have permissions set correctly" warning. When we cut it down to less than 3967 lines, it saves as expected.
When looking for signs of what might be wrong in the developer toolbar, the call "http://xxxxxxxx.umbraco.io/umbraco/webservices/codeEditorSave.asmx/SaveCss" responds with a 500 (Internal Server Error).
Did you ever figure out what was causing this issue? I am currently having the same issue and I was interested in finding out if you were able to solve it.
Thanks!
Hi guys
What browser are you using when trying to save the stylesheets? And are there any particular reason that you're editing it through the stylesheet editor in Umbraco? Usually that's not a best practice and should be done using a proper editor outside the Umbraco environment in my humble opinion. That will keep you out of these weird trouble as well :)
/Jan
Yup, we did.
Apparently for jsonserialization there is a limit of x characters (Unicode).
We added the following line in the Web.config file:
So it wasn't malformed css or something like that, the file (json) was too big.
The property maxJsonLength is an Int32 with a default value of 2097152 (which stand for 2097152 characters).
We have set it to the max of an int, which is 2147483647. That did the trick.
Thanks a lot for sharing, I will make the adjustments!
is working on a reply...