Revolution: [enhancement] System settings: change default value

Created on 14 Jan 2019  Â·  5Comments  Â·  Source: modxcms/revolution

Feature request

Summary

In the System Settings, some default settings are chosen, in my opinion, incorrectly.

Friendly URL:
_FURL Alias Character Restriction Method (friendly_alias_restrict_chars) - pattern_
Correctly put "alphanumeric", because It happens that in the current variant can stay incorrect characters in url, but with "alphanumeric" there is no such problem and this option will is suitable for most users.

Gateway:
_Strict Request Method (request_method_strict) - no_
It is better to put "Yes", because in the current version, if FURL is enabled, then the url opens with both index.php and sef-url, which is bad for search engines.

Back-end Manager:
_Manager Favicon URL (manager_favicon_url) - empty_
Why not put the favicon MODX by default? Firstly, without a favicon, the admin panel looks unfinished and it is more convenient to navigate through the browser tabs with a favicon. Secondly, if the user changes this setting, he would in any case change it, i.e. time is not added for him.

_Resource Tree Node Fallback Field - pagetitle_
The settings of the "Resource Tree Node Field" and "Resource Tree Node Fallback Field" have the same value - "pagetitle", but it is more logical for the "Resource Tree Node Fallback Field" to put another field, for example, "alias".

_Manager Date Format (manager_date_format), Manager Time Format (manager_time_format) and Week start (manager_week_start)_
These settings are more correct for USA, but for most countries the time and date format is different.

Site:
_Automatic Template Assignment (automatic_template_assignment) - parent_
Correct to put "sibling", because more often, resources with the same template are siblings pages, for example, news or articles.

_Published default (publish_default) - no_
In my opinion, resources are published more often than not published. Better to set "yes".

_Hide From Menus Default (hidemenu_default) - no_
Same comment as "Published default".

Perhaps some settings should be left as is, or change some other, in any case, we need a discussion.

area-core proposal

Most helpful comment

We shouldn't be changing documentation based on issues. Only based on actual changes made in PRs once they are accepted/merged.

All 5 comments

I'd personally be OK with the new default permission suggestions. I know I've been caught on more than one occasion wondering where the heck the content went (to go back and remember to, you know, actually publish it…).

Please add label "needs-docs" - I'll update doc settings, default values

We shouldn't be changing documentation based on issues. Only based on actual changes made in PRs once they are accepted/merged.

Sure @opengeek I will be happy with this label after accepting the changes :)

I'm saying the label should go on the PR where the changes are actually made.

Was this page helpful?
0 / 5 - 0 ratings