Upgrading WPMU to WordPress 3.0
-
Good afternoon, all. I was wondering if anyone could help me out with this issue. I followed the tutorials for setting up a Nginx server and the tutorials for Wordpress and they work great. But when I try to upgrade to Wordpress 3.0 multisite, I have an issue. The issue I have is that the dashboard widgets don't load because javascript is not responding around the whole site, so the install becomes unusable and then I have to downgrade back to 2.9.2. Has anyone else ran into this issue or know why I would have this issue? Also, for background info, I don't do the automatic upgrade nor do I use the svn, I upgrade with ftp, I have directory structure of /home/parkerj/public_html with user and group as parkerj:www-data. I look forward to hearing from you. Thank you.
Posted 1 year ago # -
cdroo
MemberHi Joshua,
There's some painful changes in the structure of WP3 from WP 2.9.x - most especially in regards to MU to the 3.0 multisite. I too have had some issues, am hoping the new scripts may address this. Will be doing an clean install on a VPS tonight. Will let you know how it goes. My guess as to what's ailing your install is permissions. It's possible the WP java (wp-includes directory files) where they need to be marked as executable are not marked as such.
Posted 1 year ago # -
cdroo
MemberHi Joshua,
OK. Installed a new system on a clean VPS with Guv's updated stack scripts. Top Cat + the WP stack. Upgraded it to multi-site and applied a reworked NGinX sites config. It works flawlessly. I forwarded the config to the Guv', so I won't jump the gun and let his keen eye peruse the changes. I'm pretty sure he will have some suggestions for you that will assist.
Personally, given the changes inside WP 3 a clean install on another VPS image isn't a bad idea if it's logistically reasonable to consider. YMMV.
Best
Scott
Posted 1 year ago # -
Hi Joshua .. bit odd huh, I'd have thought the Automattic's would have tested this.
I suspect you wouldn't be the only one with this issue so take a peek at the WP forums.
Failing an answer, this would work, but I would say is a last resort just because it shouldn't be necessary.
- launch the WP stack, call the domain mysite2.com .. note the 2, or mysiteNEW.com or whatever .. use a *new* database
- copy over the theme, any uploads and plugins
- access the new site using the "hosts" file trick .. see the tut "how to move a site or blog" for how to do that
- backup yoursite.com original db, to be safe (see tut .. mysqldump)
- go into wp-config.php and change the db details to use your live one.
- when the new site looks identical to the old one with the same functionality and those widgets working, change the *original site's* virtual host settings to reflect the new public_html/mysite2.com path
- remove your "hosts" file hack so you're seeing the right site, delete the *new* database a the *new* virtual host file.Thassit.
This is not ideal .. but it may be the quickest remedy in your situation. Very odd though.
Posted 1 year ago # -
@the_guv, thanks I will try that out. But before I do, I have a question for you. I am using an nginx WordPress plugin. Do you think when I upgrade to WP 3.0 that this plugin might be what is giving me issues: http://wordpress.org/extend/plugins/nginx-compatibility/ when I upgrade? Furthermore, my vhost is not set the way that this plugin recommends as well. Thanks for your help.
Posted 1 year ago # -
@the_guv, so my issue is that my uploads and images are missing. Below is what's in my vhost files. Can you tell me what is wrong with my rewrite rules? Thanks.
server { listen 174.142.142.92:80; server_name _ 5pt.us *.5pt.us; access_log /home/parkerj/public_html/5pt.us/log/access.log; error_log /home/parkerj/public_html/5pt.us/log/error.log; # Set this to off if you're hosting more than one site server_name_in_redirect off; location / { try_files $uri $uri/ @wordpress; root /home/parkerj/public_html/5pt.us/public/; index index.php index.html; client_max_body_size 10M; client_body_buffer_size 128K; #rewrite ^.*/files/(.*) /wp-content/blogs.php?file=$1; rewrite ^.*/files/(.*)$ /wp-includes/ms-files.php?file=$1 last; if (!-e $request_filename) { rewrite ^.+/?(/wp-.*) $1 last; rewrite ^.+/?(/.*\.php)$ $1 last; rewrite ^ /index.php last; #rewrite ^(.+)$ /index.php?q=$1 last; } } location @wordpress { fastcgi_pass 127.0.0.1:9000; fastcgi_param SCRIPT_FILENAME /home/parkerj/public_html/5pt.us/public/$fastcgi_script_name; include /usr/local/nginx/conf/fastcgi_params; fastcgi_param SCRIPT_NAME /index.php; } location ~* ^.+\.(html|jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|doc|xls|exe|pdf|ppt|txt|tar|mid|midi|wav|bmp|rtf|js)$ { root /home/parkerj/public_html/5pt.us/public/; rewrite ^/.*(/wp-.*/.*\.(html|jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|doc|xls|exe|pdf|ppt|txt|tar|mid|midi|wav|bmp|rtf|js))$ $1 last; rewrite ^.*/files/(.*(html|jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|doc|xls|exe|pdf|ppt|txt|tar|mid|midi|wav|bmp|rtf|js))$/wp-includes/ms-files.php?file=$1 last; } # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000 #location ~ \.php$ location ~ wp\-.*\.php|wp\-admin|\.php$ { try_files $uri @wordpress; #rewrite ^/.*(/wp-.*/.*.php)$ $1; fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; include /usr/local/nginx/conf/fastcgi_params; fastcgi_param SCRIPT_FILENAME /home/parkerj/public_html/5pt.us/public/$fastcgi_script_name; } }Posted 1 year ago # -
Joshua .. truth is, I'm knackered .. been up 48 hours straight .. but take a look at the new WP tuts, they may shed some light. You've got a lot going on there though ..
Posted 1 year ago # -
hi Joshua .. that's intentional, it's because otherwise Linux thinks that'sa variable to parse. look at the lines beneath the vhost and you'll see a bunch of "sed" commands replacing various strings with variables, and replacing fastcgi_script_name for $fastcgi_script_name.
I would recommend productions sites to launch WP3 fresh, rather than try to upgrade .. test the lot and export/import data when functions are working.
there are quite a few changes as cdroo says. not the smoothest transition from 2.9 to 3, for sure.
Posted 1 year ago # -
@the_guv, I will give it a go when I have more time and I will try to do a fresh install. I think the most frustrating thing for me is that I moved this site from a server where it was working. Granted there are some differences. The previous server had apache and once I installed nginx, I stopped apache and secondly the previous server has PDO_MYSQL while the new one has MYSQLi. But I don't think any of those differences matter unless it is the way mysql is setup but I seriously doubt it. I will try a new install on a new site and see what I come up with. Thanks again for all your help.
Posted 1 year ago # -
Those elements, from the point of view of your LEMP setup, should work fine, unless WP wants something new but I would doubt that .. it would be a silly move from Automattic to require every server to be tweaked, after all.
I wonder if this is:-
* a permissions issue (shouldn't be tho) .. try:-
wpupgrade, revert with wpsafe after
* a plugin incompatible with WP3 (there are *many* of them) .. try disabling all plugins, activate one at a time, testing testing
* WP3 incompatible theme .. having tested plugins first, set your theme to the default .. any joy? If so, you will need to comb the code of your theme, of course. Bear in mind that some previously acceptable PHP variables may now either not be allowed, else new WP PHP may somehow be conflicting (whether with plugins or theme) ..
From what I have heard it is likely there are a number of 'anomalies' with WP3, which without having digged into the code I would guess is radically different to cope with the MU integration.
.. are there similar cases on the wordpress.org forums?
I would Google things like "wordpress 3 incompatible theme" as well to see what shows up.
Your fresh install is the first essential step, Joshua. Let me know what the above turns up.
Posted 1 year ago # -
@the_guv, thanks again for your help. Unfortunately, no plugins are installed and only the main theme is installed and activated. I have checked the Wordpress forums, and I have done and indepth google search and nothing comes up showing any else having an issue like I have. So, maybe it is a permissions thing but I've used parkerj:www-data and www-data:www-data and still no go. I have tried everything you suggested, and I still can't get it to work. Maybe I should wait for 3.1
Posted 1 year ago # -
it must be your theme Joshua .. some conflicting code .. it isn't WP3, because everything works out of the box.
.. unless we're both missing something here.
Posted 1 year ago # -
@the_guv, I don't think it's the theme since both sites that I've tried were using different themes and the new install is using the standard theme. Even when I try to install a plugin or theme via the backend, I get a "502 Bad Gateway" error. Does this tell us something?
Posted 1 year ago # -
I've actually gotten a little further, but the dashboard widgets don't load and some of the pages don't load fully. Also, this is what I see in my error log:
2010/07/26 22:42:13 [error] 2443#0: *7 readv() failed (104: Connection reset by peer) while reading upstream, client: 71.233.150.173, server: _, request: "GET /wp-admin/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "joshparker.us"
Posted 1 year ago # -
well, bless my ol' cottons
.. ruddy Suhosin, after all that.
I'll be relooking at the patch for an upcoming couple of PHP tuts, Joshua.
Posted 1 year ago #
Reply
You must log in to post.
Want HTML?
a blockquote code em strong ul ol liPlace code between backticks `codeHere`
You've got it.