• Resolved moviesteve

    (@moviesteve)


    Hi there,

    First: thanks for the great plugin. Looks good too!

    I’ve just been looking at my debug log and have absolutely thousands of this same message.

    [13-Mar-2024 05:24:00 UTC] PHP Warning: Undefined array key “imdbdelayimdbrequest” in /home/xxxxx.cloudwaysapps.com/xxxxxxxx/public_html/wp-content/plugins/lumiere-movies/class/plugins/class-imdbphp.php on line 75

    I’ve x’d out the actual identifiers.

    The error is registering roughly ten times a second.

    Do you have any idea what’s going on here? I’m also having periodic intense CPU activity on the site – to 100% quite often – and was wondering if it was related.

    All the best

    Steve

    • This topic was modified 11 months, 3 weeks ago by moviesteve.

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author JCV

    (@psykonevro)

    Hi @moviesteve

    Thanks for your kind words ??

    Seems like that for some reason, the update of the new settings wasn’t processed.

    Could you go to your admin page wp-admin/admin.php?page=lumiere_options&subsection=advanced
    and click on “Reset options”? That will reset to default values your general options. Make sure to write down them before reseting, you may have made some changes you want to keep.

    Let me know if after reseting the options the problem persists. If it does, please provide your PHP version, WP and make sure Lumiere plugin is up to date.

    (on side note: If you have ten errors per second, intense CPU activity may be indeed related to that issue, even if I’m not sure that a missing var could be so CPU demanding)

    Plugin Author JCV

    (@psykonevro)

    I was correct. I found an issue in the internal updating process of the plugin. Next version will adress the issue.

    Thanks a lot for reporting it, you helped me improve the plugin.

    Thread Starter moviesteve

    (@moviesteve)

    Hi again JCV,

    Lightning response! It worked. Reset the options and the PHP warning went away. I put all my various settings back in place and it was still ok.

    Thanks so much.

    I’ve got another strange issue of being bombarded by three Amazonbots, but the only pages they’re targeting are lumiere related.

    Like this:

    Mar 15 19:02:07

    52.70.240.171

    GET /lumiere/film/?mid=1507566 HTTP/1.1″ 503 7676 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/600.2.5 (KHTML, like Gecko) Version/8.0.2 Safari/600.2.5 (Amazonbot/0.1; +https://developer.amazon.com/support/amazonbot)

    Mar 15 19:02:12

    3.224.220.101

    GET /lumiere/film/?mid=1901004 HTTP/1.1″ 503 7676 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/600.2.5 (KHTML, like Gecko) Version/8.0.2 Safari/600.2.5 (Amazonbot/0.1; +https://developer.amazon.com/support/amazonbot)

    Mar 15 19:02:17

    23.22.35.162

    GET /lumiere/film/?mid=1703147 HTTP/1.1″ 503 7676 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/600.2.5 (KHTML, like Gecko) Version/8.0.2 Safari/600.2.5 (Amazonbot/0.1; +https://developer.amazon.com/support/amazonbot)

    I suspect you’re going to say “open a new ticket”.

    Best

    Steve

    Plugin Author JCV

    (@psykonevro)

    Glad it worked out!

    Re: the bots, I made the decision to hard code (no option to remove it) the bot banning. I noticed that even major bots (Amazon, Google, etc) do not respect the HTML “no follow” rule, which is supposed to tell them not to follow a new page beyond to the page made directly available by lumiere.

    Bots are actually spiders, indexing whatever you tell them your entire website. The plugin can potentially produce hundreds of thousands of webpages. My own cache was reaching 1 Go IN A DAY because of such indexing. It wouldn’t also be fair to let them belive that a website, which copy basically the IMDb information, is the actual owner of this information. So all bots that have no referrer (that is to say, do not directly follow a link you added yourself on your own website) will be banned. It’s better for your website that will not have to cope with dozens of Go of cache data, and fairer towards the IMDb. Everybody wins ??

    You will have for some time these Apache reports, then the bots will slowly space out the visits.

    I may in the near future change the 503 error status to a 400 error which is probably more appropriate, and should not be displayed in the Apache error log if the settings are standard. I guess was upset against the bots when I implemented this feature ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Thousands of PHP warnings’ is closed to new replies.