-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permalink Structure Docs (wysiwyg) #58
Comments
Can I be assigned to this, please? |
I would also like to add that these docs should probably mention something about setting up 301 redirects since that can have a negative impact on a multitude of things. |
Bear with me because this is my first edit. 😅 ... A lot of the content on this document should simply be moved to the development documentation — namely all of the content that contains code and/or anything instructing users to edit their .htaccess file. The main part that needs to be added to this document goes something like this...
|
Maybe this is a better search term? https://wordpress.org/plugins/search/seo+301+redirect/ |
Heads up @docs-reviewers - the "[Status] Review" label was applied to this issue. |
Issue Description
The documentation containing instructions to edit permalinks is too technical and many hosting platforms now limit SSH access. The new documentation should show users how to use the Settings > Permalink feature of WordPress@latest.
Note: SFTP is a viable option, but not for wysiwyg (non-API) users.
Linked to #30
URL of the Page with the Issue
https://wordpress.org/support/article/using-permalinks/
Section of Page with the issue
https://wordpress.org/support/article/using-permalinks/#using-pretty-permalinks
https://wordpress.org/support/article/using-permalinks/#fixing-permalink-problems
https://wordpress.org/support/article/using-permalinks/#tips-and-tricks
Why is this a problem?
Because this is too technical for front-end wysiwyg users.
Suggested Fix
Correct instructions: https://wordpress.org/support/article/using-permalinks/#automatically-updating-htaccess
The text was updated successfully, but these errors were encountered: