[mmr 1.6.11] How to use custom js and css cache url?

Hi Virgodesign,

Is your define a typo? It looks like your defining the CSS constant twice?

If you are going to specify a seperate location for CSS and JS then you will need to specify the server path for MMR_CACHE_DIR as well as absolute URL for MMR_JS_CACHE_URL and MMR_CSS_CACHE_URL

Hi,

I’m sorry, I did a copy-paste typo error in the above post.

My running configuration is

define('MMR_JS_CACHE_URL', MMR_CACHE_URL.'/js');
define('MMR_CSS_CACHE_URL', MMR_CACHE_URL.'/css');

I’m using the default mmr cache path, as defined in MMR_CACHE_DIR.
Even if I define a custom path, the issue should remain, because custom urls point to a wrong directory. Or maybe I’m missing something?

Thanks again.

• This reply was modified 8 years ago by virgodesign.

Hi,
could you provide an example on how to setup properly custom js and css urls?

I’ve defined constants as following:

define('MMR_CACHE_DIR', WP_CONTENT_DIR.'/mmr');
define('MMR_CACHE_URL', WP_CONTENT_URL.'/mmr');
define('MMR_JS_CACHE_URL', MMR_CACHE_URL.'/js');
define('MMR_CSS_CACHE_URL', MMR_CACHE_URL.'/css');

Thanks in advance.

When you specify MMR_JS_CACHE_URL and MMR_CSS_CACHE_URL then MMR_CACHE_URL becomes unnecessary.

MMR stores css and js together in one folder (specified by MMR_CACHE_DIR). MMR_JS_CACHE_URL & MMR_CSS_CACHE_URL were added so you could use a different url on a CDN.

Currently you can’t tell MMR to store JS in a different folder to CSS. I’m thinking I could add this without too much fuss. Maybe I create a MMR_JS_CACHE_DIR and MMR_CSS_CACHE_DIR. What do you think?

Here is how to use the current setup:

define('MMR_CACHE_DIR', '/var/www/sitename/public_html/cache'); //absolute path to where the mmr cache is stored
define('MMR_JS_CACHE_URL', '/'); //eg. https://js.website.com/ (setup as a subdomain to /var/www/sitename/public_html)
define('MMR_CSS_CACHE_URL', '/'); //eg. https://css.website.com/ (also setup as a subdomain to /var/www/sitename/public_html)

Hi,
thanks for the reply and sorry for the delay, I think that storing css and js files in different folders could a be nice solutions. People can better choices how to organize assets.

Another suggestion could be, the ability to choice if delete or not the mmr dir after plugin deactivation. I think that people should choice if delete or not the mmr folder when plugin is deactivated. For example, If you set a custom mmr folder, suppose “/cache”, and you use even for other pourpose with other subfolders and assets, you won’t delte this folder if you deactivate for any reasons mmr plugin.

In my opinion could be very useful the following choices:
– choose where to store js, css, and log files (separately).
– choose if delete or not directory in plugin deactivation.
– choose if use cron for creating files or process them instantly.

If the purpose of the custom urls is for using them in a cdn, this could be explained or suggested in plugin doc as this could not be always clear, of people could get confused on how to use this.

Anyway I found mmr a great plugin. Congratulations!
It’s very very powerful. I use it in a large network in a dedicated server, toghether with w3tc, and I manage the minify process ONLY with mmr. it’s absolutely error free, it respects perfectly scripts orders and position and it is perfect for browser caching, due to the fact that as soon as you edit any js or css file, the resulting minify-merged file changes its name. And this force browser (with or without browser caching) to reload the resource without serving users an old version.

Last, but not least, adding the html minify feature would complete definitely the plugin functionality.

Thanks again!

• This reply was modified 8 years ago by virgodesign.