-
Notifications
You must be signed in to change notification settings - Fork 33
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
Conflict with WordPress 6.1 (wp_rand() bug on 32-bit platforms) #974
Comments
Hello In the logs : On the frontend an encoding error is shown when the script fails. |
@donnchawp please update your original post with the requested details so that your issue can be fully evaluated. All:
Thank you. |
|
My original post has been updated. Thanks for the quick response. |
Thank you for the additional details. SLB has been directly tested on multiple image-heavy WP 6.1 sites and I have not been able to reproduce this issue. "Maximum execution time exceeded" errors are cumulative, so disabling plugins until the error stops may not identify the actual plugin(s) causing the issue, but may just reduce the total processing time under the configured threshold (aka "the straw that broke the camel's back"). Following these instructions on identifying plugin/theme conflicts would be recommended to confirm whether SLB alone functions properly, or whether other plugins/themes may be causing a conflict. @donnchawp SLB does not make any direct use of the code referenced in the error message you provided. More detailed debug output with Also, as SLB appears to be working on single posts, but not on archive pages (home, category, etc.) on your site, please create a single test post with a single image link in a temporary category to see if the issue is encountered when loading the archive page for that category. (Tip: You can change the sample post's publication date to a date in the past so that it does not show up at the top of your home page, if you're testing on the production site.) Please let me know what you find. @benjamin-rota please create a test post with a single image link to see if the issue is encountered there as well. When testing, temporarily activating a default theme (e.g. Twenty Twenty-One) and disabling all other plugins will help to isolate SLB from any other conflicts. (Tip: You can change the sample post's publication date to a date in the past so that it does not show up at the top of your home page, if you're testing on the production site.) Please let me know what you find. Thanks. |
Hi If I create a simple post with a single image it works fine. But if I insert a galery then the issue appears. To reproduce : Not sure vocabulary is exactly the same as I use WP in french. Thanks |
@benjamin-rota glad to hear you were able to isolate the issue further.
You also previously noted that the same issue is occurring on 2 websites. Are both sites hosted on the same hosting provider? Can you please provide a link to the hosting provider these sites are on? |
Yes.
Twenty twenty two.
No. 2 or more images need to be in the gallery for the issue to occur.
Yes, attachment page or media link.
Classic editor.
Yes, www.ovh.com Hope you can reproduce the issue. |
same happend here. automatic update to wordpress 6.1.0 and every post with a gallery is not able to show any content. |
I've created a test branch to help isolate the issue. Please follow the instructions below to install the test plugin:
Once the test plugin is installed and activated, test the same page(s) on your site as before to confirm whether the issue remains or not and report your findings. Thank you. |
@benjamin-rota What version of PHP is the site running on? |
@domi-a please provide the following details:
|
7.3.32 |
I have installed the test plugin and tested again. Now galleries with 1 or 2 images are working, but the issue is still there with 3 or more images. |
@benjamin-rota what is the error message in the logs? The code referenced in your original log message is not active in the test version, so the error message should be different. |
|
@domi-a please provide a link to the "official docker image" you are referring to, and I may hopefully be able to reproduce the issue. |
https://hub.docker.com/_/wordpress docker style vs host installation doesn't make any difference as it is build from official wp sources - in kinds of a plugin. |
[09-Nov-2022 11:03:42 UTC] PHP Fatal error: Maximum execution time of 165 seconds exceeded in [path]/www/wp-includes/pluggable.php on line 2660 |
Hi I managed at last to update PHP to 7.4 with a "stable64" execution engine, on both websites where the issue occured. |
@benjamin-rota glad to hear you were able to find the solution to your issue! I'm not sure if something changed with WP 6.1 that requires a 64-bit environment, but that could be the case. @domi-a as the details you provided noted |
my hardware is armv8, but my host OS is armv7, as you can read in my reply. and we are talking about a plugin in one of my hosted applications - nothing to dictate my host OS. |
This issue has been confirmed as a bug in WordPress core, where the A hotfix may be released for SLB to avoid this bug until WordPress is updated, but upgrading to a 64-bit platform is recommended, as |
wp_rand()
(32-bit platforms)
wp_rand()
(32-bit platforms)
Description of Problem
I haven't had time to look into the source of your plugin but there's something in it that causes a problem when I load the front page (or archive links such as category pages) of my blogs after upgrading to WordPress 6.1. The page continues to load, and shows a blank page until it times out.
A not too useful error appears in the error log:
PHP Fatal error: Maximum execution time of 30 seconds exceeded in [path]/htdocs/wp-includes/pluggable.php on line 2662
When I deactivated Simple Lightbox the problem went away. I deactivated other plugins first but the error continued until I tried yours.
Details
The issue was only occurring on the homepage and archive pages. Single posts appeared fine. The plugin is now deactivated, so the URL above doesn't show the problem any more.
The text was updated successfully, but these errors were encountered: