Hey Rikard,

Thanks for the very fast answer and sorry for the late reply.

This worked perfectly:)

Have a nice day!

Best regards,

Dessy.

Hi Mike,

Thank you for the suggestion. I tried it on the EN version of the site (dsign.bg/en) – enabled the preloader and added the code above to the quick css in the child theme. I cleared the cache multiple times, but the spinning wheel still shows on the single portfolio and blog post pages, and they’re back to loading for more than 5 seconds before displaying… Here’s an example: https://dsign.bg/en/portfolio-item/industrial-story/
Please find below a link to a screenshot of the Quick CSS on dsign.bg – the code is on top and everything is saved. You can also check via the logins provided above.

Maybe I’m doing something wrong?

Thank you or your support.

Best regards,
Dessi

Hi Ismael,

Thank you for the test. However, I’m not sure this kind of test is relevant to what the user experiences in different browsers.

Please find below a quick video of a side-to-side comparison of this page https://dsign.bg/en/portfolio-item/pastel-palette-on-the-last-floor/
On left I have Chrome, on right I have Internet Explorer. I hit F5 to reload both, first on Chrome, then on IE. You can see how the page on IE shows the main content in 1-2 secs and then gradually loads all the elements, and Chrome shows a spin wheel until all the elements are loaded… Note that Chrome sometimes behaves like IE, sometimes not. In Safari I get the same results as in IE.

https://drive.google.com/file/d/1_B8dhLLmzMCc02Q7_FLTvRzF3wrLMFxZ/view?usp=sharing

I’m not sure this particular behavior in Chrome/Firefox would be solved by a caching plugin or a general optimization… Maybe there’s some settings in the theme that I should toggle to get those pages always load like in IE/Safari?

Thank you for your help,
Dessi

Hi Yigit,

Thank you so much for the quick help!

I reviewed the site right after your intervention, everything seemed to be working fine. I was aware of the Instagram widget problem before the update – I was hoping that updating the theme/WP will solve it, but since it didn’t, I followed your post and it worked, although it was a bit tricky to make the feed look like your old widget:)
I also tested the backup plugins – they worked fine. I updated the 2 default WP themes to make disappear the red alerts, no problems there either.
I created a Personal token in the Envato site, it was verified successfully in all the child themes, hopefully next time I’ll be able to update the main theme from the WP Dashboard.
Finally, I did a bit of research about the PHP version, apparently WordPress recommends using 7.4 but in the same time their recommended plugin for PHP compatibility checks isn’t updated for 7.4 yet, so I was reluctant, but eventually decided to give it a go. The site seems to be working fine after this final update, I was also able to do backups with the plugins:)

I believe we’re done with the update process for the moment. I’ll continue with adding more content and optimizations. I’ll open another ticket if needed.

Thank you for your kind support and have a nice evening!

Best regards,
Dessi

Hi Yigit,

Thank you for your answer and for your kind proposal to update the theme, I’ll gladly take it!

I’ll create the temporary logins you requested and add it to the private area later, meanwhile could you advice what exactly I should do to prepare the site for the theme update? Should I first update WordPress itself, PHP and the plugins, and then let you update the theme? I also read that “cashing off” is recommendable, but I’m not sure at which step of the process it should be done and if it refers only to browser cache or to other things as well?

I guess that the very first step to do is to make a backup with the backup plugins:)

Understood about the Personal token, I’ll add it after the theme update in order to make easier future updates.

Thanks again!

Best regards,
Dessi

Hi Rikard,

This works!

Thanks a lot and have a nice day:)

Hi again,

I found a solution right after posting the above comment:)

It’s actually an answer from you in another thread on the forum that I’ve somehow missed on my first search:
https://kriesi.at/support/topic/how-can-i-change-the-word-all-for-the-portfolio-category-filter/

I replaced ‘avf_portfolio_sort_first_label’ with ‘avf_masonry_sort_first_label’ and it worked.

Apparently people are having trouble with this occasionally, so why not add it to the documentation at some point:)

Anyway, thanks again and have a nice week-end!