[SOLVED] No way to undo when "Apply" while editing CSS 1.11

[fearmydesign]

On versions prior to 1.11 I was able to work on html + CSS on stylesheets or templates while having the option to quickly *undo* (ctrl+Z) if I didn't like the results when hitting *Apply*... now on version 1.11 once you hit "Apply" there is no way to undo; another words it's like hitting "Submit"... does anyone else think that was useful, or is it just me? not sure what the technical term for this would be, but I guess it's just part of 1.11

Thanks!

[HoofArted]

It's probably not the exact solution you want, but this may come handy: http://dev.cmsmadesimple.org/projects/externalizer/

[fearmydesign]

It's probably not the exact solution you want, but this may come handy: http://dev.cmsmadesimple.org/projects/externalizer/

Thank you for sharing this. However this was an automatic feature already embedded in 1.10.3 and below that I loved using.... I could just make changes to my CSS, click *Apply* and if the changes weren't to my liking, I could easily just undo... Now on 1.11 clicking *Apply* is like hitting *Submit*

[HoofArted]

I know what you mean... I also use apply/ctrl-z a lot and you just persuaded me not to upgrade.

[calguy1000]

Although there is absolutely insufficient information and this post is in the completely wrong thread I tested it anyways because I was concerned that there may be some kind of javascript error.

Conclusion: There isn't. I just tested this in chrome with both admin themes in CMSMS 1.11 (I have no funky plugins installed in chrome, and only my modules installed).

Editing a stylesheet... pressing 'apply' did not cause a page reload. Therefore I could reload a page in another tab, view the CSS, and see my changes. Press Ctrl+Z, hit apply, then reload the css in another tab and see those changes disappear.

I suspect that some other module you have installed is causing problems. It would be useful to check your javascript error log, and http error log before posting.

[fearmydesign]

Although there is absolutely insufficient information and this post is in the completely wrong thread I tested it anyways because I was concerned that there may be some kind of javascript error.

Conclusion: There isn't. I just tested this in chrome with both admin themes in CMSMS 1.11 (I have no funky plugins installed in chrome, and only my modules installed).

Editing a stylesheet... pressing 'apply' did not cause a page reload. Therefore I could reload a page in another tab, view the CSS, and see my changes. Press Ctrl+Z, hit apply, then reload the css in another tab and see those changes disappear.

I suspect that some other module you have installed is causing problems. It would be useful to check your javascript error log, and http error log before posting.

Thanks Calguy, that's the thing, I don't have any modules installed but a few of yours, and I tried this on a fresh install and an upgrade. I will check the javascript/http error logs though and see if I can interpret... by the way, I didn't realize this thread was in the 'completely wrong place', I guess it was just a reflection to CSS cause I was referring to the stylesheets, my fault, I don't know how to move the thread.

Regards

[fearmydesign]

On Google Chrome I am showing the following errors - Does this mean that my server is preventing me from doing some things, such as the "Apply" without a page-reload ?

Failed to load resource: the server responded with a status of 406 (Not Acceptable) http://whirlzyogurtbar.com/admin/themes ... kie.min.js
Uncaught TypeError: Object function (a,b){return new e.fn.init(a,b,h)} has no method 'cookie' standard.js:82

[calguy1000]

Any JS Errors could result in the site not working very well.

First... try the NCleanGrey theme. I'm willing to bet that that will work.

Now, seeing that the cookies stuff is getting a 406 error I'm willing to bet that the OneEleven theme isn't going to work well for you. Cookies are used to remember where popups are placed, and other things.

my googling tells me that 406 errors are most often caused by mod_security (which we hate, and don't support).

So if the other theme works, then contact your host and get mod_security disabled.

[fearmydesign]

Any JS Errors could result in the site not working very well.

First... try the NCleanGrey theme. I'm willing to bet that that will work.

Now, seeing that the cookies stuff is getting a 406 error I'm willing to bet that the OneEleven theme isn't going to work well for you. Cookies are used to remember where popups are placed, and other things.

my googling tells me that 406 errors are most often caused by mod_security (which we hate, and don't support).

So if the other theme works, then contact your host and get mod_security disabled.

Thank you. As you said the *NCleanGrey* theme works perfect! Too bad I can't use OneEleven. I also contacted my hosting (InMotion) and they said that mod_security helps block IP addresses that abuse the server, so I don't know where the link is, but they said I have to submit a request for it to be disabled.

[calguy1000]

mod_security is a 'firewall' for incoming requests to a web server. Since firewall rules can be arbitrary, there's no way we support it. We never have.

[Dr.CSS]

I've had this problem but only because when I went back to that browser tab to use Ctrl/Z I hadn't clicked inside the stylesheet/template area(box) to give it focus...