Replies: 0
Hello Emre,
First of all, thanks for this amazing plugin. I use it on all of my sites, and force all clients to use it as well 🙂
I have a question about how the set_content_url() function uses the WPFC_WP_CONTENT_URL definition.
I see that you check to see if a plugin called hide-my-wp is enabled, and if it is, you then replace the wp_content folder with what I assume is a user-defined option on that other plugin. You then define("WPFC_WP_CONTENT_URL", $content_url);
So my problem is that left alone, cached assets always show as /wp-content/, even if you’re someone like me who may have changed the folder to something like /core/.
I can easily fix this myself by editing the WPFC and adding $content_url = str_replace(basename(WPFC_WP_CONTENT_DIR), "core", $content_url); above the define, but this os obviously not a good solution as it would revert on every update of WPFC.
What are your thoughts about this? In the next version, could you perhaps add a hook to set_content_url(), so that developers can override the $content_url var?