Hello again.
One thing to remember is that there are several cache locations which can reproduce the results of your problem even after it was fixed.
1. Server cache (hosting environment) Never had any trouble here
2. Browser cache (Chrome is the worst in my opinion)
3. Plugin cache (plugin specific like EA) a bit redundant if you ask me…
4. WP Cache (could be a plugin for site cache)
I would recommend the sequence 3,4,2 before checking the site.
Depending on your setup, you may not have access to the server cache, but I’ve never had issues there (hence the skip). The results of the error could still remain in your site cache and your browser cache after you have flushed the EA cache. This error doesn’t seem to overwrite the styling, it just prevents it from being loaded. (I could be wrong here)
Remember also to reload all pages you had open at the time of clearing any cache.
On my other sites, I cleared the EA cache before updating the plugin. For me, this prevented those sites from breaking as well.
At first I only cleared the EA cache (which didn’t work), and I didn’t think to clear the other caches as well, so I restored a backup. On the third restore, I cleared the EA cache before the update, and this worked for me. It is a pity that I neglected the other caches during this whole process. It might have saved me a lot of work, but I’m not rolling back anything to check this theory.
The bottom line is that the results produced by the error could be cached elsewhere as well. It does seem that the error in the plugin’s coding is confined to the cache management only.