Custom_data is not working correctly

Status
Not open for further replies.

katori

New member
I used function delete_data_by_key to delete all key 'users'.When I used function get_data_count('users') to check, the count still returned 9 (total repo before delete). It seems to be a soft delete.
Moreover, there are cases where I used function get_data_by_id with different ids, but it returned the same data even though I checked and found different data in custom_data.
 
I used function delete_data_by_key to delete all key 'users'.When I used function get_data_count('users') to check, the count still returned 9 (total repo before delete). It seems to be a soft delete.
Moreover, there are cases where I used function get_data_by_id with different ids, but it returned the same data even though I checked and found different data in custom_data.
After reviewing, we found that the issues you reported do not exist. The delete_data_by_key and get_data_by_id functions are both functioning correctly and do not have the errors you mentioned.
 
After reviewing, we found that the issues you reported do not exist. The delete_data_by_key and get_data_by_id functions are both functioning correctly and do not have the errors you mentioned.
This is the video of my actions. I have deleted all the 'users' keys and checked in custom_data.
But when I call the function, I still see the count is 2. Similarly, the 'chatbox' key is no longer there, but I still see data. I wonder if there is data caching somewhere.
 
This is the video of my actions. I have deleted all the 'users' keys and checked in custom_data.
But when I call the function, I still see the count is 2. Similarly, the 'chatbox' key is no longer there, but I still see data. I wonder if there is data caching somewhere.
Thank for your report. We have promptly fixed the issue.
 
Thank for your report. We have promptly fixed the issue.


It hasn't been completely fixed.
It seems there is still cache somewhere. In the video, I currently have 2 users with IDs 1 and 2. On the login page, I am printing out values like this. Comparing with the values in custom_data, I find they do not match.
ID = 2, however, the log shows the password value of ID = 1.
 

It hasn't been completely fixed.
It seems there is still cache somewhere. In the video, I currently have 2 users with IDs 1 and 2. On the login page, I am printing out values like this. Comparing with the values in custom_data, I find they do not match.
ID = 2, however, the log shows the password value of ID = 1.
Try again and see if the error still persists.
 
Status
Not open for further replies.
Back
Top