Important WP 3.0 Upgrade Instructions: PLEASE READ BEFORE UPDATING!
WPMU DEV Community
Important WP 3.0 Upgrade Instructions: PLEASE READ BEFORE UPDATING!
Staff
7011 pointsLike some sort of WPMU DEV God"Mindblowingly helpful memberLifetime member
Aaron
Lead Developer
—
17th June 2010 17:35
After more than 6 months of development, WP 3.0 is out! Many of you will be anxious to update right away, but there are some important things you should know first:
General Info
WordPress MU has been merged into regular WP, which means whether or not you need multiple blogs (sites now) you will download it from the same place (http://wordpress.org/download/). We will be updating our manuals over the coming weeks with the new installation process. For now, check out our simple upgrade guide here: How to Upgrade WPMU 2.9.2 to WordPress 3.0 in 5 Easy Steps
New Terminology
Also it is important to know that much of the terminology we were used to in WPMU has changed, so to avoid confusion here is a quick glossary:
WordPress MU -> WordPress Multisite (or "MultiSite", "MS", etc. This is WP with MultiSite enabled)
Blog -> Site (a blog that a user can signup for)
Site -> Network (a group of blogs are tied together, usually with a main blog to head them up and accept registrations. Unless you are using a special plugin a MultiSite install only has one Network)
Site Admin -> Super Admin (the super user that has access to everything in the Network)
All the admin menu's under "Super Admin" have also changed to reflect this new terminology.
Updating Plugins & Themes
Due to the vast amount of changes made in 3.0, many plugins and themes will be broken unless they are updated to work with 3.0. This is especially true for WPMU plugins and BuddyPress themes. Almost every single one will be broken if you don't update them. Luckily as a member of WPMU DEV you have an upgrades guarantee, and we have every single one of our plugins & themes compatible now!
When you update to 3.0, you will need to also update to the latest versions of all our plugins and themes! If you do not, there is a very good chance your site will be broken or even inaccessible until you do. It is also important to know that many of our 3.0 compatible plugin and theme versions WILL NOT be backwards compatible to WPMU 2.9.2 due to the vast changes between versions. If you are running 2.9.2 and want to install a plugin or theme from here you will need to go into the past versions and download an older one.
If you are doing a fresh install of WP 3.0 MultiSite there is a very important step to consider. The /wp-content/mu-plugins/ folder will no longer be created by default. Many MultiSite plugins will still need to be installed in this folder though. Simply create the /wp-content/mu-plugins/ folder if it doesn't exist and follow the regular install instructions. We will be updating our documentation to reflect this fact soon.
Final Instructions
So in summary, when updating to WP 3.0, you will also have to update all your plugins/themes, especially WPMU ones at the same time. We HIGHLY recommend setting up a test install and upgrading that first to make sure everything works before upgrading a live site. It will save you and your user's a lot of pain!
I will leave this thread open as it's a good place to ask any general upgrade questions. If your question is about a specific plugin or theme please start a new thread in the correct place.
After more than 6 months of development, WP 3.0 is out! Many of you will be anxious to update right away, but there are some important things you should know first:
General Info
WordPress MU has been merged into regular WP, which means whether or not you need multiple blogs (sites now) you will download it from the same place (http://wordpress.org/download/). We will be updating our manuals over the coming weeks with the new installation process. For now, check out our simple upgrade guide here: How to Upgrade WPMU 2.9.2 to WordPress 3.0 in 5 Easy Steps
New Terminology
Also it is important to know that much of the terminology we were used to in WPMU has changed, so to avoid confusion here is a quick glossary:
WordPress MU -> WordPress Multisite (or "MultiSite", "MS", etc. This is WP with MultiSite enabled)
Blog -> Site (a blog that a user can signup for)
Site -> Network (a group of blogs are tied together, usually with a main blog to head them up and accept registrations. Unless you are using a special plugin a MultiSite install only has one Network)
Site Admin -> Super Admin (the super user that has access to everything in the Network)
All the admin menu's under "Super Admin" have also changed to reflect this new terminology.
Updating Plugins & Themes
Due to the vast amount of changes made in 3.0, many plugins and themes will be broken unless they are updated to work with 3.0. This is especially true for WPMU plugins and BuddyPress themes. Almost every single one will be broken if you don't update them. Luckily as a member of WPMU DEV you have an upgrades guarantee, and we have every single one of our plugins & themes compatible now!
When you update to 3.0, you will need to also update to the latest versions of all our plugins and themes! If you do not, there is a very good chance your site will be broken or even inaccessible until you do. It is also important to know that many of our 3.0 compatible plugin and theme versions WILL NOT be backwards compatible to WPMU 2.9.2 due to the vast changes between versions. If you are running 2.9.2 and want to install a plugin or theme from here you will need to go into the past versions and download an older one.
If you are doing a fresh install of WP 3.0 MultiSite there is a very important step to consider. The /wp-content/mu-plugins/ folder will no longer be created by default. Many MultiSite plugins will still need to be installed in this folder though. Simply create the /wp-content/mu-plugins/ folder if it doesn't exist and follow the regular install instructions. We will be updating our documentation to reflect this fact soon.
Final Instructions
So in summary, when updating to WP 3.0, you will also have to update all your plugins/themes, especially WPMU ones at the same time. We HIGHLY recommend setting up a test install and upgrading that first to make sure everything works before upgrading a live site. It will save you and your user's a lot of pain!
I will leave this thread open as it's a good place to ask any general upgrade questions. If your question is about a specific plugin or theme please start a new thread in the correct place.
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
17th June 2010 17:56
#
Just to throw this in, I've been trying to tag all of the threads/ topics here discussing wp3.0 with the Wordpress 3.0 tag. Hopefully this way folks here can quickly find what they're looking for.
It would be a plus if folks would help out with that tagging. Not a biggie but I did want to point that out.
Thanks,
-drmike
edit: In case anyone is wondering, we're waiting for 3.0.1 :)
Is there any point at all in trying to use the automatic upgrade option or am I better going manual. I see lots of failed installs on the WP forums! I'm a bit scared but eager to upgrade.
I noticed a few plugins show an update date of 6-17-2010, but they still say compatible up to 2.9.2. Are they good to go with 3.0 if it shows today's date?
We ALWAYS recommend against using autoupgrade with WPMU. Too error prone for a WPMU site when you have users depending on you. Backup your db and files, then upgrade manually using FTP. You'll have to use FTP anyway to update your .htaccess file.
@tesla - anything updated today will be 3.0 ready, we've just yet to update the plugin pages fully.
We've been sitting waiting for 3.0 to be released, so have all made a mad rush to get the plugin updates uploaded and available (I think it took us less than an hour to get them live :) ).
Yes, they should be. We'll be changing those numbers tonight when we've finished uploading them all. Also if you click the "Other Versions" link you can see release notes, like this: http://premium.wpmudev.org/project/anti-splog/download
Had a WP.MU Install last week which was 2.9.2 and have only just started putting the site together. There has been a few bugs. Tammie has suggested perhaps a WP3 upgrade might be better for me considering I am new to WPMU and rather than learn 2.9.2 it will be better to learn 3 as it is different.
But then here you admit it may be smart to wait. I need to get this site going and am now worried about how buggy WP3 may be.
@AquaPebble: my points were mainly about terminology and also about the fact the themes you wanted to use have had large updates for wordpress 3.0 that was the big factor towards you going onto wordpress 3.0 as you haven't gone live yet against those on this thread who already have quite a bit of data set up so a bug in 3.0 would impact them perhaps more hence their caution upgrading. That being said yes you do run the risk as I have said of it being a new version.
Ultimately it's a decision you have to make my choice with what you have said and done so far would be 3.0 but it's your call. I was also responding to your query when you asked should you upgrade as you seemed interested in doing so - I never suggested first you upgrade to 3.0.
Thanks Tammie. I know your advice is good and with good intentions. I realise the choice is mine and am really torn, as I agree with your advice, but when I read here that it is smart to wait, I became concerned as I was ready to do the upgrade.
I feel I don't have enough information to make the choice, hence asking for additional advice.
@AquaPebble if I was in your situation I would upgrade to WP3, as you said, your site is new, and if you do experience any hassles it will be a good learning curve for you. :-)
Hi Aaron, I upgraded to 3.0, and the problem I'm having is that the url's are not working, because they are adding in the word "blog" into the previous blog posts url. For example, the links are now directing to:
I didn't see a show on home page option on settings - reading, but there was the option to set a static page, which I did and then set it back. That didn't work.
Then I went to the permalink structure and added a "category base" with the word "blog" and that worked...now the question is, will this mess with the other blogs that get set up?
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
19th June 2010 15:08
#
@camaran, you need to give a lot more details then that. Best bet actually would be to start with a new thread since I have a feeling that this is a general issue, not one specifically dealing with 3.0. Please be sure to give these a read:
So, is it safe to ass/u/me that all wpmudev plugins and themes are good to go as far as wp3 is concerned? Even the ones that haven't been updated a few months?
Cool. Thanx @Aaron.
I'm building a final, pre-live version of one of my projects now. I hope to be good to go as soon as a few wp3.0x fixes come down the pipe.
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
21st June 2010 13:42
#
Most likely you deleted the blogs.php file without updating the line in your htacess file.
Or the edit didn;t take due to the ownership of the file not allowing edits by your user account. The .htaccess file is created by the webserver so chances are it;s completely owned by the webserver.
I read that the all the plugins @ WPMU Dev have been updated and are 3.0 compatible. Have the install instructions been updated as well? Are plugins still uploaded to the MU folders or has that changed?
The install instructions are the same. The one exception is what I pointed out in the first post here is you may need to create the wp-content/mu-plugins/ folder as it's not included in the default WP3.0 zip file.
What is the process to upgrade 3.0? should I use the automatic upgrade or using file zilla? if I use file zilla, should I just copy the 3.0 files and replace the old version files? Also, should I upgrade the plugins first or the main site? Thanks.
@GreatAtlantic or anyone else who has an image issues after the upgrade, check your .htaccess line. You can't just change the blogs.php to ms-files.php - make sure you're also changing the directory part of the line.
won't mention why that's on my mind... /*whistles and looks innocent*/
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
24th June 2010 14:57
#
Also make sure the edit actually took hold. I know with some servers (ie CPanel) it assigns ownership to of the wp-config.php file to the webserver. While CPanel does everything as root, edits have been known to not take hold.
edit: Sorry but the best thing they could have done if they closed the old forums was to actually merge the old ones into the new ones. Now there's no past experience or "institutional intelligence" (that's not the term I'm thinking of but I can;t think of it) to draw on.
What a huge work you have with the new versión of WP :P
Well, My issue is regarding admin ads, admin messages, messages and TOS, I downloaded the new code and rewrite the plugins, but still not working just show me a 404 page and I can´t find how to fix it on the instructions.
Thanks for the link. The five steps seem easy enough indeed, but they always make it look easy!
One thing I don't see addressed is the order of things. I asked on that post if we should upgrade WP first or all the plugins. Sarah suggested doing the WP upgrade first, then plugins one at a time. We've already got all current wp plugins. Should we update all our mu-plugins first or take care of the WP upgrade first?
There will be less potential errors if you update WP first. When you are managing a complex WPMU site you should really be keeping a local copy where you can update everything (and test), then upload it all at once. SVN is great for this.
So... 3.0.1 was just released. I have a WPMU 2.9.2 install and thinking about taking the plunge. Probably will wait for the weekend. I'm actually more concerned for non WPMU DEV customized themes and such then plugin breakdowns. We'll see. Been prepping for this for awhile!
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
31st July 2010 15:19
#
Can you confirm the changes have been made to the htaccess file? Please actually check. I ask as that file is usually owned by the webserver and folks won;t be able to make modifications while logged in as their user account on many hosting platforms like CPanel even though CPanel tells you the edit was made.
Hi guys, so i'm finally starting to use the new Dev plugins with 3.0 and i realized that the mu folder was missing so i wanted to make sure that i was indeed supposed to create it and i finally found the answer in this thread.
I'm going to suggest that you add notes to the install instructions of all the updated plugins that explain that users need to create the folder with a fresh install of 3.0 because it certainly caused me some confusion and took some time to find the answer. I'm sure that others will feel the same way as you continue to grow your membership.
I am going to follow all of the instructions in all of the plugin install directions exactly and put everything where they say to. In the past i was able to use plugins by putting them in regular plugins folder for some reason. I will report any issues that i have with using this plugin folder to this thread i guess.
It says above that not all of the Dev plugins go in the /wp-content/mu-plugins folder. I think it would be nice to see a definitive list of which ones go where if at all possible.
ok so i put all of the files in the mu-plugins folder that i created and everything seems to be working fine. for the first time i noticed that there are install instructions under where we download the plugins (duh) but i also noticed that the install .txt files were not found with every plugin and the folder structures weren't always consistent. not to be nit picking hehe i just think new users would appreciate more consistency in terms of the files and install instructions included in the downloads. regards!
Responses (62)
Keeper of the Dark Chocolate — 17th June 2010 17:56 #
Just to throw this in, I've been trying to tag all of the threads/ topics here discussing wp3.0 with the Wordpress 3.0 tag. Hopefully this way folks here can quickly find what they're looking for.
It would be a plus if folks would help out with that tagging. Not a biggie but I did want to point that out.
Thanks,
-drmike
edit: In case anyone is wondering, we're waiting for 3.0.1 :)
Lead Developer — 17th June 2010 18:03 #
Same here on the 3.0.1. There will be a lot of dust to settle from this one...
Member — 17th June 2010 19:11 #
Is there any point at all in trying to use the automatic upgrade option or am I better going manual. I see lots of failed installs on the WP forums! I'm a bit scared but eager to upgrade.
Member — 17th June 2010 19:18 #
I noticed a few plugins show an update date of 6-17-2010, but they still say compatible up to 2.9.2. Are they good to go with 3.0 if it shows today's date?
Lead Developer — 17th June 2010 19:18 #
We ALWAYS recommend against using autoupgrade with WPMU. Too error prone for a WPMU site when you have users depending on you. Backup your db and files, then upgrade manually using FTP. You'll have to use FTP anyway to update your .htaccess file.
Developer — 17th June 2010 19:22 #
@tesla - anything updated today will be 3.0 ready, we've just yet to update the plugin pages fully.
We've been sitting waiting for 3.0 to be released, so have all made a mad rush to get the plugin updates uploaded and available (I think it took us less than an hour to get them live :) ).
Lead Developer — 17th June 2010 19:22 #
Yes, they should be. We'll be changing those numbers tonight when we've finished uploading them all. Also if you click the "Other Versions" link you can see release notes, like this:
http://premium.wpmudev.org/project/anti-splog/download
Member — 17th June 2010 19:25 #
Great work guys. Thanks.
Keeper of the Dark Chocolate — 17th June 2010 23:09 #
heh Looks like they're still having problems on remembering to hide the plugins page:
http://core.trac.wordpress.org/changeset/15271
;)
Member — 18th June 2010 02:32 #
Well done guys, this must have been a whole lot of work on top of everything else.
I will wait patiently for the core bugs to phase out before I do any upgrade.
THanks.
Erstwhile founder — 18th June 2010 04:09 #
I have my fingers crossed that most people will be smart enough to wait a bit.
Thanks,
Andrew
Member — 18th June 2010 04:39 #
@georgef @andrew
Sounds like sage advice. I'll wait for a bit as well.
Great work though.
Member — 18th June 2010 09:27 #
I am torn about what to do.
Had a WP.MU Install last week which was 2.9.2 and have only just started putting the site together. There has been a few bugs. Tammie has suggested perhaps a WP3 upgrade might be better for me considering I am new to WPMU and rather than learn 2.9.2 it will be better to learn 3 as it is different.
But then here you admit it may be smart to wait. I need to get this site going and am now worried about how buggy WP3 may be.
Any other advice?
Theme Designer — 18th June 2010 09:34 #
@AquaPebble: my points were mainly about terminology and also about the fact the themes you wanted to use have had large updates for wordpress 3.0 that was the big factor towards you going onto wordpress 3.0 as you haven't gone live yet against those on this thread who already have quite a bit of data set up so a bug in 3.0 would impact them perhaps more hence their caution upgrading. That being said yes you do run the risk as I have said of it being a new version.
Ultimately it's a decision you have to make my choice with what you have said and done so far would be 3.0 but it's your call. I was also responding to your query when you asked should you upgrade as you seemed interested in doing so - I never suggested first you upgrade to 3.0.
Member — 18th June 2010 09:47 #
Thanks Tammie. I know your advice is good and with good intentions. I realise the choice is mine and am really torn, as I agree with your advice, but when I read here that it is smart to wait, I became concerned as I was ready to do the upgrade.
I feel I don't have enough information to make the choice, hence asking for additional advice.
Member — 18th June 2010 10:31 #
@AquaPebble if I was in your situation I would upgrade to WP3, as you said, your site is new, and if you do experience any hassles it will be a good learning curve for you. :-)
Keeper of the Dark Chocolate — 18th June 2010 12:18 #
Just to clarify, has anyone looked at the theme pack? It still has the previous date on it:
http://premium.wpmudev.org/project/farms-133-theme-pack
edit: The Older Versions page also shows the older versions.
Member — 18th June 2010 12:53 #
Same here.
How ling will this thread remain a sticky? I'm thinking of waiting awhile.
Member — 18th June 2010 13:14 #
OK so I took the plunge and did the upgrade according to those 5 steps and it went really smoothly. Thanks for the advice (especially Tammie).
Keeper of the Dark Chocolate — 18th June 2010 15:32 #
We'll probably go through this when the next version rolls around.
I did notice though that they're gone straight to 3.1. Hopeful thinking?
http://core.trac.wordpress.org/changeset/15275
Member — 18th June 2010 15:32 #
Got to be!
Lead Developer — 18th June 2010 16:10 #
They are punting everything to 3.1. They are taking a release cycle off, so 3.1 will be at least 6 months away.
For sure there will be some 3.0.x releases, likely soon with bugs like http://core.trac.wordpress.org/changeset/15271
Member — 18th June 2010 21:24 #
Hi Aaron, I upgraded to 3.0, and the problem I'm having is that the url's are not working, because they are adding in the word "blog" into the previous blog posts url. For example, the links are now directing to:
http://modernsingleparents.net/blog/2010/03/13/creating-a-positive-co-parenting-partnership/#comment-159
When it should be:
http://modernsingleparents.net/2010/03/13/creating-a-positive-co-parenting-partnership/#comment-159
In order to work correctly. This is happening for every post and category.
How can I fix this?
Thank you!
Lead Developer — 18th June 2010 21:33 #
Check the show on home page option under settings->reading. Try changing it then back to see if it resets your permalinks.
Member — 18th June 2010 21:40 #
I didn't see a show on home page option on settings - reading, but there was the option to set a static page, which I did and then set it back. That didn't work.
Then I went to the permalink structure and added a "category base" with the word "blog" and that worked...now the question is, will this mess with the other blogs that get set up?
Thanks Aaron.
Lead Developer — 18th June 2010 21:47 #
No it shouldn't. If you don't want the /blog/ try removing it on the permalinks page again.
Member — 18th June 2010 21:49 #
You mean after I just added it, try taking it back out?
Lead Developer — 18th June 2010 22:05 #
Yes, I think it will reset your urls.
Member — 18th June 2010 22:20 #
That worked, thanks!
Member — 19th June 2010 08:37 #
in my installation the problem is character encoding.
Keeper of the Dark Chocolate — 19th June 2010 15:08 #
@camaran, you need to give a lot more details then that. Best bet actually would be to start with a new thread since I have a feeling that this is a general issue, not one specifically dealing with 3.0. Please be sure to give these a read:
http://trac.mu.wordpress.org/browser/trunk/README.txt
http://codex.wordpress.org/Debugging_WPMU
Member — 20th June 2010 00:48 #
So, is it safe to ass/u/me that all wpmudev plugins and themes are good to go as far as wp3 is concerned? Even the ones that haven't been updated a few months?
Lead Developer — 20th June 2010 05:07 #
Yes, we didn't have to update all of them.
Member — 20th June 2010 15:37 #
Cool. Thanx @Aaron.
I'm building a final, pre-live version of one of my projects now. I hope to be good to go as soon as a few wp3.0x fixes come down the pipe.
Member — 21st June 2010 06:33 #
Followed the upgrade instruction to the Tee and following the upgrade ALL USER's photos, avatars, logos and everthing is gone.
content /files/2010/06/grtatlmedia_logo.png
Lead Developer — 21st June 2010 12:48 #
Most likely you deleted the blogs.php file without updating the line in your htacess file.
Keeper of the Dark Chocolate — 21st June 2010 13:42 #
Or the edit didn;t take due to the ownership of the file not allowing edits by your user account. The .htaccess file is created by the webserver so chances are it;s completely owned by the webserver.
Member — 21st June 2010 14:37 #
I read that the all the plugins @ WPMU Dev have been updated and are 3.0 compatible. Have the install instructions been updated as well? Are plugins still uploaded to the MU folders or has that changed?
Lead Developer — 21st June 2010 15:28 #
The install instructions are the same. The one exception is what I pointed out in the first post here is you may need to create the wp-content/mu-plugins/ folder as it's not included in the default WP3.0 zip file.
Member — 22nd June 2010 20:47 #
I have 3.0 setup on a test server, however I am having the same problem I did on 2.9.2. In the "WPMU DEV" Area, I am not seeing any content. Here is my previous thread, and it looks exactly the same but with WP3.0
http://premium.wpmudev.org/forums/topic/nothing-displayed-in-wpmu-dev?replies=1#post-38622
Lead Developer — 22nd June 2010 22:19 #
Yes, there are bugs with this plugin we are working on.
Member — 23rd June 2010 06:49 #
What is the process to upgrade 3.0? should I use the automatic upgrade or using file zilla? if I use file zilla, should I just copy the 3.0 files and replace the old version files? Also, should I upgrade the plugins first or the main site? Thanks.
Lead Developer — 23rd June 2010 15:16 #
http://wpmu.org/how-to-upgrade-wpmu-2-9-2-to-wordpress-3-0-in-5-easy-steps/
I would just follow the directions, overwrite the files via FTP.
Member — 23rd June 2010 19:23 #
@GreatAtlantic or anyone else who has an image issues after the upgrade, check your .htaccess line. You can't just change the blogs.php to ms-files.php - make sure you're also changing the directory part of the line.
won't mention why that's on my mind... /*whistles and looks innocent*/
Member — 23rd June 2010 19:29 #
Got it.
Keeper of the Dark Chocolate — 24th June 2010 14:57 #
Also make sure the edit actually took hold. I know with some servers (ie CPanel) it assigns ownership to of the wp-config.php file to the webserver. While CPanel does everything as root, edits have been known to not take hold.
Keeper of the Dark Chocolate — 28th June 2010 13:29 #
The closing of the mu forums have been made official:
http://mu.wordpress.org/forums/topic/18502
Member — 28th June 2010 16:40 #
New multi site forum here.
http://wordpress.org/support/forum/14
Keeper of the Dark Chocolate — 29th June 2010 12:38 #
Fixed. :)
edit: Sorry but the best thing they could have done if they closed the old forums was to actually merge the old ones into the new ones. Now there's no past experience or "institutional intelligence" (that's not the term I'm thinking of but I can;t think of it) to draw on.
Member — 5th July 2010 23:47 #
Hi Aaron,
What a huge work you have with the new versión of WP :P
Well, My issue is regarding admin ads, admin messages, messages and TOS, I downloaded the new code and rewrite the plugins, but still not working just show me a 404 page and I can´t find how to fix it on the instructions.
how can I fixed?
Thanx.
Lead Developer — 6th July 2010 00:11 #
You mean a 404 page when you try to save the settings? That's the main symptom of the plugins NOT being updated.
Member — 7th July 2010 19:23 #
Thanks for the link. The five steps seem easy enough indeed, but they always make it look easy!
One thing I don't see addressed is the order of things. I asked on that post if we should upgrade WP first or all the plugins. Sarah suggested doing the WP upgrade first, then plugins one at a time. We've already got all current wp plugins. Should we update all our mu-plugins first or take care of the WP upgrade first?
Lead Developer — 7th July 2010 20:36 #
There will be less potential errors if you update WP first. When you are managing a complex WPMU site you should really be keeping a local copy where you can update everything (and test), then upload it all at once. SVN is great for this.
Member — 7th July 2010 20:49 #
Thanks! We hope to get everything working on our test install, so the upgrade of the live site will be quicker and smoother.
Sales & Support Lead — 30th July 2010 00:48 #
So... 3.0.1 was just released. I have a WPMU 2.9.2 install and thinking about taking the plunge. Probably will wait for the weekend. I'm actually more concerned for non WPMU DEV customized themes and such then plugin breakdowns. We'll see. Been prepping for this for awhile!
Member — 30th July 2010 06:09 #
Im right in the middle of upgrade and cross my finger
Member — 30th July 2010 06:21 #
i still get the yellow nag screen about the .htacces change that i have done!
any ideas?
Keeper of the Dark Chocolate — 31st July 2010 15:19 #
Can you confirm the changes have been made to the htaccess file? Please actually check. I ask as that file is usually owned by the webserver and folks won;t be able to make modifications while logged in as their user account on many hosting platforms like CPanel even though CPanel tells you the edit was made.
Founder & CEO — 3rd August 2010 03:06 #
FYI unsticking this now :)
Member — 8th October 2010 22:50 #
Hi guys, so i'm finally starting to use the new Dev plugins with 3.0 and i realized that the mu folder was missing so i wanted to make sure that i was indeed supposed to create it and i finally found the answer in this thread.
I'm going to suggest that you add notes to the install instructions of all the updated plugins that explain that users need to create the folder with a fresh install of 3.0 because it certainly caused me some confusion and took some time to find the answer. I'm sure that others will feel the same way as you continue to grow your membership.
I am going to follow all of the instructions in all of the plugin install directions exactly and put everything where they say to. In the past i was able to use plugins by putting them in regular plugins folder for some reason. I will report any issues that i have with using this plugin folder to this thread i guess.
It says above that not all of the Dev plugins go in the /wp-content/mu-plugins folder. I think it would be nice to see a definitive list of which ones go where if at all possible.
Thanks!
Justin
Member — 9th October 2010 04:23 #
ok so i put all of the files in the mu-plugins folder that i created and everything seems to be working fine. for the first time i noticed that there are install instructions under where we download the plugins (duh) but i also noticed that the install .txt files were not found with every plugin and the folder structures weren't always consistent. not to be nit picking hehe i just think new users would appreciate more consistency in terms of the files and install instructions included in the downloads. regards!
Justin
Lead Developer — 9th October 2010 20:05 #
Yes we are moving all docs to this site and Working on more consistency.
Become a member