Nic Windley

Thank you for clarifying and I will look out for the reply.

Thank you.

The link on the site shows version 16.9, however the paid version is showing 16.9.1 ?

Makes perfect sense and fantastic support as always.

Thinking further ahead, is it possible to simply determine which price tier group the values should be taken from? i.e. whether it should be b2c or b2b?

Excellent, thank you.

I may open a ticket as that function could be useful.

• This reply was modified 1 year, 8 months ago by Nic Windley.

Thanks.

Locale is UK

Version is 5.3.1

If I create a new contextual unit, even without the additional keywords, it seems to return results. Will monitor it to see if it expires for some reason.

• This reply was modified 1 year, 9 months ago by Nic Windley.
• This reply was modified 1 year, 9 months ago by Nic Windley.

Fantastic! Thankyou. For some reason I didn’t get the email.

Very usesful, thankyou. It flags becuase it’s “expecting” option ID to be the primary key.

• This reply was modified 1 year, 11 months ago by Nic Windley.
• This reply was modified 1 year, 11 months ago by Nic Windley.

Makes sense. As I will be using Redis, I can probably ignore index tuning.

• This reply was modified 1 year, 11 months ago by Nic Windley.

Thank you! For now, I’ll ignore the warning message.

Thank you for the clarification René and your offer, much appreciated.

Ollie’s point is that database management systems are designed to update their keys as tables grow. Thus, extending the WP-Staging check would be beneficial since keys may change without impacting the table content or the cloning process.

Would that be possible ?

Ok, so I need the Pro plugin active to prevent this. I now have this installed, however the free trial is refusing to activate ?

Is this (above) the expected behaviour of Index WP MySQL For Speed Ollie ?

I checked the changes made by Index WP MySQL For Speed?in the wp_options table, and it does indeed cause the primary index to change from option_id to option_name.

Please see attached screenshots. This is on a new build site.

Before Index

https://snipboard.io/Uv9wob.jpg

After Index

https://snipboard.io/PGmRCI.jpg

Yes, the DB collation issue is no surprise and I have access to phpmyadmin and will look into your suggestion. Thank you again!

However, please refer to my earlier post. This issue is happening on a clean build where I added the index and then installed WP Staging resulting in the missing primary key index or autoincrement flag? The table exists, AUTO_INCREMENT is set and I can see the indexes?

I’ve also raised the issue with the devs at WP Staging and pointed them at this thread.

• This reply was modified 1 year, 11 months ago by Nic Windley.
• This reply was modified 1 year, 11 months ago by Nic Windley.
• This reply was modified 1 year, 11 months ago by Nic Windley.
• This reply was modified 1 year, 11 months ago by Nic Windley.
• This reply was modified 1 year, 11 months ago by Nic Windley.