studioavanti

Yes, w3tc_minify was the field involved.
I cleared it in the DB, flushed W3TC cache as you recommend: it lost weight (980 Ko > 5 Ko) but it now continues to grow each time i visit a page on front-end.
I suppose each page has to be minified and it makes this field grow.
Is it W3TC standard behavior?

Hi helpers,

My issue is now solved.
In summary: since my recent updates of WP 4.9.6 and plugins, the minify content W3TC had to write in DB exceeded MySQL max_allowed_packet allowed by my shared hosting.
So it couldn’t be write and i finally got an empty minified CSS stylesheet.
This heavy content was reported in debug.log and made it grow up to 31 Mo.
My host provider increased the max_allowed_packet value and the W3TC minifying process is now running normally.

Please what do you think of this content weight W3TC generates for minifying: about 1.2 MB?

• This reply was modified 6 years, 6 months ago by studioavanti.
• This reply was modified 6 years, 6 months ago by studioavanti.
• This reply was modified 6 years, 6 months ago by studioavanti.
• This reply was modified 6 years, 6 months ago by studioavanti.

OK, you put me on the track, thanks.
Although this is a shared hosting, i think it’s correctly setup for WP.
And it worked well before i updated to WP 4.9.6 + updated some other plugins too.
My bet is one of them is no good for W3TC anymore.
I’ll check with the hosting company about the logs anyway.

I thought of switching to WP Rocket too as it’s reputed to be more simple to setup, but maybe i’ll find the same type of issues… so i continue digging into W3TC issue for the moment.

• This reply was modified 6 years, 6 months ago by studioavanti.

Hi,
Thanks for the details.

About checking the error log, i can not do it: first time i tried, the debug.log file was very heavy (31 Mo) and “unreadable” in a word processor or MacOS console software as it had no lines breaks… weird.
It didn’t load in WP Log Viewer plugin neither: infinite loading, no result.
I re-created the debug.log file that was just 4 Mo this time, but still unreadable: no line breaks…

About checking @import, i don’t find it in the theme stylesheets, but not sure it’s easy to do because i use a page builder (Beaver) so some stylesheets are dynamically created.

• This reply was modified 6 years, 6 months ago by studioavanti.
• This reply was modified 6 years, 6 months ago by studioavanti.
• This reply was modified 6 years, 6 months ago by studioavanti.

Hi,
Thanks for the tip.
Sorry, i’m not sure which main stylesheet i should check.
Do you mean check in original stylesheets (17 on this site), before W3TC try to minify them?
Cause there is nothing to check in the final W3TC minified stylesheet, it’s empty.
The website URL wouldn’t currently give you much, it’s a live site, i temporarly disabled minification so that it’s not broken by this issue.

Or maybe you mean check the @import method in CSS minify options?
I tried the 3, none worked: None, Bubble or Process.

• This reply was modified 6 years, 6 months ago by studioavanti.
• This reply was modified 6 years, 6 months ago by studioavanti.

Sure it helps, thank you!
I will try it then report.

Hi, thanks for your advice.
Would this potential error show in browser console or in error logs only?
If error log, i must see how to access it (don’t know for the moment).

This issue seems related to Ajax, the author recommends to disable it waiting for a Safari update:
https://www.ads-software.com/support/topic/file-uploads-on-safari-form-wont-submit/

For instance, you can put add_filter( 'wpcf7_load_js', '__return_false' ); to your function.php.
The page containing CF7 form reloads after the form is submitted, not so user friendly but it works.

I customized the filter to target Safari, it limits the removal of Ajax to this browser only:

function wpcf7_load_js_not_safari11() {
	global $is_safari;
	if($is_safari) {
		return false;
	} else {
		return true;
	}
}
add_filter( 'wpcf7_load_js', 'wpcf7_load_js_not_safari11' );

