• Resolved hoopdreams

    (@hoopdreams)


    Hello,

    First of all – we love Tablepress, and have supported it in the past. Thanks for all the hard work!

    An odd issue did come up today, however.

    Our auto-importer was working just fine, and then I changed the time frame from 1 hour to 15 minutes. Since then, it hasn’t fire at all, AND my site has gone down twice (could be coincidence, but I don’t know – it has had 100% uptime otherwise this year).

    I read through other threads – we don’t have any caching enabled at present, and reduced the number of tables to a more manageable amount. Is there anything we might be missing?

    Our site is dailyfantasysportsrankings.com, though the tables are behind a paywall at present (though I could unlock them if you’d like to look at them).

    Thanks for your help.

    https://www.ads-software.com/plugins/tablepress/

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Tobias B?thge

    (@tobiasbg)

    Hi,

    thanks for your post, and sorry for the trouble.

    I’m not sure what could be causing this. To make sure that you are really using the latest version of the Extension, please re-install it from a fresh download (even if that has the same version number, as there were some small changes for which I did not increase the version number).

    Then, please also try the ideas in this thread, about the WP_Cron functionality and the WP_DEBUG and WP_MEMORY_LIMIT constants: https://www.ads-software.com/support/topic/auto-import-stopped-working-with-36?replies=16

    Regards,
    Tobias

    Thread Starter hoopdreams

    (@hoopdreams)

    Well, it’s now auto-importing, but still occasionally creating a database connection error (which causes me to have to restart the MySQL database).

    I’ve set the WP_DEBUG constant to true. What should I do now?

    Thanks!

    Thread Starter hoopdreams

    (@hoopdreams)

    And, the WP_DEBUG constant seems to destroy the whole website and spit out tons of errors. Have to turn it off.

    Plugin Author Tobias B?thge

    (@tobiasbg)

    Hi,

    yeah, that’s the idea of the WP_DEBUG constant ?? It shows errors instead of hiding them ??

    Unfortunately, I have no idea about those mySQL issues ?? Neither TablePress nor the Extension perform any direct mySQL queries, they only use the WordPress API functions. I suggest that you try to debug this with the help of the server admin or webhost company, as they might have access to the DB or server error log files.

    Regards,
    Tobias

    Thread Starter hoopdreams

    (@hoopdreams)

    They said something about the server potentially thinking that the auto-importer was causing a continuous loop?

    I’ve also triggered this problem by simply clicking “save auto-import configurations.”

    Plugin Author Tobias B?thge

    (@tobiasbg)

    Hi,

    I’m not sure how that could happen. The Extension does indeed use loops, but those are looping over a defined set of elements, without the potential for an infinite loop.
    Also, if this were to happen, it should “only” stop the PHP execution but not the mySQL server connection.
    So, I don’t really have a clue what could be going on here ??

    Regards,
    Tobias

    Thread Starter hoopdreams

    (@hoopdreams)

    Oy, okay. Thanks for your replies.

    Plugin Author Tobias B?thge

    (@tobiasbg)

    Hi,

    sure, no problem!
    If you find out more about this, please let me know!

    Regards,
    Tobias

    Thread Starter hoopdreams

    (@hoopdreams)

    Hello Tobias,

    It seems as though the auto-importer might have a memory leak. Does that sound like a possibility on your end? We had to restore our site to an earlier version of itself because the problem kept getting worse and worse – even after the auto-import plug-in was deleted!

    Plugin Author Tobias B?thge

    (@tobiasbg)

    Hi,

    I can’t really imagine that. PHP memory for a request is free’d when the request has been processed. Also, when the Extension is deactivated, none of its code is even loaded by WordPress, so that can not be the reason for the memory leak that you describe here.

    Regards,
    Tobias

    Thread Starter hoopdreams

    (@hoopdreams)

    Hey Tobias,

    No luck. Even deleting the importer has had no positive effects. It continues to disconnect the MySQL database from our site even after the entire plug-in has been deleted.

    Plugin Author Tobias B?thge

    (@tobiasbg)

    Hi,

    if this happens even with the Auto-Import Extension deleted, then this must have another cause. The Extension is then definitely not it.
    Unfortunately, I’m not a DB or server expert, so I don’t know what else could be doing this. ??

    Regards,
    Tobias

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Auto-importer not firing’ is closed to new replies.