Carl France

Thank you Emma for the quick turnaround on this.

@abdulwahab610 I sincerely appreciate the time and effort you invested in identifying the issue initially, and I am grateful for the dedicated efforts of your lead developer in resolving the problem. Thank you.

@abdulwahab610 we have this issue on several sites where we had changed the image to repair the damage done when you released the version 3.0 update. This would lead me to believe that the issue might be rooted in the compatibility of the plugin rather than being site-specific.

To rectify the problem, we have taken the step of downgrading all affected sites to version 1.8. Subsequently, we were able to set and save the image (and, if necessary, the background image) with success. Afterwards, we upgraded back to version 3.0.1, and the functionality was fully restored, we are unable to change the logo or background image in version 3.0.1 as earlier described to you by me and other users.

As you have requested I have initiated a support ticket to address this matter. However, there seems to be a discrepancy in the resolution process. Your suggestion to create a temporary administrator user and share the credentials via email raises security concerns at our end. For obvious reasons, we refrain from emailing password credentials, and I’m surprised that this method is being encouraged by you.

In the interest of security, could you please confirm if there is a more secure method to provide the necessary access credentials for your use? We want to ensure the integrity of our sensitive information.

Additionally, I kindly request that you keep us informed about any upcoming updates or releases aimed at resolving the image-saving issue.

Thank you.

I have just uninstalled and reinstalled version 3.0.1 of the plugin, the background image has the same issue as the logo image, they show in the customiser but when saved they do not show on the login form, it shows the template background image and the ‘W’ logo, when the customiser is reopened it also shows the template background image and the ‘W’ logo.

If it assists the site is running on php version 8.0.28

@khoavo Thank you, I have used this plug in for a long time too on several client sites and have been exceptionally happy with it, this update has been disappointing, hopefully, as you say, the issues I still have will be fixed soon.

@khoavo – Thank you for the CSS although we shouldn’t need to apply that as it should have been fixed with the v3.0.1 update.

if you haven’t changed the logo since the v3.0.0 update then the originally logo remains fine, if you changed the logo then you will more then likely experience the issue I describe.

Version 3.0.1 has been successfully installed, and I have chosen the ‘Default’ theme; however, this has not entirely resolved the issue and has introduced a new problem.

The login form is currently positioned at the top of the login page rather than being centered vertically. Additionally, the problem with the logo persists, as mentioned earlier. When selecting a new logo from the media library, it seems to have been applied, but upon publishing, the logo is replaced with a default “W” logo. Upon reopening the customizer, the default “W” logo is once again displayed.

Likewise, I’m experiencing issues with the layout – images are not appearing within the form background. Even when the image is updated, only the default ‘W’ image is displayed. As a temporary measure, I’m disabling images on various client website login pages. However, if this issue isn’t addressed universally, I’ll have to consider replacing this plug-in with an alternative. It’s disheartening that a major update was released with fundamental functionality issues like this.

Please ignore, it seems this was a caching issue which is now resolved.

Thank you

It appears that cpGuard have now pushed out updated virus definition files and the issue is now resolved.

After a little bit of investigation, the file wordfenceClass.php was being downloaded each time but the file was being removed by cpGuard virus scanner.

Clearly a false positive but of concern that this should happen, we have lost over 15 WordPress sites this evening because of this, we have white listed the file now and are recovering them all.

Have done a complete delete and uninstall using WF Assistant and then a fresh reinstall and the same issue.

Another of my sites has also just upgraded automatically and the same issue on that site.

I have just checked and the include file wordfenceClass.php called by the line

require_once(dirname(__FILE__) . ‘/lib/wordfenceClass.php’);

Is not included within the ‘lib’ directory of the plugin.