Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Update Failed" when using FTP or SFTP via WordPress #389

Closed
rideralberta opened this issue Jan 3, 2015 · 21 comments
Closed

"Update Failed" when using FTP or SFTP via WordPress #389

rideralberta opened this issue Jan 3, 2015 · 21 comments
Assignees
Labels
Milestone

Comments

@rideralberta
Copy link

@rideralberta rideralberta commented Jan 3, 2015

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?

@jaswrks
Copy link

@jaswrks jaswrks commented Jan 4, 2015

What version of Quick Cache Pro are you currently running please?

@rideralberta
Copy link
Author

@rideralberta rideralberta commented Jan 4, 2015

Version 141205

Mark


www.markmallett.com http://www.markmallett.com/

On Jan 3, 2015, at 10:10 PM, JasWSInc [Masked] FWD_RFgv4KlN@opayq.com wrote:

Preview: What version of Quick Cache Pro are you currently running ple
This email is forwarded from a MASKED EMAIL you created using DoNotTrackMe https://dnt.abine.com/help.
IF THIS IS SPAM, CLICK HERE TO BLOCK. https://dnt.abine.com/#/block_email/efc16983@opayq.com/FWD_RFgv4KlN@opayq.com

Want to shop safely and privately online? Get DoNotTrackMe Premium https://dnt.abine.com/#premium.

What version of Quick Cache Pro are you currently running please?


Reply to this email directly or view it on GitHub #389 (comment).

@jaswrks
Copy link

@jaswrks jaswrks commented Jan 4, 2015

Thank you. I'm making an attempt to reproduce this now.

@jaswrks
Copy link

@jaswrks jaswrks commented Jan 4, 2015

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?

@rideralberta
Copy link
Author

@rideralberta rideralberta commented Jan 4, 2015

I’m using 4.1

Here’s are the steps:

  1. At the top of Wordpress, I get the notification: "Quick Cache Pro: a new version is now available. Please upgrade to v141231 http://www.markmallett.com/blog/wp-admin/admin.php?page=quick_cache-update-sync.”
  2. When I click the upgrade, it takes me to your QuickCache Updater within Wordpress, where I enter my WebSharks Username/Password. This then takes me to WordPress’s Update Plugin page where I enter my FTP username/password. After I click proceed, I get the notification "The plugin is at the latest version."

Mark


www.markmallett.com http://www.markmallett.com/

On Jan 4, 2015, at 12:01 AM, JasWSInc [Masked] FWD_KqURZlSz@opayq.com wrote:

Preview: Just tested this against WordPress v4.1 where I upgraded from
This email is forwarded from a MASKED EMAIL you created using DoNotTrackMe https://dnt.abine.com/help.
IF THIS IS SPAM, CLICK HERE TO BLOCK. https://dnt.abine.com/#/block_email/efc16983@opayq.com/FWD_KqURZlSz@opayq.com

Want to shop safely and privately online? Get DoNotTrackMe Premium https://dnt.abine.com/#premium.

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?


Reply to this email directly or view it on GitHub #389 (comment).

@jaswrks
Copy link

@jaswrks jaswrks commented Jan 4, 2015

his then takes me to WordPress’s Update Plugin page where I enter my FTP username/password.

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.

@jaswrks
Copy link

@jaswrks jaswrks commented Jan 4, 2015

Successfully reproduced the bug. Taking a closer look.

2015-01-04_00-43-31

@jaswrks jaswrks added pro and removed needs testing labels Jan 4, 2015
@jaswrks jaswrks added the in progress label Jan 4, 2015
jaswrks pushed a commit to wpsharks/comet-cache-pro that referenced this issue Jan 4, 2015
jaswrks pushed a commit to wpsharks/zencache-pro-original that referenced this issue Jan 4, 2015
@jaswrks jaswrks added ready to merge and removed in progress labels Jan 4, 2015
@jaswrks
Copy link

@jaswrks jaswrks commented Jan 4, 2015

