westham60

A further week on, and nothing has changed with the problem. I have spent considerable time on the phone to GoDaddy support, firstly being told it was a plugin problem so not their fault (we can fix for you if you pay). Then today after I asked them to do a restore from March, and being told it was underway but would take 3 hours (why when their control panel restore takes 20 minutes?), 7 hours later my site is still showing a message I wrote on April 27, so that doesn’t seem like there has been a restore from late March – did the person responsible finish their shift and go home, I wonder?

But here’s the thing: I had already tried the same March restore and it failed (no admin access or categories/tags etc). When I looked at the database via phpAdmin, I found that all the tables related to tags, categories and users were completely missing – no wonder I get the message “Could not insert term into the database” when trying to create a tag because there’s no tag to insert into. However when I downloaded that March backup and imported it into a local WP install on my PC, everything was perfect – all tags, categories etc. So with my limited knowledge of how the WP system works, it seems to me that the GoDaddy restore process isn’t restoring properly (or am I missing something?).

I hope someone here can help, because I’m quickly losing confidence in GoDaddy’s support.

The host is GoDaddy so certainly could do this, but the inability to create new tags/categories/menus currently suggests there is a significant database issue that needs addressing first.

Thanks for this, George. Looking at my hosting dashboard, there is a Flush Cache option, so I have done that and we shall see (there is no reference to Cloudflare).

Saurabh

Thank you for this. I will start with the preload suggestion, and then move to the Cloudflare area (it must have been chosen by the host because it is not something I specifically opted for). Do you happen to know of any plugins that work with Cloudflare?

David

Thanks Amir for your quick reply.

I can confirm that disabling the Views Column in Content List does allow the post/page lists to be displayed instantly. And no, that plugin is not used.

Nothing that is identified as an error (unless I’m not looking in the right place). There is one Issue, which would seem not to be relevant: Cookie sent in cross-site context will be blocked in future Chrome versions

I worked out that the problem was to do with offset, and even found code and advice that should have solved everything on an external site titled “Changing the posts per page on first page without breaking pagination in WordPress” (I am not going to include its URL) as the code simply doesn’t do what heading says.

However, I could follow the code, so went old school with pen and paper, and did some simple arithmetic with the code formulas to get the post ranges that I wanted, i.e. posts 1-8 on homepage, 9-32 on page 1, 33-56 on page 2 and so on. I made the adjustments to offset and posts_per_page, and it works.

bcworkz, thank you so much. This did the trick perfectly.

For anyone else needing this solution, I used the following code for archives (category, tag, author, date), is_search() for search pages and is_paged() for the main pages off the home page (e.g. …com/page/2):

function archive_pagesize( $query ) {
if ( ! is_admin() && $query->is_main_query() && is_archive() ) {
// Display 24 posts for archives
$query->set( 'posts_per_page', 24 );
return;
}
}
add_action( 'pre_get_posts', 'archive_pagesize', 1 );

• This reply was modified 3 years, 4 months ago by bcworkz. Reason: code format fixed