-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Editor Crashes with Custom permalinks #11463
Comments
I have the same Issue on Gutenberg version 4.2.0 Desktop: This Problem does not occur on our staging server, where WP is hosted on a subdomain. Might be related to: #8802 or #8456 (comment) I double checked, but I couldn't find any failed XHR requests. I expected to find them if either the server configuration would break a request by not passing through the parameters or the firewall would prevent calls. But user, taxonomy and so on showed the correct data as response while debugging. |
Found the Problem: I had the base URL set to https since the page is being served from https. Now i've changed the protocol to http and the editor finally allows me to create new posts and does no longer crash, even if the permalinks are configured with /%category%/%postname%/ |
Turns out I was a bit quick to think this problem would be resolved. I did set my home path to http, but now the preview und save function won't work, since those request would be sent from an https admin panel to http endpoints and those mixed content requests aren't allowed. Tried to use |
As long as the custom permalinks are disabled the JSON request is fetched from |
I noticed the same problem testing Gutenberg 4.4.0 on Wordpress 4.9.8. I discovered that my issue was my server lighttpd was not populating the $_SERVER['QUERY_STRING'] or the
This is the output from my debug.log file for the link you posted.
Now things are working well. I know there's more to parsing the query string beyond this (see php.net - parse_url Notes), but it only needs to work for Wordpress permalinks for now. |
same bug here. Wordpress 5.0.2 I use "Month and name" as permalink structure. Changing this to plain, resolves the issue. However I cannot just change this, as there are a lot of permalinks out there which would become deadlinks. I assume, there are a lot more people affected by this, but ended up stuck here: #12655 |
Same problem, same Javascript error. Wordpress 5.0.2 served by nginx Curious: I have disabled the Gutenberg plugin. Changing the permalink structure is not really an option. Update: |
I don't know that it's the permalink setting alone which is causing this issue, as I'm unable to reproduce the error myself when testing a custom structure ( Based on previous comments, server configuration may be a factor. The |
This. On In nginx, I'm only using Solution for nginx is to append arguments to the try_files index:
|
This is also documented in the Nginx configuration documentation for WordPress:
|
Unless demonstrated otherwise, I'm going to close this as attributable to server misconfiguration in losing query arguments as part of a rewrite rule. Refer to the following documentation for more information: Apache: https://codex.wordpress.org/htaccess If continuing to be an issue, it would be most helpful to share server configuration relevant to pretty permalinks rewrite rules, or to contact your host if managed on your behalf. |
You guys are amazing. The permalinks custom plugin nailed all issues I was having. Thank you for contributing |
The editor crashes when a new post is made/edited. It seems to be linked to permalinks. (see below)
To Reproduce
Steps to reproduce the behavior:
TypeError: Cannot read property 'show_ui' of undefined
at index.js?ver=1541283461:50
at i (lodash.min.59550321.js:6)
at An.filter (lodash.min.59550321.js:99)
at index.js?ver=1541283461:50
at yh (react-dom.min.82e21c65.js:95)
at lg (react-dom.min.82e21c65.js:120)
at mg (react-dom.min.82e21c65.js:120)
at gc (react-dom.min.82e21c65.js:127)
at vb (react-dom.min.82e21c65.js:126)
at ub (react-dom.min.82e21c65.js:126)
Desktop (please complete the following information):
Smartphone (please complete the following information):
Plugins/Other
Disabling all plugins but Gutenberg produces same behavior.
Fix?
Changing permalinks to plain stops the crashing.
This doesn't happen with pages.
The text was updated successfully, but these errors were encountered: