Hi Ernest,
It’s good to hear from you. It’s been a while!
You didn’t respond to what I said happened with my license. I know this is managed by Envato, but can you shed some light on this? Now I have two ASP licenses, when I only needed the one. All I wanted to do was renew the support for a year.
…..
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.
Hold on, this is a big issue. You’re saying that the plugin is using the “style.instances-ve-ho-po-no-au.css” file and NOT the “style.instances.css” file?
If that is the case then shouldn’t I be dequeueing that specific file and enqueueing it from our static location?
…..
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.
My main concern here is with these two css files:
“style.basic.css” and “style.basic-ve-ho-po-no-au.css”
If I have this feature disabled, then are these files used at all by the plugin? My concern is because we need to custom enqueue all the css files to be static. I need to know if we need to make these into static files or not.
From the warning you wrote by this feature, it seems to me that we shouldn’t use this. I prefer we load css files simply from a static location.
…..
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.
Without me having to understand all the intricacies of the new css management, I have only one concern here. We cannot have any dynamic css stored in the uploads folder and sub-folders. I need to dequeue all such files and enqueue them as static files. This is what we’ve always been doing. So I really need to know clearly from you which files we need to do this for.
It sounds like you’re saying that the new style.basic-ve-ho-po-no-au.css file is smaller and more efficient. That is great, but right now we aren’t using this in our static files. So I’ll have to take care of this asap once I hear from you.
…..
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.
This is definitely not working on our site. Just go to eruditely.com and run a search for “animated.” You’ll see a bunch of bird animations that a friend of mine made. These are all gif animations. As you’ll see none of them are animating in the search results when rolled over. If you go to those posts you’ll see they all animate properly.
…..
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;
Is there at least a warning confirmation screen if these are accidentally pressed? I think it would be wise to have a way to disable these settings with a constant. Then it can just say “Disabled from wp-config” in the settings area.
…..
6. Yes, that looks correct
But this isn’t for the “style.basic-ve-ho-po-no-au.css” file which you said is the file actually being used. Don’t we have to now dequeue that specific file and then custom enqueue it to load statically?
…..
Thanks for your help as always!
~ Michael