Hi there,
I will take a look, don’t worry.
Regarding your bonus question, could you please elaborate? I don’t quite get what you would like to ask.
I will take a look, don’t worry.
Thank you. BTW, I just installed the latest development version (3.4-beta2-20478) and it seems to have some other issues. π I guess we have to wait for the final release.
Regarding your bonus question, could you please elaborate?
Happy to.
First of all after my post here I went on and installed and network activated BWP Minify on a test multisite and seems to work fine for mapped domains as well. π
There is something else I noticed though on the multisite while logged in as an admin and NOT as super-admin:
Under Minifying Options we read:
Cache directory (double-click to edit):
/home2/mainsite/public_html/wp-content/plugins/bwp-minify/cache/
Important: Changing cache directory is a two-step process, which is described in details here. Please note that cache directory must be writable (i.e. CHMOD to 755 or 777).
(Don’t these settings affect ALL blogs/sites on the network? If so, what happens if every admin decides to change it to something different?)
I don’t think I would like any of my 200+ different admins to first of all know where exactly on my network the folder is located. After all they have no access to the File manager or my control panel.
Second of all (for mapped domain admins) this would only be more confusing since they would expect something like
/home2/mappeddom/public_html/wp-content/plugins/bwp-minify/cache/
And in any case I most certainly don’t want anyone else start messing with that setting and changing the url to
/home2/mainsite/public_html/wp-content/ or even
/home2/mainsite/public_html/wp-admin/ or wherever.
As a conclusion I believe these URL settings should ONLY be available to super-admins. π
Thank you for your time,
marikamitsos
Oh, that’s actually a bug, the cache directory setting should only be set by super admin, what you said was correct :). I will release a fix (1.2.1) addressing this bug and some incompatibility issues with 3.4 soon.
Oh, that’s actually a bug
Glad we found it π
I will release a fix (1.2.1) addressing this bug and some incompatibility issues with 3.4 soon.
That’s great. Looking forward to it.
Just letting you know…
When having “Minify JS files automatically?” unchecked it produces NO conflict.
I have already upgraded to wordpress 3.4-beta3