@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 /wp-config.php file; and this way you won't be bothered to enter them again when you're working inside the Dashboard.

Here are the lines that I added at the top of my /wp-config.php file to get this working...

<?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
~ For the full documentation regarding FS_METHOD and the FTP_* config values.

@rideralberta
Copy link
Author

@rideralberta rideralberta commented Jan 4, 2015

Great, thank you!

Sent from my iPhone

On Jan 4, 2015, at 4:42 AM, JasWSInc [Masked] FWD_xQeTgKYa@opayq.com wrote:

Preview: @rideralberta Thanks again for reporting this! I've had the i
This email is forwarded from a MASKED EMAIL you created using DoNotTrackMe.
IF THIS IS SPAM, CLICK HERE TO BLOCK.

Want to shop safely and privately online? Get DoNotTrackMe Premium.

@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 /wp-config.php file; and this way you won't be bothered to enter them again when you're working inside the Dashboard.

Here are the lines that I added at the top of my /wp-config.php file to get this working...

@raamdev
Copy link
Contributor

@raamdev raamdev commented Jan 4, 2015

@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.

@raamdev raamdev added this to the Next Release milestone Jan 4, 2015
@rideralberta
Copy link
Author

@rideralberta rideralberta commented Jan 4, 2015

Thanks for thanking me and each other!

;-)

Mark


www.markmallett.com http://www.markmallett.com/

On Jan 4, 2015, at 2:37 PM, Raam Dev [Masked] FWD_odG8Urny@opayq.com wrote:

Preview: @rideralberta Thanks so much for reporting this! @jaswsinc Th
This email is forwarded from a MASKED EMAIL you created using DoNotTrackMe https://dnt.abine.com/help.
IF THIS IS SPAM, CLICK HERE TO BLOCK. https://dnt.abine.com/#/block_email/efc16983@opayq.com/FWD_odG8Urny@opayq.com

Want to shop safely and privately online? Get DoNotTrackMe Premium https://dnt.abine.com/#premium.

@rideralberta https://github.com/rideralberta Thanks so much for reporting this!

@jaswsinc https://github.com/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 http://www.websharks-inc.com/r/quick-cache-beta-testers-list/.


Reply to this email directly or view it on GitHub #389 (comment).

@rideralberta
Copy link
Author

@rideralberta rideralberta commented Jan 5, 2015

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/

On Jan 4, 2015, at 4:42 AM, JasWSInc [Masked] FWD_xQeTgKYa@opayq.com wrote:

Preview: @rideralberta Thanks again for reporting this! I've had the i
This email is forwarded from a MASKED EMAIL you created using DoNotTrackMe https://dnt.abine.com/help.
IF THIS IS SPAM, CLICK HERE TO BLOCK. https://dnt.abine.com/#/block_email/efc16983@opayq.com/FWD_xQeTgKYa@opayq.com

Want to shop safely and privately online? Get DoNotTrackMe Premium https://dnt.abine.com/#premium.

@rideralberta https://github.com/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 /wp-config.php file; and this way you won't be bothered to enter them again when you're working inside the Dashboard.

Here are the lines that I added at the top of my /wp-config.php file to get this working...

@raamdev raamdev reopened this Jan 6, 2015
@jaswrks
Copy link

@jaswrks jaswrks commented Jan 6, 2015

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…

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.

  • Log into your site via FTP; perhaps using FileZilla.
  • Delete this file: /wp-content/advanced-cache.php
  • Delete this directory: /wp-content/plugins/quick-cache/
  • Remove this line from your /wp-config.php file: define('WP_CACHE', TRUE);

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 );
@raamdev
Copy link
Contributor

@raamdev raamdev commented Jan 6, 2015

@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.

@raamdev raamdev closed this Jan 6, 2015
@rideralberta
Copy link
Author

@rideralberta rideralberta commented Jan 6, 2015

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/

