http://mu.wordpress.org/forums/ WordPress MU Forums Tag: upgrade en Wed, 25 Nov 2009 19:49:04 +0000 http://mu.wordpress.org/forums/topic/15556#post-88942 Thu, 19 Nov 2009 14:25:40 +0000 LanceGrigsby 88942@http://mu.wordpress.org/forums/ <p>OK, thanks. </p> http://mu.wordpress.org/forums/topic/14614#post-88926 Thu, 19 Nov 2009 11:14:07 +0000 gazouteast 88926@http://mu.wordpress.org/forums/ <p>I remember now - LOL</p> <p>It was in the SMF forums script, and related to the old RSS feed poster plugin over there - it had the option of a "fake" cron each time a page was loaded by a browser (or search engine crawler bot as it later turned out - talk about cyclical cause and effect) or do the stuff and use a real cron.</p> <p>The fake cron was OK during site development with just the site developer online, but by the time 2 or 3 people were on-site at the same time, it completely killed performance with number of queries per page load going through the roof.</p> <p>It was good early lesson for me about the importance of balanced scheduling of "real" cron jobs, rather than per page load crons .... dare I say - like WP-cron for example?</p> <p>Gaz </p> http://mu.wordpress.org/forums/topic/15556#post-88893 Wed, 18 Nov 2009 23:05:49 +0000 kgraeme 88893@http://mu.wordpress.org/forums/ <p>The security issues are typically with php code, so when you update the core code the security fixes are there. The update script generally just goes through and makes sure the blog's db tables match the changes. </p> http://mu.wordpress.org/forums/topic/15556#post-88889 Wed, 18 Nov 2009 22:57:38 +0000 LanceGrigsby 88889@http://mu.wordpress.org/forums/ <p>Stupid question, perhaps, but when it comes to security releases, is it better to try and upgrade every blog or wait till the user next logs in? Or in other words, are idle blogs a security risk? </p> http://mu.wordpress.org/forums/topic/15528#post-88837 Wed, 18 Nov 2009 14:35:26 +0000 pipstar 88837@http://mu.wordpress.org/forums/ <p>Cheers Andrea! Thanks for the response... </p> http://mu.wordpress.org/forums/topic/15528#post-88745 Tue, 17 Nov 2009 18:25:00 +0000 andrea_r 88745@http://mu.wordpress.org/forums/ <p>That menu item just runs any db changes against each blog. Since you already uploaded the new files, all blogs will have them. Any needed changes should get applied when the user logs in to the backend of their blog.</p> <p>Quick check: visit a user blog in the backend. there, it's done.</p> <p>I can't recall any db changes (other than minor), so you should be good. </p> http://mu.wordpress.org/forums/topic/15526#post-88741 Tue, 17 Nov 2009 18:13:24 +0000 ccolvin 88741@http://mu.wordpress.org/forums/ <p>Looks like I found what was causing the issue. We're using the Advanced Category Excluder. Seems the older version we were using doesn't work well. :D After upgrading it, the Pages are displaying properly.</p> <p>DeannaS thanks for the help... </p> http://mu.wordpress.org/forums/topic/15528#post-88739 Tue, 17 Nov 2009 18:12:29 +0000 pipstar 88739@http://mu.wordpress.org/forums/ <p>I appear to have been successful in my upgrading my files to 2.8.5.2, and the version number in the footer confirms my success at that level. The admin section and the blogs still seem to run successfully.</p> <p>So far, so good.</p> <p>However, when I try to Upgrade the blogs found under Site Admin &gt; Upgrade, the page loads for a while and then stops loading at all leaving menus but blank content. (/wp-admin/wpmu-upgrade-site.php?action=upgrade)</p> <p>I've looked at the page source and the page consistently appears to stop loading at the "Themes" section of the side menu. </p> <p><code>...&lt;div class=&#39;wp-menu-image&#39;&gt;&lt;a href=&#39;themes.php&#39;&gt;&lt;br /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;wp-menu-toggle&quot;&gt;&lt;br /&gt;&lt;/div&gt;&lt;a href=&#39;themes.php&#39; class=&quot;wp-has-submenu menu-top menu-to</code></p> <p>like above.</p> <p>Is there a way to run the blog upgrades individually and manually? And how can I check if the tables have been modified?</p> <p>Thanks for any help. My site's working, but I don't want to leave any security holes. </p> http://mu.wordpress.org/forums/topic/15526#post-88726 Tue, 17 Nov 2009 17:01:14 +0000 ccolvin 88726@http://mu.wordpress.org/forums/ <p>:D</p> <p>The upgrade was from 1.5.2 I believe. I test a test run before upgrading the main site and the test blog shows fine for these users (albeit with a little older posts). The only other recent change was an upgrade/recompile of PHP so that we have GD support for resizing images. Honestly, I'm concerned this might have more to do with it than the upgrade of WPMU. </p> <p>The post tables for these blogs are identical to the test blog tables for these posts. .htaccess files are identical as well. </p> http://mu.wordpress.org/forums/topic/15526#post-88725 Tue, 17 Nov 2009 16:39:37 +0000 DeannaS 88725@http://mu.wordpress.org/forums/ <p>Weirdness. Pages and posts are stored in the same table in the database. But, they have different meta data so that the system knows if it's a page or post.</p> <p>Question - what version were you upgrading FROM? </p> http://mu.wordpress.org/forums/topic/15526#post-88721 Tue, 17 Nov 2009 16:21:19 +0000 ccolvin 88721@http://mu.wordpress.org/forums/ <p>I recently upgraded our blogs to 2.8.5.2 and I'm having a weird issue on some of the blogs. Basically, Pages will either show all of the posts for a blog if you're signed in, or if you aren't signed in you'll get a 404 not found.<br /> <a href="http://podcasts.shelbyed.k12.al.us/ehinton/">404 Example</a><br /> <a href="http://podcasts.shelbyed.k12.al.us/rbevilacqua/about/">All Posts</a></p> <p>When looking at their Pages screen, it doesn't show just the Pages, it shows media and post info as well. (<a href="http://podcasts.shelbyed.k12.al.us/ccolvin/files/2009/11/edit_pages.png">Screenshot</a></p> <p>Now, some sites seem to work fine yet others are displaying the problems above. Does anyone have suggestions on where to start looking or how to fix? </p> http://mu.wordpress.org/forums/topic/15410#post-88348 Wed, 11 Nov 2009 19:45:14 +0000 tmoorewp 88348@http://mu.wordpress.org/forums/ <p>There's a serialized array stored in the wp_sitemeta table. Look for meta_key = 'update_core'. It checks the data in that serialized array against what is available at mu.wordpress.org twice a day, by default. </p> http://mu.wordpress.org/forums/topic/15410#post-88346 Wed, 11 Nov 2009 19:12:45 +0000 davidctaylor 88346@http://mu.wordpress.org/forums/ <p>So can we tell what version a blog is on based on some field in the database? How does the upgrade code know whether a not a blog should be upgraded? </p> http://mu.wordpress.org/forums/topic/15410#post-88340 Wed, 11 Nov 2009 17:36:36 +0000 andrea_r 88340@http://mu.wordpress.org/forums/ <p>The number not being updated doesn't correspond with the blog being updated. I have some in my own install that are 3458, yet when I check the backend, they are clearly running the latest version. </p> http://mu.wordpress.org/forums/topic/15410#post-88336 Wed, 11 Nov 2009 16:38:18 +0000 davidctaylor 88336@http://mu.wordpress.org/forums/ <p>"If the number n the db is the same as new version, then it won't upgrade that blog. "</p> <p>Ok, that is what I assumed. However, NONE of our blogs are the same as the new version yet we believe those people who have logged in are upgraded--or appear to be upgraded. The version number in the database is from 2.7 which we went to back in April. If some of those blogs have been updated (and we know they have) then why aren't at least SOME of the version numbers more current? I don't understand. </p> <p>If it works like you said it should work and since all of our blog version numbers correspond to 2.7, shouldn't EVERYONE be upgraded EVERYTIME they've logged in since April? I just don't think I follow... </p> http://mu.wordpress.org/forums/topic/15410#post-88332 Wed, 11 Nov 2009 16:07:59 +0000 andrea_r 88332@http://mu.wordpress.org/forums/ <p>I went and checked one of my installs, and they don't even all have the same number.</p> <p>MU just looks at it to compare against the current version when it does an upgrade. If the number n the db is the same as new version, then it won't upgrade that blog. If it's lower, it will.</p> <p>The actual number is almost irrelevant, as a previous issue (blogs showing they needed upgrading when they in fact did not) was fixed when we manually went in and changed this number to something arbitrary. Subsequent upgrades after that were fine. </p> http://mu.wordpress.org/forums/topic/15410#post-88327 Wed, 11 Nov 2009 14:30:16 +0000 LanceGrigsby 88327@http://mu.wordpress.org/forums/ <p>Andrea, our biggest concern is that we want to make sure we're testing upgrades from 2.8.4 to 2.8.5.2 and not something like from 2.7.1 to 2.8.5.2. Trying to avoid unexpected problems when we upgrade our production server, and if we can't clearly determine which version are users are actually on ... anyway, I suppose the widgets look right--they're drag 'n drop, if that helps. Here's a similar thread about this problem: <a href="http://mu.wordpress.org/forums/topic/9259?replies=5">http://mu.wordpress.org/forums/topic/9259?replies=5</a>. </p> http://mu.wordpress.org/forums/topic/15410#post-88326 Wed, 11 Nov 2009 13:54:25 +0000 davidctaylor 88326@http://mu.wordpress.org/forums/ <p>I work with Lance, so let me follow-up.</p> <p>Assuming he is upgraded, what problems will this incorrect version number in the database cause for future upgrades? Surely some process uses this when doing upgrades, right?</p> <p>Has anyone else experienced this bug? It appears that the last time this field was updated was when he upgraded all blogs. Once we went to the new process of upgrading as users log in, it seems that this field was never updated again. </p> http://mu.wordpress.org/forums/topic/15410#post-88298 Tue, 10 Nov 2009 23:14:54 +0000 andrea_r 88298@http://mu.wordpress.org/forums/ <p>Easiest way to check so the numbers don't confuse:</p> <p>- go to a user blog<br /> - login to the backend<br /> - look at the widgets page</p> <p>If it's the newer widgets, then yes. You are upgraded. </p> http://mu.wordpress.org/forums/topic/15410#post-88290 Tue, 10 Nov 2009 21:22:57 +0000 LanceGrigsby 88290@http://mu.wordpress.org/forums/ <p>I've got the latest MU version on my test server (2.8.5.2), and I notice that in the <code>wp_blog_versions</code> table, the <code>db_version</code> value is 11548--which is consistent with what regular WordPress db version is (at least, according to <a href="http://codex.wordpress.org/FAQ_Installation">http://codex.wordpress.org/FAQ_Installation</a>. I did a SQL query to see what my 2.8.4a production instance would show, and it's listing db_version for ALL my blogs as 9842, which according to the aforementioned link is what the verison is for 2.7. </p> <p>So that begs the question ... did my blogs ever get updated going from 2.7 to 2.8? I used the upgrade site option when we rolled out 2.7 but didn't do so when going to 2.8 because it was explained to me that all blogs would be updated when users next logged in. And didn't the upgrade site feature disappear from 2.7.1 to 2.8 and again reappear from 2.8.4a to 2.8.5? Is this because the "user login" upgrade method never worked?</p> <p>I'm confused. In any case, if someone can explain what the db_version table is used for, that would be great. I assume this is what gets checked when the application gets flagged for an upgrade ... </p> http://mu.wordpress.org/forums/topic/15281#post-87827 Wed, 04 Nov 2009 14:28:19 +0000 LanceGrigsby 87827@http://mu.wordpress.org/forums/ <p>Thanks, Andrea. </p> http://mu.wordpress.org/forums/topic/15281#post-87784 Tue, 03 Nov 2009 23:18:25 +0000 andrea_r 87784@http://mu.wordpress.org/forums/ <p>"will users still be upgraded when they next login?"</p> <p>that's what's supposed to happen, yes. </p> http://mu.wordpress.org/forums/topic/15281#post-87781 Tue, 03 Nov 2009 22:31:31 +0000 LanceGrigsby 87781@http://mu.wordpress.org/forums/ <p>Just a question ... noticed when I upgraded my test server to 2.8.5.2 today that "Upgrade Site" feature has been re-introduced (at least, I seem to remember it disappearing around 2.8.3 or something). As the admin, if I disregard that option, will users still be upgraded when they next login? I like the idea of that "Upgrade Site" option, it just seems to take several tries to get all the blogs processed--and that can get time consuming with 800 blogs. </p> http://mu.wordpress.org/forums/topic/15278#post-87775 Tue, 03 Nov 2009 21:08:32 +0000 rbigworm1506 87775@http://mu.wordpress.org/forums/ <p>Disregard</p> <p>I've solved the problem on my own. I needed to go into Settings&gt;Permalinks and simply re-save the changes and it was corrected. </p> http://mu.wordpress.org/forums/topic/15278#post-87774 Tue, 03 Nov 2009 20:57:37 +0000 rbigworm1506 87774@http://mu.wordpress.org/forums/ <p>After upgrading my website (via the web based upgrade tool) all of my secondary blogs posts (all other than ID 1) are bugged and I receive a "404 not found" error. It appears everything else is functioning as it should.</p> <p>Has anyone else came across this issue? Is there an easy fix? </p> http://mu.wordpress.org/forums/topic/15264#post-87718 Tue, 03 Nov 2009 13:05:44 +0000 tobbe_l 87718@http://mu.wordpress.org/forums/ <p>Me again: and I found the problem. And of course it was a human error: I copied two files to the wrong directory!</p> <p>RTFM ;-) </p> http://mu.wordpress.org/forums/topic/15264#post-87713 Tue, 03 Nov 2009 11:52:48 +0000 tobbe_l 87713@http://mu.wordpress.org/forums/ <p>Im trying to upgrade wpmu från 2.6 to 2.8.5.2 and having problems with it. </p> <p>Ive followed the instructions (2.6 to 2.7. Seems to be the same as for 2.8.5.2, right?)</p> <p>After upgrading I can log in too site-admin. But running the Upgrade sites doesnt work. It runs for a while and then shows two rows with titles of two of my 20 blogs. Then it stops. Neither theese two blogs or any of the other works after this procedure.</p> <p>Thanks for quick help on this one. We're kind of offline right now. </p> http://mu.wordpress.org/forums/topic/14614#post-87651 Mon, 02 Nov 2009 16:05:50 +0000 gazouteast 87651@http://mu.wordpress.org/forums/ <p>aaargh - you're going to keep me awake all night now - the cron v each page load issue related to something I did a couple of years back and I can't for the life of me remember what it was now - but it sure made a heck of a performance difference, I remember that much - but can't even remember which script it was for. Dammit - that'll bug me all night now.</p> <p>LOL - who said senility is a gradual process? </p> http://mu.wordpress.org/forums/topic/14614#post-87393 Fri, 30 Oct 2009 00:09:43 +0000 kgraeme 87393@http://mu.wordpress.org/forums/ <p>Cool, even before you quoted that bit I was thinking a daily cron job might be a better way to go. Let us know how it goes if you do change it. There have been several threads about slow backend after upgrade lately so it would be good to identify a known culprit. </p> http://mu.wordpress.org/forums/topic/14614#post-87365 Thu, 29 Oct 2009 19:26:14 +0000 tomaltman 87365@http://mu.wordpress.org/forums/ <p>Yea - it tells you in the fine print...but one of our data team made an adjustment, which it turn caused it to reload after each post was edited.</p> <p>From the dev site:<br /> • Enable manual sitemap building via GET Request<br /> This option allows you to refresh your sitemap using a special URL which is displayed when you click on the "[?]" sign. This url can be used with a cron job for example which refreshed the sitemap every day or every hour. <strong>This mode is preferred if you have thousands of post and the automatic building needs to long.<br /> </strong> </p>