Can't edit custom css

Permalink
I get this message when I try to edit custom css

"Forbidden

You don't have permission to access /ccm/system/dialogs/page/design/css/submit on this server."

Any ideas what this means?

 
Linuxguy2 replied on at Permalink Reply
Is that not a Database error?

I have the exact same problem on Host Tornado
However it works on the site I have on Go Daddy .
Version: 5.7.5.2 Elemental Theme.

My problem is when I try to include an URL in the css.
Saves without error when I remove "url(images/single_leaf_15x15_01.png)"

li.leaf-bullet:before {
background:url(images/single_leaf_15x15_01.png) no-repeat;
position: absolute;
height: 15px;
width: 15px;
content: '';
left: -30px;
background-size: cover;
}
Linuxguy2 replied on at Permalink Reply
Haven't been able to verify this yet but if your hosting provider has mod_security (or some other security feature) turned on this may be preventing us from writing to the database.

On a Zen cart installation I had to get them to turn it off because I couldn't use a AND or OR or some of the other operators in my PO number entries..... As you probably know those are database operators that are commonly used for SQL Injection.

Thanks
Linuxguy2 replied on at Permalink Reply
I have a workaround for this issue.
Some security setting at my Hosting provider was preventing me from writing to the database.
Therefore I was getting the FORBIDDEN error message when trying to save a custom CSS file which is stored in the database.
I determined it was the "background: url(images/single_leaf_15x15_01.png) no-repeat;" statement causing the issue.

SO I removed that line from my CSS and the system happily saved the rest of the CSS code.
Next I edited the database with phpMyAdmin , found that entry in the Table structure for table `StyleCustomizerCustomCssRecords` and added the entry "background:url(images/single_leaf_15x15_01.png) no-repeat;" back in and saved it.

Badda Bing Badda Boom life is good!.

Be sure you are editing the correct entry. There may be several entries in the database. In my case I put some special comments in the CSS so I could recognize it.


The other approach would be to have your hosting provider remove the restriction from the system but with the workaround all SQL injection security measures are left intact.

Thanks for your time.