Opened 15 years ago
Closed 14 years ago
#11135 closed defect (bug) (worksforme)
Problem with automatic upgrade - works only once
Reported by: | pavelevap | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.8.5 |
Component: | Upgrade/Install | Keywords: | |
Focuses: | Cc: |
Description
I encounter following problem on some websites:
There were problems with upgrade, so I asked for safe_mode=off.
There were still problems:
Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/tmp//wordpress-2.8.6.zip) is not within the allowed path(s): (/home/www/alan-grey-page.cz:/usr/local/lib/php) in /home/www/alan-grey-page.cz/subdomains/www/wp-includes/functions.php on line 2118 Warning: touch() [function.touch]: open_basedir restriction in effect. File(/tmp/wordpress-2.8.6.zip) is not within the allowed path(s): (/home/www/alan-grey-page.cz:/usr/local/lib/php) in /home/www/alan-grey-page.cz/subdomains/www/wp-admin/includes/file.php on line 175
So, I added following to wp-config.php:
define('FS_METHOD', 'direct'); define('WP_TEMP_DIR', ini_get('upload_tmp_dir'));
And there was following error:
Could not create directory: /home/www/alan-grey-page.cz/subdomains/www/wp-content/upgrade
In the end, I added only following line to wp-config.php (I had to insert FTP password manually during upgrade):
define('WP_TEMP_DIR', ini_get('upload_tmp_dir'));
And everything worked! Great. But.. When I tried to reinstall it once again, there was following error:
Could not copy file: /subdomains/www/wp-content/upgrade/wordpress-2.8.6/wordpress/wp-comments-post.php
And there is a folder "upgrade" (CHMOD 0755) in wp-content with all unzipped WordPress files. So, I deleted the whole upgrade folder and automatic upgrade works again. But only once, then I had to delete upgrade folder with its content. Strange. Any help? Thank you...
Change History (2)
#2
@
14 years ago
- Milestone Future Release deleted
- Resolution set to worksforme
- Status changed from new to closed
I'm closing this for 2 reasons: Primarily, I believe this is a combination of a few fixed bugs, and server configuration issues (which may have also been worked around).
Closing as worksforme; Please create a new ticket for any new issues.
No patch.