I have a site with a number of dynamic "areas" that are not displaying/refreshing correctly due to caching. One primary area of the site is an online LMS (Learning Management System) made up of multiple lessons, topics, and quizzes. I could list each URL individually, however, it would be well over a 100 just to get started, and would also require me to continue updating the list of URLs as I continue to add new content/lessons, etc.

Ideally, I could enter in a relative url with a wildcard or utilize regex to not cache all URLs matching the pattern, such as "/courses*" for example.

Currently the plugin will delete all the info from all the fields if you submit and it finds an error. In the UX world, this is considered undiluted evil. Why is the plugin punishing me?

Furthermore, the UX writing is profoundly unclear. The field marked "application folder" is actually for the MYSQL database name. Who would ever figure that out?

If you really want to make it good, don't force the user to enter any of this stuff. Just make an "export settings for the migration plugin" button. It can create a key code that includes all the settings. Copy, paste into the single field in the plugin, click.

Other plugins have this functionality, so you probably won't have to reinvent any wheels.

I see that cloud ways supports elastic press plugin on wordpress after activating ES on server side. Yet, there is another plugin that has much better functionalities named WPSOLr.
When I tried to use it, it requires ES v 5.0+ (with mapper attachments plugin) or SOLR on the server. Now Cloudways have option of ES 5.4, but mapper attachments plugin not there, and we can't install it due to root access.Due to that, I had to use outside hosts just to host my ES/SOLR index $40per month.
I would suggest that cloudwaays provide the mapper attachments plugin to ES5.4 or Add SOLR integration, and provide a documentation on how to integrate WPSOLR plugin rather than current elastic press.
This would allow me to upgrade my current server on cloud ways for the index hosting/ or have another server on cloud ways for that, rather than going for another company.
Additionally, wpsolr has drupal support.
Appreciate if you could look into this, as I believe it is simple for you to integrate.
Thanks.

My suggestion is that all WordPress apps use the Woocommerce Varnish by default.

This way there's no risk of a user installing a normal WordPress app and later installing Woocommerce on it, only to find out that their cart is broken because of Varnish.

Here is why:

I found out that the WordPress app uses a unique Varnish and the Woocommerce app uses it's own unique Varnish.

I ran into a problem with a WordPress app that I later decided to install Woocommerce on. Once I did, the normal wp Varnish did not support Woocommerce and it broke my cart functionality. I had to make a new Woocommerce app and migrate my site over there so it could use the Woocommerce Varnish.

The support team told me that Woocommerce Varnish would also work for a plain WordPress app without Woocommerce.