EVE Technology Lab

Actually the Notice error you are getting might be part of the problem you're having as it's a bug that seem to have crape in with a bad cut and paste I've updated svn and archives to fix it.

Make sure you are using the archives (zip/bz2) or current svn from trunk/. If you are using archive check the revision in revision.php the YAPEAL_VERSION line will let you know which you are running. It should be 1231 or later. Also make sure if you do use archives you cleared out old version before unpacking the new one where you have it installed. Clear just the class/ directory should be enough but it doesn't hurt to backup your config/yapeal.ini file and wipe the whole thing if you still have problems. Also remember the RegisteredCorporation/Character tables can be totally empty when using registered_mode=optional like you are using but do make sure in utilSections that account row's isActive=1 or it'll come back to bite you later.

BTW you can also get the corporationID etc from the accountCharacters table just like Yapeal does for active keys

Yes you can have as many as your system can keep up with in a single DB. Everything is either keyed by keyID, characterID, corporationID in each table. If a column by those names don't exist in the XML I add an ownerID column with the correct type for the section of the API it's in. So for char section API it will be characterID etc

The only place in Yapeal that table was used was with some of the scripts in install/. They were used to interface with a GUI installer that I tried with it at one point but few people liked it or used it so it was dropped at least for now. The scripts still exist they are the addTestCharacter.php and addTestCorporation.php scripts. In the installer it would show you pictures of chars/corps to choose from on an account to add to the Yapeal database for testing. At one time the pictures were in the Registered tables but to streamline and normalize them I moved the pics to where they are now. Since they aren't really used in Yapeal you would be free to use them in your application if you want just keep in mind that at some point I may start using them in Yapeal for what they were made for so I would keep them just for character and corporation pictures.

Your right there was an error in getSQLQuery(). Actually all 3 modes can use the same query so I'm dropping the switch.
(Fixed in revision 1232)

I'm not seeing the notices and I believe those errors were cleared up in a revision of keys so I'm guess you're using an old version of it and not the latest trunk/. There are some errors popping up for some of the API that aren't implemented yet and I'll try to make some changes so Yapeal returns a different error message so it's clearer what is actually happening.

Yeah database needs to be updated to get the changes made in util* tables etc

Did a couple more updates the install/*.xml tables that should make database updates work better.

I have been upgraing my previous yapeal version to a new one to start working with the new api structures?

I am now succesfully downloading all kinds of information through a corp api to start with, but for some reason, I cannot get yapeal to get the conquerable stations downloaded, the corresponding table stays empty. In the sections table, I did mark eve and map data to be downloaded

Any tips??

PS: Yapeal is AWESOME !

Hey,

I am a complete noob and have a been coding a php based site myself for use with the API but i am interested if i can use this framework instead.

I want what the full API no gives us but i wish to use the new API system to archive this.

I have downloaded Yapeal but had a lot of issues with getting it running from the guide i was wondering if there is a more detailed guide or if i could get some help.

Cheers Louis

Just thought I'd let everyone know I've been working on some major refactoring of Yapeal and doing something that has been long over due which is learning how to use PHPUnit to add some much needed testing beyond what is possible now. If I do the refactoring right there should be little or no visible changes to anyone using it but anyone using some of the lower level internal classes in their application will need to make a few changes. For anyone interested you can take a look at branches/queues/ but keep in mind everything is in early alpha at best and nothing really works except some of the classes with finished tests and they may not be in their final forms yet either. Most of them won't work outside the tests for now until some of the other classes have been re-factored as well. Adding the tests and refactoring is slow work because almost everything in Yapeal is either database or network related or both which makes developing tests hard at best. I'm trying to do the classes from class/util/ first as they are the public facing classes everyone should be using plus they are some of the first classes used by yapeal.php as well either directly or indirectly.

Anyway back to work on things.

Start by reading http://code.google.com/p/yapeal/wiki/UtilDatabaseTableDependences from there the best thing is to look at the code in some of the classes and understand both the SQL queries and how the filtering in class/Section*.php works. The DocBlocks on ignoredFilter(), optionalFilter(), and requiredFilter() and other comments there should help.

Just to maybe help make things a little clearer Yapeal tries to be at least a little bit intelligent and use any info available from APIKeyInfo in addition to the utilRegistered* tables and won't do stuff with char/ and corp/ section APIs without some of it being available. I do allow you to shoot yourself in the foot by turning APIKeyInfo off but if you do you're on your own.

Also make sure you understand how many to many relationships (don't) work in databases. That's where accountKeyBridge comes in. It's job is to change the many to many relationships between accountAPIKeyInfo and accountCharacters into a couple of one to many relationships instead which the database can handle.

The above should help you with what you're trying to do but I believe you are also looking at relating multiple keys together in regards to some kind of 'user' account in your application which is beyond the scope of what Yapeal does. Yapeal really only understands keys and that they are sometimes related to characters, corporations, and their APIs nothing more. To manage keys as a group is totally up to the application developer which will probably mean you'll need to have a few database table of your own

Brought issue 76 back to life and have some new code for you to try as well which you can find in my post there.