w3-total-cache-fixed
w3-total-cache-fixed copied to clipboard
0.9.7 is out
https://wordpress.org/plugins/w3-total-cache/#developers
0.9.7 reintroduces the PHP_Flag issue in htaccess. This is something I believe was fixed in the 0.9.6 community edition. Could this be corrected in the 0.9.7 community fix?
https://wordpress.org/support/topic/w3tcs-php_flag-causing-500-internal-server-error/
@timeassistant Usually after official releases we do a comparison and make up a list of what to patch again
Any news on the new update @szepeviktor ?
This project moves on with PR-s by contributors. You're free to start the comparison!
We have a new brach. This is the commit to reset to the official 0.9.7 release: https://github.com/szepeviktor/w3-total-cache-fixed/commit/7d8e9b815ec3f62371af1c2f253f3e16c3da8bd0
I have a project, where i had to apply changes every time the original developer released code. To accomplish this, i created patch-sets grouped by topic/functional-group, which allowed me to react on changes in the original code that prevented the applying of a patchset.
But looking at the "reset commit" above i feel lost on start.
That is a huge changeset, and if i understand right, there are changes that added functionality and changes that fixed problems, so i would not even try to manually upgrade from 9.5 community to the current :(
Probably you have to wait till someone goes through our changelog and removes fixed items.
Yikes, 2 months after the official release and no release here yet. Is anyone still actively working on the -fixed project?
Decided to help again.
Cherry picked and pushed missing commits to 0.9.7 branch, everything else was merged to original version.

Attention:
- I didn't updated readme.md
- I didn't changed 0.9.7->0.9.7.1
- And i didn't tested plugin after update as i don't use wordpress at this moment, so be carefull before marking 0.9.7 as default branch.
any updates?
any updates?
This project is pretty much dead, I think. It served us very well while W3TC had many serious bugs, but now perhaps it's OK to go back to the upstream codebase?
@archon810 Sadly, I agree with you. Perhaps we should ping the dev team to get responses.