No more “next page”

Just for clarification:
Are we talking here about the next/prev posts navigation?
or, about the case when a single posts is too long and the “next page” tag is included to break it in multipe webpages?

(this latter one has two versions and one seem to be deprecated: https://codex.www.ads-software.com/Template_Tags/link_pages)

I wish you could read this before upgrade:
https://www.transycan.net/blogtest/2007/01/24/to-upgrade-or-not-to-upgrade-to-wp-21/

Well, I wish I had read that, too. I have so many broken sites it’s not even funny.

Can I downgrade????? Back to 2.0.6??? I never even upgraded to 2.0.7 …..

I am SO upset over this. Can I simply just download 2.0.7 and overwrite all the files in 2.1?? Will this fix this issue?

By itself it will not.
I hope you have database backups made before the upgrade to 2.1.
If you have, then simply upload the 2.0.7 files and restore the old database. The DB backup is crucial since the DB structure has been changed.

I have backups from the WP Backup Plugin which contains the db.

I never upgraded from 2.0.6 to 2.0.7 … so what do I do now?

Is there a way for the blogs to be fixed as they are now so the next/previous tags show? I have no issues with the more tags (as others do), no issues with Blogroll links … just the next/previous

Ugh, not everything was backed up as it should have been. I can copy the posts that weren’t backed up right now, of course, and then just copy/paste them in.

What you can try before getting into the big adventure of degrading…

Many older themes use the WRONG next/prev tags! Try to update them with this:
https://codex.www.ads-software.com/Template_Tags/next_post_link
https://codex.www.ads-software.com/Template_Tags/previous_post_link

EDIT. I just figured out 15 minutes ago that on my blog (not upgraded to 2.1) the netx/prev links were also missing because of the old tags…

Ok … I’ll take a look before I totally panic. I’m more angry at myself as I never upgrade quickly so I can see if there are bugs. This is why I didn’t go to 2.0.7! I can’t figure out why I rushed to upgrade this time.

(I’ll go read your links, thanks, and will post if I fix it — if not, you’ll know I’ll be back)

This is much, much, much more complicated than I thought it would be, and not being a programmer …

What is the simplest way to fix my sites quickly? Is there someone “here” I can hire to fix my broken blogs? That would be the easiest rather than trying to restore a db and restoring posts

Read the first link and my code in one broken site appears correct to me.

<p align=”center”><?php next_posts_link(‘« Previous Page’) ?>   <?php previous_posts_link(‘Previous Entries »’) ?></p>

Re: your question about fixing.
Since the database has been oevr-written in the upgrade process – there is no other way than restoring the backup and, eventually, adding what is missing from the backup file. Sorry.

Great, so I install 2.0.7 and then restore my backup.

Ok, how do I restore the backup?

(I’d cry over this but that’s a waste of energy and time I could be devoting to fixing this)

Here you will find detailed instructions both for backup and restoring:
https://codex.www.ads-software.com/Backing_Up_Your_Database
Hope this helps!
Post back if you have more questions or need help.

One last question — I did the backup via the standard WP plugin. I can restore in phpMyadmin (that’s what I use), correct, but I’m only going to restore the db and no other tables or things?

I know you are nervous and anxious now (I’d be, for sure) but please, read carefully the backup/restore insrtuctions.

Actually, you do not delete the database, just drop the existing tables and then by using the Import feature the new(old) tables will be recreated and populated with the data.