EVE Technology Lab

They have totally changed all the Industry stuff include what some of the column values mean so chances are you can't import them but the good news is the new IndustryHistory API will let you get the older jobs with the data updated by CCP so if you really need it as far back as they allow you can get it. You are really going to be limited in this case by what CCP has done.

hi, how i can understand, yapeal give interface to gather data from api, but not to use it from database, yes? If i'm wrong, can you show me example? Thank you.

_______
Sorry for my English

Okay some updates have been pushed to fixes some issues I came across. First like I figured there was a couple things incomplete on AssetList. It wasn't deleting the old orphaned records. Couple of the other newer APIs had to same issue and fixed them as well. I'll try to go through them all and make sure none of the other are doing the same thing.

For those of you that haven't paid attention Yapeal for a little while now is adding into the cached XML file what is called a 'processing instruction' generated by Yapeal. Think of it basically as a comment for an application in XML. Yapeal doesn't really use it in any way at this time but it can be a useful tool for me during troubleshooting. Current it's writing the API parameters being sent to the server with the vCode cut off so it's safe to just cut and paste to places if I should ask for it. Anyway to make a long story short it let me trace down a long standing thing I've been noticing that even with just one active corp key during testing I'd often end up with more than a single IndustryJobs cache file for example after running Yapeal manually a couple times. This probably wasn't noticeable if you have several keys but is with single key testing. Before I couldn't figure out what was causing it but now I know it's because left over parameters like accountKey from accountBalance or one of the other APIs that need extra parameters was not being reset between the different API calls. It came down to one miss placed line in one of the XML network classes in the end.

Anyway I've pushed the update to fix it but I highly recommend that everyone clear out your cache/*/*.xml files to get rid of the bad files and let Yapeal refresh the cache as needed. This could save you a lot of disk space as well since the are cases where you'd end up with as many as eight files instead of one per API/key combo after a few runs.

Next I'd like a little more input on which API everybody needs next. I'll go back through thread as well to look at the votes people already made but new people can have a chance to vote now or you can update your vote if you changed your mind.

As always thank you for using Yapeal, Dragonaire.

And another problem: it seems that yapeal doesn't update my marketorders anymore. in the old yapeal table all seem to be correct (actual data from today sell orders) but in the new yapeal table the last sell order is a few days old. i have deleted all the cache stuff and run yapeal manually but nothing changed. found nothing special in the logfile, besides there seem to be only one entry for 61 orders?



edit: checked again and don't know why but seem to work now.

Fixed some things I ran across with AccountBalance, and the Wallet stuff. Came to light while I was looking at some corp stuff. One small DB table update for the corp AccountBalance table to allow for the new mercenary stuff. Fix also should keep corp/AccountBalance from making a bunch of unneeded cache files so like before worth deleting all the cache/corp/AccountBalance*.xml files and Yapeal will recreate the ones it needs.

I haven't decided for sure which API to work on next but leaning towards corporationSheet to match up with characterSheet. Looking at making it useable with and without API key info so you can use it in your apps to grab public corp info with just the corporationID but not sure if I can make it work yet so stay tuned on that.

Hi there -

I was wondering if there is a "getting started" tutorial that is up to date? The one I am using now is outdated and causes "not found" errors to be thrown.

Thanks for the reply.

Let me edit my response:

I've successfully installed everything according to the install and config files.

From there though I'm in the dark what should be done.

Must I:

• Execute some file on a hourly/daily chron?
• Include some file to give me access to methods?
• Do something I haven't noticed...

I had installed it in the root of my project - but should this be installed in PHP itself?

So really, after installation how is it run?

Thanks for your time, I should be able to hack the rest myself after this :D

Base way as an application programmer is to look at it is you have a database that just magically always has the most up to date data possible. You are right in that to make that happen you do need to have Yapeal running in a crontab which is outlined in one of the Wiki pages. I don't have direct instructions for Windows because you usually do it through the GUI which is much harder to explain without a lot of screen shots etc. Also each version of Windows is a little different and I'm not going to take the time to try figuring it out with each of them. Most people will use Yapeal on a Linux server anyway so I don't expect that to be much of a problem since they have crontab.

As to how often Yapeal should run in the background I'm always very clear about that. Yapeal should run every single minute to insure the lowest server load on both ends and the most up to date data. Yapeal internally manages which APIs are ready for refreshing from the Eve API servers and trying to second guess it on that just causes you more load and problems NOT less like everybody seems to think.

How to use Yapeal for things like site signup etc does take a little more work but not much as I made a utility class you can use to add the API key info into the right table which you can find in bin/UtilRegisterKey.php. After that or possibly before you can also use any of the API classes you'll find in lib/Database/*/ directories directly just like the main Yapeal class does or even just extend from it. You'll find it in lib/Yapeal.php. You can just ignore the AutoMagic() method or override it to do what you need. The code is the best documents you will ever find in any project on how something works so don't be afraid to poke around in it a little.

Just an additional hint for things like signups etc is to use the oneShot() method in the lib/Database/Account/APIKeyInfo class. It'll put the EVE API result info into the account database tables where you can check the mask and get the character and corp info you might need.

Hope this helps you get going or at least gives you some idea where to find out some more about some of the stuff. Remember the database is the interface everything else is just setup to make it work

CCP - we need some code-wrapping in this forum

I'm using your predefined method to set up initial API info - namely class UtilRegisterKey

This is how I've executed it:



Yet it doesn't go through, and I've found that the below function adds quotation marks in places making the query invalid.

I've posted this question:
http://stackoverflow.com/questions/25756074/php-pdo-syntax-issue#25756099

Your library is expertly created, so I'm assuming I must be doing something wrong. The error is shown in above thread.

I'd use my own query, but I'd rather learn your library



On a side-note - is the verification code just a typical hash? If it is always a typical hash, I could build in hash validation for it in the APP I'm making.

Actually the quote marks are correct but I use ANSI mode in MySQL for all the SQL in Yapeal. What I probably do need to add into the class is the SQL to set that mode up first in a class where it's more likely to be used by others. I'll try to push out something to do that later today. If you look in lib/Configuration/Wiring::wireDatabase you'll see the exec() commands that is used in Yapeal to set the correct mode up right after the connection is created. You can add those into your code before passing it to utilRegisteredUser.