Tom

Yes, I believe so to. Sorry for this ticket.
And thanks!
Best, Tom

Hello Till, yes, it still persists after disabling. So it seems not being caused by Redis. 80% of the log lines has “POST /?wc-ajax=get_refreshed_fragments HTTP/2.0″ 200 0” in it.
Best,
Tom

I have the same issue. Rolled back to 1.0.7 and it works again.

Hello team, we got the same issue. When will this issue be picked up?
Best, Tom

Hi Eugene,

It seems it took an hour to get them green without further action.

Thanks anyway.

Best,

Tom

• This reply was modified 7 months, 3 weeks ago by Tom.

Hello Oleg,
When will this be released?
Best,
Tom

Yes, with this setting the problem stopped here

You’ll find it under Avada > Options > Performance > Combine Third Party CSS Files. If you don’t see it, turn on CSS Compiling Method > File

Hello,

I deactivated 3th party combine in Avada (adviced by Avada Support) and the problem is gone.

Best,
Tom

Hello,

I have the same issue on a website. It happens when you press +1 on the fly cart. It happens on multiple devices. I deactivated the cacheing plugin.
I do also have this issue on Mobile Chrome.
I rolled back version 5.5.6 to 5.4.2, but still the same issue.

• This reply was modified 1 year, 6 months ago by Tom.

Hello,

Thank you so much, that worked great! The fields are now visible in the mails.

Best,
Tom

Hello,

Super, this works great!
Thanks!

Best regards,
Tom

Hello, thanks for your reply. Very nice!
I tried it and see a “Export FooEvents” option on the bottom.
After checking this I get lines like these in the first column. How can I solve this, and get this in columns?

a:1:{i:1;a:1:{i:1;a:21:{s:26:"WooCommerceEventsProductID";s:5:"66595";s:24:"WooCommerceEventsOrderID";s:5:"72767";s:27:"WooCommerceEventsTicketType";s:0:"";s:23:"WooCommerceEventsStatus";s:6:"Unpaid";s:27:"WooCommerceEventsCustomerID";s:1:"0";s:29:"WooCommerceEventsAttendeeName";s:0:"";s:33:"WooCommerceEventsAttendeeLastName";s:0:"";s:30:"WooCommerceEventsAttendeeEmail";s:0:"";s:34:"WooCommerceEventsAttendeeTelephone";s:0:"";s:32:"WooCommerceEventsAttendeeCompany";s:0:"";s:36:"WooCommerceEventsAttendeeDesignation";s:0:"";s:27:"WooCommerceEventsVariations";s:0:"";s:28:"WooCommerceEventsVariationID";s:0:"";s:22:"WooCommerceEventsPrice";s:129:"€29,95";s:35:"WooCommerceEventsPurchaserFirstName";s:6:"Nameclient123";s:34:"WooCommerceEventsPurchaserLastName";s:8:"Last Name123";s:31:"WooCommerceEventsPurchaserEmail";s:25:"nameclient@hotmail.com";s:31:"WooCommerceEventsPurchaserPhone";s:9:"06123456789";s:37:"WooCommerceEventsCustomAttendeeFields";a:11:{s:37:"fooevents_custom_ilnymcstkqbtuqwfbnds";s:6:"Jongen";s:37:"fooevents_custom_pbduqvun3u923umzhhojv";s:2:"10";s:37:"fooevents_custom_cxvervrvo3unv93un4v9ui3n4fiti";s:8:"Februari";s:37:"fooevents_custom_l4ve3f34f34fsdfc3wfpubin";s:4:"2010";s:37:"fooevents_custom_wavfjgrodvnomjlmhjht";s:5:"NameChild";s:37:"fooevents_custom_fkuaznuzetiwekdrljad";s:2:"De";s:37:"fooevents_custom_ttqrrnnxkfmtqdjlxvlg";s:5:"Lange";s:37:"fooevents_custom_lcqgqdlexvqgbvvcomfa";s:9:"Location123";s:37:"fooevents_custom_owfqydesveuexfqyyqpo";s:6:"Speler";s:37:"fooevents_custom_jnrrverv34vzlmrrerv";s:0:"";s:37:"fooevents_custom_regskt4f34f3wlbnvbrz";s:0:"";}s:30:"WooCommerceEventsSeatingFields";s:0:"";s:31:"WooCommerceEventsBookingOptions";s:0:"";}}}

Thanks, and I see WP_MEMORY_LIMIT is for the frontpage processes and WP_MAX_MEMORY_LIMIT is for backend.
I will mark this topic as solved.

Best, Tom

Hello Jason, thank you for your reply.

if I set it to:

define( 'WP_MAX_MEMORY_LIMIT', '8224M' );

will this make I use max 8gb of the servers total of 12gb? And when I when it to 2048, will this make 10gb unused?