Title: joetower's Replies | WordPress.org

---

# joetower

  [  ](https://wordpress.org/support/users/joetower/)

 *   [Profile](https://wordpress.org/support/users/joetower/)
 *   [Topics Started](https://wordpress.org/support/users/joetower/topics/)
 *   [Replies Created](https://wordpress.org/support/users/joetower/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/joetower/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/joetower/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/joetower/engagements/)
 *   [Favorites](https://wordpress.org/support/users/joetower/favorites/)

 Search replies:

## Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Autoptimize] Plugin no longer working on Pantheon (hosting provider)](https://wordpress.org/support/topic/plugin-no-longer-working-on-pantheon-hosting-provider/)
 *  [joetower](https://wordpress.org/support/users/joetower/)
 * (@joetower)
 * [7 years, 1 month ago](https://wordpress.org/support/topic/plugin-no-longer-working-on-pantheon-hosting-provider/#post-11683097)
 * [@optimizingmatters](https://wordpress.org/support/users/optimizingmatters/) 
   As an update on the issue I was experiencing: our issue had to do with our build
   setup not properly copying over our wp-config.php file into the build directory
   on Pantheon. Which means that the fix for Pantheon and Autoptimize in setting
   a different location via `AUTOPTIMIZE_CACHE_CHILD_DIR` isn’t being read at all,
   prompting the failure.
 * So on my end, the issue the OP discussed is resolved. Thanks again for your assistance
   here and again, for creating a great plugin. I appreciate your responsiveness.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Autoptimize] Plugin no longer working on Pantheon (hosting provider)](https://wordpress.org/support/topic/plugin-no-longer-working-on-pantheon-hosting-provider/)
 *  [joetower](https://wordpress.org/support/users/joetower/)
 * (@joetower)
 * [7 years, 1 month ago](https://wordpress.org/support/topic/plugin-no-longer-working-on-pantheon-hosting-provider/#post-11678742)
 * [@optimizingmatters](https://wordpress.org/support/users/optimizingmatters/) 
   Hello and thank you for the response.
 * Here are some answers below. Just as an initial note – I am starting to think
   our specific site issue might be unrelated to your plugin. As I note below, I
   will update here if this is the case.
 * * _how_ does the CSS & JS break? do the files 404? or do they cause an internal
   server error?
    Since the plugin’s functionality is completely disabled due to
   it being unable to write to the cache directory, nothing breaks or 404s. When
   you’re logged in to the site, you simply see an error stating:
 *     ```
       Autoptimize cannot write to the cache directory (/srv/bindings/c6cf2ec7251745139b2efad85e1f6408/code/web/wp-content/cache/autoptimize/), please fix to enable CSS/ JS optimization!
       ```
   
 * * what happens if you turn CSS optimization on with the “inline all CSS”-option
   on?
    Because the plugin’s functionality is disabled, you can not access any of
   the plugin’s configuration in the admin interface. So I can not view any options
   to toggle functionality and troubleshoot further.
 * * what happens if you disable “aggregate JS” and/ or “aggregate CSS”?
    Same as
   above. The plugin is effectively disabled if it can not write to the cache directory.
 * * “after a recent update” of what? AO or your theme or a plugin?
    I am now thinking
   that the error we’re seeing is either specific to this site’s setup or Pantheon
   environment. I realize this question was directed at the OP. In my case, I discovered
   the issue while updating WordPress to 5.2.2 and the Autoptimize plugin to 2.5.2.
 * If we discover that this error is due to a site-specific build setup (we use 
   a composer-based continuous integration setup for this site) which may be causing
   this issue. We’re just trying to troubleshoot all options right now. I will post
   here if this was the cause of the issue on our end.
 * * any (relevant) errors in your PHP errorlog when this happens?
    There are no
   relevant errors in our PHP logs.
 * * have you reached out to Pantheon and if so, what was their feedback?
    I will
   do this next.
 * —
 * Totally unrelated, but important – thank you for creating an awesome plugin and
   caring about front-end performance in WordPress.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Autoptimize] Plugin no longer working on Pantheon (hosting provider)](https://wordpress.org/support/topic/plugin-no-longer-working-on-pantheon-hosting-provider/)
 *  [joetower](https://wordpress.org/support/users/joetower/)
 * (@joetower)
 * [7 years, 1 month ago](https://wordpress.org/support/topic/plugin-no-longer-working-on-pantheon-hosting-provider/#post-11676010)
 * I am also experiencing this issue on Pantheon seemingly as the result of a recent
   plugin update.
 * Did something change with the AUTOPTIMIZE_CACHE_CHILD_DIR value?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Advanced Typekit] [Plugin: Advanced Typekit] FOUT visible in Webkit Browsers](https://wordpress.org/support/topic/plugin-advanced-typekit-fout-visible-in-webkit-browsers/)
 *  Thread Starter [joetower](https://wordpress.org/support/users/joetower/)
 * (@joetower)
 * [15 years, 9 months ago](https://wordpress.org/support/topic/plugin-advanced-typekit-fout-visible-in-webkit-browsers/#post-1750846)
 * I am now thinking maybe the FOUT has more to do with how WordPress loads the 
   plugins and/or assets. I’m probably wrong but I’m not sure what is causing this.
 * [@jeremy](https://wordpress.org/support/users/jeremy/) Just a note, you will 
   see FOUT using Typekit in Firefox – it is simply how the browser loads content/
   assets and displays them on the page. However, you can style and control what
   that FOUT state looks like. You can style the .loading, .inactive, .active dynamic
   classes. At least we have control – though, not ideal.
 * Thanks for the corroboration Jeremy! I’m glad I’m not the only one having issues.

Viewing 4 replies - 1 through 4 (of 4 total)