EVE Technology Lab

Just a note: I applaud you for trying to make it as user friendly as possible, but it still has a long way to go in that department. Understandable due to the projects' complexity. Last time I tried this was way back when there was a web UI for setting it up and showing you how you could insert everything into the DB and whatnot. I personally wouldn't mind if that made a comeback. ;)

Question: Say you have 2 keys, one that is essentially a Full API key with all the characters on the account and all the APIs unlocked, and another key which just has your main (Sable, in this case) and a few APIs unlocked for use. Which key does Yapeal use if they are both present? Also, would we enter Sable into `utilRegisteredCharacter` both times for each key? How does one deal with this redundancy? Should we, the developers, check to make sure we don't already have a similar key belonging to the same character or whatnot?

Dragonaire Have you considered leveraging Log4PHP for all of the internal logging? this would allow people to configure logging to their specific level of verbosity and would allow you to have very verbose logs for troubleshooting, with only Warnings/Errors for production runs. Also it gives people the ability to log to STDOUT, a file, a DB, syslog, etc at their own choice simply by editing a single XML file.

I have the automated/scheduled part of my project using it and I am able to log trace level and above events to a big fat daily log file and only warnings/errors to STDOUT so that cron emails me when it needs attention and I can refer back to the low level logs events for deeper troubleshooting/verification of what's happening.

http://logging.apache.org/log4php/

Hi Everyone,

Firstly thank you Dragonaire for the time and effort you put into this it is much appreciated.

Now for my question... and sorry if its a bit dumb of me to ask but all this sort of stuff is very new for me.

I am using Yapeal to basically help me with getting information about industry jobs. Currently I have it installed on windows PC running XAMPP and its all working great I have the tables populated with the data about the jobs.

My question that I have is what is the best way to get this working on my hosted domain? Can I just copy the sql database and files that are in the Yapeal directory up to my server and it will work as is or are there special extra steps or is this just not going to be possible?

I am sorry if its already been posted I have read through all this thread and searched as best I can.

Many thanks for any help and advice.

Nori.

Can you support adding a character id to the db and fetch the publicly available data for them?

If you are talking about /eve/CharacterID.xml.aspx and /eve/CharacterName.xml.aspx they are really outside of the scope of what Yapeal does and it's unlikely I'll add support for them except maybe in some kind of util script if I find and need for it or a few extra days with nothing else to do

If you mean /eve/CharacterInfo.xml.aspx it would have already been done except CCP was stupid and put an API that requires apiKeys and vCodes in the eve section instead of where it belonged in char or account. You can get all the same information from the other APIs anyway so I've never seen why anyone would find it that useful as it is. I've got some ideas for changes to Yapeal that MAY in some distance future be able to overcome CCP's stupidity on the placement of this API but let's just say being able to support this API is going to be purely an afterthought in any changes.

Yapeal should do this for you by default but CCP has made some changes in the past that may have broke it and I don't have enough activity on my chars to do any testing

Yapeal doesn't even look at that table without a key in utilRegisteredKey so no that won't work.

All of the corp APIs have been changed to require a key from a director or the CEO and there is no way around that.

Public access to the corp APIs has been turned off you have to have a corp key now to access them there isn't a way to bypass.

Or to put it another way NO and it can't be done

Is that clear enough?

Dam you just got owned son

Not really since that ability is going away when old keys do from what I understand and once again by design Yapeal expects to have keys etc for anything in account, char, or corp sections in the requests plus the database expect the full data you only get from having the keys.

Yapeal is a made to be used when you have the required keys etc not for just general random access to the APIs if that's what you need there are several other libraries for that but of course it's up to you then to parser the XML and put it in the database yourself too

Instead of just trying to say indirectly that Yapeal is doing something wrong why don't you learn how to use it correctly first.