Timeline for Permalinks settings page blank
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 27, 2020 at 10:12 | vote | accept | RexTheRunt | ||
| Apr 12, 2019 at 14:18 | history | edited | RexTheRunt | CC BY-SA 4.0 |
Added actions taken since posting.
|
| Apr 11, 2019 at 13:24 | answer | added | Дтдця | timeline score: 0 | |
| Apr 11, 2019 at 13:15 | answer | added | DHL17 | timeline score: 1 | |
| Apr 11, 2019 at 13:11 | comment | added | DHL17 |
@RexTheRunt deactivate all plugins and then try or Increase PHP Memory Limit in WordPress for ex. place this code in wp-config.php before ‘That’s all, stop editing! Happy blogging.’ define( 'WP_MEMORY_LIMIT', '256M' );
|
|
| Apr 2, 2019 at 8:08 | comment | added | RexTheRunt | I can't find any errors in my host's error logs, so I'm stuck. I tried changing PHP versions on the server, but that didn't help. I've downloaded a backup of the site and I'm going to try and rebuild it locally. | |
| Apr 1, 2019 at 17:46 | comment | added | RexTheRunt | I enabled debugging and got Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 72 bytes) public_html/wp-includes/kses.php on line 1758 | |
| Apr 1, 2019 at 16:25 | comment | added | RexTheRunt | It's just that page on the back end, all others are loading. Front end has no pages loading. | |
| Apr 1, 2019 at 16:20 | comment | added | Loren Rosen | Possibly dumb question: Is it just the permalinks page that's blank/giving the 500 error, or is every other page having that problem too? | |
| Apr 1, 2019 at 15:55 | review | Close votes | |||
| Apr 16, 2019 at 3:05 | |||||
| Apr 1, 2019 at 15:31 | answer | added | phatskat | timeline score: 0 | |
| Apr 1, 2019 at 15:31 | comment | added | Tom J Nowell♦ |
A 500 error is just Apache/Nginx's was of saying something bad happened in PHP, don't know what it is, look at the PHP error logs for the actual error
|
|
| Apr 1, 2019 at 15:30 | comment | added | phatskat |
In your wp-config.php add the line define( 'WP_DEBUG', true);, or make sure it's set to true if it's already defined and set to false. Then, you can define( 'WP_DEBUG_DISPLAY', true ); to show errors and define( 'WP_DEBUG_LOG', true ); will create a file called wp-content/debug.log that will log errors. I would start debugging like that to find out what's going on.
|
|
| Apr 1, 2019 at 15:24 | history | asked | RexTheRunt | CC BY-SA 4.0 |