Hi Michael,
I may have read your email some time ago, I don’t recall – sometimes I do postpone some emails after support is done, but there was a major update in preparation, so I think I completely missed some other messages too.
1. It uses only the “style.basic-ve-ho-po-no-au.css” file, the other one is left there for backwards compatibility convenience only. It might be removed in a later release.
2. The feature can be enabled here. You can still use that, but in that case you don’t have to get the contents from either stylesheet files, the plugin will load them later – and it would also defeat it’s purpose.
3. Not exactly, it applies to both methods. The base CSS file had been separated to parts, and after saving any option on the plugin back-end, the plugin checks all options and search instances if they use specific features. If not, then that CSS part is completely excluded. In previous versions, the base CSS included all features. In your case it is actually a huge step-up, as the “ve-ho-po-no-au” part of the file indicates which feature CSS is not generated (vertical, horizontal, polaroid, noUI and certain parts of autocomplete: “ve-ho-po-no-au”)
The filename changes if the requirements change (but the old one is also kept). I did this for better cache control, as well as for easier error checking.
4. It should be automatic. I can check that out, if you want to, all I need is a link to a page and a search phrase I can try. It is not possible to turn it off at the moment.
5. Only programatically. You can disable it by editing the wp-content/plugins/ajax-search-pro/backend/maintenance.php file. Put this after the first line of the file:
return;
6. Yes, that looks correct 🙂