• Resolved moviesteve

    (@moviesteve)


    Hi there, The latest update is causing my site to jam up. I just get a timeout. “A timeout occurred. Error code 524. Visit cloudflare.com for more information.”

    Completely no way to get into WordPress any more so went into the back end and disabled it. All was fine again. Have now gone back to 4.3 and that seems to be working OK again.

    The page I need help with: [log in to see the link]

Viewing 10 replies - 16 through 25 (of 25 total)
  • Plugin Author JCV

    (@psykonevro)

    Thanks. I’m totally in the dark, since the logging works in the WP administration, but apparently it doesn’t in the front (it should definitely reports what’s happening).

    Could you try deactivating the cache? I see you’re using a caching system.

    • This reply was modified 1 month ago by JCV.
    Thread Starter moviesteve

    (@moviesteve)

    Hi, If you mean a caching plugin, I”m using Breeze, the Cloudways one. I’ll turn it off.

    PS. I just tried turning off as much as possible in plugins and disabled Cloudflare. It made no difference.

    I then downgraded the Lumiere to 4.3 and it is now throwing up debug info (above the widget displaying properly).

    [DEBUG] [Lumiere][Widget_Frontpage] Shortcode [lumiereWidget] found.

    [DEBUG] [Lumiere][Widget_Frontpage] Custom field lumiere_widget_movieid found, using "0023563" for querying

    [DEBUG] [Lumiere][Movie] Using the link maker class: Bootstrap_Links

    [DEBUG] [Lumiere][Movie] The following plugins compatible with Lumière! are in use: [imdbphp]

    [DEBUG] [Lumiere][Movie] Calling IMDbPHP class.

    [DEBUG] [Lumiere][Movie] Movie ID provided: *0023563*.

    [DEBUG] [Lumiere][Movie] Displaying rows for *0023563*

    [DEBUG] [Cache] Purging old cache entries

    [DEBUG] [Cache] Cache hit for [gql.TitleYear.{"id":"tt0023563"}7e5e54cb1775761ed989d18fd0a88412.json]

    [DEBUG] [Cache] Cache hit for [gql.Runtimes.{"id":"tt0023563"}b9668097397e1617df139086a558e09f.json]

    [DEBUG] [Cache] Cache hit for [gql.CreditCrew.{"id":"tt0023563","after":null}5f138b0160e1f03c01a11142fdb9478c.json]

    [DEBUG] [Cache] Cache hit for [gql.CreditQuery.{"id":"tt0023563","after":null}5eb39a11ab4cba3656a9c7eb3aea4754.json]

    [DEBUG] [Cache] Cache hit for [gql.Genres.{"id":"tt0023563"}0f07f6da43af6ecc7ef9c944543fcd0c.json]

    [DEBUG] [Cache] Cache hit for [gql.CreditCrew.{"id":"tt0023563","after":null}69748072933f46990cfc14911b44e3e6.json]

    [DEBUG] [Cache] Cache hit for [gql.Plots.{"id":"tt0023563"}c4da1ec4fdc84aeae4e3e49ead4f8b4a.json]
    Plugin Author JCV

    (@psykonevro)

    Thanks for the tests!
    In order to narrow down the issue, could you kindly also try with intermediary releases? (4.3.1 and 4.3.2) can be downloaded here.

    Thread Starter moviesteve

    (@moviesteve)

    Hi again,

    4.3.1 works and gives this as a debug log.

    [DEBUG] [Lumiere][Widget_Frontpage] Shortcode [lumiereWidget] found.

    [DEBUG] [Lumiere][Widget_Frontpage] Custom field lumiere_widget_movieid found, using "0058213" for querying

    [DEBUG] [Lumiere][Movie] Using the link maker class: Bootstrap_Links

    [DEBUG] [Lumiere][Movie] The following plugins compatible with Lumière! are in use: [imdbphp]

    [DEBUG] [Lumiere][Movie] Calling IMDbPHP class.

    [DEBUG] [Lumiere][Movie] Movie ID provided: *0058213*.

    [DEBUG] [Lumiere][Movie] Displaying rows for *0058213*

    [DEBUG] [Cache] Purging old cache entries

    [DEBUG] [Cache] Cache hit for [gql.TitleYear.{"id":"tt0058213"}7e5e54cb1775761ed989d18fd0a88412.json]

    [DEBUG] [Cache] Cache hit for [gql.Runtimes.{"id":"tt0058213"}b9668097397e1617df139086a558e09f.json]

    [DEBUG] [Cache] Cache hit for [gql.CreditCrew.{"id":"tt0058213","after":null}5f138b0160e1f03c01a11142fdb9478c.json]

    [DEBUG] [Cache] Cache hit for [gql.CreditQuery.{"id":"tt0058213","after":null}5eb39a11ab4cba3656a9c7eb3aea4754.json]

    [DEBUG] [Cache] Cache hit for [gql.Genres.{"id":"tt0058213"}0f07f6da43af6ecc7ef9c944543fcd0c.json]

    [DEBUG] [Cache] Cache hit for [gql.CreditCrew.{"id":"tt0058213","after":null}69748072933f46990cfc14911b44e3e6.json]

    [DEBUG] [Cache] Cache hit for [gql.Plots.{"id":"tt0058213"}c4da1ec4fdc84aeae4e3e49ead4f8b4a.json]

    4.3.2 does not work. Gives the [lumiereWidget]IMDb information[/lumiereWidget] message only

    Hope this helps

    Steve

    Plugin Author JCV

    (@psykonevro)

    That helps a lot, thank you very much @moviesteve! I appreciate you taking the time to go through painful techy things ??

    Limiting my investigations to the 4.3.2 changes, I have been able to reproduce a situation where the widget is not displayed and no log either. Only the text [lumiereWidget]IMDb information[/lumiereWidget]

    Would you be kind enough to replace

    if ( Widget_Selection::lumiere_block_widget_isactive( Widget_Selection::BLOCK_WIDGET_NAME ) === true ) {
    	add_shortcode( self::WIDGET_SHORTCODE, [ $this, 'shortcode_parser' ] );
    }

    by

    	add_shortcode( self::WIDGET_SHORTCODE, [ $this, 'shortcode_parser' ] );
    

    in file yourwebsite/wp-content/plugins/lumiere-movies/class/frontend/class-widget-frontpage.php?

    Let me know if it makes a difference.

    Thread Starter moviesteve

    (@moviesteve)

    Hooray, that seems to have done the trick. Thanks very much for all the hard work, really appreciate it.

    Plugin Author JCV

    (@psykonevro)

    So happy you’ll be able to continue using the plugin ?? Sticking to an old version is never a sustainable solution.

    So now it’s more relax. My guess is that the widget you’re got corrupted at some point. Either using an old WordPress widget with “classic widget” plugin. I haven’t been able to reproduce this issue, so I’m just guessing. In any case, the reason of the “bug” is that I added an extra checking in 4.3.2 to make sure the widget is active. In your case, it fails to find an active widget.

    Could you let me know wether you use “classic widget” plugin or any plugin that modifies the widgets?
    Or rather just copy-paste form wp-admin/site-health.php?tab=debug the list of “active plugins”. I’ll install them all to see if any of them changes the widget behaviour.

    Once we solve this, we’ll see what’s happening with the cache.

    Thread Starter moviesteve

    (@moviesteve)

    Hi again (and thanks again)

    Don’t think I”m using a classic widget but to be honest I am stumbling around in the dark a bit. If it’s not affecting anyone else then it must be something specific to me, I suppose.

    Here’s the list of plugins. As for the cache, it’s quite big 5.7gb or something last time I looked.

    Cheers, Steve

    FS PosterVersion 6.6.3 by FS-Code | Auto-updates disabled

    GenerateBlocksVersion 1.9.1 by Tom Usborne | Auto-updates disabled

    GP PremiumVersion 2.4.1 by Tom Usborne | Auto-updates disabled

    ImagifyVersion 2.2.4 by Imagify Image Optimizer – Optimize Images & Convert WebP & Avif | Auto-updates disabled

    Kadence Blocks – PRO ExtensionVersion 2.5.4 by Kadence WP | Auto-updates disabled

    Kadence Blocks – Gutenberg Blocks for Page Builder FeaturesVersion 3.4.6 by Kadence WP | Auto-updates disabled

    Lumière MoviesVersion 4.3.2.1 by psykonevro | Auto-updates disabled

    PerfmattersVersion 2.3.8 by forgemedia | Auto-updates disabled

    Pods – Custom Content Types and FieldsVersion 3.2.8.1 by Pods Framework Team | Auto-updates disabled

    Pods Alternative CacheVersion 2.2.0 by Pods Framework Team | Auto-updates disabled

    Rank Math SEOVersion 1.0.236 by Rank Math SEO | Auto-updates disabled

    Schema ProVersion 2.7.23 by Brainstorm Force | Auto-updates disabled

    Wordfence SecurityVersion 8.0.3 by Wordfence | Auto-updates disabled

    Yet Another Stars RatingVersion 3.4.13 by YetAnotherStarsRating.com | Auto-updates disabled

    Plugin Author JCV

    (@psykonevro)

    I tried to install the free versions of this list, couldn’t reproduce any issue. But since some of them allow to highly change the core of WordPress, I would need your specific customized wordpress blocks to understand what’s going on. Would be too much work.

    Since I can’t remember why I made this modification on the widget, I will remove it in the next WordPress. But beware, it may happen I had a good reason, so it may come back at some point. I don’t expect that, though.

    Regarding the cache, since you have 5 Go of data, I don’t believe it’s related to the latest Lumière releases, but to your huge amount of files. I tested up to 100 movies, I couldn’t see any issue to display the cache, but the manage cache page retrieves the files then do queries to the IMDb, which means something like 2500 queries in a couple of seconds…

    The only solution I can forsee is to disable the cache display as you already did. The latest Lumière versions actually improve the efficency of that page of administration. There is still room for improvement, like implementing a cache system, but I don’t want to create a cache for cached files. Let’s see if more users have this need in the future.

    In the meantime I close this request and thanks again for going through all of this.

    Thread Starter moviesteve

    (@moviesteve)

    Hi JCV, I think it all worked out OK in the end. Thanks for all the hard work. I’ll keep my fingers crossed for the future!

    Steve

Viewing 10 replies - 16 through 25 (of 25 total)
  • You must be logged in to reply to this topic.