EVE Technology Lab

Make sure the char section in utilSections has isActive=1
It sound like you did the rest right though you didn't say what your activeAPIMask value was but if it's NULL the one from sections will control it.

As to the wiki yes it is outdated on a lot of stuff but the UsingClassUtilClasses and UtilDatabaseTableDependences are still useful for understanding the things you're having trouble with and have been updated to the current way things work since I last wrote about them being outdated.
If you have any other questions just ask I'm much better answering questions here than I ever have been trying to write about how to use stuff for new people in general

Most of them it should be able to handle on it's own if you stay within a couple versions of current version on the few times when I have to break it and you need to handle it manually I make sure to put something in the CHANGELOG plus say something about it here in the thread also with instructions on what to do or look out for.

charContactList error about inWatchList sounds like CCP made a change to make it optional without telling anyone or its a new bug in their code with the same effect There is nothing in the blog when the API was added that says it can be optional and it really doesn't make sense for it to be so that needs to be followed up on with CCP. The blog that talks about the new API is here: http://www.eveonline.com/devblog.asp?a=blog&bid=757 I'll follow up with them on it but I'd like it if you'd also do a bug report on it so they get an example of the XML file that has the error.

The error about duplicate entry can only happen if somehow in your in game contact list you have the same character/corporation listed twice some how. If it isn't show something twice then there is a bug either in the API or the CCP database. I've had another report about duplicate entries in a different API which I know is a bug in their database so this could be the same thing happening here too. I'd follow up with CCP with a bug report on this too and let me know what they say as on the last one they initially responded they couldn't test it and the player would have to check it He followed up with them saying they had to fix it with some more info but as far as I know he has not heard back from them yet

Edit: I've bug reported the inWatchList problem in bug ID 122907. If you could refer to it in you report it would be helpful.

Also make sure you have updated Yapeal for the problems with KillLog as it was just updated for the new 'singleton' field that was added to the rows in the XML and you'll need to run install/createMySQLTables.php again to update the database.

There seems to be an issue with error logging.



I first noticed this error when it was giving me the following error

I added a bit of extra logging to find out that it actually meant that it couldn't find the table. The problem occurred when I transferred the database from my windows dev server, which had converted all the table names to lowercase and is case-insensitive to my linux webserver which is case-sensitive.

Szelene - Might actually get an ask if you did your own thread instead of using one that is about something else.

Spike Keikira - Give it a day the day after patches often the APIs do some strange things but if KillLogs still isn't working sometime after DT let me know and I'll look into it some more.

Controller Vrelk - That's one issue between Windows and Linux that Windows doesn't always track the case correctly The easiest way to fix it is to do a MySQL dump on the Windows machine and edit the table names before using it on the Linux one Yes it sucks trying to edit all 80+ table names. If you don't really need to transfer your data its much easier to just create the tables on Linux. Also there is a setting in MySQL's settings to have if use upper and lowercase on any platform it's just that they (MySQL) decided to default it differently on the two platforms even though Windows does normally keep the case just ignores it in most cases. You might try changing that settings so you have less issues in the future.

Szelene - Since it's a thread about an EVE API library and your question isn't in even the right forum since it's not about it or even third party development then your chance are about zero here. You might try doing an actual search with something you heard about called Google or there's even s few search engine just for the Eve forums that work very well and it's just a guess but I'm sure someone else has asked your question before and you can find it if you look without even having to post. You'd probably even have a better chance having your question answered in one of the general threads then going out of your way to find one that has nothing to do with the Eve client but the API instead which is on the Eve website.

So 2 Days later the killlog still dosen´t work.

The error log is empty exept an Warning:

and the ContactList also emty.

Spike Keikira - First make sure you have the latest version of Yapeal since there have been a lot of changes to it lately. Next make sure you also ran install/createMySQLTables.php to update your DB. Next check that the chars/corps that are having problem haven't had their KillLog APIs deactivated. Finally if you are sure all of that is good clear the cache by deleting the KillLog xml files in cache/{char,corp}/ and the DB cache in utilXmlCache also in that order with any crontab/scheduled task stopped. Then try running Yapeal manually from the command line and see if you notice any more details in some error message that might help figure out what the problem is.

If it won't cache to the database you should look at the cache/ADOdb/util.sql file and maybe try it manually to figure out what is wrong with your utilXmlCache table but glad you're making progress

There was someone working on the contract APIs but he has took a break from Eve it seems so someone is going to have to pick it up and finish it If someone is interested in finishing it let me know else it might be a little while before I have a chance to look into it. I believe there was some technical snag he was running into at the time because of something CCP had or hadn't done but I think they have ironed it out now.

The reason I'm reluctant to upgrade yapeal, is that every time I do, it blows up in my face. Today was the database upgrade script.

I'm running it from the command line, but it kept complaining about not being able to find the database password, which is logical, as there isn't any. It also seems to be trying to connect over a unix socket, which is never going to work, but I guess this has more to do with php than with yapeal, as it worked later.

Now I'm not to worried about this, so I took a look at the script and modified it so that password is not required anymore.

I run it again and am confronted with the following message:

---
Failed to execute schema for util
Failed to execute schema for util
There were problems during processing please check any error messages from above and correct.
---

I probably do not have to explain that this does not help at all

What I would like to see is:

- What sections is the script updating at the moment?
- What queries is it going to execute?
- What is the result of the queries, and the result per section?

I've now added these things manually, but every time I update yapeal they are overwritten again. Hopefully adding yapeal as a repository instead of a folder will allow me to push some of these changes back to the community.

EDIT: That said, while I'm bitching about Yapeal a lot, I'm very happy you made it, since even if it's mostly just a black box for me, once it's working, it's working perfectly .