knowitallninja

The graph is for premium customers, so what you’re seeing is some placeholder data I think.

Thanks Frank. I appreciate the support.

It’s worth nothing that V2 “I’m not a robot” works perfectly on my contact form. So I am sure I haven’t done something specifically wrong myself.

V2 invisible worked before I updated the plugin. It still works on anything that is automated by your plugin (such as the forgotten password form) but doesn’t work for my contact form (a custom coded form). Instead it just stops the form from being submitted.

Cool, well hopefully this is something they’ll fix in future but for now I’ll just not use the Reddis Object Cache.

I call this resolved!

Hi,

I tried to log the incoming password, hash etc. nothing seemed to be going wrong.

However!

Due to a seemingly unrelated issue with my website, I have had to disable redis object cache. This appears to have resolved the problem. I’m not sure if that really means anything to you.

I am going to stick with having the redis object cache disabled for now unless you have any further thoughts.

Dan

The post is definitely going through. I check that it’s posted through plus I can echo it out at the exact point in the code where the function runs. So the data is being posted.

I’ve also tried hard writing the password into the function. No luck.

I’ve checked the error log. There are no errors being logged.

I’ve used query monitor to check out if the query appears to being run. It is and the query appears to be structured correctly. The hashed version of the password that can be seen in the query in query monitor is being updated in the database to this hash. However, the hash appears to be for the old password as I still can only login with the old password, not the new one.

So it appears that something is making it create a new hash of the old password not the new one, then it is successfully querying the database.

The only extra options set were greyed out when I unticked the various “optimise code” check boxes. Which I presume means they are deactivated.

I also removed the CSN url and cleared the cache.

Okay, so here is something strange.

I tried unchecking the “also optimize for logged in users” as you suggested and that didn’t help.

So instead I tried deactivating everything, I deactivated optimise html code, js code and css code as well as deactivated the two misc options at the bottom. The wp_set_password still didn’t work.

So even though autoptimize is essentially doing nothing, if it is activated it interferes with this function.

Does that provide any clues at all to you?

It’s being run in the front end and is not done using Ajax.

Sadly that bit of code for deleting the log entries doesn’t seem to work for me at all.

Would you know if I could send a query directly to my database in phpMyAdmin. I can figure out how to get rid of the entries in the posts table:

DELETE FROM <<NAMEOFMYPOSTTABLE> WHERE post_type = ‘badgeos-log-entry’;

But that would leave all the post_meta orphaned.

Ok thanks.

Wouldn’t suppose you could advise on a query I could run in my database to clear these logs instead of using the log entry section of Badgeos? It’s taking a long time as I can only do them around 250 at a time from within WordPress.

Either thanks for the help.

Ok, thanks. What purpose are the log entries then? Is it just so you can manually check who got achievements from the backend? BY deleting them I presume my users won’t suddenly lose their achievments?

Hi,

That sounds like good news. I have a couple questions, if you don’t mind:

1) What is the impact of disabling the log entries?

2) Will disabling the log entries delete them form my database? Or will I need to do that myself manually?

Thanks