wrip

@vupdraft Thanks for letting me know. The screenshot I took was from the “Preload” tab. Next to the Run Now button, it shows the following information:

Last preload finished at 6:23 pm, 17 September 2025

I wanted to completely remove the above preload cache information. I optimised database tables but that didn’t help.

My current WP-Optimize cache setting is as follows:

Enable page caching: On
"Automatically preload content after it is purged" checkbox: unticked
"Generate separate files for mobile devices" checkbox: unticked
"Serve cached pages to logged in users" checkbox: unticked
Cache lifespan: 8 hours

Btw, my current settings are:

Enable page caching: On
"Automatically preload content after it is purged" checkbox: unticked
"Generate separate files for mobile devices" checkbox: unticked
"Serve cached pages to logged in users" checkbox: unticked
Cache lifespan: 24 hours
Gzip compression: Enabled
Browser static file caching headers: Enabled and expiration set to 5 days
Minify: Not enabled

@johnny5 I had a look at the developer page. It doesn’t look like I can grant permissions to the Editors to have access to only a certain group within the plugin. E.g. I created a group called “Temp Redirects” within the plugin. I want Editors to have access to this group only where they can add or delete redirections. Is this doable? I can’t see any specific Redirection permissions that allows me to do this.

Thanks, will check this out!

@alanfuller Yes, I’ve managed to resolve this using a custom endpoint.

@abretado1985 Simply registering the post type and taxonomy; and then re-saving the Permalinks did not automatically load the content on this URL: https://www.example.com/books/arts/modern/sample-book/. This needed additional rewrite rules (see below) and permalink rewrites.

@bcworkz Yes, I’ve managed to fix the issue by using the add_rewrite_rule() function inside the init hook. I have a couple of questions in regards to the efficiency of the code.

In my code, the rewrite rule includes nested foreach() statements that generates several of these rewrite rules to capture parent/child hierarchical taxonomy terms like the following (there might be hundreds):

https://www.example.com/books/arts/modern/sample-book/
https://www.example.com/books/arts/african/book-2/
https://www.example.com/books/arts/tattoo/needle-works/
https://www.example.com/books/comedy/classics/comedy-book-1/
https://www.example.com/books/crime/europe/crime-book-mafia/
https://www.example.com/books/crime/asia/crime-book-japan/
https://www.example.com/books/drama/classics/romeo-and-juliet/
https://www.example.com/books/drama/comedy/hello-world/
https://www.example.com/books/cars/classics/history-of-cars/

This is the code:

function book_category_rewrite_rule() {
    $parent_terms = get_terms(...); // Get parent terms
    
    foreach( $parent_terms as $parent_term ) {
        $child_terms = get_terms(....); // Get child terms
        foreach( $child_terms as $child_term ) {
            add_rewrite_rule( '^books/' . $parent_term->slug.'/'.$child_term->slug . '/([a-z0-9-]+)[/]?$', 'index.php?books=$matches[1]', 'top' );
        }
    }
}
add_action( 'init', 'book_category_rewrite_rule' );

Does this always need to be fired from the init hook or can this be fired from other hooks? I was wondering if this could potentially slow down the site if this gets fired on every page load.

Thanks Tom. I didn’t realise there was a demo menu on your site earlier.

I think that answers my questions.