Tobseb
Member
You need to find allow_url_fopen=0 and change it to allow_url_fopen=1 in your php.ini or ask your host to do it on your shared hosting.
Ok, thanks. I solved that one.
You need to find allow_url_fopen=0 and change it to allow_url_fopen=1 in your php.ini or ask your host to do it on your shared hosting.
Changes in this release:
Please report...
- Users only have to click Update Username, not Change Username and then type their username.
- When a user registers after changing their username, and someone else had their new username before and had also registered but not updated it on the site, the person who used to have the name will get renamed to their correct name and registration will proceed. This also happens on the validation in the form.
- Updated some Mojang API stuff.
Thanks!What a perfect time for a update!
Was just about to download this resource onto my new website
Will do soonThanks!
Hope it works well for you, please tell me how well it works.
We're running it on a Xenforo 1.4.1 board with 21k members. It's working perfectly fine.Does it works with 1.4.x XF? Can someone please confirm?
Thanks
Yeah, I could definitely add a task. I think the reason I did it before was that it couldn't really process 10k members in one run, it would have to do 100 at a time or whatever. I don't know if Mojang have spam protection but that could also be an issue. Maybe I'll check on user login instead?Our forum members tend to change their in-game name and not update their forum name. This causes some confusion with who they actually are in-game.
So, I think that a task that manually update all, or all active, forum names is needed.
Could the task check who logged on or posted that day and check & update their username? Then have a monthly task that runs through every forum account.
Not really sure, we'll probably end up integrating our in-game logins to update their Xenforo account if it exists. But, the task would still be useful for full checks.
I think having it check on user login could be too much, at least for larger boards? It would either have to check on login with a once a day limit or it could check at midnight and update anyone who logged on that day. Just would have to be something that would check active user's name, but not get banned from Mojang's API.Yeah, I could definitely add a task. I think the reason I did it before was that it couldn't really process 10k members in one run, it would have to do 100 at a time or whatever. I don't know if Mojang have spam protection but that could also be an issue. Maybe I'll check on user login instead?
HTTP Status 429 is from too many requests.Getting this error when regenerating UUIDs
Version 0.1.0
Our forum members tend to change their in-game name and not update their forum name. This causes some confusion with who they actually are in-game.
So, I think that a task that manually update all, or all active, forum names is needed.
Could the task check who logged on or posted that day and check & update their username? Then have a monthly task that runs through every forum account.
Not really sure, we'll probably end up integrating our in-game logins to update their Xenforo account if it exists. But, the task would still be useful for full checks.
I think some sort of cronjob to periodically cycle through all users over a long period of time would be fantastic, and it would make this resource twice as useful. Also, perhaps some sort of auto-generated list could be parsed that shows users whose usernames don't match up with a UUID (so that it can be fixed by hand using some sort of Minecraft account history tool, like this one) would be nice.Yeah, I could definitely add a task. I think the reason I did it before was that it couldn't really process 10k members in one run, it would have to do 100 at a time or whatever. I don't know if Mojang have spam protection but that could also be an issue. Maybe I'll check on user login instead?
Server Error
file_get_contents(https://api.mojang.com/profiles/minecraft): failed to open stream: HTTP request failed! HTTP/1.1 429 429
XenForo_Application::handlePhpError()
file_get_contents() in C:\xampp\domains\MCBuffalo.com\htdocs\library\mcUUID\Model\UUID.php at line 20
mcUUID_Model_UUID->_post() in C:\xampp\domains\MCBuffalo.com\htdocs\library\mcUUID\Model\UUID.php at line 39
mcUUID_Model_UUID->getUUIDsByNames() in C:\xampp\domains\MCBuffalo.com\htdocs\library\mcUUID\ControllerAdmin\Tools.php at line 33
mcUUID_ControllerAdmin_Tools->actionUUIDsRegenerate() in C:\xampp\domains\MCBuffalo.com\htdocs\library\XenForo\FrontController.php at line 347
XenForo_FrontController->dispatch() in C:\xampp\domains\MCBuffalo.com\htdocs\library\XenForo\FrontController.php at line 134
XenForo_FrontController->run() in C:\xampp\domains\MCBuffalo.com\htdocs\admin.php at line 13
If I had to take a guess, Mojang changed something in their API again. I'm not sure on that, but I know it's happened before and broke other add-ons I use that are dependent on UUIDs.Seem to be getting this error when i go to regen UUID's
It's a brand new Install of xenforo with only 1 user.Code:Server Error file_get_contents(https://api.mojang.com/profiles/minecraft): failed to open stream: HTTP request failed! HTTP/1.1 429 429 XenForo_Application::handlePhpError() file_get_contents() in C:\xampp\domains\MCBuffalo.com\htdocs\library\mcUUID\Model\UUID.php at line 20 mcUUID_Model_UUID->_post() in C:\xampp\domains\MCBuffalo.com\htdocs\library\mcUUID\Model\UUID.php at line 39 mcUUID_Model_UUID->getUUIDsByNames() in C:\xampp\domains\MCBuffalo.com\htdocs\library\mcUUID\ControllerAdmin\Tools.php at line 33 mcUUID_ControllerAdmin_Tools->actionUUIDsRegenerate() in C:\xampp\domains\MCBuffalo.com\htdocs\library\XenForo\FrontController.php at line 347 XenForo_FrontController->dispatch() in C:\xampp\domains\MCBuffalo.com\htdocs\library\XenForo\FrontController.php at line 134 XenForo_FrontController->run() in C:\xampp\domains\MCBuffalo.com\htdocs\admin.php at line 13
+1 one for this idea. Since their is a limit on the Mojang API, perhaps a scheduler could be done to automatically queue name changes as a cron job and prevent someone's forum installation from maxing out the Mojang API request limit.Also a feature suggestion, not sure if this plugin does it already while try get mine setup. Would it be possible to have an option to automatically change their usernames? You could have it check everytime they login or something along those lines.
If I had to take a guess, Mojang changed something in their API again. I'm not sure on that, but I know it's happened before and broke other add-ons I use that are dependent on UUIDs.
+1 one for this idea. Since their is a limit on the Mojang API, perhaps a scheduler could be done to automatically queue name changes as a cron job and prevent someone's forum installation from maxing out the Mojang API request limit.
We use essential cookies to make this site work, and optional cookies to enhance your experience.