SUGGESTION (UPDATED): Show hidden settings

There are several very useful settings  (example: 'catalogsettings.defaultviewmode','catalogsettings.defaultcategorypagesizeoptions', etc. etc.) which are not published within the configuration>settings sections and one has to guess and find whether they exist within the All Settings section. It would be great to have a couple of new columns in the settings tables: Published (false/true) and Description (as per v1.9) which could have a short explanation of the use of the setting. Both columns should be published in the All Settings grid and should have a filter. By filtering the Published=false anyone could easily  find all the hidden beauties of Nop :=).

Rather than Published field, how about fields: Group (or Section or Page?)  and InputType.  This way, the system can automatically display the field/description/input-box in the appropriate settings page, without the team having to update the Model, View, & Controller  (which is probably why many of these hidden settings don't make it on the page :)

(Yes, some might have dependencies, but I suppose that too could be automated with another field and a little more work)

Thanks for suggestions.

For description field please the work item is here.

Automatically generated UI for settings. I don't think that it's possible. Yes, for most settings it's OK. But what about some complex settings such as:
1. General and miscellaneous settings > "Mobile devices supported". This setting should restart the application once changed
2. General and miscellaneous settings > "Encryption private key". IT has some complex handler
3. General and miscellaneous settings > "Use SSL". It writes to web.config file
4. General and miscellaneous settings > "Store closed". This one shows one more "nested" setting ("Allow an admin to view the closed store") once checked.
4. Order settings > "Gift card statuses". Selected from dropdownlist.

Furthermore, we should also add some kind "display order" to settings in this case. It's too complex for this task.

a.m. wrote:
Thanks. I see its coming in 2.7 :). Dont forget the Published column (if there is not something better) sinces thats the way users can find those hidden settings.

Well, if "Yes, for most settings it's OK.", and only complex for a few, then consider...
Add field for "Auto generate" (boolean) (and also add Display order).  Then each setting page can just display these at the bottom of the hard coded stuff.

It would seem that the upfront effort for this dev task pays dividends in that in most cases, as per above, no extra work will be required to update M/V/C every time a simple setting is added.

eadameg wrote:

UPDATE:
This is kind of a hack:
Instead of adding the Unpublished property simply at the end of the description  add some tags (I assume it will have a filter, mthat can also be used to find them) such as Unpublished, Performance (for settings that affect performance, such as displaying number of products besides each category/manufacturer) and display them in the heading text "To find text or a specific setting (by name), you can apply a filter via the funnel icon in the "Value" or "Setting name" column headers. There are some tags..."

v3.3 comes with several "hidden settings". I think now there are dozens of them and is more relevant to think of a solution for making them known. The work item created by Andrei was due in v2.7 but was later deleted

eadameg wrote:
Hi Eduardo,

You're right. Store owners should be aware of all important settings. Do you have any suggestion on certain settings which should be "visible"?

a.m. wrote:
Hi Andrei:
I dont quite understand what you mean. If you mean which settings should be visible, I would say that all should be visible. If you mean how to make them visible, I would go for my original proposal here of adding a settings description with an indication or tag words for those which are invisible. Another would be to have in settings a miscellaneous section as in v1.x.

Maybe with the new admin and documentation something can be done to publish in another way all hidden settings or at least list them with a small description in the documentation so they are searchable.

¿Does anybody has any suggestions in this matter?