• This reply was modified 6 years, 6 months ago by studioavanti.
• This reply was modified 6 years, 6 months ago by studioavanti.
• This reply was modified 6 years, 6 months ago by studioavanti.
• This reply was modified 6 years, 6 months ago by studioavanti.
• This reply was modified 6 years, 6 months ago by studioavanti.

Hi,

same recent issue here with Safari 11.1: with or without any file selected, the CF7 fields validation process runs indefinitely (spinning arrows icon), preventing the form to be sent.
No error showing in browser console.
I first thought it was related to WP 4.9.6 and CF7 5 update and tested in many ways (including downgrade to CF7 4.9.2) until i found this thread, tried in Chrome and discovered it works fine!

I hope the author will be able to fix this…

Pablo, don’t be sorry, you fix faster than lightning, ??
PRO works now, thanks.

Hi Pablo,

Well done, it works now: your plugin renames the file AND let “WP Media Folder” rename the title.

Quick and efficient, thanks.
A lifetime unlimited sites licence for me!

Keep on going

[Update] Is PRO version fixed too (before i replace free version)?
[Update 2] Just tested, PRO version is not fixed yet.

• This reply was modified 6 years, 7 months ago by studioavanti.
• This reply was modified 6 years, 7 months ago by studioavanti.
• This reply was modified 6 years, 7 months ago by studioavanti.

Hi @karzin,

WP Media Folders support answered my ticket and seems to confirm that your plugin override their plugin during their media title renaming, if i understand well.

They say this:

WP Media Folder plugin used:

add_action(‘add_attachment’, array($this, ‘updateFileTitle’), 2); to format title but it overrided by File Renaming on Upload plugin.

I see File Renaming on Upload plugin used action:

add_action( ‘add_attachment’, array( $this, ‘add_attachment’ ), PHP_INT_MAX );

in ‘plugins\file-renaming-on-upload\classes\Options\General\class-permalink-update-option.php’ file

Hi @karzin,

Thanks for your answer, i understand your plugin focus on what it’s meant to do, and it does it perfectly!
Anyway, i may pay for a licence as it will be very useful on all my sites handled by clients (who don’t care too much about medias file name ;-).

WP medias titles sanitizing on upload would be a plus and complementary to medias file name sanitizing.
Currently, on my site, it should be handled by “WP Medias Folders” plugin. I just have to understand why this option is ineffective when your plugin is enabled.

• This reply was modified 6 years, 7 months ago by studioavanti.
• This reply was modified 6 years, 7 months ago by studioavanti.

Hi again,

I finally found a solution to fix TinyMCE Advanced broken icons in Beaver Builder 2: just copied the CSS below (part of R3DF plugin) in my theme’s child style.css. It did the trick, i could also disable R3DF plugin.

.mce-toolbar i.mce-i-table,
.mce-toolbar i.mce-i-emoticons,
.mce-toolbar i.mce-i-cut,
.mce-toolbar i.mce-i-paste,
.mce-toolbar i.mce-i-subscript,
.mce-toolbar i.mce-i-superscript,
.mce-toolbar i.mce-i-image,
.mce-toolbar i.mce-i-copy,
.mce-toolbar i.mce-i-print,
.mce-toolbar i.mce-i-anchor,
.mce-toolbar i.mce-i-visualblocks,
.mce-toolbar i.mce-i-visualchars,
.mce-toolbar i.mce-i-code,
.mce-toolbar i.mce-i-insertdatetime,
.mce-toolbar i.mce-i-media,
.mce-toolbar i.mce-i-nonbreaking,
.mce-toolbar i.mce-i-rtl,
.mce-toolbar i.mce-i-backcolor,
.mce-toolbar i.mce-i-searchreplace
{
	font-family: tinymce, Arial !important;
}

I did this on various sites and realized R3DF was effective on some sites, not others. All of them are running the same version of Beaver Builder 2.0.6.3, so i guess the issue is somewhere hidden.
But it’s simpliest now, one plugin less (that did help anyway ;-).

• This reply was modified 6 years, 8 months ago by studioavanti.

OK, thanks to you.