EVE Technology Lab

Hey Magotchi, I've noticed that after my users become part of the API group, they dont get assigned that group as a default group.

TA5E:
I don't know what's happening for you, but all of my members have their default group (in phpBB) set as the group it assigned them to. As has been said before, default group colors are currently not working with this, so don't base it on that.

Rache:
The way that shows up for you is actually sort of correct, in that that's how the symbol shows up when you aren't viewing it as Unicode, but since you said it looked like a single-quote last time we talked, it seems that on your host it must be that it's inserting the symbol wrong, not that you're viewing it wrong. I may have to look into inserting the name value as hexadecimal instead of as a string to ensure it gets properly inserted on all platforms. It's supposed to show as a modifier letter prime symbol.

It looks like a good idea, and your code seems fine. I'll see what I can do in the next release or so.

Update 2011-10-20 (after new release below): I ended up changing your code quite dramatically. In my version, the phpBB settings regarding the use of avatars are not changed every time a user is checked (or at all for that matter). To do that and have it work, I would also have had to get phpBB to clear (or update) its global data cache (cache/data_global.php). For the sake of simplicity, to reduce the load of the script (not making the update query every time and not clearing or altering the cache every time a user is checked), and for a more predictable user experience for admins changing settings in the ACP, I opted to not have the script make such changes, and instead, admins must enable remote avatars in the ACP (and it's documented as such). The feature as a whole now only uses one single MySQL query (an UPDATE query that, if not using forced mode, adds an extra clause to only update the user if their avatar isn't already set). I also tweaked the rest of the code to conform to the way I do things (config. naming, indentation, etc.).

Could it be requested that the scritp checks for director role and if the person got it then its add's them into an "director" group also

I accidentally used nowdoc syntax again on line 221 of index.php ('EOL') instead of heredoc syntax (EOL), so those using PHP less than 5.3 would have had issues with yesterday's release.

I've updated the package, but I didn't change the version number or date.

If CEO puts in the Corp key then it could cache directors char ID's and auto place them in the 2nd group when they enter a char API i guess

I don't have any plans to add channel groups, but I will spend some time looking into it, and if it's not very difficult to add, I may just do it. Don't count on it, though.

In what way would it be easier: upgrading purposes only or for some other reason? As it's just one uninterrupted block of CSS code, and it only relates to that one page/script, it seems logical to me for it to be in the script itself. If it's that you believe it will make upgrades easier, as I don't change the CSS often between different versions, you're right, but copying one block of CSS of your custom CSS into the file every time you upgrade it doesn't seem like a big issue to me, and I believe keeping it simple outweighs the benefit of not having to do that.

If you're getting a blank page when you visit index.php "eg. http://example.com/eve-api-reg/", check your Apache error log (or other places where PHP errors are shown on your host), and see if there are any errors being generated for the script.

The config.inc.php file doesn't need to be edited any differently for those with an older version of PHP than 5.3.

The reason that the config. options composed solely of numbers don't have quotes is because they don't need them. In this case, the script would work identically even if you did put single or double quotes around those port numbers. In more technical terms, I'm assigning them as integers, but PHP is weakly typed, and therefore even though I plan to use the numbers in a string context later in the code, I'm not required to specify them as strings ahead of time. With non-numeric text, though, if I didn't put quotes around it, PHP would assume I was referring to the name of a constant.

If you need some help working through these problems, if you want to give me your TS3 info in a mail, and I can likely help get it figured out. It also helps me to find unexpected bugs or compatibility issues that I wouldn't otherwise notice on my own system.

I don't know what Windows hosts provide as a cron equivalent. Basically you need a scheduled task to run the PHP5 executable with that check-users.php script. Locally, this would probably look something like "php.exe C:\path_to_website_root\eve-api-reg\check-users.php". Alternatively, you could allow web access to it (with the assumption it's even blocked, as you're probably not using Apache as your web server, so the .htaccess file is probably doing nothing), and you could remotely access it via the web from another machine via a Scheduled Task or cron job (there are many cron job services if you Google that sort of thing), probably using cURL, or if you really wanted to, through a web browser. There are actually quite a few ways to do it, but all of them would take some explaining, and I really don't want to take the time to support this on Windows. PHP on Windows is somewhat of an unholy abomination in the first place.

A popup saying, "Error getting API data from EVE server." likely means neither the cURL extension for PHP is loaded nor the allow_url_fopen option is available.