csmicfool

Hi Scr00chy,

I’m sorry but the current version does not support wildcards.

My day job(s) have been keeping me sidetracked from my WP plugins. As such, I’ve not posted an update in about a year, so I will consider an update in the near future.

I see that users have submitted several thousand new domains I can add to the public blocklist in the next update as well.

Public support (in the form of feedback, positive reviews, and generous bribes/donations) is always appreciated and helps fuel time for new feature requests and development.

Thank you!

It appears that the source API for the currency conversions, bitcoinaverage.com is no longer serving the API on which the plugin was built.

I see that they have a new API which requires individual user registration.

At this time I will have to plan an update to add support for their new authentication requirements.

I’ve not updated the plugin in a while so I did not keep aware of changes from the data provider.

I happy to help solve the issue with you. A 502 error should only be occurring with an improper configuration.

Would you please provide any relevant exerpts from your PHP/Apache error logs to assist me with diagnosing your problem?

I’m confident we can resolve this issue and hopefully improve your feedback rating.

I look forward to the opportunity to support you. Please contact me with the requested information for assistance.

Thank you!

Hi dimizu,

Sorry for the slow response.

I tried to replicate the issue locally but could not.

Just to confirm – you said that the issue no longer occurs with latest versions of everything? I want to ensure the problem is resolved.

Thanks!

Hi Dimizu,

Can you please provide steps to reproduce?

What version of Yoast do you currently have installed?
Which version of my plugin do you currently have installed?

There are no deactivation hooks in my plugin which should be affecting any other plugins so I’d like to investigate this issue immediately. Upon deactivation, my plugin doesn’t touch and wordpress options or settings and should be clean with regards to other plugins.

-Jacob

Hi – Sorry for late reply.

Yes, the goal of this plugin is to block all that weird crap showing up in Google Analytics so you do not need crazy filters. I cannot guarantee to stop 100% of it, only that which is “honest” traffic to your site and not “ghost spam” which can occur without your site actually being loaded.

Please let me know if you have any questions.

Thanks for the info.

Repo shows it’s using maybe_serialize() which is the WP way to do it. Should be good since it won’t double-serialize.

The issue came up again today with a different character (umlaut) in wp_options table.

What we were able to diagnose was that there appeared to be some discrepancies in how each server in the farm was serializing/de-serializing. We also saw that serialized values in options.php could be retrieved ok because it wasn’t being pulled from the object cache, but get_option() was failing to load it and returning a null value without logging an error because it does use the object cache.

Updated all servers to use phpredis (pecl) w/ igbinary enabled for PHP (still not 100% sure if that’s being used in the path to redis or not but I followed whatever documentation I could find for our oldass servers). Then flushed the redis object cache and was no longer able to reproduce in the same way.

• This reply was modified 8 years, 4 months ago by csmicfool.

The character is “??”

Encodes as \ud83d\udc4d

stored in wp_postmeta, mysql using utf8mb4, and redis clients should be using igbinary

Thanks for the feedback. No clue what’s changing the button color, quite odd. I assumed it meant something was configured wrong.

We traced the issue down to a strange emoji character (thumbsup) from user input which passed json validation and didn’t get encoded, but choked under serialization. Removing the stray characters restored all of the data w/ next sync.

Do you have any advice regarding serialization? Are there params within the plugin or is it purely up to the phpredis/predis client?

Are the colors just different wordpress versions? I see in one version button-primary is blue, orange in the other. The class is from WP, not the plugin.

previously was volatile-lru, I haven’t hit the limit again yet but I’m confident it’s not on the plugin side.

Thanks!

For Azure, it looks like the correct setting is under Advanced Settings > maxmemory-policy. ‘allkeys-lru’ is one of the dropdown options.

Correct

I solved it. Was related to TLS support (using Azure Redis).

Appreciate the fast responses.

Testing out some naked calls against phpredis to be sure it’s not on my end too.