| Author |
Thread Statistics | Show CCP posts - 0 post(s) |

Labrena
Muppets Released
0
|
Posted - 2012.07.15 21:48:00 -
[1] - Quote
Installed, no errors.
Cleared cache
Enabled API registration is set to Yes
When trying to register, it does not display the API fields. They are also not in the profile for existing users.
Disabled/Uninstalled/Reinstalled, deleted cache, same result.
Using the 6.0.2 on a new install.
Copied the changes to a different theme, and still had same result.
Do you have a manual install package? This automod install just seems messed up. |

Labrena
Muppets Released
0
|
Posted - 2012.07.16 01:08:00 -
[2] - Quote
Cyerus wrote:I think it has to do with the settings. Can you see if those fields show on the default Prosilver template? If not, contact me ingame when I'm online.
I was able to get it to work, after completely wiping the folder, and tossing in a fresh download of 3.1.0.
I do have one issue though....
It seems that when anyone registers, they are not added to a 'default group' automatically. (Those in corp go to the correct group, just not any not associated with a setup corp)
Is there a way to set it so who ever registers, is tossed in to the default "Registered Users" group, as without having a group assigned there is no way to change password if you don't remember what you typed.
And if you have further instructions in a public area on the forum, you are not able to view that either.
Basically not having a user in the default "registered users" group, is having the user inactivated.
and on the eveapi_update.php, there are like 10 copies of the vcode/apikey boxes. Didn't see a template file to check if it's duplicated there. |

Labrena
Muppets Released
0
|
Posted - 2012.07.20 03:08:00 -
[3] - Quote
21646854 wrote:I have a new problem... when ever someone puts their api in the registration form and submits they get this - 'Character and API settings do not match -> [random eve name]'.
this has happened for a few different people in the corp.
It seems to want full api access key to work. Getting same thing, not sure what the fix is.
|

Labrena
Muppets Released Fedaykin.
2
|
Posted - 2014.06.19 04:43:00 -
[4] - Quote
For the openfire integration it is able to modify the jabber groups.
Since you cannot add groups to rooms yet, is there a way to have it modify the access list for rooms instead?
It would also be good, when a forum group is immune to API checks, that if their API is invalid or they are no longer in the corp/alliance to remove it from the group regardless. Right now, it will remove them from the corp/alliance groups, then disable the account but leave them in the other groups. Could be security issue when they re-activate.
Would also be good to have the option to just remove all user groups, and not deactivate the account. This way people can still access public forums if available without extra steps. |

Labrena
Muppets Released Fedaykin.
2
|
Posted - 2014.06.20 02:40:00 -
[5] - Quote
delakut wrote:Over the Top wrote:How do you use this with Open Fire?
In the admin panel for openfire http://serverip:9090 I went to Server -> Server Settings -> External Components and Enabled External Components to connect on the default port 5275, and set a shared secret.
In the PHPBB ACP, I provided this password to the EVE API Jabber page.
What next? I am not sure what I am to expect or how this is to work. I still can't log in with my Forum credentials.
Thanks! You need to install the plugin 'User Service' under openfire. You find it under the Plugins tab. Enter the Secret key under Server -> Server Settings -> User Service and execute the 'eveapi_cron.php' from your phpbb forum root folder. Don't forget to set the openfire group for your users under your group management in phpbb. Every phpbb group has it's own 'EVE API settings'.
Yeah I got that all just fine. It adds people to the proper groups.
But for the actual rooms, you can not assign groups to the room access list. So it's virtually useless if you want to use secure rooms.
|

Labrena
Muppets Released Fedaykin.
2
|
Posted - 2014.06.28 14:40:00 -
[6] - Quote
Will this be updated to support the new 3.1 version of extensions?
Looks like release will be in the near future. |
| |
|