penfil

I’m going to mark this “resolved” even though the problem really isn’t resolved… Not much the community can do to help at this point, so no sense in keeping this in limbo.

Thanks guys for all your help.

@wpsec – You make a great point. I guess I don’t have much else of an option at this point. I guess I was just getting spoiled with that feature when updating some other peoples blogs for them… manual it is.

If they tested for compatibility first as you mentioned, at least then they could allow a link to the actual plugin repository page for the plugin in need of an upgrade. Have to go search for it manually to download it now, can’t even click on the link to it as it’s only setup for the auto-update.

Well thanks for your help.

@samboll – Thank you for the link. I read it and it all makes much more sense now. It looks like unless I can find a work around, I’m just out of luck. This webhost is really not very friendly or helpful.

Thanks again.

If anyone knows a way around this, I’d be happy to know. Meanwhile I’ll be wasting my time on the phone with a tech support who pretty much refuses to budge.

Check your wp-config.php file… Make sure all your DB settings are correct.

Also make sure you correctly changed the special keys too match the ones you had in the 2.0 config.

Can you go to your homepage and see all of your posts and/or pages?

@samboll – Are you kidding me?! I have called them before… Several times… They will not help with anything that is not specifically included with their “scripts” package. Since I installed WordPress 2.7 on my own (since they don’t offer it), they will not help with anything.

They had a server problem with .htaccess files and I called about that and I had to call 3 times just to speak to a manager so he would “look into it” and miraculously it was fixed the same hour (without any admission of fault on their part).

Isn’t there some other way I can get the auto-update to work without using the php.ini defined temp directory? Even if it requires hacking a few additional WP files… I can handle that… Just need to know what I’m looking for.

@samboll

I already tried the second function you listed:
define('WP_TEMP_DIR', ini_get('upload_tmp_dir'));

The results are listed in my original post.

As for the first command you suggested:
define('WP_TEMP_DIR','/tmp');

I get even more errors, as follows:

Warning: touch(): open_basedir restriction in effect. File(/tmp/1233258421) is not within the allowed path(s): (/usr/local/pem/vhosts/154599) in /usr/local/pem/vhosts/154599/webspace/httpdocs/wordpress/wp-admin/includes/file.php on line 174
Warning: fileowner(): open_basedir restriction in effect. File(/tmp/1233258421) is not within the allowed path(s): (/usr/local/pem/vhosts/154599) in /usr/local/pem/vhosts/154599/webspace/httpdocs/wordpress/wp-admin/includes/file.php on line 628
Warning: unlink(): open_basedir restriction in effect. File(/tmp/1233258421) is not within the allowed path(s): (/usr/local/pem/vhosts/154599) in /usr/local/pem/vhosts/154599/webspace/httpdocs/wordpress/wp-admin/includes/file.php on line 630
Warning: touch(): open_basedir restriction in effect. File(/tmp/1233258421) is not within the allowed path(s): (/usr/local/pem/vhosts/154599) in /usr/local/pem/vhosts/154599/webspace/httpdocs/wordpress/wp-admin/includes/file.php on line 174
Warning: fileowner(): open_basedir restriction in effect. File(/tmp/1233258421) is not within the allowed path(s): (/usr/local/pem/vhosts/154599) in /usr/local/pem/vhosts/154599/webspace/httpdocs/wordpress/wp-admin/includes/file.php on line 628
Warning: unlink(): open_basedir restriction in effect. File(/tmp/1233258421) is not within the allowed path(s): (/usr/local/pem/vhosts/154599) in /usr/local/pem/vhosts/154599/webspace/httpdocs/wordpress/wp-admin/includes/file.php on line 630 

AND

Warning: ftp_rawlist(): open_basedir restriction in effect. File(/tmp) is not within the allowed path(s): (/usr/local/pem/vhosts/154599) in /usr/local/pem/vhosts/154599/webspace/httpdocs/wordpress/wp-admin/includes/class-wp-filesystem-ftpext.php on line 203
Warning: ftp_rawlist(): Unable to create temporary file. Check permissions in temporary files directory. in /usr/local/pem/vhosts/154599/webspace/httpdocs/wordpress/wp-admin/includes/class-wp-filesystem-ftpext.php on line 203

And yes, I did go as far as to create the tmp directory and give it the appropriate permissions.

I think the problem is that the webhost (AllDomains) did not properly set up a tmp dir for this account, or something in the php.ini is wrong… But I don’t know how to fix it… or bypass it…

Any other suggestions? Anyone?

I guess a simple “Chill out” would have been appropriate here. It was just the webhost having issues with their db server apparently. I called tech support (who in the past has been worthless to me) and they were very helpful (for once)!

Also worth noting is that I cannot access Gallery2 either. WP and G2 share the same DB… So my guess is there is a problem there.

Is it possible the webhost could be blocking access to the DB? How can I resolve this? I’m fairly new to DB admin.

No one has a clue huh? I tried getting more specific details about the error… but nothing…

I deleted all of the plugins from the webhost hoping perhaps it was a plugin issue, but that didn’t make a bit of a difference…

No one has a clue huh?

yes… As far as I can tell nothing has changed in it…

Also, I was able to access the blog yesterday. The only thing I did differently was I uploaded a new plugin via FTP but I tried removing it and it didn’t make a difference… I never even activated the plugin…

Thanks to moshu and Otto42 for your help.

I set the necessary file permissions to 777 (although I’m still a bit uneasy about it) and it works.

Now the only problem I have is that I am still not able to keep the .htaccess on the server. For whatever reason it is removed within seconds of uploading it. *shrugs* so much for permilinks.

@otto42 – Regarding 777 permissions you said:

This does not necessarily open you up to hacking, though. It would allow anybody else with access to that server to write to that directory, but they’d have to gain access to it first.

I’m still a little new to the server administration, so how exactly would one get access to it? If a parent director had a more restrictive permission set, say 755, would that prevent them from getting access to the child directory? It doesn’t seem that it would as the parent would be readable. If you could help clarify I’d appreciate it.

Also, what about the .htaccess file, what would cause that not to function properly. Since my boss intends to use this blog for business purposes, it would be nice to have permilinks enabled.

Thanks.

@moshu – OK, I switched to 777 just to import and then back to 775. It worked for the import. However I still will not be able to make any changes to the themes or to upload any images through WP.

You mentioned that what permissions are needed depend on the host. That is what I thought as well. That is why I contacted the web-host to figure out why I cannot get proper access because I believe it is something on their end. But they are not willing to help. I still cannot get a .htaccess either.