WordPress 6.0 upgrade mostly failed

  • Resolved redraider90

    (@redraider90)


    3 years, 11 months ago

    Hi WP community,

    I tried twice to do the upgrade but it was mostly a fail. I say mostly because the widgets and menu pages stayed in tact. Those actually work. I’m not sure why. But I get 404s on every other portion of the site, though the links and nav links remained in tact also. The other weird thing is that the old Yoko theme remained on the admin section while some new theme went to the home page. And I can apply with preview new themes and they will work on the first page, but nowhere else. Now, I did back up all of my wp-* dirs: admin, content and includes. But does that get me anything? I have rolled it back once, and would like to prevent that again if possible, but I thought this might be a short downtime for the site.

    I read the Read this First verbiage and followed that. I deactivated the plugins prior to the upgrade and also copied over the then current wp- folders to a different directory, a tmp dir. I also backed up htaccess file and recopied the contents into the new root one, under Site (WP root).
    Any ideas where I could find these slug pages or how I can restore them? I think it would be working great if I can get that solved!

    Any help is appreciated!

    Thanks,
    RR90

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Moderator t-p

    (@t-p)

    3 years, 11 months ago

    try reviewing this: How to fix 404 error when using Pretty Permalinks?

    Thread Starter redraider90

    (@redraider90)

    3 years, 11 months ago

    Well, I tried the permalinks recommendation but this whole thing was pretty much a fail and I had to roll it back. At first I could get the home page and one other to work. The rest of the nav links failed and would give 404s. The IT tech support guy was very nice and tried to help but he claimed the DB was corrupted and tried to upsell me on SiteLock, which if I had a corrupted DB I should have been having ongoing problems and I really haven’t. It’s just the upgrade has again not worked. I deactivated all of the plugins. Oh, the advanced cron manager upon one restoration was failed, and one support person got that working as it was activated but she deactivated to get it up and going after a roll back. Bottom line, I’m open to suggestions but this is not working. Side note: the first IT support guy at the web host tried to upgrade to 5.9 instead of 6 after the first fail.

    Any help is welcomed.

    Thanks,
    RR90

    Thread Starter redraider90

    (@redraider90)

    3 years, 11 months ago

    I did find ONE BIG discovery on this, and I am not sure how to fix it.
    If I click on my permalinks link, it messed up the site and causes PHP files to start being downloaded.
    But what happens is it alters the htaccess file in the root to look like the following:

    
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /Site/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /Site/index.php [L]
</IfModule>

# php -- BEGIN cPanel-generated handler, do not edit
# Set the “ea-php74” package as the default “PHP” programming language.
<IfModule mime_module>
  AddHandler application/x-httpd-ea-php74___lsphp .php .php7 .phtml
</IfModule>
# php -- END cPanel-generated handler, do not edit

<strong># BEGIN WordPress
AddHandler application/php-56 .php
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /Site/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /Site/index.php [L]</strong>
</IfModule>

# END WordPress

    That last part in bold (Between the strong tags) gets added, and should not be there. Any way to work around that?

    BTW, addendum: I tried this recommendation in full
    https://themanifest.com/web-design/blog/how-to-fix-broken-permalinks-wordpress#:~:text=You%20can%20fix%20broken%20permalinks,issues%20on%20a%20WordPress%20site.
    and it was not successful! I deactivated all plugins and tried resetting permalinks and it continues to break the site and add that 5.6PHP reference in the wrong place. Any ideas here?

    • This reply was modified 3 years, 11 months ago by redraider90.
    • This reply was modified 3 years, 11 months ago by redraider90.
    Thread Starter redraider90

    (@redraider90)

    3 years, 11 months ago

    OMG! I think I stumbled across the fix on anoother site!

    https://theme.co/forum/t/updating-permalinks-breaks-site-with-strange-code-in-htaccess/4619

    THIS seems to have the answer. After I deleted this file or rather renamed it, the problem stopped!

    I wonder if I can now commence with this upgrade!

    Thread Starter redraider90

    (@redraider90)

    3 years, 11 months ago

    WELL GUESS WHAT!! MISSION ACCOMPLISHED! I got this done. I will say that the permalinks issue was not entirely inconsequential or irrelevant. It partially was.

    But that part about the Endurance Page Cache was the main thing. How that guy ever figured that out I have no idea, but I am indebted. I will put down my small doco for this approach that worked. There have to be scads of others having this issue.

    1) Backed up and rewrote htaccess file at the root WP level.
    2) changed the endurance page cache file name — giving it a bogus ext in the wp-content root.
    3) deactivated all the plugins
    4) commenced with the WP 6 install, successfully no less.

    After which, I have one by one reinstalled and activated my plugins. I had one acting up, causing the download issue of PHP files on one sole link! In a Paid Subscription plugin for payments. I got that fixed though.

    I am now updating themes, plugins and the like that have been sidelined for 4 years now. Even applying a long overdue bootstrap theme to this site!

    Thanks, folks!

    Moderator t-p

    (@t-p)

    3 years, 11 months ago

    Glad its sorted 🙂

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘WordPress 6.0 upgrade mostly failed’ is closed to new replies.