EVE Technology Lab

You should tell your host that PHP 5.3 has been a stable release for 2.5 years and that they need to get their act together if they want to keep business.

If you have 5.2.x, then certainly the 'EOL' (nowdoc) syntax won't work and the single-quotes must be removed. Furthermore, you'll need to find any situations where there are dollar signs in the heredoc string and escape them with a backslash, but I believe only the index.php has a section like that. I know this is just a rephrasing of what I already wrote.

If you absolutely cannot update away from your old version of PHP, I am willing to walk you through fixing the errors in comms, (your Ventrillo if you want). I don't have an old version of PHP to test on.

Also, the reason it goes past line 161 is that we weren't even talking about the same version of the code that exists now.

EDIT:
Apparently you don't need to escape the $ signs. I just tried it (switching from nowdoc to heredoc on that section), and it worked fine without doing so. You only need to do that sometimes, in cases where PHP could easily mistake the $ for a variable, like if a letter comes immediately after it. I guess since that jQuery code all starts with "$(", it's not a problem.

Also, here's a list of files that have the 'EOL' (with single-quotes):
admin/index.php
index.php
eve-api-get-names.json.php (a file index.php makes use of when doing the AJAJ stuff)

The dollar signs don't need backslashes, and there should be absolutely no spaces on the same line after EOL. I would just replace your index.php with the latest copy and replace all the 'EOL' (with single-quote) parts with EOL (without single-quotes).

I can't write the syntax on these forums exactly, because whenever I post left less-than signs (angle brackets), I get an error that I can't post HTML.

Heredoc and nowdoc syntax are documented at the Strings page of the PHP manual.

"EOL" is just the string delimiter I choose for my code. The delimiter could be anything, including "TACOS".

Here's how the registration page works: A user visits the registration page. They see the form as in the screenshot (with some minor variation based on your config.inc.php settings). They enter their API Key ID and API Key Verification Code. Once they change focus away from either the Key ID or Verification Code boxes, and if there is something in them, the AJAJ process starts (using a Javascript "onchange" event), calling the "eve-api-get-names.json.php" script. "eve-api-get-names.json.php" does some basic validation of the Key ID and Verification Code, then it gets their character list via the API page "account/APIKeyInfo.xml.aspx". If the key works, the access mask is correct, the account type is correct, and they have at least one character in a configured corp., the script sends that data back to the registration page, and Javascript plugs those names into the Character Name dropdown box. If the key had an expiration date, the user is warned about that as well. If there was an error, the error is shown instead, and the first two fields are cleared. The user then enters their TS UID and submits the form (if that's enabled). Most of the same API things are then verified again, except using the character name they specified. Some other things related to their forums account are verified. It's verified that the TS UID they entered has been used before on the TS server (if that's enabled). Their entry in the EVE Registration table is then either added (or replaced if it already exists). The check-users.php script is then called.

Group assignments are done in config.inc.php at and after line 80 of the current version with the $config['Corps'] array. There is a giant block of documentation above it.

The Forums DB information is the connection information for connecting to the database your installation of phpBB uses. This should match the information in config.php in your phpBB installation's files.

Looks like I'll have to start fresh...dug myself into a hole...but got an additional question.

Your documentation says corporate ID's for group assignments.

Is it possible to use the Alliance ID number?

PS: This weekend I'll plenty of free time to finally get it off the ground.

Drake:

No. The instructions do show you how to quickly grab a list of every corp. in an alliance, but you will have to update your config as corps. join or leave your alliance. I'll think about this and it may be a feature down the road.

---

Phoebus:

Problem 1: Good catch. That's exactly right. That would certainly be a problem. As I said upon releasing that feature, I figured there was a chance it may have issues. I had only tested with myself, so it was the only record,and I didn't notice. For optimization's sake, it's better to have that as a unique key, but I guess a regular index will have to do the trick for simplicity's sake combined with the option to disable TS.

Problem 2: Good catch again. I hadn't noticed, as we don't use our forums much at all. I'll figure out the exact proper way that phpBB does that when it does group assignments and make that happen. I think clearing user_permissions may cause problems with actual user-specific permissions admins can give users in phpBB.

I'll be releasing a new version with these fixes soon, and I think I'm going to get rid of all the nowdoc stuff (in favor of heredoc). I'm a fan of nowdoc, because I don't see the point of parsing for variables when there's no need, but it's not too intense of a script anyway, and if it opens it up to more people, then I guess it's worth it.

Update: Apparently the "user_permissions" field is a cache that is regenerated if empty, so your solution is exactly correct, and I'll have the code do it in that manner.

Would be graet if it did...less opprotunities to mess with critical core files the more reliable the package.

But so noted...I'll stick with corp ID's from here on out.

Ok its not pulling the API key... its just sitting there.... I'm pretty sure I got all the files updated as specified... the DB connection is good... so whats causing it to not load the API information?

Sent email. Look forward to contacting you.....

Phoebus:

I just did some testing on it, and it appears to work correctly:

I did API registration for myself. I deleted my API key (at CCP's site). I then tweaked my Cached Until time to be really old. Then when the cron job kicked in and did the check, since the API's "account/APIKeyInfo.xml.aspx" for my key ID and verification code was still cached (CCP currently caches it for about 5 minutes), my groups in TS and the forums were not changed. I changed my Cached Until time again to something old. This time when the cron job ran, my groups were revoked in TS and in the forums, and I verified that my user_permissions field in the "users" table was cleared.

Let me know if it still doesn't work for you.

Ran a test to act as if I booted a corporation. Still hasn't kicked said users... how long before it actually does that? Seems kinda odd that it hasn't done that as the cache has come and gone. (All I did was remove the entry of the corp in the config file)