Peter Smits

After the update to Versie: 1.0.0.7 this error is still present
After installing the missing webfont into the “fonts” folder, the error is gone

Hi,

I am running on all latest versions of WordPress and PHP

Hi Michael, there is no confusing on my site. Have a look at the link I showed you. The theme is calling “fonts” instead of “webfonts”. This happens on every site where Fameup is installed. It generates 404 errors listed in my All in One Security add-on.

Hi Michael,

Thanks for your quick response. I have several sites where Fameup is installed. They all show this error in the developers console. It shows up when I am opening the Admin screen. So it is not shown visually on pages visited. Those sites are all running on the latest WordPress version, and on PHP 8.1

With latest version this issue is still not solved

Thanks for your information, I will test your solution

I am having the same problem, and can also not login with this plugin active. Even worse my home IP gets banned

Alan, the translation is working fine regardless of the indication “this plugin is not properly prepared for translation”

So everybody can propose text improvements if they find something wrong

However It does not look good such an error. It could cause people not to use the plugin

Thanks will download and install this patch

Then you need to find out what has changed in your installation. I know there has been a security update from WordPress. Did you update other parts of the site? E.g. perhaps a country blocker that prohibits access. You need to check the settings from your plugins to find which plugin generates the warning.

Hi, I think you have a permissions problem. The admin has a higher rol then someone that is at your frontend. If a user has to login before submitting, you need to check the rol this person has. If the rol does have upload permissions, then you need to check your folder permissions, where the user images are stored

• This reply was modified 1 year, 1 month ago by Peter Smits.

here is the confirmation that it is a WordPress core problem

WordPress 5.9 and PHP 8.0-8.1

Maybe this gives a clue what needs to be done to prevent the warnings

@mattinventive when testing with 8.1 and 8.2 the result was the same. Even without MLF I get the error when going into menu “articles” for instance. So this is caused by WordPress or theme used. Going back to version PHP 8.0 resolves the error message. The message do not indicate which project causes them. MLF is working fine regardless of the errors, nor do I get problems anywhere else.

Hi winspeed,

That is normal behavior as it is part of the package. You do not need to activate it. You only need it if you need to reset the database belonging to MLF if it is corrupted.

Thanks that is something I did not test, as I normally select one, and see the results for the others with the same IP.

Glad that it has been reproduced