nicegamer7

Actually, to be honest, we might just start using one of the the remaining photo services that are already integrated into Photonic.

I see, that makes sense. I think there are maybe some solutions such as caching in the DB and asynchronous calls, but this would require time and effort to implement and might not be worth it in the end. Would you be open to a contribution if I ever come up with something like that? Or maybe it could be a add-on plugin of sorts.

Also regarding the changes to the API, you reminded me, I wanted to ask you what exactly this means for the plugin. Just for clarification, is this the change that’s supposed to take effect on March 31, 2025? I got an email about a month ago about this and I wanted to ask you about it.

Thanks for getting back to me. Your comment about {+thumbnail_url+} being extracted from {+link+} helped me out.

I found that I had a filter on wp_get_attachment_link that was affecting MLA.

Thanks a million!

While I understand the feature may be useful, you must understand the author’s point of view.

The author maintains several plugins, each of which are extremely popular and used on many WordPress sites. Adding more features makes the plugin more difficult to maintain, and possibly more complex. Additionally, the author provides these plugins and support for them free of charge, and most likely in his spare time.

Regardless, since I need this feature, I planned to make an addon plugin that will do this. Once I finish, I will publish it and let you know.

Thanks for getting back to me.

While you are correct that when the WAF is optimized, the rules will be updated before anything else runs, that is assuming that the rules are to be updated on that day. For example, take the free version of Wordfence. Rule updates happen at most once a week. If you miss the threshold (which I believe is set to 2 days), you’ll have to wait for the next week for them to be updated automatically.

Even though this is not ideal, this is the best that can be done for sites that are not using their server’s cron. But for sites that are using their server’s cron, it would be beneficial for them if an option was added to Wordfence to use WP Cron, since it is guaranteed to be run periodically, and therefore there is no need to run these jobs for every visitor.

Also, please consider that there are sites that are set up to run WP Cron periodically without a web request. In this situation, the site would again benefit from an option to use WP Cron jobs, since that would allow the rules to be kept up to date. See Trellis’ implementation using wp-cli here.

I acknowledge that this would not be beneficial in every situation, but for sites that do use their server’s cron, the option to use WP Cron jobs would mean less work is done on every page load, and in the case of Trellis (for example), the rules would always be kept up to date. So in the end, I would really appreciate it if an option to use WP Cron jobs was included with Wordfence (maybe buried in the settings). Thanks for taking the time to read all this 😛

• This reply was modified 5 years, 2 months ago by nicegamer7.
• This reply was modified 5 years, 2 months ago by Steven Stern (sterndata).

Okay, thanks for getting back to me 👍.

Okay, I do see both. So I suppose all is good.

So it is caused by RocketLoader.

After turning RocketLoader off, the warnings go away. Although, even with RocketLoader on, the script still had the correct type attribute.

Regardless, I’ll just keep it off. Thanks, Sayontan.