zuoothomas

I put the two files in a differencer myself, and spotted the difference at the same place that google console spots the error:

https://ibb.co/R7gDmbR

The regex messes something up at that part of the code.

Hey,

Alright, that clears it up.

Here is a wetransfer link to the two js files and screenshot:

https://we.tl/t-BVkRtI5LBD

Let me know if it works!

Thomas

If you can comment that line out (prefix a # before it) and test it again, and if it works, let me know.

Commenting out that line makes it work! So that is probably it then?

The differences between 2.8.3 and 2.8.4 are very very minimal.

Do you mean between 2.8.2 and 2.8.3? That is where the issue started.

Thanks for all the other information. I’ll check it out for a second and if I can’t figure out anything unusual we’ll just use the ignore list.

Thanks for all the help!

Hey Raul,

Sadly the new update (2.8.6) did not fix it. Again, only when putting frontend-builder-scripts.js on the ignore list the error goes away.

Strange that you can’t reproduce the error on your side. I just installed FVM on a fresh Divi site and again version 2.8.2 did not give any error but starting from 2.8.3 the error occurs.

This makes me think how this could be a server side issue. If you need anymore information, let me know!

Btw, I also noticed “/wp-content/themes/Divi/core/admin/js/react-dom.production.min.js” is not on the ignore list anymore, any reason why?

BTW, i see on the changelog of 2.8.4:

added frontend-builder-global-functions.js to the list of minification exclusions, but allowing merging

but it is not frontend-builder-global-functions.js that is causing it but frontend-builder-scripts.js

Hey,

Thanks for the quick reply.

If disabling minification fixes it, you have confirmation that it’s a minification issue, which is basically PHP Minify action on top of merging it.

Disabling minification did not fix it for me, only completely disabling merging or putting the file on the ignore list fixed it for me.

Thanks for the tip of downloading older versions. I tested a few version multiple times and it seems like version 2.8.3 is when the error started happening. On 2.8.2 i do not get the error.

The thing is, I still have a website running an old version of FVM. I’m not having the error on that website. So I have no idea what happened in between updates of FVM that is causing the error. On that old version of FVM it merges and minifies frontend-builder-scripts.js without any problems, while running the same version of Divi (and every other plugin).

So it must be something from one of the updates of FVM that changes the way it behaves around frontend-builder-scripts.js.

I know they are still assumptions but to me personally, that sounds logical to me.

Thanks for pushing out the new update, it sounds like that would’ve fixed it.

But for some reason the error just doesn’t want to go away. I cleared all possible cache there is, leave the status tab of FVM open on one screen (with no processed js files). Then i open the website on an incognito browser, and see a newly created footer.min.js file created. The filename (including all hash code) matches the file giving the error.

Turning off javascript minification does not get rid of the error. “Disable javascript processing” does get rid of the error, same with disabling the plugin.

Opening the log of the footer.min.js i still see /wp-content/themes/Divi/includes/builder/frontend-builder/build/frontend-builder-scripts.js on the list of processed items.

if I put that file on the ignore list it also fixes the error but then it obviously is not merged.

Sorry for taking so much of your time, I really don’t want to switch to an alternative as FVM has been the best experience so far!

Thanks in advance,
Thomas

Hey man,

Weird..I don’t see anything that could cause double minification. Divi did not add anything new or something.

Also disabling minification of js files does not fix it. Could it be something else?

Thanks for the response!

EDIT: Hey man, it has something to do with version 2.8.2 or 2.8.3 of FVM. I just updated FVM on a site that didnt had the error (running 2.8.1) and as soon as i updated the error started happening.

• This reply was modified 4 years, 11 months ago by zuoothomas.

https://simple-membership-plugin.com/giving-wordpress-admin-user-access-protected-content/

• This reply was modified 5 years ago by zuoothomas.

Yeah it seems like there are quite a few scripts loaded manually and not via the enqueuing. Just cache enabler but that plugin is compatible with FVM right?

Guess that’s just what it is then.

I do have another question:
In the FAQ it states that when you notice multiple header or footer files being created i should put the files in those footer files on the ignore list. (Whenever you see a duplicate). Is this correct. I think it would mean putting around 20 js files in the ignore list. Doesn’t really feel like that is going to help haha.

Let me know!

• This reply was modified 5 years, 4 months ago by zuoothomas.
• This reply was modified 5 years, 4 months ago by zuoothomas.

I almost found a workaround by making a custom data column and manually typing in the dates but then i can’t sort properly on it because it sorts it like a string and not like a date.

Ah okay! I used WP PSB for the gzip compression, did not know it interfered with fvm. What way of gzip compression would you recommend in combination with FVM?

Thanks for the help,
Thomas

yes i was! thanks for asking ??