![]() ![]() The corruption at the end of the htaccess file isn’t easy to replicate unless you manually add it to the end just to see it’s effect. Just clear the cache and then browse the sub-sites while watching the wp-content/cache/minify/.htaccess file change for each sub-site that is visited. You can recreate the htaccess file changing situation by just creating your own multisite with subfolders for the sub-sites since the htaccess updating appears to occur on different multisites I have access to, so that would seem standard procedure at the moment that should be easily replicable. A link wouldn’t make any difference anyway since I don’t leave the site broken. If this moving would work, it would eliminate the need for rewriting the htaccess file all the time and remove the chance of corruption. …since the RewriteBase in this block is the only thing that changes at least for my configuration. htaccess files in the ID number subfolders like cache/minify/1/ read: # BEGIN W3TC Minify core Header set X-Powered-By "W3 Total Cache/2.4.1" SetEnvIfNoCase Request_URI \.js_br$ no-brotliĮxpiresByType application/x-javascript A31536000 SetEnvIfNoCase Request_URI \.css_br$ no-brotli htaccess in cache/minify read: # BEGIN W3TC Minify cache Or if needed maybe it could split up and have the. htaccess files would be directly alongside the css and js files again just like on a regular site. ![]() htaccess at the minify root, you could have static htaccess files with the correct RewriteBase with no need for constantly updating 1 htaccess file and the. ![]() htacess no alongside the files directly:Ĭausing the. htaccess alongside the css and js files:Ī multisite has the. htaccess file directly in the minify folder, but place sub-site specific. htaccess file immutable with:īut that stopped sub-sites from loading entirely so that won’t work.Īlthough, since multisite’s have the cache/minify folder segmented into subsite ID folders, would it make sense on mutlisites to not have the constantly changing. htaccess file is a recent change or some other update is at play.Īll I know is this has become an issue that may push to ditch this plugin entirely if not resolved since I can’t afford site’s failing in this manner. I don’t know why this didn’t use to be a problem. htaccess updates, it either needs to be designed to be more careful / strict or open the file with exclusive access so another sub-site’s process doesn’t try to update it at the same time. So the multsite folder at the front would seem unnecessary to remain unique. …since the blog paths for the assets still vary with the numerical id folders like: RewriteBase /site3/wp-content/cache/minify/ RewriteBase /site2/wp-content/cache/minify/ RewriteBase /site1/wp-content/cache/minify/ Isn’t there a more efficient way to handle minified cache for multisites?įor example does it need to be switching between: So, first I’d like to ask does this file really need to be constantly rewriting itself? That would seem to be problematic to begin with. It also increases the process load when it’s broken. This is enough to completely break all the sites in that it causes errors for the loading of any css and js files linked in the cache folder, and since it’s outside the WTC Minify core block it doesn’t correct itself when it updates the next time. Where extra text is being leftover below the END line. The problem comes up when I believe the traffic is unusually increased due to bots and such.īut occasionally it’s like it gets updated while it’s already being updated and corrupts itself, causing the end of the file to look like different variations of: Each time it updates it changes the RewriteBase to the different mutlisite paths. htaccess file stored in the cache/minify folder.įirst the file seems to constantly be getting updated which is part of the core of the problem. In recent months (starting around June 20th) I’ve started seeing an issue on a multisite install with the. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |