Mej de Castro

Hi @spyrosfellowship,

Thanks so much for the feedback — glad to hear it did the job! If you ever need anything else, feel free to reach out.

Kind Regards,
Mej, LoginWP Team

Hi @taka1,

Thanks for your suggestion! We’ll forward this to our dev team as a feature request.

If there’s anything else you need, please feel free to let us know.

Kind Regards,
Mej, Widget Options Team

H i@taka1,

Thanks for updating to the latest version of the Widget Options plugin.

Since the in_category function is not included in the list of allowed functions
(https://widget-options.com/docs/list-of-allowed-wordpress-functions/), the filter you added in your functions.php file is required. Without it, the code won’t be allowed or saved in the Widget Options Snippets page, and it will result in errors.

We recommend keeping this filter active to ensure the in_category function continues to work correctly with your widgets.

Thanks and please let us know if you have any other quesitons.

Kind Regards,
Mej, Widget Options Team

Hey @krolyn,

Just following up to check if you’ve had a chance to see our previous message and test the latest version on your end?

Thanks, and looking forward to your update!

Kind Regards,
Mej, Widget Options Team

Hi Dear users,

Upon further investigation, it appears that Wordfence has not yet reviewed our patch for the previously reported vulnerability. Because of this, some security plugins may still flag the current version of the Widget Options plugin as vulnerable.

Once Wordfence publishes the updated patch review on their end, these security notices should automatically be resolved.

We’re still waiting for an update from the Wordfence team, and we’ll make sure to keep this thread updated as soon as we hear back from them.

Thanks for your patience!

Thanks for the update, @weblinkde.

We’re glad to hear the issue has been resolved.

If you run into anything else, please feel free to reach out to us again through our support threads.

Kind Regards,
Mej, Widget Options Team

Hi @weblinkde @tambaqui,

A new version has been rolled out. Please update to the latest version and let us know if the issue has been resolved on your end.

Looking forward to your updates!