| Issue 15: | Simplify the General Configuration page | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Describe the enhancement: The General Configuration page is a big, gnarly mess. It should be broken down into much more manageable segments and properly categorized. For example: gravatar settings should go under Users. Why do you think this enhancement should be implemented? It makes administration a lot simpler, easier, and cleaner. Confusing the site admin is a Bad Thing. What version of the product are you using? On what operating system? Whatever version the Administration demo is running. Please provide any additional information below. I told this before to one of the devs (he goes by the name Sir Gallantmon on MSN) and here is the convo: (11:48:06 AM) Techokami: so uh why are all the settings on one big long page (11:48:12 AM) Sir Gallantmon: for what? (11:48:14 AM) Techokami: General Configuration (11:48:17 AM) Sir Gallantmon: Ahh (11:48:25 AM) Techokami: you could break that down into smaller pieces (11:48:27 AM) Sir Gallantmon: General Configuration is probably the oldest page of the Admin panel (11:48:47 AM) Sir Gallantmon: most of the other pages have been rewritten to break them up a bit more (11:48:58 AM) Techokami: you should follow suit with this one (11:49:15 AM) Techokami: maybe move the gravatars settings to be unser Users, for example? (11:49:19 AM) Techokami: *under (11:49:41 AM) Sir Gallantmon: if you have suggestions, it would be great if you would fill out a report in http://bugs.enanocms.org/
Feb 7, 2010
#1
neal%ena...@gtempaccount.com
Labels:
Type-Enhancement Priority-Medium
Feb 7, 2010
Definitely valid. I'm open to ideas (and I have a few). a) An instant-response search field b) Some hierarchical system so that config entries don't have to all be splattered on one page c) Separate config pages. The problem with b and c is the plugin API. Right now there are a bunch of hooks where plugins can throw in their own HTML in GeneralConfig, and one hook where they can save. That would have to be completely broken for something like this to work, and that would not be appropriate for a beta-3 release. Ideas and patches are welcome, but that doesn't mean I'm completely opposed to working on this myself. Unfortunately I have things to worry about that are a lot more time critical than Enano at the moment, which is why I pushed 1.1.7 when I did.
Owner:
n...@enanocms.org
Cc: d...@enanocms.org Labels: Component-UI
Feb 7, 2010
Whoops, forgot to set as accepted.
Status:
Accepted
Jun 27, 2011
(No comment was entered for this change.)
Owner:
n...@enanocms.org
Cc: d...@enanocms.org
Aug 16, 2015
greetings admin, I love to see what you created here, for that I say thank you. http://www.kencanapasutri.com |