Hi Trevor, I am definitely not having any 500 errors editing my home page on my test site with the latest version of Link Library. Have you tried enabling WP_DEBUG and WP_DEBUG_LOG in your wp-config.php file and looking at the debug.log file in your wp-content directory? If you’re getting a 500 error, I would expect some messages to come out that way, then you can see what these messages point to. If it is related to Link Library, please post the errors here. If not, then you’ll have a better idea of who to contact.
Let me know if this helps and please consider donating to support this plugin’s development.
Thread Starter
ukcw
(@ukcw)
Hi
Many thanks for your reply. I don’t have a test environment for my site, and reading up there are big warnings about not enabling WP_DEBUG and WP_DEBUG_LOG in your wp-config.php file if it is on a live site. I looked into setting up a test site, but it looks a bit complicated. I guess without more info, there is no way we can identify what the issue is. When I feel brave, I might try to enable the files for one go at seeing if I can get any extra information, but in the meantime the work around is to deactivate the Link Library plugin whenever I need to edit an affected page or post. I’m hoping that a future upgrade of either the theme or the plugin will just magically fix the problem 🙂
Kind regards
Trevor.
I understand your concerns. That being said, I have often used the following combination of debug variables on my employer’s web site to troubleshoot issues:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'WP_DEBUG_LOG', true );
With this combination, nothing changes in the way your web site is rendered. Only a log file gets created on disk when the site is visited.
And indeed, without this type of debug information, I can’t really do much more.
