WordPress.org

Ready to get started?Download WordPress

Forums

2.9 Schedule Posts "missed" (95 posts)

  1. Robert Chapin
    Member
    Posted 4 years ago #

    WordPress, if you are listening:

    (1) How could you release an upgrade that is obviously this problem-filled?

    I don't represent WordPress in any way, but I agree with you on that point. There were many known bugs (other than this) at release time.

    Here's the bottom line for this bug: We need a volunteer who can show us what's happening in the wild, and offer their expertise or offer access to their server so that an expert can debug the scheduling system when it's broken.

    Some discussion started at http://core.trac.wordpress.org/ticket/11505 and there are some theories and speculation, but it looks like none of the devs could reproduce this bug on their own servers.

    I am qualified to debug most PHP issues, so anyone willing to let me run some test cases can drop a message at http://www.miqrogroove.com/contact/

  2. naweedshams
    Member
    Posted 4 years ago #

    My website has gone awol too :(

    After heavy customization and spending alot of money fixing it to how i want it, it's all ruined.

    I think I'm going to sue somebody.

    http://www.visitlocal.co.uk

    Backed up my files, folders etc. Hit the upgrade button, got the maintainence error page, deleted it from the root folder.. clicked refresh and the website went blank white.

    I really need to get this resolved asap. Can anyone help please?

  3. 5ubliminal
    Member
    Posted 4 years ago #

    @naweedshams

    By FTP rename the wp-content/plugins folder to !plugins. See how that works and start reactivating plugins one by one. Track the one that succumbs.

    PS: Never upgrade without doing some local testing. Especially if you rely on your blog for other stuff than fun.

  4. ptmccain
    Member
    Posted 4 years ago #

    I've been blogging for nearly ten years, with various platforms, and have never had an upgrade so royally screw up my blog site. Thank you, WordPress.

  5. ofdphoto
    Member
    Posted 4 years ago #

    Getting this error message when I hit wp-cron:

    Warning: Invalid argument supplied for foreach() in wp-content/plugins/rsscloud/send-post-notifications.php on line 17

  6. ofdphoto
    Member
    Posted 4 years ago #

    So, I disabled the RSS Cloud plugin and will see if that fixed scheduled posting. It certainly makes that error go away ;)

  7. naweedshams
    Member
    Posted 4 years ago #

    I spent so much money customizing my wordpress site, we need to be compensated for such a bug filled upgrade :@ :@ :@ :@ :@ :@

  8. ofdphoto
    Member
    Posted 4 years ago #

    And how much did you pay for WordPress itself?

    All this complaining is silly. If you're serious about running a high-availability site, there's no way you'd upgrade a production system before testing it.

  9. Robert Chapin
    Member
    Posted 4 years ago #

    That's right. Until someone volunteers for debugging, no more complaints are allowed ^_^

  10. ptmccain
    Member
    Posted 4 years ago #

    I volunteer!

  11. Robert Chapin
    Member
    Posted 4 years ago #

    Great! Send me a message at http://www.miqrogroove.com/contact/ so we can get started.

  12. naweedshams
    Member
    Posted 4 years ago #

    Well that's a little late don't you think. WordPress should have tested 2.9 before releasing it!

    There's thousands of disgruntled users complaining on twitter, not just me.

  13. marie-aude
    Member
    Posted 4 years ago #

    Don't you think it has been tested ?
    And I'm sorry for you, but if YOU follow the clear instructions of always doing a back up of files and database before upgrading, it is only a question of 15 minutes MAXIMUM to put back your site in its former state.

    Instead of twitting their unsatisfaction, people should try to apply basic procedures.

  14. naweedshams
    Member
    Posted 4 years ago #

    I actually did backup my files and folders thank goodness.

    I just dont know how to backup the database files to re-install everything from scratch.

    My site is http://www.visitlocal.co.uk - hasn't been working for almost 2 hours, deleted all the plugins.. not sure whats up.

  15. I just dont know how to backup the database files to re-install everything from scratch.

    There are multiple ways: http://codex.wordpress.org/WordPress_Backups#Database_Backup_Instructions

  16. naweedshams
    Member
    Posted 4 years ago #

    Thanks for the link :)

    I checked it out before but still unsure, I'm quite a novice at the database stuff.

    What i want to do is reinstall wordpress on my site, but use the current database.. but i'm confused about how to do that.

  17. If you didn't run the DB upgrade for 2.9, then you can just restore the 2.8 files. if you DID upgrade the DB, then ... you really can't.

  18. naweedshams
    Member
    Posted 4 years ago #

    Thank god for wordpress community forums.

    Someone else suggested i should:

    Manually upload the 2.9 files using ftp? Everything except your wp-config.php file and the wp-content folder.

    And it worked :D

    Website is back live and using 2.9 :D:D:D - http://www.visitlocal.co.uk.

    Thanks for everyone's responses, highly appreciate it.

    Would love to donate somehow.

  19. ptmccain
    Member
    Posted 4 years ago #

    I'm getting some amazing help from Miqrogroove, two hours now and counting, but "we" think we have it fixed now. He'll have to explain what he did. It's all Greek to me.

  20. ptmccain
    Member
    Posted 4 years ago #

  21. JoeMac
    Member
    Posted 4 years ago #

    Before anyone upgrades to a new WordPress especially a new major release like 2.8.6 to 2.9, they need to take a few precautions.

    1) Always download your database first and also download your last version of your website, so you can easily restore the old version.

    2) New software means the plugins may nor may not be compatible, so instead of jumping on board with upgrading, you should wait a week or two for the plugins to get upgraded to the version.

    3) Always try a test version first, just to make sure. Duplicate your site in a separate folder on your server (also duplicate a separate DB) and test out the new version first. If all goes well then upgrade your public site.

    Obviously your sites are important to you or you wouldn't be jumping on upgrading. I have a number of clients who use WordPress and I haven't upgraded any of them yet. I a just using 2.9 on one site right now and have a posting problem, which can be worked around, but until it gets fully solved, and all the plugins I use get upgraded, I am not fully upgrading to 2.9.

  22. Robert Chapin
    Member
    Posted 4 years ago #

    The final results are in, and it looks like a last-minute change to the WordPress 2.9 package stepped on a very obscure "feature" of the PHP cURL library. Those goodies are implemented in the packaged file named wp-includes/http.php.

    This patch is waiting for core approval now, but I wanted to put it up here in case anyone needs an alternative to the stop-gap solution from earlier tonight.

    http://core.trac.wordpress.org/attachment/ticket/11505/ticket-11505-full.patch

    Everyone give a big happy Thank You to fellow blogger and forum member ptmccain who tolerated my intrusions on his server for the better part of the evening to get this figured out.

  23. ryancan123
    Member
    Posted 4 years ago #

    miqrogroove, so how would i take what's here: http://core.trac.wordpress.org/attachment/ticket/11505/ticket-11505-full.patch and use it to fix this issue? i don't understand, do i replace a file with a new file that is on trac? i'm lost and in panic mode about this problem.

  24. Robert Chapin
    Member
    Posted 4 years ago #

    Hi ryancan123, the linked file is in standard diff format. It's not really intended for end users. Eventually you will need to replace the http.php file I mentioned. As I am not a WordPress developer, I don't get to update the official files. ;)

  25. ryancan123
    Member
    Posted 4 years ago #

    okay so i open up http.php and replace:

    $timeout_ms = (int) ceil( 1000 * $r['timeout'] );

    with

    $timeout_ms = (int) ceil( 1000 * max($r['timeout'], 1) );

    hmmm...? thanks for your help.

  26. Robert Chapin
    Member
    Posted 4 years ago #

    If you get that far then you're doing well, yes :)

  27. ryancan123
    Member
    Posted 4 years ago #

    okay and is http.php the only file i need to find a replace code to get this problem fixed?

  28. Robert Chapin
    Member
    Posted 4 years ago #

    That's the only file covered by the patch. I'm not making any promises because there are other unfixed bugs out there.

  29. ryancan123
    Member
    Posted 4 years ago #

    wow it works. you ROCK!!!!!!!!!!!!!!!!!!!!!! thanks a million =)

  30. Dion Hulse
    WordPress Dev
    Posted 4 years ago #

    Re-posted to: http://dd32.id.au/2009/12/21/a-call-to-arms/

    I'd like to use this as an example to all here, Why WordPress needs your help. No, I'm not talking about Coding help specifically, I'm talking about Testing. WordPress requires that users test the product throughout the development period.

    WordPress is an open source application written by hundreds of contributors. While those hundreds probably use the Development version of WordPress every day, They do not use the same webhost as you, nor do they have the same theme, nor do they have the same requirements, They use different functions of WordPress than you.

    During The beta and RC stages, thousands of people download and test, These testers are end users like you, In order to prevent these bugs getting into a released product, It requires that users actually take part in the developement of WordPress and report the bugs encountered.

    Testing WordPress is not just something that Developers should do. If you use WordPress and enjoy using it, Please take some time once every few months to test WordPress, Its announced on the Dev blog when Beta's are available, On a default install of WordPress, The Dashboard should have a RSS feed mentioning the releases too.

    So please, For 3.0, When a Beta is released (Theres generally ~2-3 weeks of beta, with 2-3 beta's from my quick recolection) Install it on your website, It doesnt have to be your main one, it can be in a subdirectory (ie. your usual one at http://my-site.com/ and the test at http://my-site.com/testing/), and test that things works ok for you, and your plugins, This does take an hour out of your time, and i realise not everyone can afford it, But it may spare you 2-3 hours of your time, when after a release, a bug that affects you is found, that a Developer had not noticed.

    WordPress requires your input, Whilst I agree there are some downfalls in reporting bugs sometimes (Please do not flame me with related messages here, I'm not after that, This is mearly a request for more contributions) overall, your contributions would be greatly appreciated by all.

    In order to make it easier to test Beta's and nightly versions, Westi wrote this great plugin: http://wordpress.org/extend/plugins/wordpress-beta-tester/ It allows you to use the inbuilt upgrader to upgrade to a beta, to make it easier for you, to be involved with the project you love using.

Topic Closed

This topic has been closed to new replies.

About this Topic