Conversation
supportSwitching PHP version from 7.4 to 8.0 causes the full site to go down. Is there any chance the plugin can be updated to support 8.0? [27-Aug-2022 05:57:45 UTC] PHP Fatal error: Cannot use “parent” when current class scope has no parent in /dir_path/example.com/public_html/wp-content/plugins/wp-lynx/wp_lynx.php on line 131 Although the plugin is not supported anymore we find it very useful and function. Have not found any similar plugin in wordpress.org If anyone knows of similar plugin, please post here?
In theory, the block editor sort of already has WP Lynx like features for sites that support oEmbed. For those that aren’t using the block editor, I guess WP Lynx may still have value. I had originally intended on doing a major update to support the block editor, but I’ve found adding blocks to be a pain (especially the seemingly excessive amount of tools necessary to develop blocks) so I put dealing with this on hold. In the meantime, other things have moved on, so to speak, and look to be causing breakage (the old version of adminKit that WP Lynx uses has PHP8 problems as well). I’ll take a look at what moving to the latest adminKit will take (to fix the PHP8 errors).
John, thank you very much for your response. I use WP lynx at a couple of for non-profit sites and cannot provide much of financial support for your efforts. However, please publish a donation link so I can make a small contribution. BR/INge
I made a cut at updating to the latest adminKit and preliminary PHP8 support (tested against PHP8.1). You can try this out by grabbing a copy of the GitHub master branch: https://github.com/mtekk/WP-Lynx
John, I have tested on WP 6.02 and PHP 8.1. After disabling all plugins, debugging why a not active plugin caused problems, and activating the Classic Editor WP Lynx works! One warning message remains. Warning: Trying to access array offset on value of type bool in /wp-content/plugins/WP-Lynx-master/wp_lynx.php on line 545 Thanks so far!
Experienced this message while accessing the admin interface. Found 1 unknown legacy settings: Himage_template
Thanks for the feedback. I’ve fixed the cause of the PHP warning. As for the setting in the admin interface, that message can be ignored. That said, the 1.3.0 release should actually clean up that unused setting that was lingering around for some reason.
John, the 1.30 release is now updated on the sites I maintain. This has made our day and future proofing our sites a few years forward. Once, where is the link we can donate a small sum for your efforts? BR/Inge
In theory, the block editor sort of already has WP Lynx like features for sites that support oEmbed. For those that aren’t using the block editor, I guess WP Lynx may still have value. I had originally intended on doing a major update to support the block editor, but I’ve found adding blocks to be a pain (especially the seemingly excessive amount of tools necessary to develop blocks) so I put dealing with this on hold. In the meantime, other things have moved on, so to speak, and look to be causing breakage (the old version of adminKit that WP Lynx uses has PHP8 problems as well). I’ll take a look at what moving to the latest adminKit will take (to fix the PHP8 errors).
John, thank you very much for your response. I use WP lynx at a couple of for non-profit sites and cannot provide much of financial support for your efforts. However, please publish a donation link so I can make a small contribution. BR/INge
I made a cut at updating to the latest adminKit and preliminary PHP8 support (tested against PHP8.1). You can try this out by grabbing a copy of the GitHub master branch: https://github.com/mtekk/WP-Lynx
John, I have tested on WP 6.02 and PHP 8.1. After disabling all plugins, debugging why a not active plugin caused problems, and activating the Classic Editor WP Lynx works! One warning message remains. Warning: Trying to access array offset on value of type bool in /wp-content/plugins/WP-Lynx-master/wp_lynx.php on line 545 Thanks so far!
Experienced this message while accessing the admin interface. Found 1 unknown legacy settings: Himage_template
Thanks for the feedback. I’ve fixed the cause of the PHP warning. As for the setting in the admin interface, that message can be ignored. That said, the 1.3.0 release should actually clean up that unused setting that was lingering around for some reason.
John, the 1.30 release is now updated on the sites I maintain. This has made our day and future proofing our sites a few years forward. Once, where is the link we can donate a small sum for your efforts? BR/Inge