wpmu 2.9.2 to 3.0 pages & posts no longer work

  • After upgrading to 3.0 the main site appears fine but none of the others work. Main page on each comes up with correct theme, but pages & posts that existed are Error 404.
    Did modify .htaccess & wp.config.php per note at the end of the upgrade process. (copy/paste so not likely a typo)
    Example: This site has/had 15 pages and at least 1 post.
    https://websites.msdpt.k12.in.us/sample/
    u=sample p=letmein
    Appreciate any direction / thought you may have.

    RewriteEngine On
    RewriteBase /

    #uploaded files
    RewriteRule ^(.*/)?files/$ index.php [L]
    RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
    RewriteRule ^(.*/)?files/(.*) wp-includes/ms-files.php?file=$2 [L]

    # add a trailing slash to /wp-admin
    RewriteCond %{REQUEST_URI} ^.*/wp-admin$
    RewriteRule ^(.+)$ $1/ [R=301,L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule . – [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]

    <IfModule mod_security.c>
    <Files async-upload.php>
    SecFilterEngine Off
    SecFilterScanPOST Off
    </Files>
    </IfModule>

Viewing 6 replies - 16 through 21 (of 21 total)

  • (sub) https://webhosting.checkedbyyou.com

    Not working.

    Yeah – killed it last night trying to replace the wp-config VHOSTS define with the replacement MULTISITE_INSTALL define – threw wobblies at me about auto-fixing the database and thoroughly trashed everything.

    Wiped it, did a clean full 3.0 install and cannot get past the very initial login after install complete – it just recycles constantly back to the login screen. Not even any plugins or additional themes FTP’d up – just the base package and the installer run. Gutted that I can’t progress it.

    Ok – the login issue was a remembered login/password issue in the browser – old login had a capital initial, new one didn’t – Browser kept rewriting the login after hitting enter, so deleted the remember from the browser security list (user logins).

    Now back to an escalation of the original problem
    – under WPMU 2.9.2 subdomains worked but not posts retrieval as discussed above
    – under WPMU upgraded to 3.0MS = same as above
    – under clean WP3.0 subdomains completely fail to display (admin and public) but are in the sites list in admin
    – under 3.0 upgraded to 3.0.1 MS, subdomains have same issue as 3.0 MS clean install.

    Hosts have now admitted they don’t support wildcard subdomains, and have even gone so far as to say they refuse to support WPMU and 3.0 MS (subliminal threat to suspend account if I use it) – hosts are UnlimitedWebHosting.com – really disappointed with them over this, especially after subdomains worked on 2.9.2 without having to contact them.

    Am stuck, but VERY curious to find out why subdomains worked under 2.9.2 and 2.9.2 upgrade to 3.0 but failed under clean install and 3.0 to 3.0.1 upgrade. Guts tell me the htaccess differences between 2.9.2 and 3.0 have got a lot to do with this point – it’s the only thing that really changed config-wise on a “server side” of the install.

    Anyone else any thoughts on this?

    Get a new host, seriously.

    Also, no idea why the subdomains didn’t work – UNLESS host decided to reset something on you.

    The htaccess differences have no bearing – the wildcard subdomains are set server side with DNS records as well. It’s the only way they ever work, unless you put in manual subdomains.

    So you could tinker with the htaccess all day – if they are not set in Apache, they will never work. and your host controls apache.

    Problem is that on this host I’ve got another three years pre-paid and I want my money’s worth from them as there’s no refunds after all this time.

    However, I have been able to start getting manually set subdomains to start working now the (unbelievably slow) DNS propagation is filtering out – seriously, having a town crier walk in front of a train with a red flag would be faster for propagating the DNS than this bunch.

    They’re trying to pressure me into going with a VPS – I’m seeing and hearing a lot of reports that an increasing number of hosts are doing this where WP 3 is concerned …. I guess WordPress sites are no longer going to be cheap and fun to create.

    Thinks I need to do some reading up on Apache directives and stuff to see if there is any workarounds that can be plonked in user home directories to enable wildcards – one of my hosts said it is possible via php.ini and htaccess, but is a nightmare to initially setup.

    If you are going to be doing large or complicated setups with domain mapping and such, then yes, a VPS is recommended. even by me. ?? They come as cheap as $20-$40 a month.

    Sticking with your current host to get your money’s worth may not be worth it. especially with a switch to a new host, getting it running in considerably less time with less headache. that part SAVES you money.

    one of my hosts said it is possible via php.ini and htaccess, but is a nightmare to initially setup.

    Sorry, h’;s flat out wrong. vhosts are set by apache and can be in other files via things liek Plesk (as we’ve discussed) but there is no way either php.ini or htaccess can change that. None. And I’m telling you this before you waste hours on it. ??

    If you’d be willing to pay someone whatever it is you’ve paid for the rest of that hosting, then consider it as lesson learned and move. I know you’ve spent hours struggling with this when you haven’t needed to. trying to save you some further pain.

Viewing 6 replies - 16 through 21 (of 21 total)
  • The topic ‘wpmu 2.9.2 to 3.0 pages & posts no longer work’ is closed to new replies.