Kyle Duncan

I posted incorrectly – the fix does work, thank you. However, can you confirm that the knowledge base is now out of date? https://support.cloudways.com/en/articles/5126470-how-to-install-and-configure-breeze-wordpress-cache-plugin#h_3f620cea69

It says that adding items in this field will CACHE each one, but in fact, adding items here IGNORES them for caching purposes (which is what I wanted and what now happens).

• This reply was modified 2 months, 1 week ago by Kyle Duncan. Reason: Mistake

Sorry I wasn’t clear. I don’t care about the hashtag value or saving it, I just want the redirect to work. So I meant: will both of these URLs:

http://www.test.com/oldsite
http://www.test.com/oldsite#12345

redirect to this URL:

http://www.test.com/newsite

if the plain redirect is:

Redirect 301 /oldsite http://www.test.com/newsite

Hi John!

Thanks very much for your quick reply. Could you explain what you mean by “plain redirects”? Do you mean like Redirect 301 oldpath newpath rather than using conditions and rules? I might be able to turn off the “regex” option, but:

1. some articles will have been bookmarked by users with an annoying hashtag at the end because of our old comments system, and I wanted the redirects to work with or without the hashtag. Would I have to create 2 redirects for each article because of this?
2. Some articles may have been bookmarked before or after friendly URLs were added to the old site, so I needed URLs like /article/12345/ AND /article/name-of-post-here/12345/ to both work, hence the regex. I also can’t use a universal regex for all articles, because the old site’s friendly URLs are terrible and don’t nicely match the new wordpress URLs in most cases. So again, would I need 2 redirects for each article?

So re: the above issues, would I actually need 4 x 17,000 redirects in order to do it all without regexes? And, if I were to go that route, what would I need to do to setup a database index? Sorry if this is beyond the scope of your plugin, I’m not clear if you’re referring to a feature within your plugin or not.

And lastly, with putting the logic in PHP, could you point me in the direction of the kind of thing you’re thinking of?

Cheers

For now, I’m fixing this by adding this capability to all users above subscriber:

$role = get_role(‘contributor’);
$role->add_cap(‘read_private_multiple_post_types’);
$role = get_role(‘author’);
$role->add_cap(‘read_private_multiple_post_types’);
$role = get_role(‘editor’);
$role->add_cap(‘read_private_multiple_post_types’);
$role = get_role(‘administrator’);
$role->add_cap(‘read_private_multiple_post_types’);

Hi Jamie, thanks for the quick reply! Yes, it was a ‘post_status’ change in my functions file causing the problem, fixed now.

I’ve tested this, just by changing the includes file (replacing delete_post_meta with delete_transient), and it seems to work!

In the database the 3 meta fields belonging to the parent product still don’t update in the way they do if you manually save the product in WordPress, but the site does display the sale now – is that the expected behaviour with this patch?

Cheers!

Thanks for the advice, Jeff.

Hi there,

It seems that the Ajax Enhanced Layered Navigation paid-for plugin works correctly, it’s just the free widgets that come with WooCommerce that do not.

Cheers