On Jan 6, 2015, at 7:46 AM, JasWSInc [Masked] FWD_mYQQgMdZ@opayq.com wrote:

Preview: > but when it tried to return me to the Admin page, it was bl
This email is forwarded from a MASKED EMAIL you created using DoNotTrackMe https://dnt.abine.com/help.
IF THIS IS SPAM, CLICK HERE TO BLOCK. https://dnt.abine.com/#/block_email/efc16983@opayq.com/FWD_mYQQgMdZ@opayq.com

Want to shop safely and privately online? Get DoNotTrackMe Premium https://dnt.abine.com/#premium.

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…

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.

Log into your site via FTP; perhaps using FileZilla http://www.youtube.com/watch?v=joXUMhr8PhU.
Delete this file: /wp-content/advanced-cache.php
Delete this directory: /wp-content/plugins/quick-cache/
Remove this line from your /wp-config.php file: define('WP_CACHE', TRUE);
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.

@jaswrks
Copy link

@jaswrks jaswrks commented Jan 6, 2015

@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?

@rideralberta
Copy link
Author

@rideralberta rideralberta commented Jan 6, 2015

I’ll fire that question off to my host.

Mark


www.markmallett.com http://www.markmallett.com/

On Jan 6, 2015, at 9:48 AM, JasWSInc [Masked] FWD_7DuVeeKq@opayq.com wrote:

Preview: @rideralberta Interesting. We have not had any other reports
This email is forwarded from a MASKED EMAIL you created using DoNotTrackMe https://dnt.abine.com/help.
IF THIS IS SPAM, CLICK HERE TO BLOCK. https://dnt.abine.com/#/block_email/efc16983@opayq.com/FWD_7DuVeeKq@opayq.com

Want to shop safely and privately online? Get DoNotTrackMe Premium https://dnt.abine.com/#premium.

@rideralberta https://github.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?


Reply to this email directly or view it on GitHub #389 (comment).

@rideralberta
Copy link
Author

@rideralberta rideralberta commented Jan 7, 2015

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/

On Jan 6, 2015, at 7:46 AM, JasWSInc [Masked] FWD_mYQQgMdZ@opayq.com wrote:

Preview: > but when it tried to return me to the Admin page, it was bl
This email is forwarded from a MASKED EMAIL you created using DoNotTrackMe https://dnt.abine.com/help.
IF THIS IS SPAM, CLICK HERE TO BLOCK. https://dnt.abine.com/#/block_email/efc16983@opayq.com/FWD_mYQQgMdZ@opayq.com

Want to shop safely and privately online? Get DoNotTrackMe Premium https://dnt.abine.com/#premium.

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…

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.

Log into your site via FTP; perhaps using FileZilla http://www.youtube.com/watch?v=joXUMhr8PhU.
Delete this file: /wp-content/advanced-cache.php
Delete this directory: /wp-content/plugins/quick-cache/
Remove this line from your /wp-config.php file: define('WP_CACHE', TRUE);
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.

@raamdev
Copy link
Contributor

@raamdev raamdev commented Jan 8, 2015

@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 wp-config.php file then run the auto-update mechanism and check the wp-content/debug.log file for any errors:

define('WP_DEBUG', true); // enables debugging
define('WP_DEBUG_LOG', true); // logs messages to wp-content/debug.log
define('WP_DEBUG_DISPLAY', false); // hides debug messages from showing in the browser

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.

@raamdev
Copy link
Contributor

@raamdev raamdev commented Jan 30, 2015

The fixes applied from this issue have been released today with v150129:

  • Bug Fix (Pro): Fixed a bug where the Pro Updater would fail when FTP or SFTP details via the WordPress Dashboard are required to perform updates. Props @jaswsinc. See #389.

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).

@wpsharks wpsharks locked and limited conversation to collaborators Jan 30, 2015
@raamdev raamdev changed the title Update Failed "Update Failed" when using FTP or SFTP via WordPress Jan 30, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants