-
Posts
-
PLEASE, PLEASE, PLEASE move the “Reset All Options” button. Sorry, very frustrated that this remains. I just wasted two hours, again, cleaning up after a restoring-from-backup following accidentally hitting this button.
Placing what is essentially the “DELETE ALL SETTINGS” button front-and-center is just bad UI. I’ve accidentally hit it countless times while moving quickly through the Theme Options panel. Scanning for a specific Blog setting, noticed I forgot to recently disconnect MailChimp, instinctually hit the “Reset All Options” button and BOMB, all setting accumulated after a year of development are gone! Pray you have a recent backup which, I bet many users don’t or are newbies. Any RESET ALL button should be buried! Again, love the theme and support, but this is so frustrating and unnecessary.
Why would such a destructive button be front-and-center on every page?!
Yes, you can restore it from backup. What an absolute pain. Took two hours to fix things that didn’t restore correctly.
Yes, you can hide it in the code, but really? Users must mess with code to remove such a DESTRUCTIVE button.
Yes, the browser SHOULD show a verification button….but it did not. No warning.
No undo option either.Please, please, please move the Reset All Options. I’m not the only one encountering this. Again, the best theme out there, hands down. But for this serious design flow.
Hey Nicole,
We are sorry for the inconvenience.
There are many ways to hide it.
Please have a look at the following thread:
If you need further assistance please let us know.
Best regards,
VictoriaI can only agree with stanbrid: This button is like a kill switch for all the configuration work done by an enfold-user. It must not – I repeat: it must not! – be placed on every config-screen. The damage done by accidentally pressing it is so profund, I don’t have the words to describe it.
This really is insane. One must assume this buttons impact is limited to the context of the current panel it is displayed on. But it’s impact is global. It should absolutely be placed on a very special admin panel, with a lot of warnings that very clearly indicate that everything you’ve ever done to customise the theme will be lost in an instant when pressing this button.
So please:
Relocate this button to a remote admin panel!
Remove it from the all of the other panels!Hi marcuslepie,
I’ve brought it up for discussion with our developers and Kriesi, we’ll hopefully find a better way of adding this option to another place in the theme options, with more warnings and clearer information.
Best regards,
RikardThe KILL button is still located in the UI’s primary “execute” location….on every single page. That’s unfortunate.
Suggesting users to actually go in and change code to hide the button is unreasonable. In addition, plugin or browser pop-up blockers prevent the warning from coming up. So, not a viable solution either. Have never seen this warning once.
Come on Enfold. Your theme is a rockstar! This is a no brainer.
Yes, the browser SHOULD show a verification button….but it did not. No warning.
No undo option either.I haven’t done this in a long time. But I seem to remember there was another pop-up as a warning.
Unfortunately, most users no longer read such pop windows, and to close the part quickly, press ok.
This is my standard entry in child-theme functions.php
function admin_head_mod() { echo '<style type="text/css"> #avia_quick_css .avia_description {float: none;margin-bottom: 20px !important;padding-left: 0 !important;width: 98%} #avia_quick_css .avia_control {float: left;max-width: 98% !important;width: 98% !important} .avia_footer_links li {float: left;padding-right: 20px} .avia_footer .avia_footer_save {float: left} .avia_reset {display: none !important } #avia_options_page { max-width: 3000px!important} </style>'; } add_action('admin_head', 'admin_head_mod');it removes the button and it changes the position of the save all button to left position – due small screens
additionally the whole options field is widened and the Quick CSS field is set to large.
- You must be logged in to reply to this topic.