Many reported losing their ability to log in after introducing changes to their (url) settings. Not only that, but they also reported that they were connected to wordpress.com (C) and lost access to wordpress.org (O).
I suggest that the interface be made (more) user-friendly by noting the following:
1- According to your literature, (C) is different from (O). This requires that your software (O) should not be intertwined with the software (C). Such a relationship need be eliminated, and regardless of the nature of the (O) user’s mistake, no mistake should connect him/her to (C) and disrupt his/her access to (O).
2- Means need be devised in order NEVER to deny the (O) user access to his platform, regardless of the nature of the committed mistake. He/she should ALWAYS enjoy the right to log in being already a registered (O) user.
3-There is an urgent need for a RESET button on which the (O) user can always click in order to reset/restore the settings to their default in case of introducing changes to them, regardless of the nature of those changes.
4- There is need to alert the (O) user, after introducing changes to settings, whether he/she would go ahead with those introduced changes, together with a warning about the possible “serious” consequences, in case such consequences would exist, after those changes take effect.
Technically, your suggestions are not practical as the user will always have the ability to point his domain name elsewhere or mess something up such that the code cannot be interpreted properly.
However, regarding alerting the user or removing the setting entirely, there’s been some discussion on it.
If a reset button is added and a user loses access to the site, surely they’ll lose access to the reset button?
If someone goes into admin & changed the URL to an invalid value without understanding the consequences, and as a result losing access There is already a way of regaining access: they just need to add:
to their wp-config.php to change these setting back to the valid values.
- The topic ‘Suggestions to wordpress.org team’ is closed to new replies.