So is there any possibility to change the error message at least?

Hi Brajesh,
it works. Great! Thank you.

Just two more questions on this.

1. At the backend on the invitations table you can see that the date is saved under “date modified”. Is it possible to get this date and then add it to your function? To check if the count is more than the max_allowed FOR THE SAME DAY, then set $retval to false?

2. After the limit is reached the message pops up saying “you dont have the rights to send invitations”.
Am I able to manipulate this message saying something like “you have reached the daily limit on invitations! Try again later”?

Regards
Alex

PS: I really wonder why nobody has this implemented over the last years. Looks like buddypress core development slows down, which is not good.

Or alternatively add Recaptche to the form…?

Hello Brajesh,

I made another test to reproduce the error. On localhost I didn’t have this error yet.

Its the same procedure what I wrote above.
Plugins activated: Your data control plugin (current version), bp classic and buddypress (both current version).
Themes tested with: Astra and twenty twenty four.

The name field is the only field on xfields section which you cannot delete. Make the changes at your plugin which I made the screenshot from (switch “who can edit” from Adminstrator to Subscriber).
Then you get the warning. This time with debug on I got a more detailled warning. I also attach these image here. Hope this helps.

This is all what I can do to help to fix that issue.

Meanwhile I programmed my own plugin for my needs with the advantage that I know whats going on.

So I don’t need this plugin anymore. If you want you can mark this thread as solved.

https://postimg.cc/xXfFtdB5

Error message
https://postimg.cc/JDVF3Q8D

This is what I found out.
The warning did not occur on my staging site. So I switched on/off different parameters.

Then when I changed the username xfield in the backend at “who can edit” from all members to administrator the warning occurs on my staging site as well.
The worst is, that making this change undo didn’t solve the problem. Nor a reinstall of the plugin or cache delete.
The only way at the moment to prevent this error message from occuring is to leave the plugin deactivated. So this setting must have saved values which are not beeing cleaned after plugin deletion.

Strange behaviour also, when using query monitor to see more details of the problem the warning message doesn’t appear.

• This reply was modified 1 year ago by Alex.