Thank you very much! 🙂

Hi Anamaria,
thank you for the prompt reply and the assistance!
I followed your recommendation and used the live header search, problem solved!

For social icons, on reading your screenshot I eventually realized my problem is in the social icons that appear in the mobile menu (clicking on the “sandwich” top-left), as next to facebook and linkedin there there is also the email icon/link which is not in the social icons in the footer desktop version. I am looking in the theme/composer settings but I can’t find from where can I manage that menu. Of course I don’t mean the menu itself, I am trying to reach and manage those icons that appear just above the menu.

Regarding the other errors, I understand what you said regarding the design of the theme, although with the only addition of a free plugin I am using it’s scoring pretty high, just below the pass threshold.
Is there any way I can add some code to flex blocks so that the image too has a description attached to the link?

Again thank you so much for the help!
Paolo

Thank you for assistance.

Okay, here is what I tried, in sequence, but sadly it didn’t work…

1- deleted the theme and removed all plugins

2- ran a scan of the site and that came back clean

3- downloaded the theme full package from themeforest

4- uploaded it on the site and installed it again

5- ran the scan and found the same supposedly infected file

6- disabled and deleted the single plugin td-composer

7- ran the scan and it came back clean

8- manually uploaded the td-composer plugin from the one .zip file included in themeforest package and activated it

9- ran the scan and found the same supposedly infected file

10- deleted again the td-composer plugin

7- ran the scan and it came back clean

11- downloaded the td-composer plugin from within the theme’s plugins panel, hence straight from tagDiv cloud server.

12- ran the scan and found the same supposedly infected file

the scan returned the MetaBox.php file and virus signature {HEX}Malware.Expert.php.var.pattern.UNOFFICIAL

The tool I used is clam-av (the one available from my admin tools), the same my host uses.

I need the site running so for now I am just ignoring the file, I tried to quarantine it, but it breaks the site.

What would you recommend to do? Did I miss any step?

Honestly, I don’t know what to think…

@joema did you manage to get rid of your supposedly infected file?

thank you

I’m no programmer but it would make sense. On my part I haven’t had a single problem in nearly 4 months of use and now this shows up out of nothing.

My hosting did a second scan and still got a positive. I put contact@tagdiv.com in cc in the mail thread.

Hi everyone,
I am having the same issue here, I just searched the forum for MetaBox.php and found this fresh thread.
My hosting is emailing me similarly to @joema, that their scan has found some infected file(s), together with the info I paste below:

File path
/home/umuseooc/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/external/wpalchemy/MetaBox.php

Firma antivirus (antivirus signature)
{HEX}Malware.Expert.php.var.pattern

Last modified (which dates back to when I installed the theme)
2022-06-20 17:38:59

Quarantined status
no (which means my hosting doesn’t consider it such an evil threat)

I would be very grateful if you could sort this out.
I am happy to provide wp-admin access if needed. Let me know.

Thank you
Paolo

Hi Bettina,

thank you for your support, I tried to change the slug to “featured” but it didn’t revert to the original behaviour (hidden category etc..) then the category shows up as any other one.
Could it be related to the original category “id”? Would it be possible for you to provide me the default id category used in the original featured category?
Correct me if I’m wrong, I think I will be able to change the category id by editing the database from phpmyadmin, right?

thanks a lot!
Paolo

Hi, thank you very much for your help,
I was able to import the entire section from the cloud as you suggested.
Comparing that with my version I figured out what happened.
I had accidentally deleted the row with raw css that was positioned just above the slider (and that is of course what makes the slider look like it should).

Problem solved! Five stars support!

• This reply was modified 4 years by museooggi.