Ok perfect. Will do, thank you!

You’re awesome! Thank you so much. You can mark as resolved.

Hi Elliott, I did the following only and it seemed to work. I ignored the earlier parts of the thread you referenced. Please confirm that this is all I needed to do, thanks.

The only file I’m editing is /enfold/framework/php/class-framework-widgets.php and I’m replacing

$content = mysql_real_escape_string($content);

with

$content = esc_sql($content);

Is this correct? I didn’t change anything in functions.php as mentioned earlier in your referenced thread.

Thank you!

Nevermind, I found the issue! In case anyone else has the same problem – it looks like the theme update caused the “google maps widget” to move from the “googlemaps” box to the “social media sharing” box in the widgets tab. I just moved it back into the appropriate widget box.

Any idea why this moved with the update? Is it ok to just move it back?

Hi Yigit,

Sorry but you misunderstood the question! I am asking if it’s ok to update to WP v4.2.2 if I’m using Enfold v3.0.4? I am not yet ready to update Enfold as it’s causing issues for me that I’m still working through.

So is it ok to update to WP 4.2.2 but still run Enfold 3.0.4?

Thanks,
Jonathan

Thanks all, will do! Also, you can go ahead and mark this as closed as most issues were resolved. If there are still any issues after trying with the latest version I’ll open a separate ticket for each one. Too many in here now anyways so I’m sure confusing for everyone :)

Thank you for the continued amazing support!

It might not happen right away – but definitely after minimizing, or going to another window it happens. If you can’t reproduce then don’t worry as obviously a lower priority.

Regarding the maps issue – any idea why after the update the maps widget doesn’t work anymore, and now I need to use the map element? They are two slightly different maps and I’d prefer to use the one I was using before if possible as that also has street view on it. Any idea what changed this with the update?

Sorry to bug you guys on this – do you have any idea what content is overflowing into the footer with the update that wasn’t before? I think it may be causing issues with the testimonials occasionally not appearing.

Specifically, if the window is minimized in safari and then gone back to, the testimonials do not show. I’m wondering if the content in the footer that the overflow css fixed is what’s blocking this and the maps widget also (before I changed to the maps element).

Any idea what the new page content introduced with the upgrade is? I think all three issues here may be related?

Thanks!

Thanks Rikard. I would like to keep the maps implementation as is though – any idea why it doesn’t work within the widget area? Is it possible to use the overflow command shown above in a way that will cause this to appear too?

Thank you, that works now – but I am still having the issues with the logos at the bottom of the page. Any idea why this is happening after the update? Both the google maps and the logos. Perhaps if we figure out why the logos aren’t showing correctly then I can continue to use the maps widget as it was before and not need to change that either.

Really appreciate your continued help on this.

Hi Ismael,

Thanks for looking into. I deactivated all plugins, and then the Google Maps element area wasn’t expanded even. So I went ahead and just activated the plugins that seem to be needed for the google maps element to function and for the footer images and text to show:

– bbPress
– Image Widget
– Simple Rich Text Widget

Everything else is deactivated. I also went ahead and removed and then re-added the widget area.

It is most certainly a theme issue as this problem only starts with the upgrade.

Thank you for your continued assistance on this!

Best,
Jonathan

Will do, thanks! I’m still waiting to hear from the script developer.

Hi Elliott,

Thank you for looking into this. It’s definitely the custom script as the problem only happens with it – that’s why I reached out. I’m trying to have the script work.

It is definitely a theme issue as it doesn’t happen with the default theme. Only enfold. Any idea how to get around it? It seems that the script doesn’t see itself as being on the right domain. Weird that it’s only when within enfold though.

Thank you for continuing to look into this.

Best,
Jonathan