davek0974

That code is not good, various Google replies explain why, better to install a good revision control plugin instead.

The fix is here

upgrade fix

The fix for the update issue is here

Fix for uprgrade turned all pages into posts bug

@gofe – all three sites updated and running the latest WP version (4.2.1)
Many thanks.

@gofe – IT WORKS, well, at least it worked on my test site, it’s now happily running v4.2.1 at last. I have no idea what those changes did but wow! Thanks for that ??

Going to my live site now….

Ok, just got in and got your message gofe, thanks

Before I try it, how do you clean up revisions??

@gofe the db option table shows “initial version = 30133” but my version.php file does not have that line in it, I will add it and try later to upgrade, thanks

I too am having this exact issue and also I migrated FROM 1and1 to TSOhost but the problem seems to have migrated too. I am locked at version 4.1.1 and any upgrade trashes the content and media into posts.

If I can find anything out, i will let you know, this is most intriguing and frustrating.

The same fault as here I think
media-library-disappears-after-update-to-412

nope, nothing in that section about upgrades turning all content to posts?????

I have spent all day searching google on this and after a few hours on top of that dabbling within the damaged site database I can confirm that this mess has been caused by the update updating the “posts” table in the database and setting ALL post types to “post” and not “page” etc.

I edited a couple of lines that seemed related to my home page and the WP admin panel now reports 1 page and xxxx posts, the page is also editable again although the media is still missing.

Now we need to know what stage of the update is altering the “posts” table and why??????

Surely this must mean something to someone????

i cant see anything in that sticky related to “update turned all pages into posts”??????

the last post in that thread is out of date, it shows

/**
* Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema.
*
* @global int $wp_db_version
*/
$wp_db_version = 25824

/**

but newer versions of WP don’t seem to use wp_db_version any more.

Its hard to restore to 4.11 as WP updates instantly.

I had the same issue, still suffering and i’m currently locked to WP4.1.1

Heres the fix…

get your backup of 4.1.1. site and edit the wp-config.php file, add this at the end

define( ‘WP_AUTO_UPDATE_CORE’, false );

that will block the update from happening on restore

then you can restore your site and it should be ok running in the working 4.1.1 like mine are.

next you need to install an update control plugin so you are in control of things, block all updates then remove that line from your wp-config file.

then setup a subdomain test site which is a mirror copy of your main site, apply all updates here first – if it fails like 4.1.2 and 4.2 have then you lose nothing, just reinstall the test site for future tests.

easy peasy once you know, took me a week with three sites down to discover it though

good luck

edit – i was typing when you figured it out, might come in useful though ??

anyone ??