I will re-enable my workaround to not hurt the client’s website…
You can directly look into the file I mentioned since it it normal Enfold code. In my opinion some portfolio related code shouldn’t be in this file since the archive template is not portfolio specific.

Hi,
Maybe I found the cause of the problem that can be useful to find a solution.

Check please link in Private Content, and please tell me if you think there could be a fix in a next Enfold update.

Best regards,
Oriano

I’m concerned about all things but yes, I am currently primarily looking at speed. I use Google page speed insights, pingdom and gift of speed.
I feel like I’m rooting around in the dark with my plugin selection. There are so many things that show up in a feature list that also are in other plugins or the theme itself. I hope to avoid duplication and by extension bloat and conflicts. I am imagining the user base of this forum specifically has insights into what works well with Enfold. Most of the other information I find is generalized and not necessarily applicable to a feature rich theme like Enfold.
I am happy to say that I see no signs that Enfold has any barriers to entering the upper echelons of speed scores or core vitals. Aside from one glaring issue with a particular file type I’m getting high 90’s both on mobile and desktop with some relatively rich content. I’m going to start another thread as that specific issue is a bit of a gremlin I can’t offer an explanation for.
This thread is a more general question of what’s worked well In the past?

• This reply was modified 9 months ago by pdxammo.

Hi,

I did not specify it, but this footer display problem with Safari 18.3 on Mac M1 with Sonoma 14.7.3, I have it on all sites where I am using Enfold (I have several licences).

Please can you at least help me with a temporary solution?

Best regards,
Oriano

Hello Gunter,

I hope you’re doing well.
After updating the Enfold theme to versions 6.0.8 and 6.0.9, I encountered a fatal error when attempting to save a post type. The error message is as follows:

Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-meta-box.php on line 311

This issue seems to occur because $default_box[‘page’] is being treated as a string instead of an array. This results in in_array() failing, as it expects an array as its second argument.

Suggested Fix
To prevent this error and ensure compatibility, I recommend adding a safeguard to check whether $default_box[‘page’] is an array before using in_array().
Here’s a suggested fix for the issue:

if ( isset($default_box['page']) && is_array($default_box['page']) && in_array($data['post_type'], $default_box['page']) ) {

Would it be possible to include this fix in the next theme update? Please let me know if you need any additional details to reproduce the issue.

Thank you for your time and support!

We have resolved the issue. It seems that Enfold does not display all categories available in WordPress when the pagination of the ‘masonry’ module is enabled. In other words, if we limit the pagination to 12 portfolio items, the category filter will only show the categories associated with those items.

You can close this thread. Thanks! 😉

Hi Ismael, thanks for your help.

I entered your CSS in Quick CSS Theme Options, but this does not solve the problem.
See the screenshot

You may need to toggle or temporarily disable the Enfold > Performance > File Compression settings after adding the css.

• All Compressions are deactivated.
• I have also deactivated the cache plugin.
• I have also tried using Enfold parent. No luck.

Could you find someone on your staff who can do a test with Safari 18.3 on Mac M1 with Sonoma 14.7.3?

Best regards,
Oriano