WordPress.org

Ready to get started?Download WordPress

Forums

WP Missed Schedule Fix Failed Future Posts
[resolved] Any conflicts with w3 Cache? (23 posts)

  1. nickaster
    Member
    Posted 11 months ago #

    HI there.. I just installed and things seem to be working fine. However, I'm curious if anyone knows if there are any conflicts between this plugin and W3C cache.

    I"m fairly certain that W3C is the cause of my missed schedule problem, so I'm hoping this will play nicely.

    Any reports?

    http://wordpress.org/extend/plugins/wp-missed-schedule/

  2. sLa NGjI's
    Member
    Plugin Author

    Posted 11 months ago #

    My WP Missed Schedule plugin is ok and work fine, but W3 Total Cache "dbcache" module was reported to many users and blogs to break Missed Scheduled for more and more clean WordPress installations ... without (and with) my plugin.

    W3 Total Cache "object cache disk" is problematics ...

    W3 Total Cache "disk basic" and "minify" work fine with WP Missed Schedule.

    This is the latest topic for this question: all other same questions was dropped!

    :)

    Bye!

  3. Frederick Townes
    Member
    Posted 11 months ago #

    Remember that (any) caching will prevent WP Cron from being called unless you have a lot of WP Admin activity. So you will want to set up a system cron to call it to make it more reliable.

  4. sLa NGjI's
    Member
    Plugin Author

    Posted 11 months ago #

    This thread is off topic: please stop to "blame" my plugin support!

    Thanks :)

  5. nickaster
    Member
    Posted 11 months ago #

    Well... we'll see what happens tonight. I"ve got a bunch of posts scheduled. Fingers crossed.

  6. sLa NGjI's
    Member
    Plugin Author

    Posted 11 months ago #

    Also JetPack and others "social publishing plugins" stop WordPress Missed Scheduled to work.

  7. nickaster
    Member
    Posted 11 months ago #

    Well, something bizarre is happening, because tonight all my posts published 6 hours early ... just suddenly happend out of nowhere, but I'm 99% certain it's related to a fight between W3Cache and this plugin ... not sure I'll be able to keep this one on.

  8. Frederick Townes
    Member
    Posted 11 months ago #

    Anyone willing to submit a bug submission form from the support tab of the W3TC plugin will help me investigate so that we can get this fixed?

  9. sLa NGjI's
    Member
    Plugin Author

    Posted 11 months ago #

    For all: please read here befor posting or reviewing :)

    Frederick Townes wrote:

    Anyone willing to submit a bug submission form from the support tab of the W3TC plugin will help me investigate so that we can get this fixed?

    Fantastic spam thread!

    P.S. nickaster: your site http://www.triplepundit.com/ is misconfigured and cached files was not correctly served ...

  10. nickaster
    Member
    Posted 11 months ago #

    sLa - what did you see that was misconfigured?

    Fredrick - happy to do that. I'm going to let it go one more night and see if the problem happens again. Could have been some kind of fluke.

    sLa - to answer your questions on the site:

    01 - Version 2013.0130.2222
    02 - WordPress Version - 3.5.1
    03 - Detailed PHP Version Used ... no idea, can get later
    04 - Detailed SQL Used ... no idea, can get later
    05 - Detailed Server Type QS-1 - http://www.pair.com/services/dedicated/
    06 - Hosting Used (Pair.com)
    07 - Hosting Type (Dedicated)
    08 - WordPress TimeZone - All Pacific
    09 - Detailed WordPress Memory and PHP Allocated
    10 - Caching Plugin (W3 Total Cache)
    11 - Caching Method (Disk Basic)
    12 - Exactly Numbers of Plugin Used and Loaded - lots.

  11. sLa NGjI's
    Member
    Plugin Author

    Posted 11 months ago #

    @nickaster

    1 - All two database+server hosting and WordPress was syncronized for "Pacific Time" really!

    2 - Try to disable "object cache module"

    3 - Clean W3 Total Cache (completely) and waiting normal proxies flushing propagation ...

    4 - Use a plugin to view "cron process" (wp-crontrol for example)

    5 - Try forked W3 Total Cache instead official release ...

    6 - Try WP Missed Schedule Version 2013.0131.3333

    7 - Verify the possibility of other plugins conflict

    8 - Verify that CDN really work ...

    9 - Disable caching for loggedin users (administrator for example)

    10 - Downgrade WordPress 3.5.1 to 3.4.2

    nickaster wrote: what did you see that was misconfigured?

    Your cached files was not correctly served ... configure all W3 total Cache functions (for example browser caching) ...

    P.S. Your W3 Total Cache Version used?

  12. nickaster
    Member
    Posted 11 months ago #

    Thanks... i'll let it run for testing purposes tonight and look into that tomorrow.

    What did you see that showed that "Your cached files was not correctly served" ... it's the latest W3.

  13. sLa NGjI's
    Member
    Plugin Author

    Posted 11 months ago #

    User that visit your site download all new version of your data instead cached version.

  14. nickaster
    Member
    Posted 11 months ago #

    That's odd.... so you mean, it doesn't seem cached at all? When I look at my source code I see - <!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

    Page Caching using disk: basic
    Object Caching 1567/1594 objects using disk: basic
    Content Delivery Network via Amazon Web Services: CloudFront: cdn5.triplepundit.com

    Served from: http://www.triplepundit.com @ 2013-05-06 20:00:22 by W3 Total Cache -->

    Sorry to take this off topic, but I'm curious how you determined that?

  15. nickaster
    Member
    Posted 11 months ago #

    Okay - well it happened again... around 11pm Pacific time every single post published even though nothing was supposed to be published until about 2 am the following day... maybe it's a time zone problem? 3 hours seems to suggest that perhaps the pluging thinks this is east coast time.

    Would that be possible?

  16. nickaster
    Member
    Posted 11 months ago #

    Yes I'm sure of it....the server is actually located on east coast time. So perhaps the plugin thinks it's 3 hours later than it actually is. It seems like the plugin not correctly looking at the time zone that I have set the site to function in.

    This actually makes sense. Don't think it has anything to do with W3 Cache or any cache at all.

  17. sLa NGjI's
    Member
    Plugin Author

    Posted 11 months ago #

    Please: try this version http://downloads.wordpress.org/plugin/wp-missed-schedule.zip of WP Missed Schedule ;)

    Use http://redbot.org/ for testing if W3 Total Cache really work ...

  18. nickaster
    Member
    Posted 11 months ago #

    Alright, I've got the new version up. I'll report back tomorrow to see if things went as planned.

  19. sLa NGjI's
    Member
    Plugin Author

    Posted 11 months ago #

    WordPress comes with its own cron job that allows you to schedule your posts and events. However, in many situations, the WP-Cron is not working well and leads to posts missed their publication schedule and/or scheduled events not executed.

    To understand why this happen, we need to know that the WP-Cron is not a real cron job. It is in fact a virtual cron that only works when a page is loaded. In short, when a page is requested on the frontend/backend, WordPress will first load WP-Cron, follow by the necessary page to display to your reader. The loaded WP-Cron will then check the database to see if there is any thing that needs to be done.

    Reasons for WP-Cron to fail could be due to:

    DNS issue in the server.
    Plugins conflict
    Heavy load in the server which results in WP-Cron not executed fully
    WordPress bug
    Using of cache plugins that prevent the WP-Cron from loading
    And many other reasons

    :)

  20. nickaster
    Member
    Posted 11 months ago #

    Okay, thanks!

    Well everything worked fine last night, so I think your plugin is working. Thanks!

  21. sLa NGjI's
    Member
    Plugin Author

    Posted 11 months ago #

    Thanks you!

    :)

    P.S. Please confirm this: for your case Version 2013.0130.2222 not work, and Version 2013.0131.3333 work fine?

  22. nickaster
    Member
    Posted 11 months ago #

    This is what I currently have:

    Version 2013.0131-BUGFIX.3333-DEVELOPMENTAL

    YES it works.

    The old version that did not work was Version 2013.0130.2222

  23. sLa NGjI's
    Member
    Plugin Author

    Posted 11 months ago #

    This issue was inserted as Ticket #4163854 on to Todo List for Future Development.

    Thanks to nickaster and all others users was send me same solution via Contact form ...

    If are satisfied of this plugin, please, consider one small Donation for my free work. :)

Reply

You must log in to post.

About this Plugin

About this Topic