WordPress.org

Ready to get started?Download WordPress

Forums

W3 Total Cache
Cache Preload Fixes and Feature Enhancements (38 posts)

  1. sLa NGjI's
    Member
    Posted 1 year ago #

    :lol

  2. palPalani
    Member
    Posted 1 year ago #

    Manually removed 0.9.2.6 version and uploaded official version of 0.9.2.5, but it also not working. gives permission errors. now my site is running without cache plugin.

  3. Henk Jan
    Member
    Posted 1 year ago #

    Tip: I use the Generate Cache plugin (version 0.4) next to W3 Total Cache (version 0.9.2.7). Works like a charm.

  4. wp-fan
    Member
    Posted 1 year ago #

    All of the points raised were already in the roadmap and the contributions here have simply moved them up the queue.

    @Frederick Townes:

    Could you please clarify, Frederick, because I am not sure wether I misunderstood you: Were you able to pick up and include the contributions from wmiles in version 0.9.2.6 or 0.9.2.7?

  5. sLa NGjI's
    Member
    Posted 1 year ago #

    Frederick Townes knows, but it will never allow this and other corrections ... W3 Total Cache 0.9.2.7 is out and nothing of wmiles modification was included!

    :)

  6. wp-fan
    Member
    Posted 1 year ago #

    @ sLa NGjI's

    Thank you for clarifying.

  7. sLa NGjI's
    Member
    Posted 1 year ago #

    @wp-fan

    Thank you for support wmiles forked W3 Total Cache ;)

  8. Frederick Townes
    Member
    Plugin Author

    Posted 1 year ago #

    Could you please clarify, Frederick, because I am not sure wether I misunderstood you: Were you able to pick up and include the contributions from wmiles in version 0.9.2.6 or 0.9.2.7

    I don't know why the tone has to be negative here as if this situation is anything other than cooperation. So please read the following knowing that I'm smiling.

    Anyway, I don't know how to explain this point without risk of being misconstrued, but the entire project roadmap is private, the tickets in that roadmap are private and the current releases and therefore the "forks" and "patches" are *inconsistent* with the direction of the project. In other words, I'm appreciative of the patches that people have made, we review them etc in detail, but those patches are always behind what is in activate development.

    1. Patches rarely consider the upcoming features and have to be refactored
    2. Patches show me what is interesting to the community and the roadmap's priorities are changed based on what is relevant to users

    I don't know why this trend to cast a "shadow" on the project after all these years of working with the community has occurred, so if that is something I've done I apologize.

    The forums are *not* where the vast majority and discourse happen on this project, all of that happens in email, for now. Maintaining forum discussions especially about a plugin that manipulates file on a server and is used as a framework (meaning there are countless options and ways it can be used) is simply not sustainable right now.

    For those who want to continue to contribute, thanks so much. I've probably accepted 20 or so patches over the years from folks without issue, very few of those came from forums, they came from offline or email conversations in the end. Preloading / priming in particular is *not* a trivial issue and that doesn't mean that various patches "don't" work it means that implementations have to consider more cases than just a few; so that means contributions are just a starting point, just like contributes to WP core or any other thoughtful project.

    For those of you that think a fork is necessary or a sustainable outcome for any of us, I'd invite you to reach out to me directly so we can get back on track.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic