Zach Charo

Hello!
I’m also a support representative from Pressable.
It seems that SPL checks to see if the BWP_MINIFY class is defined in order to determine if the plugin is installed.
We actually prohibit the installation of BWP Minify on our hosting, and we define the BWP_MINIFY class as part of the measures we’ve taken to prohibit its installation.
This is why SPL is indicating that the BWP Minify plugin is installed when it is not in fact.
This said, we offer a lot of features that are also offered by plugins such as SPL.
And if your site is performing slowly, our support team will be happy to look at it to identify any slowdown problems, as well as offer solutions.
You can email us at help(at)pressable.com
-Zach C.

https://zlau.net/wp-content/uploads/2018/02/Screenshot_27.png

You *shouldn’t* need to add that section in the first place. I’ve never needed to in any child theme I’ve created.

In either case, the “theme_enqueue_styles” function must have already been declared in the parent theme, so definitely no need to add it here.

Most child themes are able to import the parent theme data without that snippet of code anyway.

Are you sure that the malware has been completely removed?
If you missed some of the malware, or mistakenly deleted a core file, that can cause an error to occur.

What method did you achieve the removal with?

Also, I can see that you don’t have wp-slimstat installed.
I would look for a similar coding issue in your active theme and plugins.

If I may interject:
I was having this same issue on a site I was working on today.
This site had a plugin installed called “wp-slimstat”. This plugin appears to have a coding issue in /wp-content/plugins/wp-slimstat/wp-slimstat.php on line 1. It has “var_” just before the php tag.
Like below:

var_<?php
/*
Plugin Name: WP Slimstat Analytics

It should be as follows:

<?php
/*
Plugin Name: WP Slimstat Analytics

I edited the file in a text editor, and it fixed it for me.

Thanks,
Zach