"Update Failed" when using FTP or SFTP via WordPress #389
Comments
|
What version of Quick Cache Pro are you currently running please? |
|
Version 141205 Mark www.markmallett.com http://www.markmallett.com/
|
|
Thank you. I'm making an attempt to reproduce this now. |
|
Just tested this against WordPress v4.1 where I upgraded from Quick Cache Pro v141205 to v141231 without issue. What version of WordPress are you running please? |
|
I’m using 4.1 Here’s are the steps:
Mark www.markmallett.com http://www.markmallett.com/
|
I see. So you're using FTP or SFTP via WordPress to perform the updates as opposed to direct file access. This could be the point that I'm missing in my tests. Taking a closer look. |
|
Successfully reproduced the bug. Taking a closer look.
|
|
@rideralberta Thanks again for reporting this! I've had the issue resolved in the development copy so that it won't be a problem moving forward. That change will be reviewed by our lead developer and included in the next release cycle. In the mean time, you can work around the issue by specifying the FTP credentials that WordPress should use inside your Here are the lines that I added at the top of my <?php
define( 'FS_METHOD', 'ftpext' );
define( 'FTP_BASE', '/public_html/jason/' );
define( 'FTP_USER', 'jason' );
define( 'FTP_PASS', 'xxxxxxxx' );
define( 'FTP_HOST', 'ftp.example.com' );
define( 'FTP_SSL', FALSE );See also: http://codex.wordpress.org/Editing_wp-config.php#WordPress_Upgrade_Constants |
|
Great, thank you! Sent from my iPhone
|
|
@rideralberta Thanks so much for reporting this! @jaswsinc Thanks for submitting the Pull Request! This fix has been merged into the development trunk and will go out with the next public release. Note: If you're interested in testing a beta release of Quick Cache before the next version comes out, please sign-up to be a beta tester here. |
|
Thanks for thanking me and each other! ;-) Mark www.markmallett.com http://www.markmallett.com/
|
|
Hm. We made these changes, and the plugin appeared to update… but when it tried to return me to the Admin page, it was blank, as well as the entire blog—just a blank page being served up. The cache appears to be broken all of a sudden… Mark www.markmallett.com http://www.markmallett.com/
|
Oh goodness! Not sure why that would have happened. You may want to seek assistance from your hosting company in this case. Have you lost all access to your Dashboard now? EMERGENCY: If All Else Fails (How-To Remove Quick Cache)Ordinarily you can just deactivate Quick Cache from the plugins menu in WordPress. However, if you're having a more serious issue, please follow the instructions here.
Quick Cache is now completely uninstalled and you can start fresh :-) If you start fresh and the problem continues, please report back and let us know about this. NOTE: If you added any of the config. values that I mentioned previously and these are somehow corrupted on your end, that could be a problem too. So you might want to review those carefully before proceeding any further. For instance, make sure you are not missing any of the single quotes seen in this example. <?php
define( 'FS_METHOD', 'ftpext' );
define( 'FTP_BASE', '/public_html/jason/' );
define( 'FTP_USER', 'jason' );
define( 'FTP_PASS', 'xxxxxxxx' );
define( 'FTP_HOST', 'ftp.example.com' );
define( 'FTP_SSL', FALSE ); |
|
@jaswsinc Thanks for jumping in here. :) @rideralberta I'm going to mark this Issue as closed, but if you discover there's still a problem after following Jason's suggestions above, and you suspect it has something to do with Jason's suggestion, please let us know and I'll reopen this. |
|
Hi Jason, My host restored an earlier backup, thank goodness. They felt it was an issue on your side now. So, I manually installed your latest version and deleted the old one. I don’t know if that’s the proper procedure, but it seems to be working. I guess I’ll wait for a future release from you that will have this fixed. Thanks again. Mark www.markmallett.com http://www.markmallett.com/
|
|
@rideralberta Interesting. We have not had any other reports of problems like this with the latest release. Was there any indication of what the problem was exactly? Can you find anything in your PHP error log? |
|
I’ll fire that question off to my host. Mark www.markmallett.com http://www.markmallett.com/
|
|
Hi Jason, This was my host’s reply: "Unfortunately, there were no errors generated in the error log when attempting to go to the blog and seeing the blank white page.” Mark www.markmallett.com http://www.markmallett.com/
|
|
@rideralberta You may want to enable WordPress Debugging prior to doing the next Quick Cache update, just so that if the update fails again, you'll have a better chance at figuring out why it's failing: Add the following lines to your See also: https://codex.wordpress.org/Debugging_in_WordPress As Jason mentioned, we have not seen this issue from any other Quick Cache Pro users, and we know there are thousands of successful updates every time an update is released, so there's a good chance this was either an unreproducible fluke, or there's a weird configuration on your server that's causing this (assuming it can be reproduced). I'll leave this Issue closed for now, but if you do find errors during the next update, please reply here so that we can reopen this. |
|
The fixes applied from this issue have been released today with v150129:
See the v150129 announcement post. This issue will now be locked to further updates. If you have something to add related to this Issue, please open a new GitHub Issue and mention this one (#389). |
raamdev
changed the title
In the WordPress Post window, there is a message to update Quick Cache. When I select it, I am taken to the QC plugin window where I enter my username and password. This takes me, then, to the plugin update window of Wordpress. However, after proceeding to update, I get the message that the plugin is already at the current version—and it's not.
Suggestions?
The text was updated successfully, but these errors were encountered: