Forum Replies Created

Viewing 12 replies - 16 through 27 (of 27 total)
  • Plugin Author Budiony Damyanov

    (@budiony)

    Update: The solution for wp-polls plugin (and also with any other voting plugin) is to exclude the page or post, on which is the poll, from caching mechanism, because mixing dynamic (polls results or voting options) with static (regular page/post) data is bad idea.

    The reason is that even if we rebuild the cache page / post after visitor’s vote, all other users on the web site will see the last voting user result and they will not be able to vote (because there is restriction by IP address per visitor). So all other visitors will see the results, not the voting options itself, as if they are already voted (because this information will be cached from the previous user).

    Easy cache plugin will not and cannot generate cache pages / posts per user IP address (this is the only way to deal with IP address restriction).

    Plugin Author Budiony Damyanov

    (@budiony)

    Hi, Hussam, indeed using polls is very frequent on blogs, Easy cache was not tested with wp-polls plugin, however stay tuned (again) and I`ll try to implement the solution.

    If you have other proposals for improvement – I`m open to suggestions.

    Take care.

    Plugin Author Budiony Damyanov

    (@budiony)

    Version 0.4 of the plugin adds compatibility support for Jetpack mobile theme from WordPress.com
    It is recommended to check the setting in Administration panel and leave it with its default value.

    Plugin Author Budiony Damyanov

    (@budiony)

    WordPress, by default, does a form of “Object Caching” but its lifetime is only a single page load. Let me explain you what exactly is the Object Cache in WordPress, because I see that you are not familiar with this matter:

    Options (extracted from database table wp_options) are actually a really good example of this. The summary:
    – A page starts
    – All options are loaded with a simple SELECT option_name, option_value from $wpdb->options statement
    – Subsequent requests for those options (eg a call to get_option never hit the database because they are stored with the WP cache API.

    Options always “live” in the database and are always persisted there — that’s their “canonical” source. That said, options are loaded into the object cache so when you request an option there’s a 99% chance that request will never hit the database.
    So to speak, Easy cache plugin make very few requests to the database to get his options and they are all cached, by default by WordPress, so the Object caching is enabled by default (because actually this has nothing to do with the plugin, but with the WordPress system).

    Transients are a bit different, but the Easy cache plugin does not use them.

    Plugin Author Budiony Damyanov

    (@budiony)

    This is excellent question and you are correct, most cache plugins have troubles working with mobile / desktop versions of the websites.

    Easy cache plugin was not tested with Jetpack mobile theme, but stay tuned, in near term I`ll post here update about if it is compatible or not.

    Plugin Author Budiony Damyanov

    (@budiony)

    Maps are cached, because in fact they are based on JavaScript code, which is injected inside your page and this very page is saved as cached file.

    The requests however, which those maps made to Google servers to pull data cannot be cached.

    Plugin Author Budiony Damyanov

    (@budiony)

    Screenshots have been uploaded. Here are the couple of URLs of websites, using the Easy cache plugin:

    http://www.foodmicrosystems.eu/
    http://www.agricistrade.eu/
    http://www.lifegreencity.eu/

    Plugin Author Budiony Damyanov

    (@budiony)

    By its very definition, the caching process is a collection of data, which duplicates original values, stored elsewhere or computed earlier, where the original data is expensive to fetch, and served later to the end user instead of the original data.

    The only way to achieve what you need is to place the dynamic content (sidebar) inside an iframe. This is the way to combine the data, computed earlier with the original data, because actually an iframe is a window inside a window. So the cached page will contain this iframe, which will point to the dynamic page, which generates the current Cart state.

    This however will require modification of the sidebar and/or the theme you use.

    Plugin Author Budiony Damyanov

    (@budiony)

    …also you can exclude any other page (which is used as container and have dynamic content on it).

    Plugin Author Budiony Damyanov

    (@budiony)

    You can exclude pages/posts with Easy cache plugin, just select the original container page (the one, which you use for displaying the “Cart”).

    See plugin’s setting “Exclude pages/posts from caching”.

    Plugin Author Budiony Damyanov

    (@budiony)

    Hello, oomskaap

    Did you try the plugin with your dynamic content? If the dynamic bar/or other HTML element uses AJAX technology (which is almost 100% certain) that means, that no modification of the plugin will be necessary, and the dynamic bar will work.

    Plugin Author Budiony Damyanov

    (@budiony)

    Hello, ramonjosegn,
    I feel your pain, really, the main reason to decide to develop a caching plugin is because of my personal experience with such plugins, which just does not do what they suppose to do.
    Currently rewriting of .htaccess file is not necessary, the plugin does not use the technique other caching plugins use, it works at very last stage of page generation. Rewriting rules of .htaccess file are primarily used to deal with permalinks structure in WordPress (and sometimes for pointing to the cached resource files – CSSs or JavaScripts – and this is the reason websites to break honestly, if not done properly). However the Easy cache plugin does not minify external resources, like CSS or Javascript, it only save and minify the generated page/post/link/etc… as regular optimized HTML file (with all links inside to resources untouched, no combining whatsoever).

    I plan to extend the plugin, so the next version 0.2 will include CSS minification and combining, although I`ll try develop it in such way, that not to require .htaccess file modification, because in general this is something which should be avoided by plugins, in my opinion, unless is absolutely necessary.

Viewing 12 replies - 16 through 27 (of 27 total)