EVE Technology Lab

nevermind. i figured it out myself. damn api errors.

I use corpContracts every day, so it's definitely working in the latest build. I'd make sure that your table structure is up to date (maybe try a fresh install to test).

I will try to find you in game and have a chat, corpContracts is super useful.

In cases like Eveboard or a corp where you want to load data sort of on-the-fly, unfortunately Yapeal doesn't have a good mechanism to do this built-in. I would suggest a simple script that goes through utilRegisteredChar and sets isActive to 0 for all except the one that you want, then runs Yapeal.

If your primary use case is this on-demand sort of thing, honestly Yapeal is probably not the best choice.

I use a simple locking mechanism to ensure that Yapeal doesn't collide-- I touch a lockfile in my homedir before running Yapeal, and exit if the lockfile still exists. When Yapeal is done, I remove the lockfile.

Is this pretty much the same for characters but in the Registered character tab?

They get extracted into several sibling tables. For example combat settings for POSes are in corpCombatSettings, and there is a posID field that you can reference.

Hmm okay. I have this in the utilRegisteredKey table and it doesn't add a new key. Feel free to point out how wrong I am....

http://pastebin.com/1pF7hBut

Apologies if this has been covered somewhere. After reading pieces of the wiki and half the pages in this thread I gave up :(

I’ve built a few corp tools using Yapeal that only has our corp key in it. This works great!

We have another copy of Yapeal installed on a separate server that has all our member API keys. This takes 4-5 hours to run through all the keys/data.

What I’d like to do, is merge these two installs.

My question is, once I do that, will my corp API data be delayed because there’s always a back log of member keys to roll through?

If the answer is yes, is it safe to run a second install of Yapeal on a separate database so they can update independently?

So pushed out update to repo for people to test. Mostly update to *.xml and *.xsds for Eve API changes that have been made. Just a warning there might be some other refactoring changes also mixed in that I was working on a few months ago so good backups and test server use only until you've tested it highly recommended as I'm not able to do any testing right now

WARNING: Did include some work in progress so you'll need to just extract the needed updated files. The list of files needed should be as follows:
class/api/char/charCharacterSheet.php
install/map.xml
install/char.xml

From lib/Yapeal/Caching/:
char/CharacterSheet.xsd
char/MailMessages.xsd
map/FacWarSystems.xsd

to cache/ directory.

I successfully installed a second install of Yapeal, and up until a few days ago everything has been working great.

yapeal Corp = My Corporation Key only
yapeal Member = All my member's keys

My corp install (the one with only my corp key) will no longer pull API data from the key.

I suspect the notice below could have something to do with it?

• The corp key works in EveHQ fine. So the key is good.
• I created a new key, just in case. That one works in EveHQ, but not Yapeal just like the original one.
• I cleared the cache (was database, switched it to file to see if that would help, but still the same problem)
• I've done a fresh install of Yapeal latest (1.03) including database tables.
• I have my key in utilRegisteredKey
• I have my corp in utilRegisteredCorporation (tried with, and without. Was working before with it)
• My IP is not banned @ CCP
• If it helps, I'm on Ubuntu 12.04 at the moment

The only data that's populating is the non-key tables. For example, mapSovereignty, eveAllianceList, etc.

When I turned on TRACE in the yapeal.ini file, I occasionally see these on the Member install. And for a while, constantly on the Corp install. Since the fresh Corp install however, I haven't seen them.



I'm at a loss at what else to check. I haven't messed with the install since I confirmed it was working after the second (Member) install. (That was around March 13th or 14th)

Any advice/direction would be appreciated.

---

Update -

APIKeyInfo was not populating accountKeyBridge, AccountCharacters, accountAPIKeyInfo tables. Manually populated these tables, and it's pulling again.

Side note, my corp key won't pull on my Member install either. Same issue.