mark_m
Forum Replies Created
-
Forum: Plugins
In reply to: [Imsanity] Error: (Resized image was larger than the original)Thank you for your very clear explanation!
I thought the error was about the size in pixels, which would be a strange error message, but now I understand it’s about file size. Very smart that Imsanity is chacking this before resizing.Oh yes, I will remove the Bulk Resize Media plugin and use Imsanity again.
Forum: Plugins
In reply to: [Imsanity] Error: (Resized image was larger than the original)Even after installing ImageMagick on the server I’m still having the same issue as Frontman had with Imsanity: ….resized image is larger than the original….
Imsanity has always been working very well on my server, but since a while it doesn’t. Could it be that something is wrong with your plugin? Should it work well with PHP7 ?
I found found another plugin, called “Bulk Resize Media” by Marty Thornley which looks like Imsanity, but this plugin can resize my images without any problem.
Ok, clear answer.
Thank you very much.
Mark
Handoko, thanks for your tips and recommendations! I will experiment with them.
At first I thought I had to do some settings per site, but after all that isn’t necessary.
Now I have set the login page hidden and that work ok for the main site, but when I try to open the login page of a domain mapped subsite it doesn’t work.
It looks like CSS isn’t loading well and when I fill out username and PW I can’t login.
This is why I thought there should be per-site settings. The code in the .htaccess for hiding the login page only affects the main site, but (in my case) messes up the login page for subsites (with domain mapping).
I think I have to insert the code in .htaccess by hand for hiding login pages other than the login for the main page.
Does anyone know more about this?I have the same problem with WP 3.5.1 multisite and Better WP Security 3.4.8.
Does anybody know how to solve this, so I can activate the plugin for all sites and not only for the main site?
Forum: Plugins
In reply to: [W3 Total Cache] [Plugin: W3 Total Cache] DONOTMINIFY constant is definedThe problem seems to be solved here now.
After I updated to the latest version 1.2.8.3, I deactivated the very annoying tracking option and flushed all caches. When I checked my site the DONOTMINIFY code was gone.
I’m not shure it has to do with deactivating tracking or with just the latest update.
I hope that all of you will get it fixed soon too!Forum: Plugins
In reply to: [Yoast SEO] [Plugin: WordPress SEO by Yoast] Yoast , You Broke W3Total CacheThe problem seems to be solved here now.
After I updated to the latest version 1.2.8.3, I deactivated the very annoying tracking option and flushed all caches. When I checked my site the DONOTMINIFY code was gone.
I’m not shure it has to do with deactivating tracking or with just the latest update.
I hope that all of you will get it fixed soon too!Forum: Plugins
In reply to: [Yoast SEO] [Plugin: WordPress SEO by Yoast] Yoast , You Broke W3Total CacheSame Same to me seriocomic.
No problems to other sites with those plugins………not yet?Forum: Plugins
In reply to: [W3 Total Cache] [Plugin: W3 Total Cache] DONOTMINIFY constant is definedSame Same to me seriocomic.
No problems with other sites with those plugins………not yet?Forum: Plugins
In reply to: [W3 Total Cache] [Plugin: W3 Total Cache] DONOTMINIFY constant is definedI’m running WordPress SEO by Yoast too.
Indead, when deactivating that the DONOTMINIFY disappears, but it comes back when I reactivate it ??
Let’s go to the WordPress SEO forum and hope Yoast will fix this soon.Forum: Plugins
In reply to: [W3 Total Cache] [Plugin: W3 Total Cache] DONOTMINIFY constant is definedOh yes, I have to add this:
WP v3.4.1
W3TC v0.9.2.4
and my theme is an older modified version of the Roots theme.
I only have troubles with minification, not with caching.
On another site with the same theme I have no problems.