Pretty much exactly what was needed... The .ct extension scheme is rather elegant. Container files have .ct endings, and the mountpoints are the same name, minus the suffix.
What will the implementation details of this be? Manually stemming text and adding values in a list like prior was far from ideal. In fact, when I full text index, I don't even want to have to think about stem lists,…
I can confirm the issue. My install was vulnerable. If you don't want to disable W3, then just add deny from all In wp-content/w3tc/dbcache/.htaccess.
Pretty much exactly what was needed... The .ct extension scheme is rather elegant. Container files have .ct endings, and the mountpoints are the same name, minus the suffix.
What will the implementation details of this be? Manually stemming text and adding values in a list like prior was far from ideal. In fact, when I full text index, I don't even want to have to think about stem lists,…
I can confirm the issue. My install was vulnerable. If you don't want to disable W3, then just add deny from all In wp-content/w3tc/dbcache/.htaccess.