JohnP
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: 3.8 update hangs on "Unpacking the update"The manual upgrade worked OK, thanks esmi.
Forum: Plugins
In reply to: [Amazon S3 Uploads] Fatal Error in version 1.9.1Thanks for this atvdev – I’ll harass my web-host.
Forum: Plugins
In reply to: [Amazon S3 Uploads] Fatal Error in version 1.9.15.2.5
Forum: Plugins
In reply to: [Meteor Slides] Excerpt does not display on slideUpdate:
It turns out to be a conflict with an old plugin called: “Thumbnail for Excerpts”.
Forum: Plugins
In reply to: [BackUpWordPress] mysqldump: Got error: 1044Thanks Tom
I ran a complete database optimization and repair from PHP MyAdmin, but I still get the same error.
I then used the wp-config method you suggested which reports that 11 of my 20 tables are okay and optimized. I presume this script only repairs the core WP tables.
But the error: 1044 remains.
Forum: Plugins
In reply to: [BackUpWordPress] Backup is only 10% of databaseThat sure is an impressive response time, Tom.
And to a dumb question; yes, when I download and un-zip the backup file it ends up the size I expected.
Sorry for the unnecessary noise.
Yes, it is a standard install, with WP in the root directory.
I can see an index file in the temp directory at this URL:
example.com/wp-content/wpcf7_captchaI’m seeing a similar issue that is probably connected.
I’m usually logged in to a client’s site as Admin; not using my own FB identity.
Suddenly, for no obvious reason I get logged out, and I see the Register page with my FB details pre-populated. Clicking the “Log-in” link simply re-loads the Register page, as does entering the login url directly.
The only solution is to log out of Facebook; I can then access the normal wp-login page.
I can then log back into Facebook and all is well.
Good luck with finding a better solution.
Thanks for your response Frederick.
FYI, the plugin wrote the additions to .htaccess during installation, so you might want to tell people to do it manually if they have other directives there.
If there is anything in the instructions about this, I didn’t find them.
That’s not the cause shortster, I don’t use this.
The address of the cached file shows with nothing in .htaccess except the standard WordPress permalinks re-write and the w3 Total Cache code.
I don’t want people linking to the cached file, or for Search Engines to index those links, so I’ve de-activated the plugin.
I see people are having problems with many of the other caching methods used by w3 Total Cache as well, looks like it isn’t compatible with the latest WP version.
I have users reporting the same problem; using WP 3.1.1 and LCP 2.0b1
If something redundant such as: ” &ref=rss ” is added after the final digit, the preview works properly again.
As Otto explains here, the answer is try, try, and try again!
Forum: Themes and Templates
In reply to: Theme has disabled toggling in wp-adminI’ve run into this on two sites since updating to 2.8, with the default theme as well as others – but only with Firefox. Other browsers worked fine.
Turned out in both cases to be FF version 3.1. and upgrading to 3.5 solved the problem.
Can you tell us what browser you using, and if it works when you test an alternative?
Forum: Fixing WordPress
In reply to: No RSS – XML parsing errorThis quick fix worked for me
Added this line to .htaccess:
AddType x-mapp-php5 .php
Long version – I had this problem on a fresh 2.8 install, default theme, no plugins – tried replacing all core files and checked all the likely suspects for whitespaces.
So I tried installing wejnswpwhitespacefix.php and in the process used this line in my .htaccess to force php5:
AddHandler application/x-httpd-php5 .phpThis fixed the error, but both feeds were now blank. I unistalled Wejn’s script, and the feed was still blank, so I tried the alternative php5 switch, and found everything was working sweet!
Forum: Fixing WordPress
In reply to: Upgraded to WP 2.6 and can’t access wp-admin areaIf you are stuck in the “Please Log in again” loop and unable to access the admin area, try visiting this address, (with your blog URL replacing example.com):
http://example.com/wp-login.php?action=logout
On sites with lots of registered users, I have added this instruction to wp-login.php and it seems to be solving the problem.