Currently we have 2 Tabs in the ACP dealing with extensions/mods.
The first one is the new Customise Tab, used to allow enabling/disabling of extensions, installing of styles and languages.
The second one is ACP_CAT_DOT_MODS used by mods in 3.0 and the first extensions in 3.1 to add their configuration modules.
My idea was to merge them into one
The three modules of the Customise Tab would be at the top of the list, the configuration modules of the mods/extensions below them.
Everything is in one place.
As for the tab, I would keep the language key 'ACP_CAT_DOT_MODS' to allow compatibility for install scripts of mods and migrations of already existing extensions. The translation should be changed to Customise, so it matches the fact that styles and translations are there aswell.
Opinions
[RFC] Merge "Customise" and ".MODs" Tab in ACP
- nickvergessen
- Former Team Member
- Posts: 733
- Joined: Sun Oct 07, 2007 11:54 am
- Location: Stuttgart, Germany
- Contact:
[RFC] Merge "Customise" and ".MODs" Tab in ACP
Member of the Development-Team — No Support via PM
Re: [RFC] Merge "Customise" and ".MODs" Tab in ACP
So the Styles would need to be changed back to like it is in 3.0, where Installed and Uninstalled are all on the same page again.
Has an irascible disposition.
- wintstar
- Registered User
- Posts: 108
- Joined: Sun Dec 02, 2012 1:38 pm
- Location: Gießen /Hessen Germany
- Contact:
Re: [RFC] Merge "Customise" and ".MODs" Tab in ACP
Yes that was my idea to 03 Mar 2014, 08:21
https://area51.phpbb.com/phpBB/viewtopi ... 10#p261289
Thus, it is clearly arranged. Customise should be renamed back to Styles.
https://area51.phpbb.com/phpBB/viewtopi ... 10#p261289
Thus, it is clearly arranged. Customise should be renamed back to Styles.
Greeting Stephan
Re: [RFC] Merge "Customise" and ".MODs" Tab in ACP
If someone installs lot of MODs (Extensions) with submodules it is very annoying to choose some submodule at the bottom of left panel and scroll up to the top to change setting and then again down to choose another submodule of the same or different MOD (extension) and scroll back up again. That's why on my forum I split MODs tab into two tabs. So I would prefer not to merge it. Maybe if we (admins) could change order of modules in the left panel, so admins would be able to move the most used modules to the top.nickvergessen wrote:The three modules of the Customise Tab would be at the top of the list, the configuration modules of the mods/extensions below them.
Everything is in one place.
EDIT: my post is not 100% correct. Read correction by DavidIQ here.
Last edited by leschek on Wed Mar 05, 2014 9:26 pm, edited 1 time in total.
Re: [RFC] Merge "Customise" and ".MODs" Tab in ACP
Please don't merge, customize is for customize the board, .mods for modifications although I prefer to place a entry for a mod in a logical place. So a mod for logging should be in maintenance tab under logs. Most customers ask to place the modlink under quick access because it's the first page in ACP.
Question, is there really a .mods tab necessary?
Question, is there really a .mods tab necessary?
Re: [RFC] Merge "Customise" and ".MODs" Tab in ACP
I sort of agree with above post that Customise tab isn't really the place for extension/mod control panels.
You could, for example, have a SPAM Protection extension, that has its settings module here, but what does that have to do with customizing your board, as the tab name implies?
I just think, as before, the .MODs tab needs a much better name is all. i.e.:
Plug Ins
Extensions
Extension Modules
Extension Module Settings
Extension Control Panels
Extra Settings
3rd Party Extensions
Other
any better ideas??
You could, for example, have a SPAM Protection extension, that has its settings module here, but what does that have to do with customizing your board, as the tab name implies?
I just think, as before, the .MODs tab needs a much better name is all. i.e.:
Plug Ins
Extensions
Extension Modules
Extension Module Settings
Extension Control Panels
Extra Settings
3rd Party Extensions
Other
any better ideas??
Absolutely! Many mods/extensions have extensive Modules that may not fit in anywhere else among the existing ACP modules. Without it, a lot of authors would just fill up the General section on the left menu, and that list would get real long, real fast. Plus it's kinda nice for an admin to know (usually) where all the new settings from their newly installed mods can be found, under one roof - the .MODs tab.John P wrote:Question, is there really a .mods tab necessary?
No. The Customise tab is for styles, language packs and Extensions.wintstar wrote:Customise should be renamed back to Styles.
Has an irascible disposition.
Re: [RFC] Merge "Customise" and ".MODs" Tab in ACP
Agreed!VSE+ wrote:I sort of agree with above post that Customise tab isn't really the place for extension/mod control panels.
That's just being plain lazy (filling the GENERAL section). Haven't MOD Authors learned that you can create your own tabs in the ACP? That's what I'm doing for my Knowledge Base MOD and Extension.VSE+ wrote:Absolutely! Many mods/extensions have extensive Modules that may not fit in anywhere else among the existing ACP modules. Without it, a lot of authors would just fill up the General section on the left menu, and that list would get real long, real fast.John P wrote:Question, is there really a .mods tab necessary?
- wintstar
- Registered User
- Posts: 108
- Joined: Sun Dec 02, 2012 1:38 pm
- Location: Gießen /Hessen Germany
- Contact:
Re: [RFC] Merge "Customise" and ".MODs" Tab in ACP
That would be my idea. With one click without the hassle to scoll. Already have the idea Sortable extension events inserted:John P wrote:Please don't merge, customize is for customize the board, .mods for modifications although I prefer to place a entry for a mod in a logical place. So a mod for logging should be in maintenance tab under logs. Most customers ask to place the modlink under quick access because it's the first page in ACP.
Question, is there really a .mods tab necessary?
Greeting Stephan
Re: [RFC] Merge "Customise" and ".MODs" Tab in ACP
+1t_backoff wrote:Agreed!VSE+ wrote:I sort of agree with above post that Customise tab isn't really the place for extension/mod control panels.
Miscellaneous (or simply Misc.)? Extensions indicates that all settings modules for extensions are located under here, which is not always the case. Thus, a more generic name that encompasses all modules that do not fall under any other tab makes more sense to me.VSE+ wrote:I just think, as before, the .MODs tab needs a much better name is all. i.e.:
Plug Ins
Extensions
Extension Modules
Extension Module Settings
Extension Control Panels
Extra Settings
3rd Party Extensions
Other
any better ideas??
That doesn't seem any better. Unless your extension contains multiple submodules and categories, there is no need for a tab. On my laptop, I can fit possibly another 6 or 7 tabs (depending on their size)... 4 if they're all the size of Knowledge Base. That's going fill up rather quickly, so I wouldn't recommend doing this.t_backoff wrote:That's just being plain lazy (filling the GENERAL section). Haven't MOD Authors learned that you can create your own tabs in the ACP? That's what I'm doing for my Knowledge Base MOD and Extension.
- DavidIQ
- Customisations Team Leader
- Posts: 1904
- Joined: Thu Mar 02, 2006 4:29 pm
- Location: Earth
- Contact:
Re: [RFC] Merge "Customise" and ".MODs" Tab in ACP
That is incorrect. If you click on a sub-module at the bottom of any tab in the ACP or anywhere else you'll end up at the top of the page since the entire page reloads. There is no scrolling up after clicking on a sub-module.leschek wrote:If someone installs lot of MODs (Extensions) with submodules it is very annoying to choose some submodule at the bottom of left panel and scroll up to the top to change setting and then again down to choose another submodule of the same or different MOD (extension) and scroll back up again. That's why on my forum I split MODs tab into two tabs. So I would prefer not to merge it. Maybe if we (admins) could change order of modules in the left panel, so admins would be able to move the most used modules to the top.