skinsch
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Unable to locate WordPress Plugin directory. ftp_base not working?Yea, same here. Appears that the FTP_BASE is not working. WordPress does not automatically use that defined variable as a base directory before it makes changes to the install.
Forum: Themes and Templates
In reply to: [Mountain Creek] SlideshowWhat “Slide Show” plugin is this on the backend? Provide reference or link. Very vague in your description.
Thanks.
Forum: Fixing WordPress
In reply to: WP 3.5 error in login to admin panel because media.phpI’m putting this note here for myself and anyone else who is still struggling with this as every time I encounter this issue and Google it, I find this post.. lol
Anyway, I wrote a basic upgrade script that does the manual upgrade of WordPress to the latest version automatically and hopefully without errors.
This issue the OP references is definitely a core problem. If you’re still getting this error after trying this (/tmp/wordpress is the extracted latest version of WordPress location):
rm -r /your/path/to/website.com/wp-includes rm -r /your/path/to/website.com/wp-admin cp -pr /tmp/wordpress/wp-includes /your/path/to/website.com/ cp -pr /tmp/wordpress/wp-admin /your/path/to/website.com/
… then make sure you not only remove the wp-includes & wp-admin directories (replacing them with the latest WordPress version), but also try copying over all the files in the root of your installation.
In other words.. after you extract the upgrade somewhere (/tmp/wordpress) copy out the root files in there as well, not just the wp-includes and wp-admin:
cp /tmp/wordpress/* /your/path/to/website.com/
That has resolved most of those issues for me in regards to the “Fatal error: Call to a member function register_handler() on a non-object in media.php on line” issue.
Forum: Installing WordPress
In reply to: Interesting “Location” header redirectiain010100 – I don’t get the “Redirect Loop”.
Otto42 – In the Settings->General screen, they are both set to the same exact URL, fully qualified and no sub-directories, etc.. i.e. https://www.SomDomain.tld
I believe I isolated this down to 1 of 2 different internal Proxy servers, so the “hanging” issue may be resolved by that… BUT, the other question is why does the Location bar show the host.domain.tld again?