Forum Replies Created
This error is related to WordPoints trying to load the translation file for the extension. Have you set WordPress to use a different language than the default?
I’ll look further into this issue shortly, but in the meantime, you should be able to prevent this error by editing line 24 in the file
That line should look like this:PHP123Domain Path: /languages
You can change it to this (just add
Xin front of
Domain):PHP123XDomain Path: /languages
That will just prevent WordPoints from trying to load any translation files for this extension.
Sorry for the trouble!
Thanks for your patience on this issue. I’ve just released updates for both WordPoints and the BuddyPress extension that should fix these issues for you. Now points are only awarded when the avatar/cover image is set, not when it is replaced, and removed only when it is deleted. Any previous transactions will remain untouched, the extension won’t try to correct them on update.
If you continue to have issues, let me know.
Thanks again for being patient on this; it couldn’t be completely fixed without some changes in WordPoints, which is why it took this long to get an update for the extension out. In hindsight, I probably should have considered doing a bugfix release for WordPoints, but I never expected version 2.4.0 to take this long. Hopefully, this hasn’t been too much of an inconvenience. Again, if you have any further issues, let me know.
Sorry you were having issues logging in. Did you get any kind of error message? I wonder if it was an anti-spam plugin.
Anyway, thanks for the feedback. I think what I’ll do for now is just change these events so that they only award on first upload and reverse on delete. I’ll wait until later to possibly introduce additional events for changes, with rate limits.
I figured that you’d already manually corrected your users’ points. If I have the extension automatically try to correct it on update, it might cause you issues then. It would basically try to recorrect it, which might cause points to be removed again. So maybe I’ll just leave it.
I’m thinking of having the extension automatically correct users’ points when the update is installed. Would that be good, or did you already manually deduct the extra points?
I’ve discovered that basically the issue with the avatar upload event is related to a bug in WordPoints core, while the issue with the cover image upload event is kind of caused by BuddyPress core (but we can probably work around it).
But I’m thinking that maybe both of these events should be changed so that they don’t reverse and award every time that the cover image/avatar is changed, but only award when it is initially set and remove when it is completely deleted (and points would then be awarded again when a new one was set.) So basically, it would have the same result as now, in that the user would have the points as long as they had an avatar/cover image set, but there wouldn’t be all of this unnecessary removing and re-adding of the points each time they change it.
Separate events could be introduced for when the avatar/cover image is changed from one thing to another. (With rate limits.)
Any thoughts on that?
For the cover image, each time a new one is uploaded, the points are awarded, but the points aren’t reversed unless you hit the “Delete my cover image” button. And then, points for all of the cover images you’ve uploaded are removed!
Some of this may be due to bugs in BuddyPress rather than the WordPoints extension, but I’ll get to the bottom of it and let you know what I find.
I’ve discovered that when you delete the image from the Delete tab, rather than just uploading a new one in one go, the points are not removed. I’m still investigating the exact cause.
- This reply was modified 3 years, 9 months ago by J.D. Grimes. Reason: Clarity
These are supposed to remove the points when the image is deleted and a new one is uploaded. But maybe the old image delete isn’t always triggered when a new one is set, or something. I’ll look into it.
It would be possible for an extension to enable the rate limit feature for any event. However, I don’t remember off of the top of my head if there might be any issues with using rate limits with events that are supposed to automatically reverse themselves. It seems like there was some reason that I didn’t enable rate limits for all events, but I can’t remember off of the top of my head what it was. I’d have to go back and look at my notes.
This bug is actually related to some issues and changes in WordPoints core. I’ve removed that extension for now, until the issue is fixed. Do you have a backup that you can restore your logs from? Or do I need to fix this ASAP? 🙂
Whoops! Looks like there is a bug. I’ll look into it. I have tested it with newer versions of WordPoints, but it appears not thoroughly enough!
The documentation is actually a little ahead of WordPoints. 🙂 The modules are being renamed to extensions in WordPoints 2.4.0, which will be released in a few weeks, and the documentation has already been updated. I’ll add a note to the docs regarding older versions of the plugin.