The "unexpected token" usually means something in a MODX processor is throwing a fatal PHP error, which makes the processor return the error message instead of what it's supposed to.
You can sometimes look at the Network tabs in FF or Chrome Dev. tools (ctrl-shift-i) and drill down to the response to to see the actual error.
Since it's a 403, it may be caused by the host's mod_security settings. Who is your host?
-
☆ A M B ☆
- 24,524 Posts
Is this when saving the .css file, or when opening it?
-
☆ A M B ☆
- 24,524 Posts
You need an FTP client that automatically loads a file into your editor of choice, and uploads it back on save. I use Cyberduck.
Of course, that doesn't explain where the problem is coming from. It sounds like it's ether a mod_security issue, or a bad file in the MODX installation.
They can disable or modify the configuration of mod_security for your domain if they want to.
Seems like this workaround will have to do. My hosting service claims they can't modify the configuration, sadly.
Thank you!
I does sound like mod_security to me. Maybe someone typed "style" when they meant to type "script" while setting up the rules or set up a rule for <s*.
For future reference:
http://bobsguides.com/modx-friendly-hosts.html