Nevermind! you can close this thread. For some reason custom.css wasn’t saved with the update, so after uploading a backup of it everything is fine. Not sure if you want to log that as an issue to fix but this workaround solved it for me.

Thanks!

Nevermind! This was the same issue as:
https://kriesi.at/support/topic/images-in-gallery-not-arranged-correcty/

If you guys figure out what the issue was and fix on your end please let me know so I can switch my galleries back to their previous sizes. Thanks!

Hi Nikko, just following up on the above to make sure before we close this thread – you mentioned some other elements missing? What were these, so I can make sure my site post-update is the same as it was before? Everything other than the backgrounds visually seems to be ok so just making sure I understood what you were referring to. Thank you!

Hi Nikko,

Yes it’s weird as we’ve never had this update issue before. What you saw on staging was a fresh clone of our live site pre-update and then I updated via ftp.

I’ve gone ahead and created a fresh pre-update install for you to take a look at, please see url and credentials in private section. I just removed enfold credentials from the dashboard in case it would conflict with the new token I inputted on my live site (so you won’t see an update prompt), but you’ll see 4.4.1 is the version currently active on this install.

You can go ahead and update via ftp and see what happens. You’ll see that even if overwriting our custom.css (so the issue you pointed out with the grey background image shouldn’t apply), the image backgrounds in both types of sections disappear and revert to just solid grey and black respectively. Even though after update the images are still showing in the dashboard UI settings modals they do not show on the front end unless each one is deleted/re-added individually.

Again, if you don’t know why this happened I have been able to work around it but it does take a lot of time so in case this happens again on the next update or if someone else has the same issue it would be great to log a better fix here. Don’t spend too much time though as I know you must be very busy.

Thanks so much!

Best,
Jonathan

No worries, Nikko. And thanks so much. I wanted to update the site this past weekend so I took the time and went through all background elements and removed/readded them. That seemed to solve the issue – it took a bunch of time but it seems ok now.

I left the issue live on staging to see if you know why those didn’t retain properly with the update in case an easier/quicker way I should know how to fix for future updates or in case something for you guys to fix in the theme. Please do take a look and let me know in that thread either way! Thank you and you can close this thread.

All the best,
Jonathan

Hi guys, just an update – this is fixed by going to each content section and removing/re-attaching each background image. Is this a known issue with this upgrade? Is there a quicker way to fix this than to go through the entire site section by section? Thank you for your time as always!

Best,
Jonathan

Hi Nikko! Thanks but I think there was a misunderstanding. Sorry my question was regarding the latest update instructions to 4.5 it says not to use the dashboard. My question was is it at all possible to do through the dashboard still or not for this version? I see the update prompt so was wondering if it’s ok to try or if this can cause issues, or if it just doesn’t work at all.

I ended up setting up a staging site and trying but I just couldn’t get it to download so I’m assuming it just won’t work that way and that’s why we need to do the other ways though. Please let me know if that’s not correct, otherwise you can close this thread. Thanks!

Hi Rikard, this worked perfectly. Thanks so much!

Hi Ismael,

Thank you very much. That seems to have worked! So just to confirm that it was right for me to have added in “$images, $post_id” between the brackets and that I implemented this all correctly so it doesn’t negatively affect anything elsewhere – all I did was added the below code (based on our discussions above) into functions.php via a script management plugin. If that is what you intended and the below code looks good then please confirm and you can go ahead and mark this resolved. Thank you so much :)

Hi Ismael,

That worked! Thank you so much. It seems like I need to use the code Yoast provides still to alter the post sitemap image urls, and the code you provided alters the page sitemap image urls. Oh and to answer your question why I want to change these it’s because with a cdn google doesn’t index the images correctly if the urls aren’t changed in the sitemap to point to the cdn which is where the html in the page is referencing. So very important to be able to do, and thank you :)

Two final questions if you don’t mind:

1) Does the code you provided only alter the image urls in the page sitemap, or is there an impact anywhere else I should be aware of?
2) Is there a script I can add to functions.php that will have the same effect of what you provided above? The reason I ask is because I manage my functions.php scripts in a plugin so that they aren’t overwritten on theme updates. It would be nice to be able to affect this change through there if possible.

Thank you again. You guys are seriously amazing.

Best,
Jonathan

Hi Yigit,

Thanks so much – yes of course please see below!

Best,
Jonathan

Hi guys, just following up on this. Thank you very much in advance as I know may take a bit of your time but I think it’s important we have a solution here for all users to benefit from when needed.

Thank you!

Best,
Jonathan

Perfect, thank you!

Hi Mike,

Thank you for looking into this! Unfortunately that doesn’t seem to have done the trick. Do you know why it might not be working? Please feel free to go into the staging site and try this out, it’s currently implemented how you’ve said but the page sitemap urls didn’t change, except for the one test page that’s not using avia elements.

Login info in the private section below.

Thank you so much.

Best,
Jonathan

Hi Victoria,

There is a chance this is an issue with how my cdn provider is pulling from the theme, as I’ve excluded .css and .js from the cdn and that (at least for now) fixed the issue. I’ll keep an eye on it and will let you know if it re-occurs. I will also update with the findings by my cdn provider.

Do you have any reason to believe there is an issue with how enfold works with https and/or cdn setups though that could be causing this? Any reason .js and .css may be called sometime as unsecure content?

My install is just a regular enfold install, only css changes with custom.css, but nothing else. So perhaps you can inspect on your install first before needing to go into mine. It is a live business website so I prefer not to give out access unless/until necessary. Thank you for understanding. Please let me know, thanks!

Thank you for your time.

Best,
Jonathan