Rick McKnight

@shovenose
5.2.17 is actually newer than 5.2.4,
17 > 4,
you’re getting confused by the decimals ??

@chellebelly
Arras has an issue with WP 3.2
You need to replace line 355 of /library/widgets.php from:

function Arras_Widget_Tag_Cloud() {
    $this->WP_Widget_Tag_Cloud();
}

to:

function Arras_Widget_Tag_Cloud() {
    parent::__construct();
}

View this thread for more info:
https://www.arrastheme.com/forums/topic6442-15-arras-1501-and-wordpress-32.html

@amplegreen420
Just make sure your host meets the minimum requirements BEFORE you update.

@shovenose
If you keep the entire wp-content folder you are not upgrading its contents, which may or may not have changed.
Also, if you have plugins that are not compatible with the new version you’ll be running into trouble again.
I prefer to reinstall the plugins again one by one after I’ve done the WordPres upgrade. That way I get to review their compatibility rankings, how old since their last update, etc.
I wouldn’t do it for minor upgrades, but for a major one like this one, I would definitely take all possible precautions.

Yes, it’s better to do a clean install, You can delete the old installation in the same way you installed it (Fantastico, I guess?)

If you have created any posts in the meantime, you can back them up by going to the navigation menu at the left of your WordPress admin area to the section called “Tools”. Click on the drop down menu and select “Export”. Later, when you have made the clean install, repeat the operation but choose “Import” instead. This only works for text. If you want to keep the pictures you have to make a copy of the wp-uploads folder, where all your pictures inserted in your posts and pages are.

Just a question, why do you spam us with a link to “Web Hosting Sites”, when you don’t even know the basics of web hosting?

You’re welcome, happy to know you got it fixed.

Summarizing,
1- Replace all files except for your Theme if it’s custom-made.
2- Same for any plugins you might have created or customized.
3- And do not delete wp-config.php either, because it holds your MySQL password and other details specific to your particular installation. (it does not exist in the package you are uploading, so you won’t be overwriting it. It is created during installation using wp-config-sample.php as a template)

P.S. Also keep the wp-uploads folder, where all your pictures inserted in your posts and pages are.

Of course, if you get your host to upgrade PHP to version 5.2.4 obviously the issue will go away, although you might have to reinstall WordPress 3.2

Give it a try, nothing to lose

That’s the way to go anyway, and you’ll have to do it sooner or later

PHP version: 5.2.14 won’t do.

First download WordPress 3.1.2 from this link:
https://www.ads-software.com/download/release-archive/

Unzip and upload by FTP, replacing all WordPress 3.2 files,
except of course your theme if it is a custom one.

Do not delete wp-config.php either (it does not exist in the package you are uploading, so you won’t be overwriting it)

BaileyMcC,

Don’t forget to mark the thread as “resolved”.
That way it helps other people to better identify the issue at hand.

Thanks.

Glad to have been of help,

Cheers

Turn back on the SEO plugin again.

If it doesn’t work yet, there are a couple of things to check:

1- Can you compare the URL of the page that returns the 404 with the one you can see by hovering the mouse over the title of the post/page from within the admin area?

2- What are your settings under Permalinks?

Minimum requirements for WP 3,2 are PHP version 5.2.4 and MySQL version 5.0

So yes, select PHP 5.3
And no, 5.2 does not mean 5.2.4

The older version is being offered for compatibility with older software

Do you have any SEO plugins that tweaks the permalinks?

My site went down after upgrading to WP 3.2 due to not meeting minimum requirements (PHP version 5.2.4 and MySQL version 5.0)

I know, I should have checked the “Read Me” first. Luckily I made back-ups, so no harm done.

You can find out what your PHP and MySQL version is by using the Health Check plugin

Try rolling back to WP 3.1.2

I had the same issue and got it fixed that way.

Apparently there are new PHP and MySQL requirements, so make sure you meet those before attempting to upgrade.

Minimum requirements for WordPress 3.2. are PHP version 5.2.4 and MySQL version 5.0

Theme may not be compatible with WP 3.2
Try switching Themes.

Also post at the Weaver Forum page at:
https://wpweaver.info/forum/