Wordpress version of SC Pro and Contol Center do not work properly

Hello,After years of using SC Pro and Control Center for Joomla I decided to purchase a WordPress subscription. Unfortunately, it doesn’t work as expected. In fact, the Control Center very rarely works smoothly.Here are the main problems I encounter with the SC Pro:

1. After installing the SC Pro on the new site the status indicates that the firewall IS NOT enabled, even though it is. What I have to do is to disable the firewall on the main dashboard and re-enable it. Only then the extension status shows „Firewall enabled”.
2. I am not able to set the backend protection properly. No matter what I do, the status still indicates that the backend protection IS NOT enabled. That results in an overall security status at maximum 81% even though the password protection option is set correctly and works.
3. Generally, some WAF configuration settings and .HTACCESS protection changes DO NOT have an effect in the extension status. That includes: user session protection active, HTTP Headers Protection, disable server signature option.

As for the Control Center it is very sluggish. It assigns tasks without problems but the sites respond randomly and very often the process exceeds the time limit. The bulk task „refresh info” almost never refreshes all connected sites. Quite often I have to refresh sites manually one by one and even then they do not refresh properly.

Everything is quite strange because on the same server the Joomla versions of SC Pro and Control Center work perfectly ok.Would you have any suggestion what can cause such problems with Wordpress version?

At this point, I am reluctant to install SC Pro on any new pages and add then to the Control Center because instead of saving time I waste it when managing multiple sites.All the Wordpress sites run WP 7.x on PHP 8.4.Thanks for help -Simon

Hi Simon,

First of all, I'm sorry for the trouble and the time you've lost with this — that's exactly the opposite of what SC Pro and Control Center are supposed to give you, and I want to get to the bottom of it.

It's worth keeping in mind that WordPress and Joomla are completely different platforms under the hood — different hook systems, different APIs for things like the firewall/.htaccess handling and remote site communication — so the WordPress codebase isn't just a port of the Joomla one, it's a separate implementation. On top of that, the WordPress versions of SC Pro and Control Center are comparatively very young next to the Joomla ones, which have years of real-world use and refinement behind them. That's not an excuse for the issues you're seeing, but it does explain why the WordPress side still has rough edges around status reporting and the Control Center refresh that the Joomla side worked through long ago.

Could you send me a few things so I can compare against what I'm seeing here?

• The Control Center task logs (the ones covering the "Refresh info" bulk runs that fail or time out).
• The SC Pro logs from the "Control Center" section/option in the plugin settings, from one of the affected sites.
• The WordPress debug.log (wp-content/debug.log, if WP_DEBUG is enabled) covering both a fresh SC Pro install and a Control Center refresh, so we can line up timestamps.
• A screenshot of the full Security Status panel showing the 81% and which specific items are marked as not enabled (backend protection, session protection, HTTP headers protection, server signature, etc.).
• Whether your server runs Apache or Nginx (or LiteSpeed) — this matters a lot for the .htaccess-based protections, since they only apply on Apache/LiteSpeed and would never take effect on Nginx.

With those logs I'll be able to compare against what's expected on my end and pin down exactly what's going wrong.

Thanks for your patience, and sorry again for the frustration — I'll follow up as soon as I have something concrete.

Regards,
Jose

Hi Jose,
Thank you for casting some light on my problem.
I'm investigating it myself according to your suggestion.
When I collect all the necessary log files I will send it to you for inspection.
At this stage it looks the server runs both Apache and Ngix. LiteSpeed is unavalable.

Logs and screenshots sent by email.
Than you.