As for displaying the lowest price, it seems OK to me.
Considering the described updates, it would be nice if I could have the option to set the duration for how long the prices are stored (the ability to auto-clear older prices has been added).
However, in my opinion, there is an error in the price table display when viewed with “debug”, where the “regular price” is also changing even it has remained the same the entire time.
@iworks Thank you. The “issue” was that I hadn’t been on the product. Of course, now I can see the entire history, which is exactly what I need 🙂
BUT… It’s not ideal to continue here, but since we’ve already started the conversation… I’ve had the plugin installed on the live site since release, and I’ve noticed for a while now that it doesn’t work quite right. Today, I also installed it on fresh test site, and there it behaves differently (correctly). On the live site, it occasionally fails to display the correct “lowest price”. However, it’s visible in the price history that a lower price was entered, and the correct “lowest price” is shown on the admin product edit tab itself. But on the frontend of product, it appears differently.
Do you have any idea where to look for the issue? Is there a way to completely clear the history and reinstall the plugin? Because simply removing and reinstalling the plugin makes no difference.
Thank you for your help. However, I don’t have the “Omnibus” submenu. I tried changing some prices. I’ll check again on the test server this afternoon.
Why would I even need a list of price changes for individual products? Because certain inspectors may request to see the price movement. And if the Omnibus plugin already records this, it would be nice to be able to use this list in case the need arises. This would probably be useful for someone else as well.
As for the “Debug Bar”. I installed it, but I didn’t quite understand how to use it. Does WP_DEBUG have to remain enabled all the time, or is the history recorded in some other table, and you just read it with the Debug Bar?
No, I don’t see any rules. I see what I pasted in the previous post. Do I need to set anything up first? Primarily, I would need to know if your plugin even works with the UNIT version of nginx.
On the "General" tab and select your caching methods for page, database and minify. In most cases, "disk enhanced" mode for page cache, "disk" mode for minify and "disk" mode for database caching are "good" settings.
1. The "Compatibility Mode" option found in the advanced section of the "Page Cache Settings" tab will enable functionality that optimizes the interoperablity of caching with WordPress, is disabled by default, but highly recommended. Years of testing in hundreds of thousands of installations have helped us learn how to make caching behave well with WordPress. The tradeoff is that disk enhanced page cache performance under load tests will be decreased by ~20% at scale.
Recommended: On the "Minify" tab all of the recommended settings are preset. Use the help button to simplify discovery of your CSS and JS files and groups. Pay close attention to the method and location of your JS group embeddings. See the plugin's FAQ for more information on usage.
Recommended: On the "Browser Cache" tab, HTTP compression is enabled by default. Make sure to enable other options to suit your goals.
Recommended: If you already have a content delivery network (CDN) provider, proceed to the "Content Delivery Network" tab and populate the fields and set your preferences. If you do not use the Media Library, you will need to import your images etc. into the default locations. Use the Media Library Import Tool on the "Content Delivery Network" tab to perform this task. If you do not have a CDN provider, you can still improve your site's performance using the "Self-hosted" method. On your own server, create a subdomain and matching DNS Zone record; e.g. static.domain.com and configure FTP options on the "Content Delivery Network" tab accordingly. Be sure to FTP upload the appropriate files, using the available upload buttons.
Optional: On the "Database Cache" tab the recommended settings are preset. If using a shared hosting account use the "disk" method with caution; in either of these cases the response time of the disk may not be fast enough, so this option is disabled by default.
Optional: On the "Object Cache" tab the recommended settings are preset. If using a shared hosting account use the "disk" method with caution, the response time of the disk may not be fast enough, so this option is disabled by default. Test this option with and without database cache to ensure that it provides a performance increase.
Optional: On the "User Agent Groups" tab, specify any user agents, like mobile phones if a mobile theme is used.
