EVE Search - Yapeal PHP API library

Check My IP Information

All Channels

EVE Technology Lab

Yapeal PHP API library

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]


Author	Thread Statistics \| Show CCP posts - 0 post(s)
Dragonaire Caldari Corax.	Posted - 2008.10.22 17:56:00 - [1] Hi all I've started a new SourceForge project for people to look at. It's based on some code I've been developing for a while and I decided to release it under GNU LPGL 3.0 in hopes others would find it useful. http://sourceforge.net/projects/yapeal/ -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.
Dragonaire Caldari Corax.	Posted - 2008.10.22 18:00:00 - [2] Reserved for future posts -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.
Dragonaire Caldari Corax.	Posted - 2008.10.25 23:14:00 - [3] New version 0.1.0 available sorry for the broken one had up before. Not that this one might not have bugs but it should at least try to run ;) Also added MySQL files to build Database to db-tools directory.
Dragonaire Caldari Corax.	Posted - 2008.10.29 00:11:00 - [4] Ok been doing a lot of bug hunting and seem to have eve and corp API stuff working but still working on the char part. Needed to make a couple changes to the membertracking table so you'll need to drop and re-create it for everything to work. I'm not doing a release at this point so if you want the most current code need to get it from the subversion. svn co https://yapeal.svn.sourceforge.net/svnroot/yapeal/trunk/ -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.
Dragonaire Caldari Corax.	Posted - 2008.11.02 20:59:00 - [5] I've moved the project over to google code so it's easier for me to manage along with another project I'm working on now. -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.
Dragonaire Caldari Corax.	Posted - 2008.11.18 00:56:00 - [6] Ok after over 200 revisions according to subversion I think I've killed all the previous bugs that made it unusable. It's got a lot of fixes to database code since I've changed over to using ADOdb (included) instead of MDB2. Yapeal is now fully PEAR free so it should be much easier to install and use.
Dragonaire Caldari Corax.	Posted - 2008.11.21 02:36:00 - [7] Thanks I'm killing bugs as fast as I find them but going to need some help from someone with some of the ones you talked about because the alt I'm using doesn't own any POS so that might make it hard testing My original code that I extracted Yapeal from had all the eve/ and corp/ stuff I used working but with breaking it out into separate project, changing DB structure, and switching DB libraries many things ended up broken I decided to work on the char/ stuff first this time since I'd never got around to making it all work before since my other project was mostly corp stuff and usually once it's working for one it's easy to move changes into the other code. That only leaves the few things that's unique to each to fix if they are still broken. I'm up to revision 249 at this time so look for some more changes to be pushed back into trunk when I'm sure they're work. I'm trying to leave trunk as the more stable branch now that it's starting to work and I don't feel like I'm losing ground like before with it Also a trick I use during debugging is to have the XML caching on and then delete the records in the CachedUntil table for main script 'eve-api-pull' and which even one I'm test like 'MarketOrder' then see if it works or doesn't It's absolute need when working with AssetList and that 23 hour timer As long as it has a good cache file it doesn't try grabbing one from API and you can cheat on that to for testing by just changing the time in XML. Saves me a lot of 101 errors from API during testing and the server from some of the worse of my typos
Dragonaire Caldari Corax.	Posted - 2008.11.21 17:50:00 - [8] Glad you like it and thanks for the catch on the logo table but it was the PHP that was wrong. All the tables and fields are directly named from the fields in the API so when there's a difference on something look at Eve-Dev or in the XML for what it should be. So in the case of 'logo' it's now logo everywhere like it was meant to be. As to the 'range' field yes it sucks and there's a couple others but that what CCP used so that what I use and I just have to make sure I use the back-ticks or let ADOdb take care of any quoting for stuff like that. I drop the other POS stuff for now because I felt it needed done differently and didn't have time to mess with it right now and no way to test it but I think I'll have some friends from another project to help me out with that now. My naming for all the main tables should be in CamelCase just like the API calls are and the "sub" tables as I call them follow the XML which seems to be camelCase. The fields are also in camelCase so far anyway so that's what I'm using. For all the backend administration tables they should follow the same naming as well and as I am getting around to it I'm converting all the naming of class, functions, methods, and variables to follow PEAR conventions with a few mods here and there. Example with the function named 'getAPIinfo' I should uppercase the second 'I' and had the 'pi' lowercase but just didn't look right to me and didn't want to re-name it either Hope this has been helpful on see where some of the changes I'm make are coming from when not smashing bugs as I find them I've never tested it with any of the proxies out there but did make it so that any that act just like the API should work fine after all what we get from CCP is all through a proxy already on their end. Even if other proxies only follow the API naming and return XML and normal HTTP errors it should work but it would probably lose some of the special caching extras I've built in to work with the main API. -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.
Dragonaire Caldari Corax.	Posted - 2008.11.21 21:47:00 - [9] Never had any problem in that function with 'range' etc because MySQL is smart enough to know that you can't have it inside the insert (range) ... values() ... in duplicate key update range=values('range') statement that it's building and adding extra back-ticks might break it. What I need to do is change to using a prepare, execute instead but I haven't yet because I figured I'd run into trouble some where along the line between my code , ADOdb, and MySQL because of the on duplicate key update part. I didn't figure out a way to make it work with MDB2 but I should take another look at it now with ADOdb and see if it could work. It should be a bit faster to, although that doesn't seem to be much of a problem once I started using transactions for the larger updates of WalletJournal, etc. I've seen an up to 10x speed up since using the transactions. It has to do with DB not have to do as much locking it seems. There was even measurable differences down to 10 records level which is what others have posted on-line so that why you'll see I check for number of records in multipleUpsert() and use transactions for the larger ones now.
Dragonaire Caldari Corax.	Posted - 2008.11.22 01:16:00 - [10] Ok transfered all the fixes from char/ to corp/ and everything seems to be working. Can't test StarbaseList at this time so it's only one I really has any questions about. Did a complete drop and re-create on DB and everything works so it seems the code and SQL are in sync now finally. Still might have a few bugs but I've began to test it in crontab off and on now that it seem to be stable enough. It's not like I've ever had it caused problems just wouldn't always run right and filling up it's logs much faster then I could use while fixing problems -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.

Dragonaire Caldari Corax.	Posted - 2008.11.23 01:28:00 - [11] Yep certificates was an easy one to do and for now I'm going to keep try to fill in some of the missing sub-tables before I really try adding more to it. I've had it run now with crontab for over 12 hours and it's never glitch even though API did once or twice on me Been trying it on another hosted site with someone else's info and had a few problems but think it's something not configured right on site and we'll have to wait a couple days until owner is back in town to make some changes. Thanks for the offer on the cache files we'll see how it goes and if I decide to get the POS stuff wrote back in (it's commented out right now) I might contact you about them if friend doesn't get back where I can use him as guinea pig first -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.
Dragonaire Caldari Corax.	Posted - 2008.11.23 19:55:00 - [12] Ok did some looking around on prepare/execute in ADOdb and found that because mysql does things a little different they only emulate using prepare with it. Since that basically what I'm doing already I might as well use my code as their's While I was looking up stuff on prepare/execute in the MySQL manual I also decided to take another look at the stuff on insert and update about the quoting and decide even though I was right that it worked without problems as is, you were right oUTSKIRTs that the field names should be quoted with the back-ticks to insure no future problems so I've added them now in the latest versions. Glad you said something that made me take another look at it. Have them in there should help cut off some possible mystery bugs if MySQL purser changes or they add something to API in the future that could break it. -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.
Dragonaire Caldari Corax.	Posted - 2008.11.24 20:32:00 - [13] Yeah sorry about that broke it for a couple there but 280-281 works again I just committed what I was working on to test it and had to fix it only took a few minutes but seems you grabbed it while still broken Usually when I break stuff like that you'll start getting error and warning logs in cache/log/ as long is you have them turned on in ini which are on by default. -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.
Dragonaire Caldari Corax.	Posted - 2008.11.29 20:09:00 - [14] Just in case you hadn't noticed Yapeal doesn't have anything implemented to deal with the generation change that has happened with the wallet journal transaction Id. You can read more about the problem in this thread: Journal API RefID change I'd kind of forgot about them doing this so hadn't done anything to work around the problem (really was hoping CCP would just move to a bigint) but since they don't seem to plan on do that I'll be looking at a way to work around their bug Since I'm already using bigint for all ID type fields in the database it shouldn't be hard to work something out but main problem will be dealing with php5's lack of an native bigint. I'll update here as I decided on how to deal with it. -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.
Dragonaire Caldari Corax.	Posted - 2008.12.02 23:44:00 - [15] Added a new incomplete RegisteredCharacterManagement class and some helper files. Plan on having a couple more for Corporation, and User plus maybe ones to manage groups/ collections of the above. Thought I'd get some feedback on wither someone out there thinks they might be useful and maybe be willing to do some of the testing for me when I finish it up Still working on the WalletJournal generations stuff hope to have something to test in a couple days on that. -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.
Dragonaire Caldari Corax.	Posted - 2008.12.17 16:52:00 - [16] Hi glad to hear someone else finds it useful The basic information need for the RegisteredCharacter table can be found with a call to /account/Characters which only needs the info from RegisteredUser to get. Setting up and 'registering' characters, corporations, or users is a frontend application function so that why I really haven't added anything in Yapeal for doing it. I have been playing around with some ideas for managing those tables which you can check out in RegisteredAccountManagement.class.php and RegisteredCharacterManagement.class.php. They are untested and just some ideas I've have on how to do it. I've done a little more work on some of the ideas in a branch but it's tied in with some other changes I've been looking at making and I'm not ready show it to others until I've worked on it some more. For something that's more of a application framework you should look at another project I'm working on with some others at EMPA. It mostly in the planning/outline stage without any real code but it was a large part of the driving force behind the changes to the design of Yapeal. -- Finds camping stations from the inside much easier. Been known to write some PHP code for API from time to time too.
Dragonaire Caldari Corax.	Posted - 2008.12.19 00:28:00 - [17] Tanja Torture - Make sure you set `isActive`=1 but from the error messages you give it seems you have. The 'Tired of waiting ...' can mean one of two things either you never tried get that API before so there's nothing in cachedUntil to compare with or it's now more than ~5 minutes pass when cachedUntil says that API expired. It's just a notice really that I setup to help keep track when the API is acting up and let you know it's doing something and follow ThyShiva advise if that still doesn't seem to let you figure it out try turning on some of the trace stuff and look in cache/log/Yapeal_trace.log and see if you can find where it's getting to. I'll need that information to help narrow it down more. ThyShiva - You'll want to learn about 'nested sets' and how you use the `lft` and `rgt` fields to find what is inside what. Basic idea is if item is inside of something else the child's lft > parent's lft and child's rgt < parent's rgt. You can find more information about it in HierarchicalData which is from another project I'm working on with some other people. If you or others are interested in help with that project you'd be more than welcome as we've seemed to have stalled a bit after the planning stage We basically want to make a GPL'd modular API application framework that will bring all our varies other API projects together into one and then expand out from there. Like to see all the people working on API applications not be reinventing the wheel so much and get out something we can all use and contribute to so it can become truly useful for everyone. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.19 07:38:00 - [18] You're the second one to have problems in that area on Yapeal so I've added some more tracing code to revision 313 to try to narrow it down a little bit more if you could grab it and we'll see if that help me figure out why. I've never had any problem with that part of the code on my test server so it's really got me puzzled what's going on. For the other guy we just copied over my code from my test server and it started work but by that time he'd also changed host so wasn't totally certain what had cause the problem before. I'm also going to do some checking and see if it's something where I change it on my test server that didn't get back into the subversion some how. If we can't figure it out after you try new version we'll get together with E-mail and I'll take a look at your config too -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.19 08:44:00 - [19] Looks like you have the ones I need on already but trace_section=YAPEAL_TRACE_CHAR\|YAPEAL_TRACE_DATABASE are the only ones I should need to track it down more. If that doesn't seem to add any more output try adding \|YAPEAL_TRACE_REQUEST. I'm sure you've notice but just in case you missed it Yapeal never clears the log files it just keeps added to end so you have to always scroll down to see latest run or delete them so they start fresh. We might also try getting together in-game or on IM if we don't figure it out soon and report back to thread what we figure out the problem. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.19 23:12:00 - [20] Ok a little update for everyone make sure curl is install on your server and phpinfo() shows something about curl because it has to be added as ext to php as well. That usually means other package has to be installed on linux system or have curl compiled into php I'll be adding some addition check to Yapeal soon also so you get error messages if it not setup right. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax.	Posted - 2008.12.20 02:04:00 - [21] Edited by: Dragonaire on 20/12/2008 02:04:36 Thanks for the bug report but the SQL was right was bad copy&paste on my part in pulls-corp.inc that needed fixed. Market orders don't have accountKeys just ownerIDs. I've updated subversion with fix. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.20 20:11:00 - [22] Sorry about that forgot to post that you'll need to update your yapeal.ini file I change to using the mysqli driver for ADOdb and I noted it in svn commit but forgot to do so here. You'll need to change the line that reads driver="mysqlt://" to driver="mysqli://" and you'll be good. Should have been using it to start with since it's for the newer MySQL DBs not sure why I got started with the other one but thought I should change. Also means only need one file for driver instead of 2 which is always nicer You can also look in the sample ini which has the new line now too. I'm thinking about adding some kind of version info for ini file that it will check for so Yapeal can issue a warning if it's incompatible with your current one instead of just failing or that you can at least check manual for which is current and what the changes are. I don't change it very often but be nicer to have something in place. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.21 00:21:00 - [23] Ryel Theon - You were right to add it. There is a accountKey field for MarketOrders. I've now corrected pulls-corp.inc, pulls-char.inc, and the SQL file and added it to them all. I shouldn't try reading the forum and making changes to code when I'm half asleep I sometimes try short cutting and not double check myself against the XML files or Eve-Dev like I should So sorry everyone and reason it hadn't been caught much soon was the alt I'd been using to test with didn't have any market orders so I'd never notice it didn't work right I've now made a couple orders with that character so in the future maybe I'll notice when I break something like that The only API I wouldn't be able to test now will be StarbaseList and if I get around to adding it back StarbaseDetails. I've push out the change to subversion revision 319 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.22 18:01:00 - [24] Ryel Theon's instructions is a good summary of how to get started and yes the documentation is lacking still for how to use it. You will find the start of a user guide in the Docs directory but it is very lacking at this point and somewhat outdated. I've only tested Yapeal on Linux myself but I did try to design it so it could be adapted for use in Windows. If someone does adapt it for a Windows system I'd like to hear about it and any changes in the code that might be needed to make it easier. I'll try to put up some kind of summary or whatever of some of the key files in Yapeal on the wiki if I get a chance that might make it a bit easier to understand. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.23 06:17:00 - [25] Hi everyone been working on Yapeal some more in a branch to update some stuff and thought I'd post about some of the highlights or at least what I remember doing anyway Added a new class for tracing and changed code to use it. The tracing code was starting to get overwhelming and had some limitations that I'm trying to overcome. Added new required setting in yapeal.ini needed by new tracing code. There is now another variable named trace_output that needs to be set to "file", "database", or "both". Sending the tracing information to the database isn't active yet but is being looked at for the future. Removed the old unused setting in yapeal.ini for use_exception since all the code had already been updated to no longer use it. It was left over from time when code used both errors and exception in areas. Code now only uses exceptions so this setting is no longer needed. Changed location and how the CachedUntil table is updated. In some error conditions when the database wasn't update the cachedUntil time still would be, now the cachedUntil time is set slightly in to the future and only set to cachedUntil time from XML if we actual update the related table(s). This should also let Yapeal recover quicker from temporary error conditions by API server. Moved the function getAPIinfo() used to get data from API into it's own file inc/common_api.inc instead of having it in the inc/common_db.inc file. Fixed some typos in trace and error messages and probably made some new ones Also did varies other small changes here and there to code formatting etc. Soon as I finish posting this message I move my changes into trunk and push it out for you to get. Don't forget to update your yapeal.ini file with new settings as missing the added one will stop it from running. revision 355 is up with the new changes enjoy. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.23 15:16:00 - [26] Sorry I copied over that file here but forgot to add it to the subversion for trunk revision 357 should be complete with inc/common_api.inc -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.24 00:46:00 - [27] Hi again someone that's been testing Yapeal for their application has found an error with the IndustryJobs table. Seems that the `installedItemLicensedProductionRunsRemaining` field is set to -1 at times but I'd made it an unsigned bigint which doesn't work so well I'm putting out an updated yapeal.sql file for everyone. Here's also the SQL to change your active tables so you shouldn't have to dump and reload your data but I would recommend doing a backup just in case anyway ALTER TABLE `industryjobs` CHANGE `installedItemLicensedProductionRunsRemaining` `installedItemLicensedProductionRunsRemaining` BIGINT( 20 ) NOT NULL Thanks to ThyShiva for finding this and sending me the fix with the alter table included. revision 358 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.27 19:12:00 - [28] There are a couple ways to get the data you need but the easiest is to go to eve-online Then go to Eve Insider > My Character and sign in as needed Click on the character you want information for Click link to get XML data and from there you can get your characterID and corporationID Go back to character info page and scroll down to the API section and click the link there Read the info on the page about API keys then click button to get full API Key and either copy & paste it to a text file to save it or just write down your userID and API Key Now you'll need to add the information you've collect to the RegisteredUser and RegisteredCharacter tables like Ryel Theon wrote up in post 46 of this thread or you can find wrote up in the Yapeal wiki pages Hope that enough to get you started. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.28 23:51:00 - [29] Glad it helped. I tried going to the files you linked and I get '404 Sorry, the stargate denies you access.' errors so think you need to check the links. Now on to you're questions. The [database] section sets the defaults for all the [database-xxx] sections. So if you have something set in both of them the [database-xxx] setting will over ride what's in the [database] section. If you set all required settings in each active [database-xxx] section then you don't have to set any of the ones in [database] at all but it is easier to use just it if you're only using a single DB. In the original application that Yapeal developed from I use a separate DB for each API group (char, corp, eve, etc) and I've so far kept that ability to allow for more versatility by anyone using it. If you decide to use multiple DBs say to have separate character and corporation DBs then you would have to duplicate the overlapping tables like MarketOrders, WalletJournals, etc. for each DB. Each DB can have their own user/password pair if you want. You could probably even have all tables from the same API groups (char, corp, etc) have different user/password pair if you wanted in a single DB because of the way they are used. Each [database-xxx] section has several constants set from the yapeal.ini settings which are then used throughout Yapeal to access each 'DB' even though in most cases they are all set to the same values when using a single DB. Using a single user/password pair and one DB for all the tables is by far the easiest way to use Yapeal but if you need the more complex setup with multiple DBs and/or users it was build to allow for that. I will say though that the single DB with multiple users hasn't been tested by me but I see no reason why it shouldn't work. There is both a tracing and debugging section for now I have looked at combining them but they do have different purposes even though they often overlap when you are actually trying to debug something. I use the tracing sometimes to track the program flow where the debugging code and error messages are either missing or not as helpful as they could be. A good example of when this has happened was with a couple users that had no error messages but Yapeal still wouldn't download their API information. What it turned out to be was they had cURL installed but not the php extension you need so php can use it and php didn't throw any kind of error messages that we could find because it had been build with cURL in an extension module and it just wasn't loaded. I thought it would have give us some kind of error message when I called the cURL function but instead it just quietly failed Okay I think I've covered all your questions and hopefully you can fix those links and I'll have a look at what you've done and thanks for the interest in trying to help document Yapeal for everyone. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.29 19:24:00 - [30] Seems Eve-files still doesn't like something it's still got the same error An error on line 102 of backend/eve-api-pull.php which is the try { line would suggest to me that you've got a bad file some how probably through an unintentional edit while looking at one of them. I've put out a new revision 363 which you might try getting and overwrite the existing files see if that clears it up. Yapeal's been running without error on my test server for the last several versions so that's the most likely cause. I've done it myself a few times while looking around at stuff before If you can when opening a file in your editor just to look at it try opening it read-only. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax.	Posted - 2008.12.29 19:55:00 - [31] Mintoko - I've been looking at adding some kind of prefix to all the table names because some of the API re-use the same names in the rowsets but with different columns (fields) An example would be 'skills' in both the CharacterSheet and SkillTree. To add any kind of prefix though will require editing most the SQL queries in Yapeal since most places the table names are hard coded into the SQL Probably a bit of lack of foresight on my part but something that often gets overlooked when try to get something working. I'm working on some changes to Yapeal that should make adding more APIs in the future easier and as part of that I plan on adding some kind of prefixing system so it's less of a problem. I'm not sure when I'll release these changes since it's very much in an early stage of development and I haven't even got any running code yet so best I can say now is it's on the list of things I plan to do If you decide you can't wait and go ahead on your own and make something hopefully you'll share it back with us and maybe I'll be able to add it into Yapeal for everyone else that might have the same need. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.29 22:59:00 - [32] Ok I now can see the files and I'm looking through them as I'm typing here. You can use the lines from my crontab examples in the CrontabSetup wiki page by just not having the ''s in front of it. So /path/to/yapeal/backend/eve-api-pull.php should work on most systems. What I like to do is cd /path/to/yapeal/ then run it with backend/eve-api-pull.php as that also let's me do things like dir cache/log/, vim -R cache/log/Yapeal_error.log, vim config/yapeal.ini, etc which makes my life easier during debugging. So far the files look good though might want to check them with spell check. I also noticed you are setting the [DATABASE-UTIL] section to use another DB in your single DB sample which isn't a true single DB setup. After I've looked through them a bit more I'll probably add them to the subversion somewhere and make any changes to them I think of so you can take a look and see what you think. -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.29 23:38:00 - [33] Ok I added the yepeal_ini_docs.txt to trunk in config directory for now. Have a look and see what you think. I missed where you asked if a bad ini file could cause errors and it could but most of them should be caught as it is read by inc/common_backend.inc -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.30 16:08:00 - [34] Fishweasel - To download the code you need a Subversion client program which there's a link to a list of them on the Source tab. I use TortoiseSVN for Windows myself as I like the way it integrate with Windows Explorer but there are several others to chose from. I just use the normal svn commands with Linux and sometime on Windows too when it's easier then TortoiseSVN. If you just want to have a look at the code on-line you can click on the Browse link in the upper left corner and have a look around. At some point I may start releasing Yapeal as zip or tar.bz archives but it's changing sometimes several times a day (360+ revisions in last 2 months) that it's not worth the extra effort right now when getting started with Subversion isn't that hard even for someone that hasn't seen it before. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.30 16:58:00 - [35] Iskandara Cho - Either still have an unintentional edit somewhere or a file got delete somehow. At that point Yapeal have only ran the stuff in inc/common_backend.inc and a few require_once on some of the error/exception code from there and I've double check all of them both in my editor and by running it on my test server over night and I'm not seeing any errors You might try backing up your config/yapeal.ini file and delete everything where you have it installed and try re-installing the whole thing again. If that doesn't fix it it'll have to be something in your yapeal.ini and we'll have to figure out how you managed to get that error from a bad config file and see what can be done to catch it before it can do that. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2008.12.31 15:36:00 - [36] Very strange because I just did same thing and have no problems I'll sent you an e-mail via eve-mail and have you send me you're config file and I'll see if there's something there that I see and maybe try to get with you in eve or on IM too. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.05 00:25:00 - [37] Okay here's some tips on figuring out problems with Yapeal. First have a look at GettingStarted on the Yapeal wiki then check out the new TroubleShooting page I just made. It also might be useful to look at the other wiki pages while you're there. Hopefully after going through the wiki you'll be able to find the problem and it'll be something you can fix yourself, if not then you should have the information and log files to make my life and yours a bit easier while we try to figure out what's going wrong revision 398 now out. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.05 00:50:00 - [38] I made a couple small changes to config/yapeal.ini so anyone using Yapeal should check out the example file. For anyone having problems with Yapeal please make sure you're using the latest version and go through the pages I link in the post above hopefully by doing that you'll be able to find the problem yourself and not have to wait on me to check the forums. Ragga daPhunk - Not sure what you're problem is if you'll try out troubleshooting page from wiki it should help you track it down if not I'll need you're log files with trace_level=2 you'll find the instructions about this in wiki. PoshaX - Make sure to double check your configuration and the required stuff in all the RegisteredXxx tables I think there's something missing there. If after check those things you're still getting an exception I'll need the trace_level=2 log files from you too and try to figure out what's going on. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.05 02:48:00 - [39] Edited by: Dragonaire on 05/01/2009 02:50:37 Might also try sending me your logs Iskandara Cho. I never saw any from you after you made contact with me via E-mail etc. If you have any that is -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.06 18:50:00 - [40] Okay been working with Iskandara Cho on her problem and found something that might be useful for anyone else that having problem getting Yapeal running to check. Assuming a Linux system from a command-line try: php --version If the output reads: PHP 4.X.X blah blah blah OR PHP 5.1.X OR anything else Except: PHP 5.2.X blah blah blah where X is a number that's the reason it's not working for you. Some of you may have looked at the output from phpinfo as a webpage and seen that it says PHP 5.2.X but the Command-Line Interface version of PHP that Yapeal uses is a different file and on some hosting sites you end up with the php4 CLI and php5 for webpages In Iskandara Cho's case on DreamHost that was what was happening If you are hosted at DreamHost and you know Linux command-line a little try their instructions Advanced_PHP_configuration to fix the problem by following the ones for php5. You don't need the stuff for FastCGI for Yapeal but you might for the other stuff you're doing on your site I can't help you decide on that part Yapeal should work with or without. The other way to fix it is to make a small change to backend/eve-api-pull.php file but you will have to do this every time you upgrade Yapeal. For DreamHost change the very first line of backend/eve-api-pull/php from: #!/usr/bin/php To: #!/usr/local/php5/bin/php I'm going to add a page to the Yapeal wiki where I can add links and/or instructions for others but until then if you have this problem on another hosting service and figure out how to fix it please post it here and I'll add it to the wiki when I get page setup. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax.	Posted - 2009.01.07 08:40:00 - [41] New revision 421 out it should fix bug where Yapeal wouldn't run if trace=FALSE in [Tracing] section of config/yapeal.ini Yapeal project home http://code.google.com/p/yapeal/ -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.07 19:13:00 - [42] Ok decided to get some more input from people using Yapeal or other interested parties on things they'd like to see changed or added to it. Here's a list of things people have already told me about: Some kind of install/setup script Some thing to help with managing the RegisteredUser/RegisteredCharacter/RegisteredCorporation stuff Better documentation Anything else? Also what other APIs would people like to see added to it next? I'd like to get a little input on this and then I might even try making/adding some kind of development roadmap on wiki so people have something else to complain about on the forums when I don't always follow it I've already got one person that offered to take a stab at making an install script while I keep working on other stuff but I sure he wouldn't mind some help with it. For that matter if anyone out there has a programming itch and you know PHP or want to learn it I'd be happy to have the help that how Yapeal got started for me. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.08 20:17:00 - [43] Hi all been working with PoshaX? about the missing required fields problem in CharacterSheet and seem to have tracked it down to a bug in old versions of php5 on some Linux systems. In this case happens to be Debian Etch. -- Rant On -- Etch was released on December 18th, 2008 but bug was fixed in PHP Version 5.2.1 back in 8-Feb-2007 but apparently nearly 2 years isn't enough lead time for them to include it or a couple months isn't enough time to release upgrade to even Version 5.2.6 which came out in 1-May-2008 which fixed several security problems etc For those interested the newest release is 5.2.8 which fix a bug that slipped into 5.2.7 or if you're a little more daring they have PHP 5.3 out which backports some stuff from PHP6 as I understand it. I've already had an official update to 5.2.8 available for my old OpenSuSE 10.3 for a while now -- Rant Off -- Anyone using version 5.2.1 or newer of PHP shouldn't see the problem since that's when they fixed the bug. I've got a work around for the problem ready to be tested as soon as I get a chance to get back with PoshaX that I'll release if it works. BTW there's is a similar problem with CorporationSheet that my work around should fix also -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.09 01:25:00 - [44] Hi all me again been doing some cleanup up and move stuff around in Yapeal to streamline it a bit and make it easier for people to use. Some of the things I changed: Moved the Docs directory out of the project directories in trunk and all the branches and put them into their own top level directory. I never seem to have any time to update them so no need confusing people with having outdated information being included. Also makes Yapeal a little faster to download and easier to integrate for people that don't want or need to include them with their projects. Added new admin top level directory. I'm looking at maybe having a download/installer setup for people that don't or can't use subversion and I need to have a place outside trunk or the branches to keep the config files for it plus a few other misc stuff that isn't needed to use Yapeal but I need while working on it. So you might notice a few more things migrating over there as I run across them. Finally I found some nice little graphics again that someone made for me to use with Yapeal a while back and I decided might be nice for me to include them for people to use in their own projects etc. If you want to include one of them on your website with link back to Yapeal's website that would be great but only do it if you feel like it. I'm happy if you just let me know with post on forum or an E-mail that you like it and are using it. That's it for this post I think fly safe.
Dragonaire Caldari Corax.	Posted - 2009.01.10 18:15:00 - [45] Hi Satis Iqulenax glad you like Yapeal. Quote: Once you updating an assetlist, will this script delete those info that have been used or sold or related to that ?? No it doesn't try to make any changes to the AssetList or any of the other API data really for that matter. I don't see that being part of the job it's trying to do. Yapeal tries to just take what it gets from the Eve API and put it into the DB in what I hope is a sensible way. To do that and be usable by multiple characters and corporations it does add a few extra columns like ownerID, accountKey, etc to the tables but I never take stuff away I leave that up to you as the application developers to decide what you want to do. Just a couple things to think about if you try to update the AssetList yourself is that the itemIDs aren't constant in many cases. For example if you split a stack of ammo to use, sell, or just move part of a stack the old itemID is dropped and Eve makes 2 new IDs for the new stacks. The same thing happens if you repackage/assemble something it gets a new itemID. There are other times when it can change also I believe but I think you can see the problems with trying to update stuff as things change. Add to that that the next time Yapeal does get data from the API any of your change to Yapeal's AssetList table will be wiped and update with the data from the API. Hope that helps you if you try to do it yourself. Also for anyone else looking at Yapeal as a way to have a full archive of all of the Eve API data keep in mind that things like ServerStatus, AssetList, etc are thrown away and replaced in effect. I did this because I felt having it act a snapshot of the in game data was what most people would be interested in and what the APIs were made to allow. I am looking at adding an ability to directly cache the XML into the DB as received and may add an ability to have it archive that data but it would be done as a single large text column not as processed data with multiple columns. I'm also looking at having all the log files optionally/additionally put into the DB but have to be careful not to get into infinite loops doing that Note that by their nature the WalletJournals and WalletTransactions are an archive and the IndustryJobs and MarketOrders form a history of old records because they are updated with the API data until it stops sending each record. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.10 22:15:00 - [46] Quote: Also for anyone else looking at Yapeal as a way to have a full archive of all of the Eve API data keep in mind that things like ServerStatus, AssetList, etc are thrown away and replaced in effect. I did this because I felt having it act a snapshot of the in game data was what most people would be interested in and what the APIs were made to allow. You need to read the full post. But the way I worded it could be misunderstood so I'll try to rephrase it to be more clear. For all the APIs under eve, and server, they will have all their records truncated and then replaced by the new data pulled from the API. In tables like AssetList all records on a per ownerID basis well be deleted and replaced with the new data from API. For tables like WalletJournal, WalletTransactions, etc because of their nature they will just be added to. In MarketOrders and IndustryJobs they will be update by the new data until it stops changing then they do the same as WalletJournal, etc and keep a record of the last update received. This let's you look up old records if you want something that you can't do in game. Here an example for a market order. You make a sell order for some ammo as people buy it from you the record is update with the amount left to sell in volRemaining. Now the API may return a record where orderState=2 meaning it has either expired or someone bought it all up before it ran out. You'll have to check if volRemaining=0 to tell if it was bought out. We will continue to receive it in more updates from the API for a while because of how the API cache works but since our order doesn't change anymore it's basically ignored at this point. just like updates to unchanging records for WalletJournal would be. The record for your order will stay around until you decide to delete it. Hopeful this makes it more clear to you how Yapeal does things. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.11 01:07:00 - [47] Glad to hear I was clearer on my second try. At some point I would like to see Yapeal do all the APIs and I plan on making some changes to how the code works so it's easier then it is now to add more APIs. I'm hoping to get it easy enough that I'm not the only one that can seems to understand it well enough to add more BTW I like what Chruker has done on his site and sometimes use it but I find the tables at http://wiki.eve-id.net/APIv2_Page_Index more useful for what I do. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.12 05:12:00 - [48] Seems I got code from a broken branch merged into trunk there. Sorry about that everyone I'll push out my other branch that I know doesn't have at least a critical error like that one but I was still in testing. Guess most of you are use to being my beta testers by now Just not the alpha testers I'm in the process of changing how I work on the varies stages of code development and seem to be having a few hiccups getting the process organized and working, I also broke my main coding machine and I just this weekend got something that should be workable going again. Ok some quick notes about the new version I'll be pushing out everyone will need to backup your config/yapeal.ini file to another location. I would do a complete wipe and re-install as many of the files have changed names and some of them have change location. I also split and added several files for the error and exception code. You'll want to copy over the included yapeal.ini-example as I've been making several changes that aren't fully backwards compatible with the old one. The new one should be a bit easier to use as many of the comments have been updated also so shouldn't have any problems with it. I've made lots of changes to the error and exception code in this version that should make finding problems much easier in the future with more useful (at least to me) logging. Most people should be able to just copy over from your backup your database and user/password info into the [Database] section like before and activate the same [Database-xxx] sections as before and it should work. Fix out as revision 437 And a big thanks out to Satis Iqulenax for catching this -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.12 15:40:00 - [49] Ragga daPhunk - That error message is saying the simplexml extension is missing which is normally on in a default install. Just to double check that that is the problem try this at a command prompt: php -r 'if (!extension_loaded("simplexml")) print "Not loaded!\n";' If you get a 'Not loaded!" message you need to find out why someone changed from the default of including SimpleXML with php5 it is possible that another package needs to be loaded with some distros on Linux. Good news is it seems the new error code and settings is doing more and gave me a clue now to your problem I'm also adding a check for the simplexml ext which should make it more clear like it does with mysql and curl that they are required.
Dragonaire Caldari Corax.	Posted - 2009.01.12 21:31:00 - [50] I just looked at the install/Yapeal.sql file and there's no 'test' table in it If you were looking at the Yapeal.mwb by chance it was put there in the past only so I could keep track of it and is now a bit outdated since I'm made some manual edits to the Yapeal.sql file since I used workbench. Since I have another place to move it to now I'll be dropping it from trunk just to head off any confusion it might be causing others. As for downloading Yapeal file by file that's the painful way to do it you should install a SVN client program of some type that's really the way it's made to be used. The one I like the best on any Windows platform is available here http://tortoisesvn.tigris.org/ It adds commands to the right click menu in Windows explorer that makes getting a complete update from the subversion take only a couple clicks. It comes with some nice help files to get you started. I use it everyday on my Windows XP machine while developing Yapeal. I'm current looking for something as easy to use in Linux because so far nothing works as well or as easy that I've tried. I usual can do it faster and easier from command prompt so if anyone has some thing that works as good for a GUI let me know. The bin file is from some software I'm testing and plan on using in the future when the develop cycle slows down a little and I've learn how to use it When I decide to do that the software will make a Windows exe installer as well as some other versions. There's some things I need to work out also with Yapeal before I can start using the new software but one of the first things I'd really need to have is some kind of install/configure script which someone has offered to help work on as well as update/create some actual documentation for Yapeal which is badly needs if you haven't noticed While I'm at it I'd like to thank all of you for the feed back both good and bad and the bug reports as I'm limited on what I can test with my characters and the time I have to use for testing and sometimes coding. Since the start of November when I move project over to Google I've been averaging better then 100 commits to subversion per month Needless to say a few bugs slip past me from time to time -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax.	Posted - 2009.01.13 23:33:00 - [51] Think the problem he had was he tried to use the project member instructions which Google decided to list first instead of reading down to the non-member ones. Project members need to have read/write on the subversion but for just downloading Yapeal and getting updates to it the second instructions give you that. Or just follow the instructions Satis was nice enough to post above if you're using TortoiseSVN Thanks Satis Iqulenax for the nice simple instructions you posted. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.14 06:49:00 - [52] If you grab the files with a subversion client on Linux it should set the permissions right but if you grab the ALPHA test download I had up it probably didn't I noticed a lot of people were grabbing it so for now I've turned off the download section again. I had it there just for my own testing but like anything found on the Internet that makes it fair game once people see it Anyone that is trying to use the download version should grab the newest version from the subversion because the one in the file had some major bugs as it turned out. I'm current working on finishing some things that I didn't have ready yet when I had to push out the latest version to fix the very broken one I'd got out there before. Mostly some added stuff for troubleshooting and changes to error handling code. Once I'm done with that hope to start on some change to make adding new APIs easier and probably at same time be adding in some changes to add the table name prefixing that people have asked for. Been think about asking people to start using the Issues tab on the project home to start making feature requests so people can 'star'/vote for the ones they'd like to see done first. Would be ok to report bugs there too but I think most of us prefer the forums here so not planning on pushing for that any time soon.
Dragonaire Caldari Corax.	Posted - 2009.01.14 18:02:00 - [53] Sorry I did miss you asking that. Here a pages with some links I found interesting when deciding how to implement it. Johnathan Roark there actually developed the test code I adapted to Yapeal to replaced what I had been using before which was extremely slow. The library I was using before took up to 20 minutes to add 2000 records where now it's done in a few seconds -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.15 07:36:00 - [54] Okay I've pushed out a new version with all the changes to the error and exception code I had planned for now. Last bit to add was a tool to help me help people having problems getting it to run. Instead of having to make a bunch of changes in to the config/yapeal.ini you can just added "-d" to eve-api-pull.php when you run it and it puts all the logs etc into one neat (or not so neat) log file. It will also include your setting from the yapeal.ini (username/password blanked) and a full trace log (if it makes it that far) in there too Here's a simple example of how to run it assuming your in the base directory where you installed Yapeal: backend/eve-api-pull.php -d'../cache/log/debug.log' After it finishes or dies with an error you should find a file named debug.log in the cache/log/ directory. It will be a large mostly boring text file that you can look through if you want If after going through all the troubleshooting from the wiki you still can't figure out what the problem is you can sent the log to me and I'll take a look but do try to figure it out yourself first. WARNING don't try using this from crontab etc it's made to be used only with a manual run for debugging and troubleshooting. In other changes you might notice are some small changes to yapeal.ini mostly that I've now added version info to it. In the future they will become important but for now if you have a running system you can ignore them and don't have to upgrade it again or can simply cut and paste them in to yours if you want. At revision 454. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.15 17:39:00 - [55] Ragga daPhunk - First thanks for giving Yapeal a try. Quote: some sort of verification for api keys. Yapeal is a library not an application you need to verify the API keys before you put them into the database for it to use. What I may do is add a helper script you can use to verify and also sometime in the future plan to finish off the management classes I had start developing for the RegisteredUser etc that you'll find laying around in the class/ directory. Quote: when there is an authentication problem the script stops. It shouldn't stop working it should just skip over any APIs that it can't get because of authentication problems like it skip over them with any other API error. For example if you have 3 characters active in Yapeal and the 2nd one has a bad apikey it should still get the data for both 1 and 3. If it isn't doing that then that is a bug and it needs fix. I've now starting on a change to Yapeal that will change how I handle the API data which when it is done should make adding new APIs easier. Also after looking closer at the new trace logs I'm going to make some changes to how it makes and drops connections with the database server. As it is now even when it's just idling waiting for an API to need servicing it makes and drops 3 or more connections per API per character, corporation, etc. which could be much less if the code was smarter about how it does things. There's some other areas that need similar attention I believe but they are less of an issue for now. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.15 18:19:00 - [56] First I'd like to thank Satis Iqulenax for offering to help with some of the document fixes and additions she's working on. I'd also like to thank her for taking on making some kind of installer to make it easier for people to try out Yapeal. I'm also planning on move the backend/eve-api-pull.php into the base directory and renaming it to yapeal.php or something similar that should make more sense to people. I'll make a wrapper at the old location so it shouldn't break anyone's stuff they already have setup but plan on change over to using the new location fairly quickly after I do this. That part of Yapeal directory structure is left over from when I split it away from another project I worked on for my corporation at the time and want it to easily be integrated back into it but I have now changed Yapeal to much to be usable with the original project and I've stopped develop on the other project for now. I may make some other changes but they shouldn't make any difference to how you use Yapeal like this change will so just a little heads up on that. I'll be sure to let everyone know when I make the change which should be Soon(tm)
Dragonaire Caldari Corax.	Posted - 2009.01.15 19:33:00 - [57] Plan is to support all the APIs when done at some point but have no time frames on when. I plan on re-doing all the currently supported APIs and make sure they still work before adding any new ones myself. If you interested in adding APIs and seeing how it's done now the easiest one to start with would be the ServerStatus one in inc/pulls_server.inc followed by the inc/pulls_eve.inc then work up to the character and corporation ones. For those programmers interested in how I'm planning to change Yapeal might want to take a look at the IFecthApiTable.php, ILoadApiTable.php, and IStoreApiTable.php files in class/ directory. Still probably will make some changes to them but you should get some idea where I'm going. Just to throw around a few programming buzz words think Singleton, Factory Patterns, and maybe even a Reflection based plug-in system and an autoloader for classes.
Dragonaire Caldari Corax.	Posted - 2009.01.15 20:42:00 - [58] Best way would be through my E-mail either from the project files or the one at Google. I'm also usually on Gchat. I use an alt's name for them just look at the Yapeal project owner to figure it out.
Dragonaire Caldari Corax.	Posted - 2009.01.15 22:40:00 - [59] Looks good so far. All you need to use Gchat is the free Gmail account. I use Pidgin to view it because I keep my web browser busy doing other things like posting on the forums and have chats from other places I need to use so something that understand several IM services was the way to go for me but the browser based one works as well and doesn't require any setup. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.16 23:39:00 - [60] I'll take the blame on this one when you both said something about installer I wasn't paying as much attention as I should have been and realize it was two different people not just two different characters and the some person Since one seems to be aiming at IGB and other normal browsers it's not really bad to have two people working at it. I'll let you guys decide if you want to combine your work or keep do parallel development and then I'll cherry pick from both after you have both finished. Let me know what you guys decided or maybe we can all get together somehow and talk it over. A little point of interest on the number of connections Yapeal was making to the database server and how the new code I'm working on effects it. In testing I've getting an ~8 to 1 decrease in the number of new connections with more then one corporation using it that number should go higher because of more reuse of connections with balances, journals, and transactions etc. This should make anyone on a shared hosting happier since lots of DB connections can really lag you out if the DB server is overloaded. After a couple more tweaks (I seemed to be low on my quota of bugs today need to make a few more for myself ) and some more testing I should get this out later day.

Dragonaire Caldari Corax.	Posted - 2009.01.17 02:28:00 - [61] Really sorry for the mix up on this Satis Iqulenax think you could drop the commits and just have one at the top referring them to the example file and maybe the wiki pages instead that should cover it but if anyone else has an idea about this speak up. Make sure to include the new fields for version etc that I added I'll need that for some updating stuff I'm thinking about as well as when people ask for help and send me their logs. Ok Iskandara Cho guess this will leave you more time to work on the docs we also talked about instead which is something that needs done just as badly as the installer did
Dragonaire Caldari Corax.	Posted - 2009.01.17 08:36:00 - [62] OK new version is out with the improved DB connection code. I'm see 9:1 decreases in number of new connections vs the old code I knew it would be an improvement but didn't expect that much really. I might be able to tweak it a bit more but not to worried about it now for some reason I'll move on to the other things I've had planned to make adding new APIs easier I think for now. current version 464 Get it while it's hot!
Dragonaire Caldari Corax.	Posted - 2009.01.18 19:30:00 - [63] Satis Iqulenax - Sound good looking forward to having a go with it when you have it finished. On other news some of you may have noticed I've had lots of problems getting out working versions of Yapeal lately. Part of is some software I was try working in unexpected ways when merging branches back into the trunk but mostly it was because of how I was working and testing the code. The way I was doing it tended to mix things like the config file from one branch or the trunk with the code from the other etc. Needless to say that just doesn't work well. So after someone got on me the other day about it I started making some changes to how I've setup my testing that should help prevent that from happening. Another problem I have is because I only have 3 of my characters and one small alt corp to test with I just can't test the code like it needs to be. To try to solve the lack of ability on my part to test stuff I'd like to ask for some of you to help out as alpha/beta testers for me so the code can be more fully tested before I bring it back into the trunk. One thing I need from anyone that wants to help out as a tester is you most have an hour or two every one or two days when you can try stuff and either report back what happened or you can be on Google's IM with me when you are testing so I can ask questions and have you try stuff. I'll try to put up some more info on the wiki or somewhere about it but for now if you're interested in giving me a hand with this sent me an E-mail to either the e-mail in the code or my alt's E-mail dragonrun1 over at Gmail
Dragonaire Caldari Corax.	Posted - 2009.01.24 21:34:00 - [64] Thanks Satis Iqulenax for all the hard work on the installer know it took a while longer to finish it then we expected but it works well. Everybody that's been having any problems understanding how to setup Yapeal should be very thankful now to you for this Now on to other news while not helping Satis Iqulenax with the installer now and then I've been working on a branch where I've making some changes that should make everyone happy when I'm done. I've been working on the code so that adding new API will be much easier to give you an example of how much easier within a couple hours of get the first API convert I decided to add a few new ones just to test it and I ended up with several from the map working and also convert the ones I had before in eve over and working. So in the time it would normally take to do one I did 7 and have another mostly done while adding another section (area) for maps that Yapeal didn't do before. This is something I'd been want to get to for over two months now but other things have had priority. I'm also starting to add and test the table prefixing code as part of the change over in code while I'm at it which brings up another change I have been thinking of making. I thought I'd get some input from the people using Yapeal before making this change since it might cause some problems. The change is to no longer support having each API section in a different DB. To better understand what I'm talking about go over to the main Eve-Dev API page. The sections I talk about are like where you see Account, Character, Corporation, etc. As it is now in Yapeal each one of those can be in different databases with different user/password and other settings. This does let there be some nice flexibly but also makes for a more complex configuration to maintain and use. By dropping this ability to use multiple database it would greatly simplify the yapeal.ini and along with some other changes I'm looking at could get it down to maybe less then six settings while adding a bunch of per character and per corporation settings for which API you actual want. So for example now if you enable a character in RegisteredCharacter and Yapeal had stuff to get the SkillInTraining API it would interfere with your EveMon With some changes including dropping the multiple table stuff that is I believe not used by anyone it'll greatly simplify add per character/corporation settings on APIs so the APIs for things like SkillInTraining, Killlog can be added to Yapeal but turned off so they don't interfere with EveMon and Killboards you might want to use. Okay I'll stop there for now before this gets any longer and see what everyone thinks of making the changes. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.01.25 14:41:00 - [65] First off the reason there is a .htaccess in backend/ is YAPEAL IS NOT A WEB APPLICATION It is a library you use to make a web application with but YOU ONLY RUN YAPEAL FROM A COMMAND CONSOLE, OR CLI as it is know in PHP. The ONLY part of Yapeal that is made to be used as a web page is the installer. Everything else in it is made to be used from the CLI.
Dragonaire Caldari Corax.	Posted - 2009.01.25 22:35:00 - [66] Okay I guess I'm making to many assumptions here that people understand some things that apparently they don't so I try to clear some of them up for everyone. CLI or Command Line Interface is a generic term that the designers of PHP use to describe any console type interface i.e. NOT windowed or web. On most Unix systems this is normal sh, on Linux it's Bash or one of several others if the user changes it. With Windows systems you have cmd.exe which you can usually access through the classic start menu by Start > Run and typing in cmd and clicking OK. If you use anything like SSH to get to your hosted web server you are also run a CLI, usually Bash, with the input and output in effect redirected to your local machine over an encrypted connection. Cron or also know as crontabs is a system available on most Unix/Linux to run CLI programs/scripts for a user at different starting times and intervals. Generally only the interval part is used where it can be anywhere from 1 minute to hours, days or clear out to years in the future. Schtasks provides the same basic functionality as crontab does for Unix/Linux systems. Yapeal short for Yet Another Php Eve Api Library is a CLI PHP5 script that gets information from the Eve XML API and puts it into a MySQL database. A web based installer has also been made for it to help people get started with it but the main script is only made to be run from a CLI or as a crontab job. Hope this is useful to people and helps make some things clearer.
Dragonaire Caldari Corax.	Posted - 2009.01.25 22:51:00 - [67] Yeah the installer is in a raw Alpha/Beta state but we thought it was useful enough it was worth getting it out for people to use as we polish it and do a newer version with some more features.
Dragonaire Caldari Corax.	Posted - 2009.01.28 23:22:00 - [68] Just ran across a web page that anyone try out Yapeal on Windows and having problems with PHP might want to take a look at. http://www.corephp.co.uk/archives/36-A-Guide-to-using-PHP-5-Extensions-on-Windows.html
Dragonaire Caldari Corax.	Posted - 2009.02.06 05:46:00 - [69] Something that might give you and others a better understand of some of the power that nested sets gives you here some examples. Finding all your assets in the -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.02.10 20:51:00 - [70] Hi all it's been a couple weeks since I've really posted about any changes or updates on Yapeal so I thought I'd let people know what's been going on. I've been in the process of doing a much needed re-factoring on all the code that will make it much easier to maintain and add to. Many of the ideas for the changes I've been kicking around for a couple months but was put on hold until I had more of the bugs fixed and what I considered the base set of APIs working. The old code though it worked had several problems with it that made it difficult to add new APIs especially by anyone other than me and sometimes when adding new APIs it would break others. It also had some limitations that made adding some requested features difficult or near imposable without changing a lot of code. I've also been learning a lot about how many site hosting locations setup stuff for their customers and where things I had done with Yapeal made it hard for many people to setup and use it. Given all the above I decided to 'crawl into a hole' so to speak and do a near complete re-write of much of the code. Okay on to what this will mean for anyone using Yapeal which is all that most of you are interested in anyway Here's a broad outline of some of the changes/additions to expect. Table name prefixes. Many people are only allowed a single database at their hosting site so they need to have their applications and Yapeal tables all play nice together. I was also running into some issues with APIs using duplicate names on some rowsets which adding table name prefixes would also help solve. Ability to use multiple database to store all of Yapeal's varies tables has been dropped. This allowed for many of the other changes to be done much easier and was believed to be a largely unused feature. With the addition of user settable table prefix name the need for this is believed to be largely mote now so it was removed. There will be some changes to the database tables. All the table names have been changed to add a two part prefix the first part is user configurable and second part set internally by Yapeal. Some new tables have been add for additional APIs or old APIs that have been expanded on to make them more complete. Each API is now implemented as it's own class which solves many of the problems of changes to one API effecting others. This has also made adding more APIs easier and should make it easy for other programmers to understand how to add an API. That should mean not always having to wait on me to get around to adding new ones. This doesn't mean I won't be continuing to add APIs just that maybe I won't have to do all of them myself. At least that is my hope anyway. Some bugs and mis-features fixed. Probably added a few new ones but I've been do much more testing on this code then some of the code I've released in the past. The yapeal.ini has had a major overhaul and been streamlined. Dropping multiple database table support was one of the main things helping with this but there were many other factors that made this possible. Ok that should get you an idea what's coming. I hope to be finished with the conversions/updates and have finished all the testing I can do this week and be able to release everything into trunk for people to try out. I'll try to have a more detailed change list available when I release the code and probably have some instructions on what you'll need to do if you're upgrade from the current version of Yapeal.

Dragonaire Caldari Corax.	Posted - 2009.02.19 00:36:00 - [71] Hi all so it took a little more than a week but someone else decided to have an extend downtime on me but I've now merged all the changes into trunk for people to try. All current users be sure to read the updating.txt file in the root directory it has some important instructions on migrating your data from the old database tables into the new ones as well as some other information you'll need. Please report any bugs you find. I've tested this revision more that many in the past but some bugs may have got through since I have limited resources to test some things with the characters available to me. The currently supported API list on the wiki has also been updated for anyone interested. revision: 572 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.02.23 20:08:00 - [72] My general principal is to make each rowset a new table or anything that acts like a rowset ie attributeEnhancers and attributes in CharacterSheet became their own tables even though they aren't exactly a perfect match. I've also been naming the tables by the name attribute given to the rowset but here that's a problem as you have StandingsTo and StandingsFrom with rowsets having the same names (corp, alliance, etc) :P Quote: (one of them an enum field for the rowset name) I don't think a enum is way to go as I've generally tried to keep the tables free of any MySQL only data types so if someone wanted to port them to another DB backend that ADOdb supports it would be easier. It's better to use a plain text field and have a list of values that is enforced in the PHP instead. I did that with MarketOrders for the buy/sell field as an example. Where I have used MySQL specific SQL I've also tried to isolate it into a function so it only has to be changed one place to make porting easier should someone want to do so. Ok after looking at the both APIs some more the way I'd do the character one is to have the 5 tables named charStandingsToCharacters, charStandingsToCorporations, ..., charStandingsFromFactions. This does end up with 5 tables but it stay more in line with how the other tables have been done I think. The corporation ones look somewhat more complex at first but you can basically use the same system with them. corpCorporationStandingsToCharacters, ..., corpCorporationStandingsFromAgent, ...,corpAllianceStandingsToCorporations, ... Doing it this way does result in a large number of small tables with long table names but will make getting data back out in applications easier I believe. You've managed I believe to have picked one of the harder APIs to tackle first :) Having said all that if you feel like trying it the other way with the change from enum to a char column and post it so we can take a look at what you're thinking. Maybe we'll get some input from others and see what they think would be easier and make more sense when trying to use it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.02.24 17:25:00 - [73] If you're interested and have a Gmail account (it's free) I can add you on to the project if you'd like. Just contact me via either the E-mail from the code or my Gmail one which you can figure out from the project. If you decided you want to do that please include you Eve character name some where in the title so don't I delete it with the spam Anyone else that's interested in developing one of the other APIs is also welcome to email about joining the project. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.02.26 18:44:00 - [74] Hi again thought I'd let everyone know we now have a new Russian translation for the installer that someone did for us. Like to thank John for getting that for us. While I talking about translations for it I'd like to see a few more so if any of you are interested in helping us out with them please contact either me or Satis Iqulenax about doing so. revision 602 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.02.27 08:33:00 - [75] You're probably on a Debian or hosted site using Debian or something similar that has the CGI version of first in your path. Most better hosting will have a wiki or other resource to help you with what you need to do. If you can't figure it out on your own on a hosted site contact support and get some help. If you have console access you can also look around usually and find the CLI version of php somewhere. Once you know the location for the CLI version of PHP you just need to use the alternate crontab instructions from wiki. http://code.google.com/p/yapeal/wiki/CrontabSetup -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.02.27 08:37:00 - [76] You're probably on a Debian or hosted site using Debian or something similar that has the CGI version of first in your path. Most better hosting will have a wiki or other resource to help you with what you need to do. If you can't figure it out on your own on a hosted site contact support and get some help. If you have console access you can also look around usually and find the CLI version of php somewhere. Once you know the location for the CLI version of PHP you just need to use the alternate crontab instructions from wiki. http://code.google.com/p/yapeal/wiki/CrontabSetup -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.02.27 08:39:00 - [77] You're probably on a Debian or hosted site using Debian or something similar that has the CGI version of first in your path. Most better hosting will have a wiki or other resource to help you with what you need to do. If you can't figure it out on your own on a hosted site contact support and get some help. If you have console access you can also look around usually and find the CLI version of php somewhere. Once you know the location for the CLI version of PHP you just need to use the alternate crontab instructions from wiki. http://code.google.com/p/yapeal/wiki/CrontabSetup -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.02.27 08:42:00 - [78] You're probably on a Debian or hosted site using Debian or something similar that has the CGI version of first in your path. Most better hosting will have a wiki or other resource to help you with what you need to do. If you can't figure it out on your own on a hosted site contact support and get some help. If you have console access you can also look around usually and find the CLI version of php somewhere. Once you know the location for the CLI version of PHP you just need to use the alternate crontab instructions from wiki. http://code.google.com/p/yapeal/wiki/CrontabSetup -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.02.27 08:46:00 - [79] You're probably on a Debian or hosted site using Debian or something similar that has the CGI version of first in your path. Most better hosting will have a wiki or other resource to help you with what you need to do. If you can't figure it out on your own on a hosted site contact support and get some help. If you have console access you can also look around usually and find the CLI version of php somewhere. Once you know the location for the CLI version of PHP you just need to use the alternate crontab instructions from wiki. http://code.google.com/p/yapeal/wiki/CrontabSetup -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.03.02 23:55:00 - [80] First thanks for trying Yapeal. That you're getting anything that looks like headers talking about html suggests your not using the CLI version of PHP or it's mis-configured. Also you should be running yapeal.php not backend/eve-api.pull.php as that's change but the documentation hasn't caught up yet. Here's a few question/ideas of things that might help in figuring out the problem: Where are you see that output because you shouldn't every get that kind of output from Yapeal. It would be helpful to know what OS (Linux I assume since you said crontab) you're run it on etc If you look at the cache/log/ directory the log files there might help you figure out what the problem is or help me know what's going on anyway Did you try running it manually from the command-line before trying it as a crontab because you'll get to see more what's going on when you do that usually. Have you tried changing 'log_level' in config/yapeal.ini to E_ALL like suggested in the example for testing? Have you tried changing all the settings to the suggested ones for testing from the example they should give you a lot more information about what's going on both on the command-line and in the log files. Last thing that I probably don't have to say but better safe than sorry Have you checked you have the latest from the subversion? Current revision is 620 something at this time. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax.	Posted - 2009.03.03 14:28:00 - [81] Okay just something to add since you're on a hosted site without command-line access Have a look at my post in 156 sound like a similar problem and you'll probably end up having to do something like that. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.03.04 06:36:00 - [82] Good to hear and since you said something about them and reminded me, I've now gone through the Linux pages and updated them to be in line with newest revisions of Yapeal. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.03.05 23:27:00 - [83] Hi again I'm like to announce a new improved Yapeal for you all to try out. I'll give a quick list of changes here. Fixed bug with charWalletTransactions. This may require you to alter a table, details below. Added standings API for characters and corporations. Thanks to Ramov Tinoga for making it and writing such nice clean code made it easy to test and add with only minor additions. APIs to pull can be selected on a per char/corp basis ie if you only want to get CharacterSheet and AccountBalance for a character or only AssetList and MarketOrders for a corp now you can. Updated configurer thanks to Satis Iqulenax. It now includes an update section for those of you upgrading a recent version. Configurer now let's you select which APIs you wish to get. Needed to work with change above. The usual minor tweaks and improvements etc that I never seem to run out of Here's the SQL you'll need to run to fix the charWalletTransactions table. Quote: ALTER TABLE `charWalletTransactions` DROP COLUMN `characterID`; ALTER TABLE `charWalletTransactions` DROP COLUMN `characterName`; You'll still need the latest revision of Yapeal to have it work right but these changes can be made either before or after updating as needed. As always bug reports or a thank you are welcome. We are currently working on a couple more APIs and Satis Iqulenax has started working on an addition to the configurer so you can use it to upgrade Yapeal using a single button more information on these changes as the code is closer to being done. revision 656 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.03.07 20:51:00 - [84] Glad you like it and good luck with the application. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.03.10 23:42:00 - [85] Hi glad to hear it's helping you out developing your application. I've limited the utilRegisteredCorporation to using only one characterID because it made Yapeal much easier to program plus I believe easier to use since you only need to associate one character with the corporation to use it. Quote: I have one suggestion regarding the corp tables. Currently the ownerID fields within the corp tables is only the corporationID, but does not include any character related information. Would it be possible to add another "ownerID" field with character identifiers? If it did that I'd also have to make it part of the primary key which would mean we'd end up have multiple copies of say corpCorporationSheet or corpAssetList which isn't a good thing. Which is the correct one? How do we handle the extra record when a director leaves the corp for example? Plus it just not good database practice to do so to better understand why look up database normalization. Quote: Maybe call it ownerIDchar, and have it contain a space delimited list of the characterID for each character (registered in utilRegisteredCorporation) that can get that info from the API. This is also related to the above as to why not to add a column for this but to help you out developing the list for your needs I'll show you how to get this information from the existing APIs. First some background information you should know. The CEO of a corporation has full access to all the corp APIs using their full APIkey. Also any Directors in the corp has full access. Some of the APIs also let you have access by just being a member of the corp or by having some role in the corp like accountant, etc. There are a couple ways to look up if a character has the needed roles in a corporation. One is to use the charCorporationRoles* tables but requires that the char is registered and active. The other way to do it is to use the corpMemberTracking table which is much easier and only requires the corp API to be active. Using it does make for a bit of a chicken and egg problem when setting stuff up but that something that you'll have to solve as an application developer I will give you a hint on finding the corp members with director access though. You'll need to do something like this: Quote: SELECT `characterID`,`name` from corpMemberTracking WHERE (`roles` & 1) = 1; Hopefully that helps you understand the reasoning and ways you can get the information you need. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.03.11 06:58:00 - [86] The first link in the sticky above is best resource http://www.eveonline.com/ingameboard.asp?a=topic&threadID=1006676 You'll also find a few more links on the main page there to places like Chucker's that covers some of the same stuff in different ways and also stuff that Eve-Dev doesn't. There's also an example class for dealing with roles that I put out for people to use and abuse in the API Building blocks section near the bottom you should find useful. Basically the roles are in a 64bit long bit map so you need to mask it to find out which ones are set. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.03.13 23:44:00 - [87] Thanks for sharing you tips for things to look for and the workarounds. Only thing I'd add to your post is that in 3) if you used /path/to/php5 -c /path/to/php.ini -f /path/to/yapeal.php -c /path/to/yapeal.ini it might be better though the '-f' is supposedly optional. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.03.15 07:44:00 - [88] Had the tables done that way before in the API application I made that Yapeal developed from and I ended up taking them out because trying to get it all working was a nightmare. Also some people don't want their skill list to disappear when they delete their CharacterSheet for example. Also how to you handle corpMemberTracking when someone leaves one corp for another and they are both in the same DB? Much better for that logic to be in the application code where each developer can decide how they want to handle it. I've tried not to build in any interdependences between API tables as any that are added might interfere with someone's application they are making with it. There were several things that got designed into Yapeal as it was because how I had used things in my other programming that I've been slowly trying to remove so as to make Yapeal more useful for more applications. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.03.15 14:45:00 - [89] From the first post. Quote: Available through subversion at new home. I also now edited my first post to add some additional information and links that might be helpful. So to put it simple there aren't any 'downloads' at this time and may not ever be you need to use a subversion client to get Yapeal. You can find out more about subversion and what you need to do to get it at http://code.google.com/p/yapeal/source/checkout there's also some instructions for installing Yapeal on Windows in the wiki. http://code.google.com/p/yapeal/wiki/InsYapWinSer This has also been asked/wrote about a couple times already in this thread as I remember so there's probably some more info back a couple pages if you look. Just some notes for people that are on hosted server and don't have command-line access or no subversion access from it, you can get Yapeal on any computer and then upload it with ftp, etc just like you would any other web page or script. The preferred place to have Yapeal installed would be outside of any directory accessible by the web server but that isn't always possible I know and does make using the configurer very hard If you use a local test server (You should be you know) you can even copy it's configuration to your live server so you don't even need to run the configurer on the remote server which should make it easier to instill it somewhere else for added security. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.03.17 22:50:00 - [90] Just thought I'd let everyone know I've added a page to the Eve online Wiki about Yapeal you can view it at http://wiki.eveonline.com/wiki/Yapeal No new information in it since I basically took the wiki page from Eve-dev and dropped it into page but thought I'd let people know about it. In other news I'm working on some issues that have come up while working on a new API and some errors that have been reported to me by some others as well. I expect to have some fixes ready in a few days. Satis Iqulenax has also been work on some issues with the configurer that have been reported and hopes to have them fixed within a couple days also. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax.	Posted - 2009.03.18 00:54:00 - [91] Your the first to report it but I had spotted that when I was doing something else with the SQL files. It'll be in one of the upcoming fixes. Thanks for the report. For those interested or needing the fix before I merge it with the trunk change line 742 of install/Yapeal.sql to read: INSERT INTO `utilConfig` VALUES('version', '$Revision: 621 $') ON DUPLICATE KEY UPDATE `Value`=VALUES(`Value`); -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.03.18 23:21:00 - [92] Ok Now that they've changed it to something easier to work with I've added the Skill Queue API to Yapeal. I've also release some minor fixes the some of the SQL files, etc. The backend/ directory with the old eve_api_pull.php file has been dropped also. It was replaced by the Yapeal.php a while ago but I left the old file in for a while to let people have time to switch over but I've decided it been long enough for everybody to make the switch Revision 690 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.03.20 00:52:00 - [93] Actual the instructions were missing a step that is needed now to have it work. I've added the step about activeAPI that was probably causing you the problem along with some addition notes that should be helpful. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.03.20 14:44:00 - [94] Most APIs are deleted/truncated and then inserted but the Industry Jobs, Market Orders, Wallet Journal, and Wallet Transactions are not. They will keep the last values from the last update received from the API for each record and there for have a history that continues to grow. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.03.21 19:48:00 - [95] Hi everyone it's me again I've just finished killing some bugs in the latest API to be added to Yapeal. With some help from Johnathan Roark on it Yapeal now has Kill Log (Kill mails). You can now get them for both characters and corporations. Also in this revision Satis Iqulenax and I have been trying to fix all the problems that have crept into the SQL lately for both the main files and the ones used by the configurer. We're looking at making some changes to decrease the number of SQL files that need to be updated and kept in sync which should help some of the problems we are having now. There was a small bug in the Skill Queue that I also fixed in this revision. Work is still continuing on the problems with Wallet Journal and Wallet Transactions not walking back through API correctly but has been held up by a need to rewrite much of the code that Yapeal uses to connect to the API servers so has been slow going since it ends up effecting all the APIs to a degree and I'm trying not to break everything all at once for a change Revision 702 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.05.02 06:43:00 - [96] Hi guys I've fixed a few more things. The class/api/AssetList.php files for char/corp have been updated to use the new lvl column. charSkillQueue should now update correctly also. Revision 758 -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.05.02 19:48:00 - [97] Some more fixes. Fixed errors caused by merging a project member's killboard version of the KillLog xml definitions from one of his other projects instead of one without the extra columns Fixed minor missed edit to corpAssetList that caused warning messages when running yapeal.php Revision 759 -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.05.03 13:12:00 - [98] Quote: X-Powered-By: PHP/4.4.8_pre20070816-pl1-gentoo Your trying to run it with PHP4 instead of PHP5 which won't work. Yapeal requires at least version 5.2.1. I'm also guessing from some of the rest of the message that you're trying to run it with the CGI version of PHP and not the CLI. Just as a guess you're at a hosted site and you're using their so called 'cron' setup and not using the crontab command directly through a remote login like SSH to try setting it up which seems to cause all kind of problems for people. There is some help on the Yapeal website including some pointers in one of the issues on how to work around that. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.05.13 14:07:00 - [99] You have to use subversion to get it there's some instructions earlier in this thread and also in the wiki that should help you with getting it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.05.14 02:19:00 - [100] Glad to hear you've got it now. Quote: It is possible with yapeal when my user is register and put the api key, this key save it on database for future use from user? Any users, chars, corps that you add to the util.RegisteredUser, ...char, ...corp tables and is active Yapeal will get their info once you have the crontab setup but since Yapeal is made as a library for other developers to integrate into their own applications we haven't include anything to do that directly except for a single test user that you can do during setup for your own testing to make sure it's installed correctly. You should be able to find some more info from some of the other posts in this thread and comments in the issues and on the wiki that should help you more with Yapeal. You can also look at the code which is generally will commented IMHO anyway . You might also look through the stuff in the docs directory by browsing in the source code tab. I will say that much of it is meant more for a programmer then for an end user since Yapeal isn't an application but a library -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.05.19 02:45:00 - [101] My suggestion is try it with PHP 5.2.x or better and only with the extensions it needs to run. I'd also suggest looking through the install and troubleshooting info in the Yapeal wiki and see if that doesn't help you figure out where it's going wrong better. If that doesn't seems to help with your problem we'll probably need you to send us some some of your log files so we can figure out better where the problem is. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.05.22 11:15:00 - [102] Grandolfer The DB name can be anything you want so you can install Yapeal so it just adds it's tables to your existing DB if you want. If you look in the inc/common_db.php file you'll find the main functions that are used to do the queries to the DB. To use different tables in the DB for the userID, ApiKey etc you would have to modified the queries there and it should work The only problem would be when we put out new versions of Yapeal you would have to modify them again. A better way might be to make a view in MySQL to map your exist table so it overlays (renames) the table/columns that it wants but to tell the true I'm not sure if/how well that might work as I've never tried something like that and I am not a DB guru so don't know if that would work or not Maybe someone else will have some ideas about this also and share them with us. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.05.28 13:14:00 - [103] Hi everyone just thought I'd update everyone on some stuff we've been working on. Finally after many requests and a long time coming I've added the Starbase Detail API. This makes what I consider the 'core' APIs complete now. This means that any other APIs that get added by me will probably only get added if I find I need it for any of the other projects I'm working on that use Yapeal. I'll still be adding and improving Yapeal as I get time or I get inspired to work on something but doing so will take a backseat to other things for now. As always I will continue to fix any bugs that get found or reported. Hopefully other people will decide to write and share some of the missing APIs with the project as I would like to see Yapeal have all the APIs implemented and be truly complete. Since I've said something about working on other projects I'll tell you all about an old project that has come back to life that in part was why I made Yapeal to start with. It's called EMPA and is now currently it a very early alpha state of development by part of the development team of Yapeal plus a couple others. We're now working on the core framework which we should have to a usable state in the near future but everyone is welcome to download it and try it out but be warned it's in a rough state and subject to regular major changes and probably more than a few bugs I'd like to thank Satis Iqulenax and the others who have took up the project and really got it going again. I will probably also be working on some other small projects related both to Yapeal and EMPA but none of them are complete enough to talk about yet. revision 786 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.06.04 14:47:00 - [104] To Dirty Snipe and others that have tried to use the upgrade instructions in Updating.txt I'd like to apologize for the confusion they have been causing. Those instructions were for some changes we made back sometime in the revision 400-500 range and does not work for more current revisions. As often seems to happen during development the documentation doesn't also get updated when it should. As you noticed we have removed all the SQL files from Yapeal now that we've switch it to using the newer AXMLS system to do database updates in a semi-automatic way. To help people determine which revisions need to do what and what resources they (i.e. addition older files needed etc.) we'll try to put together something on the wiki to help out in the next couple days. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.06.05 04:52:00 - [105] lillitheve try just installing/copying Yapeal to your web server and browse to the url for install/setup.php once you've done that you'll want to try running yapeal.php from a command line so that Yapeal populates the database tables with the data APIs you have set active during setup. Once that seems to work right you'll need to create a crontab/scheduled task to run it every minute. For more details refer to the wiki pages from the project's home. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.06.05 13:54:00 - [106] Have a look at this article http://help.godaddy.com/article/1083 and look around at some more of their help about the path you may need to use to run the PHP5 CLI since it looks like they are like most hosting places and have the PHP4 version in your path by default instead of 5 Also look at the old issues at Yapeal's web site as there was some pointers there for how someone worked around a similar problem at another hosting.
Dragonaire Caldari Corax. Sex Drugs And Rock'N'Roll	Posted - 2009.06.12 06:21:00 - [107] Quote: It didn't seem to work with just my limited key. Does it really need the full access key? It also kept saying I didn't have the proper role to pull some of the data (I'm CEO so that's not right). Many of the APIs do require the full APIkey so Yapeal just assumes that what you gave it. As you've noticed it doesn't really matter if you are CEO or not some things just need the full key to work. At some point we might add Eve-Central data as well but I'm busy with new job right now and the rest of the team and I are working on EMPA which uses Yapeal for it's backend API stuff. That doesn't leave much time to add new stuff right now I am still try to get around to updating the docs so they are more current but not sure when I'll get that done. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.06.17 15:31:00 - [108] Hi looks like you solved your problem but thought I'd comment on the part about deleting the tables so the installer would re-create them. You shouldn't need to do that if you use the update part of the installer as it was made just for that. Only case where it will have problems is if you have a very old version of the tables that it doesn't understand in which case you might have to delete them so it can rebuild them correctly.
Dragonaire Caldari Corax.	Posted - 2009.06.25 15:37:00 - [109] No need to rename it that why we added the prefix stuff to Yapeal so if this became a problem there was already a fix in place When you run the instiller just make sure you use the prefix option when setting up the tables so for example all of them look like MyDB.YapealaccountCharacters etc.
Dragonaire Caldari Corax.	Posted - 2009.07.11 14:01:00 - [110] Barrington Farquharsen - What you'll need to do is add another row to the utilRegisteredCorporation table with a minimum of the isActive, corporationID, characterID, and activeAPI set with the information on the corp. ActiveAPI is a space separated list of the APIs you want it to get for that corp. You'll need a row in utilRegisteredCharacter that correlates with the characterID column. You'll also need to add a row in utilRegisteredUser that correlates to the userID in utilRegisteredCharacter and has the fullApiKey filled. You don't have to set isActive=1 except if you also want to get API data for the character. The characterID you have in utilRegisteredCorporation needs to have CEO or director level access in the corp for it to work correctly. That is because of requirements setup by CCP to access most of the corp APIs. Hopefully the above get you started down the right track. Yapeal was design to support multiple users, chars, and corps as that was a requirement for it in EMPA and also for it to be more generally useful for other developers. The installer only let's you add one of each as it is only meant to be used for initial testing for people to try out Yapeal before developing their own applications with it. Look for some useful util classes to show up in EMPA to make managing the utilRegistered* tables easier in the near future as more of what is being worked on in the branches get merged back into the trunk on it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax.	Posted - 2009.07.13 17:43:00 - [111] Can people get 'public' info about a corporation without being part of the corp? Yes Could Yapeal be modified to not require you to have corp member info to access the API? Yes. Do we plain on doing so? No, but it is open source so if someone wanted to branch it and do so they're welcome to do so and they would probably even get a few points from me on things that would need to be changed. Something that might work but I haven't testing is to point the characterID at your character info for the other corps and see if it'll let you still pull the info from the API. The only thing you might run into is Yapeal may error out because of any missing stuff in the API info returned since you aren't a member in the corp and don't have access. Also depending on how the API works when Yapeal passes your UserID and API key it may give you an error about not being a member of the corp. You would just have to try it with all the logging turned on and see what happens but it might actually work -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.07.16 15:18:00 - [112] Hi everyone been working on some stuff in EMPA and that's shown me a few areas where I could be improved in Yapeal as well. Decided to bring over the class autoloader first as it's one of the easiest and required little in the way of changes. It's something I had thought about doing before but never got around to so when the need for one in EMPA came up I wrote it and decided I should port it back into Yapeal too. In the process of adding the class autoloader I also made a couple small changes to the installer so it'll now cache the SQL it uses to build the tables. You can find the files in cache/. Some of you might find them interesting or even useful when move stuff between development and hosting servers. The ones it'll save if there's an error might also be useful during debugging for you and us Look for some more changes/improvements to show up as my work schedule and development on EMPA allows. revision 803 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2009.07.16 17:04:00 - [113] No this let's me get rid of most of the require_once statements that were scattered throughout the code. You can read more about what it effects here. I do have planned some changes that will effect some of the utilRegistered* tables and the ini file but not sure when they will be done. There will also be a few changes that shouldn't be visible to anyone using Yapeal but should improve it in several ways much like this change which doesn't really show up in anyway to the outside developers. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.07.22 13:24:00 - [114] Hi there has been some talk about adding Eve-Central and/or other pricing data but the latest person to talk to me about it is very busy with a couple other projects at this time so not sure if/when he would get any code done. I had some code in the original project that Yapeal grow out of that worked with the CSV feed. You could try the e-mail approach as well if you think you really need minute by minute updated data but the extra overhead and complications getting and decoding the e-mail would probably outweigh the benefits if you don't need that. If either or both of you would be interested in work on this let me know via my G-mail account from the project and I can add you to the project if you're interested in working on it in a branch. I could also dig up my old code for you to have a look at too. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.07.27 18:09:00 - [115] OrderID does recycle every so often so might think of using it and the date/time of the order but you will still end up with dups. In my old code I used the daily CSV and sorted and got rid of any dups in it as I went then when I upserted it to the DB I let MySQL take care of dups between the dailies. How ever you do it make sure you use the one with the latest date/time or you can end up outdated data. Out of all the orders in each CSV I'd say probably 33% were dups with the main trade centers running closer to 75-90% dups at times. In my old code I had it deleting any record older than a year and really anything older than 3 months is ancient history with Eve but just in case someone want to do some market trend stuff a year might be useful. Hope that helps. Like I said if you are interested in having a look at my old code let me know it was really rough but did seem to work well. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.07.31 17:11:00 - [116] Would probably cause you issue when trying to use the installer to update. The normal setting for MySQL is mixed case so I'd look at it's settings on your server myself to see if I couldn't fix that. I do know on Windows they seem to use a forced lower setting but it doesn't seem to cause any problems since MySQL just silent converts everything for you so the mixed case doesn't matter. I may look into adding settings to the DB connections in ADOdb to set for mixed case but you're the first one to have noticed it outside of one of the developers using Windows and I don't think it cause him any problems but let me know if it is and I'll look into it some more. The reason for the mixed case is the match the API as closely as possible and CCP does use mixed case in a very specific way in their naming. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.01 05:26:00 - [117] Yeah once you're sure it working the notice messages can usually be turned off without any problems do leave on the warnings and errors though as they can be helpful when something goes wrong. You'll also want to make sure you didn't turn on the tracing which is off by default -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.03 17:30:00 - [118] Ok just ran across something again and decided to add it into Yapeal. You can now view the syntax highlighted source code of any of the PHP files in a web browser. For example: http://localhost/path/to/yapeal/yapeal.php?viewSource=1 will return the highlighted source code for yapeal.php This is mostly for show but thought I'd add it anyway Developers or someone trying to learn PHP might find it useful. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.17 14:41:00 - [119] Aedrine if you just want the raw XML to start with why are you trying to use a library when you can just grab the XML directly from API if that's what you want -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.20 18:13:00 - [120] If your server doesn't have mysqli I think you'll find there are also other things missing as it's a normal part of the standard build as defined by the PHP org that everyone seems to ignore but as to you're question since Yapeal uses transactions for some things (most of the API table updates) which the mysql drive doesn't support you'll run into trouble. There are reasons that I've set the requirements to what they are and they really aren't that hard to meet given a relatively new and correctly configured server. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.21 04:38:00 - [121] Don't know if it'll help you much with them but point them to this: Quote: Note: If you are using MySQL versions 4.1.3 or later it is strongly recommended that you use the mysqli extension instead. from the docs for PHP 5 which you can find here and might also point out that mysql ext is in maintenance only mode now which is shown in the table at the bottom of that page and next step is to drop support for it. Hope that extra information can help you to get them to move out of the dark ages -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.23 04:49:00 - [122] Think the problem is you don't understand what Yapeal does for you and how it works. I'll quote from the main page: Quote: Here's an extend explanation of what Yapeal does since it a little different then the other PHP API libraries people are using. It not only grabs the data from the API for you but also saves the data into a MySQL database as well. It was made to be ran from a crontab job and works in the background to 'Auto-magically' as I call it, keep the database updated so all you have to do is work with the database tables not the API and XML. It was made to be set and forget once configured. So basically it's grabbing the XML data from the Eve API and storing it into database tables for you and you get to write the application that takes the data from the tables and shows it to the web browser in some interesting way No part of Yapeal works with the IGB as other than the installer/test configurer nothing shows a webpage. There is a little code in all the PHP files now to show their source code in a web browser when passed ?viewSource=1 as part of their URL but that's so people can look at the files with source code highlighting not as any kind of normal operation. Hopefully that makes things clearer for you. You might also take a look though the wiki as it has some additional information you will probably find useful. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.23 07:31:00 - [123] Yapeal is made to be ran every minute in a crontab and keeps track of the cachedUntil times itself so it plays nice with the API servers. The data in the database will be update as often as the API allows with a tiny bit of randomness to help disperse bursts of calls to the APIs. As to if the API servers can handle thousands of accounts grabbing all that data that's a better question asked of CCP than of me. You put your info into the utilRegistered* tables for any characters and/or corporations you want data for. We are currently working on some changes that should make managing available APIs etc in applications easier as all the settings will be in the DB instead of a mix of the DB and the ini file. The installer is last part that needs updated before it's released in the trunk so people can try it. The main programmer for the installer was busy in RL plus his MySQL server had crashed on him and needed re-installed Hope to have new version out this weekend or this next week at latest. Also look for future version to add a way to call APIs in an 'on demand' basis in addition to the current crontab system. Using that should scale much better for larger web applications while causing less loading of the API servers. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.23 15:01:00 - [124] If you look through the revision history of Yapeal you'll see where it's gone from a completely procedural library to a nearly completely class based one over time as it has been refined. The changes that I'm currently working on will move it farther in that direction and will add some new or at least better refined options for proxy support and other things. All the changes are coming about because of some need that the development team has thought of, has come up during development in EMPA or one of our other projects, or been brought to our attention by someone using it. Some of the things that are being added to Yapeal now or are looking at adding are things that we said no to in the past. There have been many reasons for saying no to stuff in the past the main ones being: The state and design of the code at that time just didn't support it The main developer (me) didn't have time to do it The problem wasn't explained well or more often mis-understood by the developers Developer knowledge and backgrounds. On that last point in my own case this was only my second PHP project though I've programmed in many other mostly procedural languages on projects before. For some of the other developers this was their first project ever in anything or at least in PHP. We have also had developers with more experience helping along the way too. Time frame for the 'on demand' code is unknown at this time but is being developed by us for a designer of another project with a large community of Eve users (Thousands of users) as part of a re-coding project on their site. It'll be some time after the current changes we're working on as some of them are needed to make it work. So figure on any where from a week to a month or more depending how that project goes and when we get these current changes done. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.28 06:38:00 - [125] Some corp APIs can be access with some of the other roles but basically you do need to use the CEO's or a director's full API key to access stuff and the best info for that is to look at info from eve-dev wiki and/or stuff at Chucker's site which are in the sticky above. As it is now the roles aren't being updated correctly but that will be fixed when I do the next merge from the current branch I've been working on. There will also have some what more intelligent handling of some of the API errors so it can auto deactivate users, chars, corps, and their APIs. I'm hoping to merge the new stuff into trunk on Friday or at latest this weekend. When I do I'll try to post a good list of all the changes that have been made and bugs fixed. Yes the roles are in the character sheet so you can see what roles and titles they may have in their corps. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.28 18:14:00 - [126] OK here the short version of the changes in Yapeal. All the Eve API classes have had some code clean done to them New abstract classes have been made and are used by the the Eve API classes The inc/pull.php files have been replaced by new class/Section.php files Much of the code dealing with API sections in yapeal.php have been moved into the section files where it belongs now Required memory footprint for Yapeal have been reduced by breaking up the larger API upserts into 1000 record pieces instead of one huge upsert. Most error and tracing log messages have been updated and should be shorter and more useful Yapeal should now use less connections to the MySQL database server by re-using existing connections Yapeal now uses SPL Iterators directly in many of the new/updated classes and functions/methods where it didn't before New utilSections table was added to database and some new fields were added to the utilRegistered* tables to support the new proxy config stuff config/yapeal.ini has been change with many of the settings having been move into new utilSections table to make managing them in an application easier Now each char/corp can have their own proxy setting as will as each API section can have it's own default that will be overridden by the individual char/corp one Yapeal is now more proactive when it come to dealing with Eve API errors by deactivating users, characters, corporations, or individual APIs of them as needed and logs an error message when doing so Yapeal now 'soft' limits how long it will run to approx. 5 minutes Many other change that I've forgot Everyone should make a backup of their DB before updating to this revision of Yapeal, then make another one just to make sure Anyone run a revision of Yapeal before about revision 800 will probably have some problems upgrading because of all the change to both the code and DB. Everyone needs to run install/setup.php from a webbrowser and it should update the DB and config/yapeal.ini for you. I will try to document the changes more on the weekend. For anyone that is really interested in understanding the code have a look at https://yapeal.googlecode.com/svn/docs/Developer Guide/phpDocs/ where you'll find two version of Yapeal in HTML format. revision 857 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.30 18:17:00 - [127] Ok here's a list of some bugs that were fixed: Sub-tables of CharacterSheet like rolesAt* and titles were not clearing old data. Now the old data is delete before adding new ones so no one just accumulates roles Same type of fix was done on several other APIs that had same problem as above with accumulating stuff Time out error exceptions, etc. from cURL were not being handled at all in the API files. They are now catching these exceptions correctly -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.31 15:41:00 - [128] Even if you obey the cachedUntil time sometimes you get that error it's a pain in the A$$ that the Eve API servers sometimes get behind on their accounting for which ones you've got already (I've added all kind of delays, etc to try minimize the number of errors) but sometimes you'll still get a few You'll also get some of those errors if you stop and restart the MySQL server as the utilCachedUntil is stored in memory and is cleared every time you restart it. So to directly answer you question yes it normal to get a few of those from time to time but it should only do it once in a while usually when the API servers are under heavy load or having other issues. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.08.31 16:34:00 - [129] Just was going through my logs this morning and noticed some errors with the new exception code functions Everyone should grab revision 867 BTW Teavan it could have been related to the extra error messages you were seeing as it was effecting updating the utiCachedUntil table. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.01 06:01:00 - [130] How can something work without any errors for a week then after merging it into trunk it starts throwing all kind of errors and exceptions Anyway give revision 870 it has the fixes. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.01 16:38:00 - [131] Think I've finally fixed a long standing bug with KillLog, WalletJournal, and WalletTransactions walking code where it would throw mostly errors instead of working right. As goes with most errors of this type the fix was simple and easy to do once found revision 873 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.03 16:12:00 - [132] I haven't been changing yapeal.php that's why the revision number doesn't change. That's cause by way svn works I'll have to remember to make minor change to it so it'll update too once in a while As to the locking up problem I don't know why you're having problem as I've been running it even minute in crontab for several days without any problems. I would suggest you setup your crontab correctly by having it run every minute. * * * * * /path/to/yapeal/yapeal.php By not letting it run every minute you're keeping it from doing part of it's job correctly which is pulling the APIs by the cachedUntil times and also it tries to even out server load over time with some randomness which also won't work as well with running it only every 10 minutes. To get more error logging to see what's going on try these settings in config/yapeal.ini: cache_xml=TRUE log_level=E_ALL\|E_STRICT trace_active=TRUE trace_level=2 trace_sections=YAPEAL_TRACE_ALL That should give you a LOT more logging that may point to where the problem is. As far as I know no one is work on MemberSercurity if you want to work on it send an E-Mail to the project manager's G-Mail with your G-Mail account and I'll add you to project and we'll setup a branch where you can work on it in the svn. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.04 15:22:00 - [133] An issue has been reported with the MemberTracking API in issue 20 only storing the last corp member for each corporation. Thanks for the error report Matthew. You can read about the fix in the issue. I've also corrected an error that was leaving all the Eve API error XML files in the main cache/ instead of cache/{section}/. Revision 880 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.06 19:03:00 - [134] The problem is the docs haven't caught up the the code it seems, sorry about that. Try putting the API names in without adding "char" or "corp" to them that was a change that was made when updating to use utilSections table etc. that just was done a couple weeks ago. I'll look through the docs again and try to get them updated as it seems I missed that. Maybe a little while as I was just up until 5am re-doing Linux on my development machine after making mistake of trying the bleeding edge version of my desktop and still trying to get everything setup right again . -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.06 20:40:00 - [135] Guess you missed this: Deprecated - Use web installer I've updated it to: WARNING Deprecated - Use web installer but I did update the part about adding APIs to reflect the setting for ActiveAPI also while I was at it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.08 18:09:00 - [136] In install/setup.php it does have a test character section to it after the basic config but it only does one char and corp. It wasn't made as a full application just something to help people try it out before building their own app around it We are working on adding some wrapper classes around the utilRegistered* table to make it a bit easier for anyone using it to work with them. They are in alpha testing now and should be done within a couple weeks. Also just started on some per char/corp on-demand style API classes that should be useful for apps that don't want, need, or can't use crontab for some reason. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.08 18:19:00 - [137] I know some people have had some luck using Yapeal with CGI instead but it's not something I've done. From what I understand of it you may be able to just use it directly but not sure. Have a look in the issues and wiki for some pointers that might help. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.14 16:49:00 - [138] When they take the API servers off line like that there's no way to get a new status so it doesn't update it again until a new one is available. If you want to know if it's stale also look at the date/time and if it's more then say 15 minutes old it's probably not being updated. Once again this is something to be handled in the application being developed it's not Yapeal's place to be deciding if it should return something other than what the API servers tell it as that would be beyond it's function which is to only return the most complete and current data as possible in a useful format for you to use. Quote: In computer science, a library is a collection of subroutines or classes used to develop software. Libraries contain code and data that provide services to independent programs. from Wikipedia You are the programmer for the 'independent program' that uses it but Yapeal isn't the program it just makes it easier to write one IMHO anyway -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.17 05:30:00 - [139] The peak memory use is nothing to worry about that is just there as it says as a notice. If you ever see one larger than about 12 MB do let me know as I've been trying to reduce that and in my testing it's not going over about 12 MB now. Do you see a record in the charAccountBalance table? If not then there might be a problem. First make sure you've activated that API both in the utilSections->char->activeAPI setting and in the utilRegisteredCharacter. You might also try deleting the record and see if it reappears if it does it's being updated but the API isn't changing which is an issue for CCP to solve -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.18 04:37:00 - [140] For that check out the stickys about the static data dump which you can get in MySQL format and look at the invTypes table. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.19 17:38:00 - [141] Ok someone has found an error in the charMarketOrders and corpMarketOrders tables that is cause duplicate records to be created. You can read more about it at http://code.google.com/p/yapeal/issues/detail?id=21 and find the fix at http://code.google.com/p/yapeal/wiki/Issue21fix I'll be releasing an update in a couple days for Yapeal but because of the nature of the error the above instructions MUST be used first or running install/setup.php again will either fail or end up deleting all you data which could be a bad thing on a production application with real data you'd like to keep. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.21 16:13:00 - [142] Ok I've deployed the fix for issue 21 to trunk all existing users please make sure to look at http://code.google.com/p/yapeal/wiki/Issue21fix before updating as this revision could cause you problems like lost of data. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.09.27 19:47:00 - [143] Sound like you maybe try to use an yapeal.ini file from before the latest changes to it's format. I would suggest backing it up and then deleting it and try running setup again and see if it doesn't work better for you. The installer should have been able to update it for you but not sure how well that was tested. On a related note look for Yapeal to be moving to a totally new and different installation and configuration system soon(tm). It will have a multi-platform GUI and CLI installer instead of the current drop into web directory and configure system. The current system will be kept in place for now but long term it will need to either be rewritten or just dropped if it is determined that it isn't needed anymore. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.10.03 19:13:00 - [144] Notice: Talks about something that someone may find interest to look at Warning: Something probably went wrong but the program could continue to run. Can mean an bug in the program or just some bad input and output (GIGO) Error: Something went wrong and the program stopped running. Usually a bug in the program that needs fixed. Can be cause by either logic error or getting unexpected data that wasn't taken into consideration by programmer in program which probably needs to be fixed also. Exception: Similar to a warning and usually used to handle something that might cause an error if it hadn't been caught by the programmer and handled in some way. Uncaught exception: This is a exception that happens when the programmer some how missed handling an exception but was smart enough to add something to let him know he missed it. From the above the only ones that normally need to be worried about are warnings, errors, and uncaught exception and be reported as they will need to be fixed or at least figured out why they have happened. Notices and exception are mostly use to help figure out where something want wrong or right, or just so you know something is really happening -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.10.04 16:58:00 - [145] The proxy can be left blank except if you want/need to use one. The default is to use the normal API servers if not set. Quote: In the table utilconfig : fields charAPIs and corpAPIs are null... is it normal ? If you didn't run the config/install that would be normal and that table isn't use by anything but it and can be ignored. Do make sure in the utilSections table you've add the APIs to activeAPI that you want to get for each section as they act as an admin override to what utilRegisteredCharacter/Corporation are allowed to do and of course isActive needs to be set in it too. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.10.05 00:22:00 - [146] Just like with assets the order of the items and locations isn't sorted come from the servers. It's common to have assets say in corp hangers at a station be in the order item, item, item, container, item, container, ... From want I've seen the killlog seems to do the same thing. The only constant is if something is inside something else it will always be inside it's parent container but even between 2 different pulls the order of the containers and/or the things inside them can change. Welcome to the world of most DB systems where if you don't add any 'order by' clause you get it in some random order that even the DB designers couldn't tell you how it decided Since we don't have anyway to pass an 'order by' to the API server and CCP didn't include any in their queries it was decided that Yapeal would 'pass the buck' on this too and let the developer using it decided how to handle the order after the data is in the local DB At some point I might re-visit that part of the code and see about re-ordering at least the container vs the stacks of stuff. Probably it would end up like: container, container, ..., item, item, ... but doing that is a very low priory for now and unlikely to be done for a long time if ever. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.10.06 05:18:00 - [147] Yapeal just stores them as it gets them. The flags are the locations where stuff was from which you can check what each means in the table here. http://wiki.eve-id.net/API_Inventory_Flags -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.10.15 07:06:00 - [148] Seems you've found some kind of bug that causing an uncaught exception and elog isn't being included soon enough to log it which cause another error Try adding these lines to install/setup.php right after line 48 and see if at least it'll log the actual error that you're having so we can properly fix it so that exception gets caught. /* * Require elog file / require_once('..' . DS . 'inc' . DS . 'elog.php'); Once we have a better idea what's the root cause of error I'll add fix to trunk for everyone. -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.10.15 16:00:00 - [149] Thanks Ariacus for finding the bug seems when I committed that last one the changes I was making didn't all get saved to disk before I did it I was trying to make sure I had a good 'off site' backup of my work before going on a trip in case something happened to the laptop I've been using as main development machine. As usual when doing those things in a hurry something got missed revision 904 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.10.16 16:37:00 - [150] Quote: Is there a way to get yapeal to autocheck during the API update cycles and update the details in utilRegsitered tables. It does do some changes now. Example if a eve account isn't paid up and the APIs aren't available it does deactivate the user, chars, corp for that one so you don't get loads of API errors from the servers, etc. As to having it update them with corp changes etc. there are several problems with that ie how do you handle when they change corps and in the old corp they were a director and use in RegisteredCorporation but in the new one they aren't or in their new corp some other char is set to do it should their information over write the existing? Depending on the application the answer can be different and that just one example. That why I've left those types of things out of Yapeal as it needs to be decided at the app developer level what to do and not in the library. I only very recently changed it to change isActive based on API errors because I'd changed the code in a way that it wasn't really possible to handle it any other way any longer. For some more example of why not to make how Yapeal of even your app to depend on the API for that type of stuff just look at the several thread in the forums here where people were using the APIs to add and remove people from their corp/alliance forums and when the API was down for patches etc everyone was dropped from their forums include in some cases the admin user One reason I took a path that used isActive was I didn't want a bug or any type of logic error on mine or someone else's part to be able to screw those tables up because they are so important to how everything works. It's one thing to use the API information to say prompt an admin that they should update the information and even offer to do it for them but to do so without their knowledge is asking for problems IMHO -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.10.27 18:32:00 - [151] Hi all, Thought I'd let everyone have a look at something I've been working on. I've been working at a replacement for the current install system used by Yapeal.The current system was largely the work of Satis Iqulenax and has been a great help in making Yapeal easier to install and setup which I have no doubt helped to make it more popular. Satis has done a great job with it and has been one of the best programmers I've worked with and has done a good job keeping up with the very demanding work load in Yapeal and not just on the installer but help on many other things with Yapeal. Unfortunately Satis has had to move on to some other Eve related projects for his corporation and others. That leaves me with the task of keeping the installer up to date and change it as Yapeal changes that Satis use to do. In getting up to speed on the code it reminded me of several things I'd always want in the installer but we'd never got around to doing. One thing that had always bothered me is it was web base but Yapeal is really a library that is meant to be run from a CLI. Nothing in it required a web server except the installer and there was no install/configure help if you did install it on a computer without a webserver. So after think on that and some other issues with it I decided to go a different way and switch to a commercial installer that provides free licenses to open source projects. It's called Bitrock InstallBuilder and I release a early ALPHA test installer examples in the download section of Yapeal's website for people to try. I need to cut this post short as I'm running late for work but I would like some feed back on what people think of it so far. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.01 06:22:00 - [152] Make sure you're running at least PHP version 5.2.1 or later and that the date extension is installed. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.01 08:49:00 - [153] Look at activeAPI, isActive in utilSections as it will override utilRegisteredCorporation. Make sure you increase the logging also as it might give more information about what's going wrong. Just to let you know Yapeal hasn't been tested with PHP 5.3.x at all so it could have something to do with that as well. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.03 15:09:00 - [154] My guess is you some how ended up with a php.ini file made for PHP on Windows onto your Linux server. Try changing any lines that look like extension=php_xsl.dll to extension=php_xsl.so and see if it works. This is more a problem with your PHP setup then having to do with Yapeal and might be better to get help on a Centos forum for it. BTW Yapeal doesn't use XSL so could just comment out that line but you'll probably still have some other problems if your php.ini file isn't right. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.05 18:08:00 - [155] Glad to hear you've found Yapeal useful. It's been a while since I looked at why I set 5.2.1 as minimum but I believe it was because there's a bug in SimpleXML that was cause problems with any version before that. Since all the API parsing is done with SimpleXML it would make it hard to work around. It is possible that changes I've made to Yapeal since then have made the problems I was having go away but I think it was something that couldn't really be worked around or I would have done so at the time of course. There is another way for you or anyone else to work around problems like this with your hosting sites CHOOSING to put your site at risk by staying with older versions that have know bugs and security issues. If you have the HD space you can install your own copy of PHP. This can work with Yapeal because it's really a console application and you can just use a full path to PHP in the crontab. I.E. something like * * * * * /path/to/private/php /path/to/yapeal/yapeal.php If you decide to go that route make sure the version of PHP you get is made for your host's distro version or is statically linked so it can run anywhere. One place you can find statically linked versions of a full LAMP (Linux Apache MySql PHP) stack or WAMP (same for Windows) is at http://bitnami.org/ which is made just for these types of problems to help you work around them. There are other similar packages out there but I found this one because it uses the same BitRock InstallBuilder that I'm now planning on using as Yapeal's installer once I'm finished learning to use it. Hope this gives you some ideas how to go forward from here. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.06 19:21:00 - [156] Best way to contact me direct for stuff you don't want to have in the thread would be through G-mail to the Yapeal project owner's account and we can get together via G-talk etc from there. To run Yapeal on Windows I would suggest you install the stack from http://bitnami.org/ which has Apache, MySQL, and PHP and I've done some test on and seems to work. The other option is the setup as outlined on the Yapeal wiki as it's also been tested and work though some of the instructions maybe a little out of date. Yapeal may work with what you have already with IIS7 but it is an un-test setup. Remember the only part of it that needs a webserver at this point in Yapeal is the old installer and you can do everything it does manual instead if need be. Updating from a year old version of Yapeal to the current version I'm sure can be done but is not going to be easy depending on which tables you are using etc. There has been several updates to the DB table structures etc which will have to be worked out but can be done by anyone that is good with MySQL DB design. My first suggestion would be to backup your current DB and then back it up a couple more times some where else just in case then put together the SQL needed to move the data from the old DB into a new one with the current table setup. I can help provide some pointers on that part but it probably would be best if you have someone else to help you with that as my time is somewhat limited right now. BTW stay with using the trunk from svn as the other download versions are "ALPHA" and not ready to be used in a production server really as it doesn't fully install and setup Yapeal and was only put out for people to make comments on what they thought of it etc. I'm still working on it and hope to finish something that can be use soon(tm) but I've been limit on time to work on it and want to make sure it's as bug free as can be before I try have people switch over to it as an option. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.15 02:21:00 - [157] Hi everyone, After doing an upgrade from OpenSuSE 11.1 to the new OpenSuSE 11.2 I started noticing some new messages in the logs about time zones not being set etc. Don't know if it just related to something in PHP5.3 which I'm now running or (more likely really) that there's been a small change in the default php.ini file they use but it has highlighted something I was not explicitly setting either for PHP or in MySQL connection that probably should be. I've now setting both to use UTC/GMT which should take care of any issues it might have been causing. In other news the new installer is coming along nicely if a bit slower then I had planned. I've been adding checks that we never did/thought of before in the old installer but instead were making assumptions about. I'm trying to keep the simplicity from the old while adding a lot more options for those that want/need the extra control which isn't an easy task I'll try to have something that could be called an early beta out in the next few weeks as RL allows. revision 919 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.15 19:53:00 - [158] I've been using openSuSE from when they were still just SuSE (version 5.x) and have learned to adapt as it changes. I've always preferred KDE but do use some apps from Gnome too. One reason I've always liked openSuSE is I don't have to choose to only use one or the other like some other popular distros make you do. Dolphin works good once you understand it and tweak it to your liking. I have to do the same with Windows etc to as the common defaults are just stupid IMHO. I've always liked this little commentary about OSes and using them http://www.zyra.org.uk/os-air.htm I will say that 11.2 is much improved over 11.1 was and other than having to download the driver for my video card before my desktop worked correctly the install was very easy. I was able to have everything mostly tweaked to my liking and able to get back to doing useful stuff within only a few hours where often it can take me a couple days with Windows -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.17 05:22:00 - [159] First, thanks for the kind words and that's an interesting looking Blog you've got started there I've BM it and will try to keep up with it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.19 19:21:00 - [160] New 'alpha' installer versions of Yapeal are available for testing in downloads. DON'T use any of these for production servers yet but do need feedback from anyone that tries them. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.20 19:00:00 - [161] ... Continued If you choose 'Advanced' before you'll now have several more pages where you can change other settings that can be found in yapeal.ini which like the last page will default to either your current config/yapeal.ini or the ones from config/yapeal-example.ini Now it is ready to actually unpack everything and put stuff where you told it to which will take only a minute or so. If the database doesn't exist it will also be created for you. The last page gives you an option to view the very outdated README file and your instill should be done and you can start testing/using it. I'll try to get a more complete walk through done on the wiki or hopefully someone will offer to make one for me If you're interested please contact me. Also please report any bugs/problems you have so I can look into them. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.27 10:13:00 - [162] I thought I'd let everyone know I've been working on a new branch for Dominion and I've added the new APIs for char and map sections already but will wait to release it until after I had a chance to do a little testing before merging it into trunk/. I should be done with it within a couple days after the API servers come back up from the Dominion release. I'm going to wait until the final release notes to see if I need to change any of my caching code to deal with the new ideas they are talking about use with some of them. I don't think it will really effect Yapeal much because of how it works but time will tell. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.11.30 01:35:00 - [163] Where it's using that it has to be the CLI SAPI and doesn't make sense to check any other way. Only times that's used is when running CLI and passing in params to it otherwise it only pays attention to it when deciding if it should also output log messages to the terminal or not. I believe with your way it would run into problems under Windows since $_SERVER['SHELL'] isn't set there outside of when using CGI in web server. The method I use is what is recommend by the people that wrote PHP. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.01 18:27:00 - [164] Ok I've had a chance to try my Dominion branch and seems to work after a couple minor fixes so I've merged it into trunk. You'll probably have to add the new API names into your utilRegisteredCharacter tables manually as I'm not updating the old installer for them since I'm hoping to have it replaced soon(tm). Same goes for new SovereigntyStatus table in map section. It should add/update all the tables right but let me know if it doesn't. revision 935 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.02 05:29:00 - [165] You can look at this DevBlog for more info on the new APIs but I've also update the wiki page for Yapeal with the new ones that have been added. Of course there's also info on them at http://wiki.eve-id.net/APIv2_Page_Index as usual. Basically they added 4 new ones and changed 2 others and one of the updates didn't effect Yapeal at all because somehow that field was already missing in the StarbaseDetail API and had never been caught by anyone. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.02 17:27:00 - [166] Just do a svn up then svn export --force over the old copy should work fine as that's how I usually do it during development also To get the new tables into the DB you should be able to just run install/setup.php again and it'll update/add the tables for you. If for some reason it doesn't seem to work let me know and I'll look into it. Quote: ... I can't use any of the installers on my Unix box. Just wondering why you couldn't? In this case no one should be using them as they aren't updated yet for Dominion and are really in a ALPHA state anyway but I should have that fixed soon as well. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.03 05:47:00 - [167] Ah Ok that make sense then. BTW if you would like I can have it build for that as well I think but didn't have anyway to test it on so didn't do so. Also didn't know anyone was running it on BSD either Good to know it works on it as well though not surprised since both are very similar in most ways that count. If you'd like to give it a try send me a E-mail to my G-Mail account that you can get from the project and I'll send a build to to try. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.03 09:19:00 - [168] Yeah I've ran into that as well. It seems to be using a blank password or something even if you don't set one. I've thought about trying to fix it but since I'm changing away from using setup.php etc and going to be doing most, if not all of that, in the new installer I've not bothered trying to find it. I'll have something else to use for those that still install Yapeal from svn in the future but it will be different and designed for an application developer to use during testing and to learn what they need to do to manage accounts in their own apps. I do not plan to have it be web based since Yapeal itself isn't directly. I'll probably design something for the command line that using some PHP classes that should be easy to integrate with a web application as well. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.04 15:54:00 - [169] Are you still having problems? Both are working for me. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.05 06:04:00 - [170] Sraelon d'Phist - You're trying the new Alpha grade installer which doesn't use/have a setup.php. It hasn't progressed to the point of doing everything the regular Yapeal does during install. You need to add you character/corp info by hand to the tables etc. As to the problem it's having not finding yapeal.ini that's a bug and I'll have a fix out for it this weekend as it can also effect a svn install. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.05 06:59:00 - [171] Seraphina Oriana - You only need to run the update when you download a new version. It's not check anything or able to get any updates. That's only used when you install a new version over the old to let it update the old tables. The new installer will have that but the old doesn't. You don't have to keep updating it as it will just keep remaking the same tables. Just add your test char/corp and finish the install. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.05 07:38:00 - [172] For those of you having problems with some of the tables not working it may be something I've just noticed. For some reason Yapeal seems to be using up to 10x more memory then normal at times. To see if that's causing your issue try upping the memory PHP allows and see if it works for you then. I'm looking into what's cause the memory increase and hope to have it fixed soon once I figure out the cause. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.05 17:54:00 - [173] Got a fix to the svn for the excessive memory use that was causing problems. Those of you having issues give it a try and let me know if it fixes stuff for you. Also included the fix for the hard coded path to config/yapeal.ini that was causing issues if you move config/ somewhere other than the default. revision 939 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.07 01:16:00 - [174] Quote: I don't know if it was because of the update or because the api was down during deployment of Dominion. But setting the values back to 1 fixed the problems I had. update.php will reset those because it over write your setting from the install/.xml files. I'll look at changing that as it isn't very nice that it does that Seraphina Oriana - Are you trying to use the Alpha installer version from downloads? They are all broken right now as I've been busy working on some other things and haven't done a new build of them and uploaded them yet. Quote:* So are there two versions of 937? Yes and No Since I'm using a branch for the new installer I'm working on so there can be differences between the version from downloads and the one you get from the SVN trunk. Just to make it clear for a production server and most developers you should still be using the SVN trunk for now. If you want to help me debug/test the new installer and make suggestions on how to improve it then give it a try and let me know how it works otherwise use the SVN for now. I'm trying to decide how I want to do the test char/corp part right now and maybe have it be an outside program/library that isn't just useful with the installer but I've been hitting some walls doing what I would like to do. I'm thinking about starting with something just for the installer for now and maybe switch to something else in the future. It keeps seeming to grow bigger every time I look at what I was thinking about doing and seems to keep go father down the slippery slope to being part of an application and not just something to be used during testing for developers. I'll try to make up my mind on some of the things I've been looking at today and once that's done progress should increase on the new installer again and will have a version that lets you add the test char/corp as well and at that point the push to Beta version shouldn't take long. Once it's at that point it will become the default installer for trunk and the current setup system will be retired. Once that is done I'll probably start suggesting everyone use downloads instead of SVN. The SVN will of course always be available but for most people the version from downloads and the updater that comes with that version will because the preferred way to get Yapeal. Hope that help clears up any confusion there might have been and gives everyone some idea where things are going with the project. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.07 17:12:00 - [175] For those of you that never read sticky threads they have turned off the /map/SovereigntyStatus.xml.aspx API as they thought it gave away to much intel. Have a look at the Removal of /map/SovereigntyStatus.xml.aspx API thread about it. You'll need to remove SovereigntyStatus from activeAPI for map in utilSections table to keep from get a lot of errors reported in log/yapeal_error.log. I'm going to probably hold off for a couple days before I release an updated revision of Yapeal in case they decide to bring it back but in a changed form like has already been suggested on the thread above. Morgenholt Blue - Yapeal takes a simple approach to stuff. It grab the information from the APIs and puts it into the tables. If it can't get it do to say a connection error, the API is down, etc it leaves it alone. I've tried to never make assumptions that I know better that the XML what is true. If you want Yapeal to report the ServerStatus correctly during DT etc then report it as a bug to CCP (which it is IMHO BTW). You can always look at the cachedUntil time from utilCachedUntil on any API to determine how 'fresh' something is and act accordingly in your application. You could even update the ServerStatus table yourself based on the assumptions you wish to make and when Yapeal starts receiving data again it will simply update it with what it has. Just make sure your application plays nice by looking before changing any of the tables and uses SQL transactions. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.08 08:27:00 - [176] I could be wrong but last time I knew EveMon was still polling the server directly instead of using the API but they could have changed by now. I'll take a look into it some more because after looking at the XML I see they seem to be setting <serverOpen>True</serverOpen> instead of 0/1 so that could be causing some issues with it not being understand somewhere along the chain and always returning 1 in the table. I may have to convert it to logical 0/1 or may just change table so it's a text field and let everyone else decide how to handle it -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.08 17:36:00 - [177] Ok I've update Yapeal with some API changes Map Sovereignty Status is now deactivated In Server Server Status the serverOpen field has been change to text instead of boolean so now everyone gets to handle it themselves and not Yapeal trying to decide how to interpret it Tried to update the old installer to let people select the new character APIs. Should work but didn't have chance to test it revision 940 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.09 06:45:00 - [178] Sorry about that didn't get the <UNSIGNED/> out of the server.xml file when switching from integer to char. You can either delete it yourself at line 45 or download new revision where I fixed it. Revision 941 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.09 06:51:00 - [179] Seraphina Oriana - Try clearing the directory where you're instilling Yapeal and download the latest revision. I'm guessing but think something is bad with the one you got. Also if this wasn't an upgrade you might try deleting and remaking the DB and see if that helps. Might look to see what's in your cache/log/setup_.log files as well for clues why it's not working for you. -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.09 17:18:00 - [180] Quote: whenever i rerun the script (i've tried it with the full api, it makes no difference) it now spits out the version number / compile date and "public_html/yapeal/inc/common_backend.php on line 64" That's normal it's just a NOTICE message so you know it did something Look in your database and see if you have some data there. I talk about all of that in post 327. Remember also that all the APIs have cache times so when there's nothing to do Yapeal just logs a few notice lines in the log and ends. Now that you have the full apikey added you may need to look at the utilRegisteredCharacter/Corporation tables and add back in the APIs that may have got deactivated to activeAPI. You can copy&paste them from utilSections table. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.10 18:28:00 - [181] Thanks to matthiasvill for reporting issue 23 about corpStarbaseDetails. I'd missed changing something and it was causing that table not to update correctly and some other problems. There's a fix in the latest revision. revision 943 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.12 10:15:00 - [182] You can also try commenting out line 85 in yapeal.php and see if it works for you using cgi. I haven't tried it but it might work. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.14 12:08:00 - [183] Make sure when you confirm Curl is load that you do so for the CLI version and not just the CGI as they do have different INI files and can have different extension loaded. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.20 19:31:00 - [184] Strombizzle - Sorry that you didn't get an answer sooner to your question but seems the forums eat my first answer from a few days ago Yapeal doesn't implement all of the skill APIs yet but info on them is also I believe available in the data dump and I'd direct you to the stickys above for more info on how to get what you need. Fixed the install/.xml files so during Yapeal updates isActive isn't changed back to the defaults which should make updating less of a hassle. The original reason for it doing that was have Yapeal a more testing mode until application developers could see if anything was broken in an incremental way but now that the code is much more stable this shouldn't be needed anymore. In other news after taking a short break from Yapeal to play a new game (AVATAR - The Game) I've now added API section activation and setting of activeAPI to the installer for the utilSections DB table. The last remain thing to be added is the test user/char/corp stuff which should make it feature complete when compared to the old installer. I'd like to hear some feedback (good or bad) from anyone trying it out on their test servers. Revision 948 -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.21 14:28:00 - [185] Yapeal has past the one year mark. The project moved over to Google Code after a very brief appearance as a project on Sourceforge. Here's some stuff I found interesting that I thought I'd share. Average commits per month: 63 (Better then 2 per day ) Number of committers: 2 (Actual number of people contributing code is much higher but only have had a couple people that ever did new releases on the trunk) Lines of code: 19534 (trunk only) Comment lines: 10151 (trunk only) Estimated 4 person years for a team of programmers to reproduce effort Estimated cost to reproduce if programmers where paid $55,000/year: $244,392 USD Actual amount ever received: $0 ISK received: 0 Hours spent working on: More than I've have for my job Enjoyment from making something useful: Unmeasurable Thanks to everyone that has helped make Yapeal what it is today and I look forward to continuing to work with all of you and many new people in the future as Yapeal continues to grow and change. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.22 08:45:00 - [186] It is made to work with multiple users, characters and corporations. The idea behind it is to work with large numbers of each but the exact number it can handle has never really been tested but by it's nature Yapeal is mostly limited by your Internet connections and the DB transactions rate of the server(s) you run it on. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.22 18:36:00 - [187] All char APIs do have a ownerID=charID and corp ones ownerID=corpID.The rest of the table are either admin tables for Yapeal (util) or general tables that don't have an owner really like the eve, map, server ones. The one from account is of course keyed to userID. Hope that helps if you need help with a particular table let us know and someone can give you an example I'm sure. You might also look back through the thread here as there is a lot of information on how things work in Yapeal in many of the posts as well plus in the wiki. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.23 17:50:00 - [188] Try the latest SVN revision 949 for the problems with charMailMessages as it has a couple fixes. As to your problem with installer version it looks like you didn't point it at a CLI version of PHP but either a CGI version (though it should work now too) or just the directory where it could be found and not the actual program. I probably need to make the instructions clearer that it needs to be set to the actual program and not just path to it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.24 14:09:00 - [189] Make sure you run install/setup.php again at least also as there is a DB update that is needed to fix it as well as the update to the code. Have a look at http://code.google.com/p/yapeal/issues/detail?id=25 for more information. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.03 13:42:00 - [190] In trunk/: Implemented suggestion by gilgamoth from Issue 22 to set cachedUntil time to +6 hours on API error 902 and also 901. This should greatly reduce the amount of error spam when the API server is down which seems to have become all to common IMHO. Update handling of fullAPIKey and limitedAPIKey from utilRegisteredUser during API fetching. Now will use either with fullAPIKey having priority. Small change to the utilRegisteredUser table and some updates to the class/Section* files' SQL so they can use either key. Make sure at least one of the keys is set or expect some nasty error messages Alpha from Downloads: For those of you having problem during install with the DB tables not being added etc. Try selecting 'Advanced' install option and it should work. Seems one or more bugs have come up in 'Legacy' option since I've been working mostly on 'Advanced' option during development. I'll be looking in what needs fixed soon(tm) For those trying out Linux versions on some distros you may have notice it aborts with an error message before it even seems to get started This is caused by a error during initiation while trying to auto detect path to PHP and it's version. I have someone testing a fix for that now and plan to release updated version later today. Been making some progress on options to add test user/char/corp to utilRegistered* tables which is last feature I planned to add. Once that is done a general bug hunt and cleanup is planned which should lead to moving all the changes to trunk/ and the retirement of the old install system. revision 953 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.03 23:19:00 - [191] Qoi - Please try the new revision and see if it helps with some of your warning messages. If it doesn't clear them up please contact me through my G-Mail account which you can find by looking at the project owner for Yapeal and I'll have you give me some more details and try some things. Scribbly - Usually you can just install the new version right over the top of the old without any problems. If you're using the SVN version you probably need to run install/setup.php at least to let it update any change in the DB tables which BTW you don't have to clear like you've been doing as it can update them with the data in them. The new installer is also made to update the DB tables with data in them though there are some bugs right now that would probably make you have to use the 'Advanced' option. revision 954 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.04 05:40:00 - [192] New version of the 'Alpha' installer out which should have fixed the errors with Map section and the problem with auto-detecting PHP under Linux. 'Legacy' should work correctly now as well as 'Advanced'. revision 955 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.08 15:40:00 - [193] How you upgrade Yapeal depends if you're using SVN or trying out the new installer version. With SVN you can use the normal 'svn up' to do it or 'svn export --force' if you use an export to keep from having .svn/ directories in web accessible locations on your server. For a somewhat more detail set of instructions that were written for Windows you can have a look at the Wiki With new installer you should find install/autoupdate-* file that you can run that works much like the installer and will check for newer versions and give you option to update to the newest revision. If you don't see autoupdate-* then you can also just grab the latest download and run it and it'll overwritten the existing install as well and then you should have the autoupdate-* to use in the future. In general updating Yapeal is mostly a matter of overwriting outdated files with new ones, adding any new ones, deleting unused ones, and then sometimes making updates to the database tables and ini file, all of which you can do manually but using svn and install/setup.php or the new installer are much easier and far less error prone of course -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.09 09:01:00 - [194] Ok a week later then expected but I've finished adding all the test user/character/corporation stuff to the new installer. It's ready to be used a bit more now. It's still not full production ready but if you make some good backups of your data it would be useful to give it a try. There have been a few changes to the util tables like adding CorporationName to the utilRegisteredCorporation table. Some things that the installer does that the old one didn't is it will add all your characters and their corps to the utilRegisteredCharacter/Corporation tables but only make the ones you select active. For more information about changes that were made look through the commit notes as well. revision 959 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.15 09:05:00 - [195] Ok did some clean up and bug fixing on the new installer. I've also enabled option for it to check for new updates on install so it can do the job of the autoupdater as well so you can always make sure you have to latest version revision 961 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.21 08:57:00 - [196] Quote: it was some getting used to due to not having that much information about it Yeah I know but I do try to document the code fairly well to help out. You can even do a SVN checkout of some auto built webpages for it from here. It's mostly made for Yapeal developers to use but there's stuff in that can be of use to everyone. Quote: If you have multiple characters belonging to the same corp, you can still only enter 1 item -per corp- in the utilRegisteredCorporation table.. as such, once there's already somebody in that list with limited view rights (say, normal member), you'll have to manually confirm that the character you are trying to add for that corp has more access than the one already in place, then replace the entry. The 'best' way to find the character to use is look at their roles in the corp from the character sheet API tables and select one that has 'Director' role and insert them into utilRegisteredCorporation. If none of the available characters have that role use the one that has to most roles that cover the API access you want. That's something best done/decided in the application code not Yapeal IMHO. Quote: allow multiple character-corp entries (and linked as such, primary key on characterID or so), that each have their own activeAPI list. The problem you run into trying to having more than one entry in utilRegisteredCorporation for a corp is you could end up trying to pull the same API more than once and the 'second' one to do so will always receive an error from the servers and cause un-needed increase in server load plus risk chance of having you IP banned from API from not obeying the cache timer -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.22 21:27:00 - [197] Yeah sorry about that ended up committing something to trunk instead being in a branch to test it You'll probably find that WalletJournal for characters fails also I'm going to revert the changes to it and just have the new Research API added until I work out my bugs with the Journal. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.24 23:41:00 - [198] Ok sorry took this long but had a couple other things going on in RL that kept me from getting the corrected update for Dominion 1.1 patch out. The new charReseach API should be working now and charWalletJournal updated with new tax columns. As always let me know if something isn't working I should have updates merged into installer downloads later or by tomorrow at latest. revision 968 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.31 05:10:00 - [199] Minor update to let Yapeal be run with CGI instead of CLI which should make it a little easier to use with some web hosts. Limited testing but worked for me To use it from CGI you may need to change the first line in yapeal.php to read #!/usr/bin/php-cgi -Cq on Linux/BSD. The path maybe different on your system but that one should work for most people. I'll merge trunk into branch I use for installer version after a little feed back from people using it with CGI then release update for them as well. If you want to try it out you can copy the updated yapeal.php, /inc/common_backend.php, and /class/YapealAutoLoad.php from trunk/ and see how it goes. For anyone that's been having problems running Yapeal from php 5.3 or latter you may need to change your php.ini file to allow 64MB memory as PHP now does proper accounting for memory use by it's extensions so you now have to deal with how much memory things like MySQLi and SimpleXML are truly using. So far in testing 55MB was highest I've seen reported but 64MB would be a nice round computer number to use revision 970 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.02 22:22:00 - [200] Ok finally got around to making a change to how Yapeal figures out the required and optional column types for ADOdb during table inserts. This change should have no effect on application developers but should make updating and adding new APIs easier in the future. Before the developer was required to put together the list manually for each table when adding a new API now ADOdb can figure it out for itself from the DB table This change has already highlight one minor bug in the StarbaseDetails tables that was missed with sovereign changes. I have a few days off and plan on looking into high memory use that has shown up with switch to PHP 5.3. I've tracked it down to the allianceList API but could also effect some of the other large APIs as well. I'll be trying out some different coding in a branch to see what I can do to reduce usage. I probably won't be updating the downloads with what I've been working on until after I finish one or two more of these type of changes but once they are in trunk/ I'm merge them out to that branch again and release update for them. I had a report of the autoupdater not working right and need to look into what changes I can do to make it work smoother before continue with work to merge that branch back into trunk/ as well. trunk revision 973, download revision 969 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.07 10:49:00 - [201] Ok added feature to Yapeal that I've wanted to do for a long time and just never seemed to get around to. You can now have XML cache to the database instead of or in addition to files in cache directories To enable the new caching you'll need to update config/yapeal.ini in the [Cache] section by changing cache_output="file" to either "both" or "database" depend on if you want to use database caching in addition to files or instead of. The XML cached in the database if valid and not expired has priority over the files during fetch so keep that in mind if you decide to use both and wonder why changes in the cache files during testing don't seem have any effect trunk revision 981, download revision 969 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.14 04:50:00 - [202] Ok I've finally finished what I can do for now on reducing memory usage in Yapeal and seem to have cut it in half at least for now from over 50MB down to 21MB or so in my testing. Farther cuts will have to wait until I can do some in-depth code profiling and tracing. That brings me to something else I've done. All the old tracing stuff have been removed to make way for an improved system that will probably be based on Xdebug instead. The time frame for adding the new code to do that is unknown at this time as changing over to the new install system and totally removing the old one is next planned thing to got finished. I have ideas for several things I'd like to add to or change with new installer but which of those get done before merge is still not decided yet but most will probably be put on hold until after merge. revision 986 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.14 10:26:00 - [203] I've updated the downloads to latest merge from trunk/ trunk revision 986, download revision 987 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.14 22:49:00 - [204] Mahoosiv - Actually right at this time the download version and the SVN are basically in sync and the download has advantage that it works correctly on new installs where the old one isn't being maintained anymore and I have no idea wither it works for them. I'm just working out some last minute issues before the branch I build the downloads from is merged into the trunk/ that you get from SVN. I've IDed a couple issues with MailMessages and StarbaseList APIs that I need to fix but once I've checked those fixes I will probably be doing the merge sometime this week. It would be very helpful for everyone to try the downloads and find any additional problems with it before then so they can be address. I'm also looking for some help with updating the existing install info on the wiki etc. and writing some more guides from a new user point of view as I find it hard to write anything given that none of it is 'new' to me Anyone interested in helping out please contact me through my G-Mail account. You'll need to have a G-Mail account yourself to be able to edit the Wiki etc. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.16 13:42:00 - [205] To do that you'll need to static data dump. from it you'll need at least the invTypes tables for the itemID to name stuff. You'll also need one or more of the map* ones to do locations. You can find MySQL versions of them in the Sticky above. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.19 01:15:00 - [206] Try creating either the log/ or cache/log/ directory that is missing. That an issue with the old installer/setup system and since it's being replace soon(tm) it's not being updated to some of the changes that have been made with directory structure. I recommend for anyone doing a new install to grab Yapeal from downloads from now on and use the new installer. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.19 09:44:00 - [207] Short answer is no. The bit longer answer is that a way to let you remotely instill over the web is planned but I'm not sure my idea will work yet. Another way of doing it is to install it on a local machine and once it's setup locally copy it over. Even the SQL files are available in the cache/ directory after install. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.19 10:41:00 - [208] It's finally done the new install system has now replaced the old system in trunk/. I know some people liked the old system and this change will make it harder with some ISPs to install but there are ways to work around them. One of the reasons for the change is so several improvements could be made so there's more options where and how you can install Yapeal. I've also setup a new automated build system that should keep the downloads up to date with trunk/ as well. revision 990 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.24 21:36:00 - [209] Did you also make sure isActive is set on everything in utilSections and filled correctly? It's used as an overall admin level control on the APIs. Quote: However, when running yapeal.php, it displays a message stating it's version 898. The installer changes that as part of the install process but now that I'm making ZIPs and TGZs available I should look at changing it during build process instead. Quote: Then, I looked for a way to add a user, a character... with the /install/addTestCharacter.php and /install/addTestUser.php, but they were not working (error with ADOdb apparently) I thought I'd made them general enough to be used elsewhere but you might look at the class/util/.php files as the scripts in install/ are most just a wrapper for them made to work in the install environment. I'd like to see what errors you were getting from them so if you wouldn't mind send them to me I'll take a look at them. Just send them to me at my project owner G-Mail address. I made the class/util/php classes to make it easier for me and everyone else working with the tables in util/. I try to make them easy to understand and useful for anyone integrating Yapeal into their applications. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.26 21:44:00 - [210] Glad you figured it out and to help you and other application developers in the future I just finished write a new Wiki page that cover how the tables and settings are and aren't related which should make it clearer and easier to understand for most people compared to trying to follow the code and it's comments. I do still recommend looking at the code for a better understanding but the Wiki page should be a first step before that and you may find it's all you need to understand as an application developer about how they work together. You can find it at http://code.google.com/p/yapeal/wiki/UtilDatabaseTableDependences -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.27 03:44:00 - [211] Check that you have at least version 5.0 of MySQL and that there is a information_schema database and the user you're try to use has at least select access to the SCHEMA_PRIVILEGES table. That user will also need create database privilege to create the DB. If you don't find any problems after that I'd try run these queries from either a MySQL command prompt or through phpMyAdmin and see what errors are being return that cause it to fail. select `PRIVILEGE_TYPE` from `information_schema`.`SCHEMA_PRIVILEGES` where `TABLE_SCHEMA`="MyNewYapealDatabase" and `GRANTEE`="'YapealUser'@'localhost'" create database `MyNewYapealDatabase` collate = utf8_unicode_ci BTW with MySQL usually the 'root' user isn't added to SCHEMA_PRIVILEGES so will always fail. Since the 'root' user always has all privileges even if named something else it's not listed since it would be pointless, at least that seems to be the thinking at MySQL You should be able to still add record yourself and it will work. Check everything above should let you find why it's failing. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.28 00:19:00 - [212] Naja Ashei - Ok that would explain the issue you were having. As I remember MySQL says using '_' is bad idea anyway in DB or table names but I will say I've done it too and then changed them because of all the problems they cause You could escape it yourself and it would work right since the installer will pass it directly to MySQL. Quote: Also, as a general note, I've never encountered a webhost that lets you create databases without using their own tools, none of the users have create database permissions. That one of the reasons Yapeal gives you an option to made it yourself with whatever tools they provide and then you tell it which one to use and it'll just add the tables to the existing DB. It even gives you option to add a table prefix to all it's tables so when you have a host that only lets you have one DB you don't have to worry about conflicts with any other existing tables from the rest of your applications. I've always tried to make Yapeal work on as many hosting sites I can but I personal never have used a host but always ran it on local computers or one I had full control of. I wouldn't use a host that didn't give me SSH access and ability to make my own DBs but that is a personal thing. I will say with all the hosts now offering low cost VM hosting where they can give you that kind of access I really don't understand why anyone would go with traditional hosting even if it is cheaper as you're getting what your not paying for (bad service and in most cases outdated hackable sites). -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.01 18:40:00 - [213] It's called developer forgetting about autobuilding and letting work in progress escape into trunk Having to change how I do things a bit and still haven't got the hang of it sorry about that. I'll have a fixed for that and a few other bugs that have come to light probably later today. I'm also looking at making a change to utilRegisteredUser to bring it more in line with the other utilRegistered* tables. Going to add activeAPI column for account section APIs. Currently that only the '/account/Characters.xml.aspx' API but if CCP decided to add any others it will become more useful in the future. The good thing about this change is it lets you now enable/disable that API without having to do the some for the user, chars, and, corps like now which should be a good thing. Look for some more changes to make the new utility classes in class/util/ more useful for application developers as I'm changing Yapeal to use them and they mature. Any suggestions on them or other 'helper' type functions that would make your life as application developers easier I'd like to hear. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.01 21:15:00 - [214] I'm glad to hear you found a work around but hopefully you'll only need it temporary. Ok from what you're saying it looks like something about how I'm building queries in the installer scripts is different than in the rest Yapeal. I'll look into it some more and see if I can figure out why that happens. Probably some missing escaping in the installer scripts some where though I don't remember doing any escaping on the table prefixes in either. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.02 22:10:00 - [215] Sorry I didn't see you're post above seems it got missing while I was making my own post I have not a clue about Out of Eve as I've never more than glanced at it's main page. I'd say you should use POS tracker for your POS stuff as it's been around for a while and works well. For tracking your BPO research etc. I'm not really sure what to use for that but there's probably a few tools but all the ones I know of you can't install on your own site or are desktop tools. As far as having someone do this stuff for you I'm not really the person for that since I've never worked with any of them. I know Yapeal which IMHO is a really nice API library and I'd be able to help you with it but what you're wanting is not something I do and you'll probably do better with your own thread find someone to help you then in this thread. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.05 02:55:00 - [216] Quote: edit2 exclamation points in the DB passwords need to be in quotes in the yapeal.ini file. It should be quoting it and most of the others as well. Have a look in cache/ for the cached .sql files you should be able to run them manually. If it's failing before creating them then you can try creating the DB and tables by running install/createMySQLDatabase.php and install/createMySQLTables.php as needed from command-line. Once you have them you can try the addTest.php files or just adding the info to the tables yourself. You'll find the list of APIs in the activeAPI column from utilSections table. Hope that helps and I'll be looking into adding some more quoting for the command line parameters used in the installer to keep it from failing to start with. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.06 01:01:00 - [217] Quote: charResearch has nothing higher than 99.99 per day. I'll make sure that's not just something weird in the way it's being returned or a max value that needs to be increased later as well. Column has been expanded so it can go up to 999.99 which should be enough Quoting in the installer has been changed which should help with non-alphanumeric passwords, etc. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.13 08:57:00 - [218] Ok thought it was time for a little update on stuff I've been working on. I'm currently still working on some cleanup on caching code and that's probably going to lead to some changes in the API fetching code as well. I'm try to go a bit slower on this so as to make sure not to break stuff in the process (Yes I'm using a branch this time ) Something else I've been working on is cleaning up, adding to, and streamlining the new build stuff as I've gotten to know more about how Xinc and Phing work. Part of that has lead to having them build the Yapeal developer documentation also so it stays more up to date with the current revision. I've also changed it from being stored in docs/ directory where it had to be manually updated to being available as downloads in html and pdf formats. These are mostly useful for people working on making changes to Yapeal itself but application developers may find some of the information useful too. Now that I've brought up the subject of documentation as most of you are aware there isn't much and what does exist needs some serious help. I've tried to write some docs but I've been finding it very hard write any that is really useful for someone try to develop an application and integrate Yapeal into it or build something around it depending on how you look view what you're doing One thing that makes it hard for me is since I do know every line of code and how everything works it's hard for me to see Yapeal as an outsider would and not knowing what it does or can do for them. So what I need is some help from those that have been using Yapeal to share some of their experiences, tips, examples, etc. Things I'd like to really hear about are things that caused the most 'head scratching' when starting to use it. revision 1024 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.14 06:13:00 - [219] First thanks for trying Yapeal. It looks like you're using an older version so first thing would be to update to the latest version 1024. Try using the installer from downloads if you can and select 'advanced' install which will have a few more pages to go through but most should have good defaults already just make sure when you get to the section part to make sure everything is on that you want. (accountCharacters will need account section and Characters API on). I've change the utilRegisteredUser table to reflect that the user has to be active to get those APIs I wrote about that change in my post 471 Hopefully I've covered enough so you can fix your problems but if not let me know. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.16 01:42:00 - [220] Ok I finally decided to tag revision 1024 as version 1.0.0 Beta. What does this mean? It doesn't really change anything but it does mean that as a developer I believe it's mostly complete in what it does and has no major bugs anymore. You also notice when you look at download in the Summary it now says '*Beta* ...' instead of '*Pre-Beta* ...' Is development stopping? No, but since it is mostly complete large scale changes to how it works or is used shouldn't happen for a while anyway (At least for a couple weeks to a month). Are you going to start on version 2.0? Not really Yapeal will keep evolving much as it has and maybe at some point it'll make it to what could be call 'stable' and at that point I may decided to call it 2.0. So what's being worked on now in Yapeal? Everything but main focus has shifted to cleaning up some of the code, looking at improving the installer, and maybe adding a couple more of the APIs. I've also been looking at ways to add a remote installer for people that don't have shell access with their ISPs but it hasn't even got to the testing stage just been looking at how others have try solving the issue. Think that covers everything for now. revision 1027 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.30 15:48:00 - [221] Try looking at the comments from issue 43 as the first couple apply even though you may not be try to use a remote DB server. I also believe there was someone else having similar problems that posted to this thread not long ago and I made some suggests for things to look at then too. You'll what to look over the last couple pages to find it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.30 17:57:00 - [222] Just an idea try the installer from download for windows and it should make the ini file for you and help you by make sure everything is set right and working. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.30 22:48:00 - [223] If you have a shared windows host you are probably out of luck except if they give you remote desktop access (unlikely). If you're host is Linux on the other hand you can grab one of the Linux installer and use SSH connection to install it. If you have an old style host that thinks not giving you SSH access makes their servers more secure you'll have to follow instructions from either this thread or in some of the closed issues on the web site where I talk about how you can do a local install on any platform and make a few minor changes that depend how closely your local machine is to the configuration on the remote one. On another matter for those of you that haven't been to the project web site in last couple of days or just didn't notice while you were there I've decided to start a new blog for Yapeal. I've named it Peeling Yapeal. I hope to cover things with it that people will find interesting and that I felt weren't being or couldn't be cover by this thread, in issues, or the Wiki from the project site either. I've written a couple posts already include the first couple from a series that will hopefully give some insight into how Yapeal works and some change that are coming. They probably will also give some insight into the process I go through when deciding on changes during development for Yapeal. I'd like to invite anyone that has ideas for things you think are missing or you feel need to be cover but this thread, the wiki or issues just didn't feel like the right place to bring it up in the past to make comments on the blog and we'll see what I can do to address them through it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.03.31 23:04:00 - [224] Qoi - Glad to hear you like and have been using it for a while. I'll just let you know how I work with Yapeal and maybe you can try doing something similar and they won't cause you any problems anymore. I have a working copy in a location where I do my edits then when I wish to try it out I do an export: svn export --force /my/wc/ /my/test/location/ Doing it that way allows helps insure I don't end up with any of my passwords or logs in the commit like has been know to happen a few times in the past you'll notice it doesn't overwrite my config/yapeal.ini and does overwrite the log/yapeal_.log files saving me doing it manually. The only time I need to do any extra work would be when I delete or move files around in the SVN. That isn't hard either as a simple rm -R /my/test/location/.php followed by an export cleans it up nicely for me One of the original reasons for including the log files was to have them there so you can insure they had the correct permissions before Yapeal looks at them and try to write to them. It use to check each file to insure they were writable but I think now it's been changed and just requires the directory be writable and may not check each file. One other reason was to insure the directory was created when using archives (zip, tar.gz, etc) as some of them will ignore any directory that is empty and not make them when you expand them. That was the reason for adding dummy.txt to all the cache// directories you see as well So there's some background on why it was done like it is now. Now back to things you can do, first you could use the export method I do and not run from you're WC which is not a good idea to start with BTW as you've seen it causes problems and yes I know some of the old documentation had an example doing that (I didn't write it) Another option is to use a different name for you log files by changing them in your config/yapeal.ini and you just end up with a couple extra empty unused log files There one more option be it's more for me then you and that's to check if Yapeal still checks the permissions on all the log file directly or not. If it doesn't I could probably just add a dummy.txt file instead and not have the log files in the SVN any more. I'll just have to remember to clear them myself during testing which isn't a big deal as I have to do that now when testing the installer since it doesn't overwrite them if they already exist. -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.04.01 00:36:00 - [225] Ok now that you know about svn export I may have fixed Yapeal so you don't need it there are of course the other benefits still. After looking at it I've decided I could remove the logs from the SVN and while I was at it I fixed revision.php as well. I thought that had already been done a while back when I noticed it be apparently it didn't get changed. To also help with the extra emails you can try adding the follow line as the first one in your crontab: MAILTO="" That should silent any crontab emails in most Linux distros. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.04.05 01:15:00 - [226] Thought I'd let everyone know I've fixed a few minor bugs lately which most people wouldn't notice but became KOS once I found them like they all should For those of you that missed it I did an interview for KaarBaak about Yapeal which you can find at http://evemetagaming.blogspot.com/. She's done a couple others now which I found interesting to read myself about some other projects/applications that people are working on. I'll be finishing off my series from the PeelingYapeal blog soon as well but in writing it it got me to thinking about some things and I decided to try out a few ideas to make Yapeal work better. Most of them are about memory usage which is of course what the posts were about but I've also been looking at making Yapeal scale better for people that want to use it with say a few hundreds or thousands of accounts ;) That's it for now. Revision 1043 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.04.06 04:09:00 - [227] I found the old post I did about this a long time ago and decided to update it a little and make it into wiki page. http://code.google.com/p/yapeal/wiki/UnderstandingErrorLogs -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.04.15 06:46:00 - [228] Bubba XXX - It not going to be easy if you are using a version that old. best way to start would be to export your data from your server to a local machine. Install Yapeal on the local machine with an installer and if you're lucky the database will upgrade correctly for you. Once you're sure that has worked you can transfer Yapeal over ftp to your server and update the database there from your local machine using a backup from it. The more similar the local machine is to your server the more likely it is it'll all work. Make sure you use 'advanced' install so you get a chance to make changes to all the settings. Hopefully that helps and I would suggest you upgrade more often as there are often many changes to Yapeal both to fix bugs and added features. The older the version the harder it'll always be to update. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.01 04:03:00 - [229] Ok thought it was time to give everyone a little update. I've started a new job so that's been taking up more of my time lately but I've been working on converting all the APIs over to using XMLReader as I outlined in my blog posts. I believe all the APIs that Yapeal had before have been converted and are working now plus I've add a few new ones along the way too I'm having some issues right now with downloads at GoogleCode but I hope that will be fixed soon and I'll be able to upload some test installers and other files for people to start trying out. Some of the changes I've decided/had to make will require some manual changes to the database tables in util. This should have little impact on most users that have been using the newer class/util/.php files and the classes they contain to interact with the tables. I'll give more information once I've done a little more testing and the download issues are solved. -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.07 14:31:00 - [230] Ok I put the Alpha test version of the installers that use XMLReader up in downloads I've not had a chance to test them so BACKUP YOUR DATABASE and current install of Yapeal before trying it. You'll need to delete your existing tables or make a new database to try it out as I haven't upload the manual conversion SQL you'd need to update existing one. Let me know if there's any problems with it and yes this is ALPHAware -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.14 01:01:00 - [231] The installer should work with CGI as well from SSH you just need to tell it where it is just like you would with CLI. You shouldn't need to change the suffix on the files either since you aren't running anything with the web server which is where that requirement usually comes from. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.14 07:04:00 - [232] You might look at the /tmp/bitrock.log file and see if there's any more info on why it's failing on some systems it could be in /var/tmp/. I'd also try a few test from command line to make sure there aren't any other issues with PHP config. Some things to try. /usr/local/bin/php.5 -v Check this really is PHP version 5.2.1 or greater. /usr/local/bin/php.5 -m Make sure all the required extensions (modules) are included in PHP. If it seems it's using a php.ini file that's wrong when entering the command to use try adding the extra parameter to yours to it. Example: Where can the CLI version of PHP be found? [/usr/bin/php]: /usr/local/bin/php.5 -c /usr/local/php5/php.ini Since it'll use simple string append of the commands in the installer that should work without problems. You might also find out where the CGI is putting it's log files as it might shed some light on why it's failing as well. If you need some help understanding any of the log files from anything you can E-mail them to me at my G-mail. You can find it (figure it out) from project owner. Hopefully you'll be able to figure out from doing some of the above tests what is causing it to fail. -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.15 03:50:00 - [233] I'm surprised those lines caused you problems but they aren't really important they are just checking if the file is being ran directly or being included from another PHP file. My only concern is the same lines are used in many of the other files in Yapeal as well. Will probably need to figure out which line is causing the problem. If it's the 'if' there maybe ways to work around it but if it's the 'fwrite' it'll cause problems with all the logging and maybe some other places. Once you get it fully installed we'll see if you continue to have any problems -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.15 22:13:00 - [234] Eduardo'o - You can do it all manually but it's not easier or quick for sure. I'll go over some of the high points of what you'd need to do. Download one of the archives (.zip, .tar.bz) Make directory where you plan on instilling it and un-zip archive into it Update any/all paths from inc/common_paths.php for where you put Yapeal Copy config/yapeal-example.ini to config/yapeal.ini Edit config/yapeal.ini and add your settings using the comments from the file for reference Create MySQL database that matches your settings from config/yapeal.ini (This could be done before last step but this order is usually less error prone IMHO) Open up each of the install/.xml files and decipher it manually and create all 70-80 database tables making sure to get the types, lengths, indexes, etc correct for each table Add any test users, characters, and/or corporations you need into the utilRegistered database tables Hope you got everything right because if something is wrong on many of the steps above you might not even be lucky enough to get useful error message and it just fails silently Try it Figure out what steps I forgot to add to this list that keeps it from working or what typo etc you made Repeat the last two steps as many times as needed until it: Runs without errors and correctly gets all the data from the API servers for all APIs If you can get it to work without doing the last step more than twice I'll turn the project over to you because I'm sure the project would be in much better hands with a 'guru' instead of me since if I tried it I probably wouldn't be successful If you can get it to work within 5 tries I'd like to invite you to become a developer and help me out If you think do the above is a great way to spend a day, week, or month of your time you probably should get some mental help but if you're interested I'm looking for some victims, uh I mean test subjects for some pre-Alpha code Personally I'd start by contact my host tech support for help fixing whatever is keeping you from running the installer. IMHO if they can't help you with any issues or you can't figure it out yourself I'd find a new host because Yapeal doesn't have any requirements that they shouldn't be able to supply. You can also try use a local test server and install Yapeal there then copy stuff over to the remote one with all the database exports etc that will be needed. I've covered how to do that already in this thread several times so I wouldn't repeat it here but feel free to ask any questions you have if you run anything new or just can't figure something out and either I or someone else on the thread will be glad to help. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.16 12:48:00 - [235] You can create the database without problems just make sure to give the name to the installer and the user you use for DB has all the privileges needed for creating the tables, etc. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.22 20:30:00 - [236] Ok I've been looking into the problems with PHP-CGI some more and seem to have a fix. I was 'ass-u-ming' that the switches I was passing and the ini overrides where changing more than they do about how it works I've now added lines to set the constants for STDIN, STDOUT, and STDERR if they aren't already set. I've updated trunk/ with the fixes and you can get the update installer from downloads now. Give it a try and see if it fixes the problems you've been having. I'd like to get some feedback about the new APIs from everyone to see which ones they would like to see added to Yapeal first. You can read about what's being added in this dev blog post: http://www.eveonline.com/devblog.asp?a=blog&bid=757 I'm also trying to decide if I will add them to the existing trunk code or just work on them in the new XMLReader code and wait until moving it to trunk/ before really making them available. Doing the latter would probably give some time for CCP to work out any bugs in them first and may work better but does mean they wouldn't be available from Yapeal for a couple weeks or more for everyone to work on their applications with. I wouldn't be as concerned with that if I'd seen more people had tried the Alpha builds I uploaded and had some feedback on any bugs with them. revision 1072 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.23 00:28:00 - [237] Really beginning to dislike PHP_CGI -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.23 22:54:00 - [238] Ok I've been digging into the changes needed to make Yapeal work with PHP_CGI and I am sorry to say at least in the case of the installer it's not possible You can have a look at this page to get a little more detail: http://www.php.net/manual/en/features.commandline.differences.php Why it wouldn't work is found in the first note. To sum it up by the time you can turn register_argc_argv on PHP has already processed the command line and put anything you've passed it into $_GET and $_REQUEST and wouldn't populate $argc or $argv with the values The good news is once it's installed Yapeal doesn't normal use any parameters and PHP-CGI works without any problems. I'll continue to look for workarounds but since Yapeal was made for the command-line it doesn't make sense to spend a lot of development time on it right now. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.24 00:21:00 - [239] Only reason I try to support it where I can is some host services don't allow access to CLI version and I do want to make it possible to use it everywhere when I can figure out how. Right now Yapeal itself seems to work fine it's just some of the scripts used during install that cause issues. The normal work around for installer issues has always been to install Yapeal on a local test server then copy the configuration over to remote production server. Many times this can even work with different OSes on each system with a little care. Something I've been try out is VMWare player and stuff from BitNami. For anyone that only have a Windows machine locally it looks like it may be an option when you have a Linux/Unix host and stuff from Windows doesn't seem to work. I've also been looking at some cloud computing stuff to see if Yapeal is going to be compatible for anyone that is outgrowing what a single server can handle. So far I haven't found any show stoppers but I wouldn't know until I actually take some time and spend some RL money to try it -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.24 03:43:00 - [240] Actually the project website use to say something about Yapeal being for CLI only but was removed after some changes where made and it seemed to work without problems. I think once you actual get it installed it'll run without problems but the installer highlights where the CLI and CGI versions are made to be use for different applications. If they weren't they wouldn't need to have two different versions after all -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.27 14:05:00 - [241] Mi'Rini Nemo - I'd suggest looking back a couple pages in this thread where the last person was asking the same questions or in some of the issues on the project site ( You may need to look at all issues including closed ones) if you still are having problems then I'll try to help but right now with all the new API changes I'm going to be busy updating Yapeal for next few days. For those wondering yes they made a few changes to some of the older APIs that have broke them so I'll be working on them and hope to have a fix out this weekend or soon if I can but been busy at work doing some certifications so a bit worn out by end of day and just haven't been feeling like working on Yapeal as much in the evenings lately -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.28 07:22:00 - [242] Ok to update the charMailMessages table all current users will need to use the following SQL before updating Yapeal with the installer. CCP renamed "toListIDs" to "toListID" and changed it from being a list to a single ID which is a type of change the SQL updater in the installer doesn't handle well on it's own use the follow SQL: alter table `charMailMessages` change column `toListIDs` `toListID` decimal(20,0) unsigned DEFAULT 0 You may need to add the database name if you don't have it selected already by prefixing the table name with it i.e. : ... table `MyDBName`.`charMailMessages` change ... You may notice some additional tables being added for some of the new APIs that were included in Tyrannis but the classes aren't done so none of them will be active until later. revision 1073 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.28 13:58:00 - [243] Quote: Is available a web installer at least? No and no current plans to add one since Yapeal is a command line library that isn't really made to be ran with web server it doesn't make sense to have one. Yapeal use to use one but since the person that wrote it has moved on from Eve and it was start to show its limitations I converted to the current installer. I have been thinking about a remote installer which would use a web-base front end system but it's not something I've had time to figure out yet. Quote: What happened: Did not pass the CLI selection. Error "The following required PHP extensions are not active: hash" How about activating the required extension? It is probably there just not turned on in php.ini even though it's include be default since 5.1.something Don't ask me why they always seem to have all the extensions turned off by default in Windows builds Quote: "User doesn't have the required privileges" Make sure the user you are using has select for `information_schema`.`SCHEMA_PRIVILEGES` and what privileges are listed there for the user you are using. Often if you are using "root" user it's not listed because it is granted access in a different way during MySQL startup so try creating one just for Yapeal to use. For the example user used in Yapeal with default database setting it would look like this: [code] +--------------------------+---------------+--------------+----------------+--------------+ \| GRANTEE \| TABLE_CATALOG \| TABLE_SCHEMA \| PRIVILEGE_TYPE \| IS_GRANTABLE \| +--------------------------+---------------+--------------+----------------+--------------+ \| 'YapealUser'@'localhost' \| NULL \| yapeal \| SELECT \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| INSERT \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| UPDATE \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| DELETE \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| CREATE \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| DROP \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| INDEX \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| ALTER \| NO \| +--------------------------+---------------+--------------+----------------+--------------+ [\code] If yours doesn't look something like that you'll need to change the privileges until it does. Quote: LAST EDIT OK... Fixed the first problem the installer had ' "" ' in the fields so I removed them. They are probably required where you removed them and are causing you some of your other problems but since it isn't clear which ones you remove I can't tell. I've had some escaping problems in the past so if you could clarify which ones you were having problems with I can maybe look into it and see if something got missed. Also try looking for a bitrock.log file in your temp directory as it may have some additional detail on why stuff is failing. -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.29 01:36:00 - [244] Rottw Adleweh - I would say converting the installer would be hard because of how it detects MySQL and the existing DB etc. but Yapeal itself could be converted with some work. Generally I've tried to use standard SQL and where I didn't I've try to isolate the MySQL only SQL into PHP methods/functions so they could be changed for other DBs. One reason for using ADOdb was to make converting it easier if I ever decided to do so. Contact me via my GMail from the project and I can discuss with you some details I don't want to bore everyone with in a forum post -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.29 20:23:00 - [245] Hi all I've been working on adding some of the new APIs to Yapeal and need a little help. Since my alliance/corp doesn't have our own Outpost (yet ) I need some help from someone that does. If someone would be kind enough to send me a copy of their /corp/OutpostList.xml.aspx and /corp/OutpostServiceDetail.xml.aspx with one or more outposts in it that would be extremely helpful. I will only be using it as a reference for typing and sizing columns for the database tables in Yapeal and I would not be sharing it with anyone (Not even corpmates) and if you want to obscure the ownerID, stationID, and/or standingOwnerID that is okay as I mostly have questions about some of the other stuff. If you can help out please E-Mail them to me at my G-Mail address from the project home page (project owner). I'm also be looking for someone that would have some time to do some alpha testing for the same APIs but that wouldn't require sending me the XML like above just a server where you can instill Yapeal and have command line access to look at log files and report any error to me via IM (preferred) or E-Mail. Thanks for everyone's time and hopefully I'll get a response today and be done with test by tomorrow and at least have out an alpha build with the new APIs for people to do their own testing with. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.05.30 18:55:00 - [246] Quote: Now how can I retrieve the data from the database, is there something ready or through custom code? That would be called your application The More detailed explanation section of the main project page details what it does for you everything else is up to you. You can just forget where the data is coming from and make your application knowing the tables will always have the most up to date data available. The idea behind the design of Yapeal was to let anyone that knows how to make a LAMP web application do so. It has been expanded to include WAMP as well or anything else that can work with a MySQL database. Quote: How can I change my char's credential, add new or edit them? Have a look through the project wiki where the http://code.google.com/p/yapeal/wiki/UsingClassUtilClasses and the http://code.google.com/p/yapeal/wiki/UtilDatabaseTableDependences pages will probably but the most useful in understanding how to add additional chars/corps, etc. Quote: Which file should be set for a cron job? Have a look at the http://code.google.com/p/yapeal/wiki/CrontabSetup for help with setting up crontab. While you're at it you'll probably want to look through some of the other wiki pages and maybe some of the issues include closed ones as they have some information that you may find help during any troubleshooting you may need to do. BTW the problem you may have been having with it not finding 'hash' extension was probably do to a typo on my part. I include a space in front of it inside the quotes that didn't get caught until I was testing the installer locally yesterday. I'll be releasing an updated alpha build once I've smashed a few other bugs I've found that are mostly in the new APIs I've been trying to add from Tyrannis. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.06.01 08:50:00 - [247] Bai Guang - Try looking at the second half of post 533 and check your access that way. I.E. select * from `information_schema`.`SCHEMA_PRIVILEGES` where GRANTEE like "%YapealUser%" and TABLE_SCHEMA="yapeal"; That gives me this on a test server: [code] +--------------------------+---------------+--------------+----------------+--------------+ \| GRANTEE \| TABLE_CATALOG \| TABLE_SCHEMA \| PRIVILEGE_TYPE \| IS_GRANTABLE \| +--------------------------+---------------+--------------+----------------+--------------+ \| 'YapealUser'@'localhost' \| NULL \| yapeal \| SELECT \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| INSERT \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| UPDATE \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| DELETE \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| CREATE \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| DROP \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| INDEX \| NO \| \| 'YapealUser'@'localhost' \| NULL \| yapeal \| ALTER \| NO \| +--------------------------+---------------+--------------+----------------+--------------+ 8 rows in set (0.00 sec) [\code] -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.06.01 16:57:00 - [248] Just a quick update for anyone that was having problems with the Alpha release not finding extensions I've released new fixed version. It also has some of the new APIs added to it but most of them you'll have to manually activate as I didn't update the instiller yet to let you select them. Once I've got them all working I plan to look into how the installer comes up with the list and see if I can't make it smarter and just maybe do something about the formating while I'm at it -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.06.03 00:32:00 - [249] Quick update I've added outpost stuff to the alpha builds in downloads you'll have to activate them manually in the util* tables but they are ready to have someone try them out and let me know about any problems. I'm now looking into updating installer but it may be a while before I have a update for it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.06.05 04:02:00 - [250] There were some changes done to several of the APIs for Tyrannis that will probably break older versions. Can I get some more information about which APIs you are using and which version of Yapeal etc? -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.06.05 10:11:00 - [251] KtoJest - If you are looking at the line that reads * @since revision 561 that isn't the version for Yapeal the actual version information is in the revision.php file. If you don't have a revision.php file then you are running a very old version and that could explain why it broke The latest version from the trunk/ (main code line) is 1073 and is the version with the changes for Tyrannis. There wasn't any changes directly to wallet transactions, journals, or assets but CCP did fix a long standing bug dealing with walking records on journals. It shouldn't have broke anything but it can have the effect of greatly decreasing the number of API errors reported by Yapeal which you may have been use to seeing from before. You should also look at the log_level= ... line in your config/yapeal.ini file and if it isn't set to E_ALL try setting it to that and you should start seeing a lot of information in the log/yapeal_notice.log every time it runs. It's off by default as it can easily reach several 100 MBs per day depending how many char/corps you have added to Yapeal A couple more questions is how did you install/ update Yapeal last time? Did you use an installer from the project downloads or get it from SVN directly? Also when was the last time you do so? -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.06.15 03:50:00 - [252] A Mac version could be done as the install builder used can make them but I have no way to test them and you've been the first to ask for one -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.06.22 14:36:00 - [253] Rottw Adleweh - I need you to contact me through my G-Mail account and see if we can get on IM because there's some things I'll need to go over with you before I can even try building one for Mac. Just E-mail the project owner @ gmail.com and we'll work out some details from there. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.06.29 16:42:00 - [254] Just a quick note. Anyone that has had problems with the installer not working with their website hosts in the past if you could please try the new alpha installer and let me know if it now works for you it would be great. I'm trying a different approach that I'm hope will work better with less privilege problems. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2010.07.14 20:10:00 - [255] Hi all just a quick update. I've added some new targets for building Yapeal to the Phing config file so it should be more streamlined to make the Alpha test builds. In the process I've add archive (zip, tar.bz2) versions to the Alpha for those that prefer them over the full installer versions. You can find them all along with the main trunk Beta builds in downloads. I've been thinking about moving the Alpha stuff into the trunk/ soon so for any of you that haven't tried it and depend on it in your own projects please test it and let me know about any bugs as I want to make all the new APIs available and get the fixes for the memory issues that are solve by using xmlReader into trunk/ soon. I've also done some changes to the scripts used during instill that should help with many of the past database issues that have been reported on some web hosting services. On another note I've been doing some testing on Amazon's Web Service with Yapeal and was wondering if anyone would be interested in having a special Yapeal Instance for it or maybe just something to use with Xen? or maybe something for VMware but not sure I can make one for it without buying VMware. Let me know if you're interested in one of more of those. I've also been toying with idea of offering an Yapeal hosting service of some kind. Not sure if it could really be done securely or exactly how to set it up but if there was some interest in something like that I would look into it. I'd like to hear from anyone that has ideas on how to make something like that work or what they would like to see it do. I've kicked this idea around off and on for a year or more but never really came up with anything solid enough to even try. Let me know if you have any other ideas about anything I've wrote above or if you have an idea for something you'd like to see changed or added to Yapeal. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Circle-Of-Two	Posted - 2010.07.24 13:26:00 - [256] Yeah that file has been deprecated but a complete reference for the util* tables is available in http://code.google.com/p/yapeal/wiki/UtilDatabaseTableDependences. There is also a link in it to other wiki page describing some utility classes that make managing them easier in your application. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Circle-Of-Two	Posted - 2010.07.30 16:13:00 - [257] It wouldn't do what you think it would even if you could do that. Once one of them pulls the data the API servers continue to use the same cached data for all of them. You can try running multiple copies on several different computers with different public IPs and see if you get different data but I'm fairly sure it wouldn't get you any more data any faster than the cachedUntil time. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Circle-Of-Two	Posted - 2010.08.12 17:33:00 - [258] Hi all thought I'd let everyone know what's been going on lately with Yapeal and ask for some help. My new job seems to keep me busier than my old one and some other changes that have happened/are expected to happen soon in RL means I'm not going to have the time to work on Yapeal like I use to. In addition to that the other couple developers/friends that helped with some of the coding/test in the background have also faded away at least for a time So what I'm looking to do is find one or two programmers to help out and keep things moving forward. I'll still be coding but would like to have others involved and be able to just work as QA for parts of it. I'll try to list what I think is important to work on Yapeal: Input and new ideas are always welcome and really expected by all Yapeal developers but I do make the finally call on things based on my vision of Yapeal and feedback from the people using it Think Yapeal is really cool and want to be a part in making it better Able to work with others Able to work by self on tasks Able to take hearing things like "That code looks like st" once in a great while and understand it might be true and ask why and how to make it better not get ped off. This doesn't happen often but even I have an off day and put things a bit harshly Some programming experience even if PHP is somewhat new to you. I don't mind you using Yapeal as a learning tool and helping you learn to become a better programmer as I've done the same thing myself. If you are new to PHP and write bad code you'll not likely to ever hear comments like above they are reserved for people that really should know better and me having a very off day Understand that Yapeal is important to the Eve development community and take pride in do your best for it with your work on Yapeal Have fun because if you aren't enjoying do this for free why would you what to do it? Don't take the list as complete or anything it's a quick off the top of my head in two minutes thing based on some past stuff. If I haven't sared you off with stuff in the above list let me know via my Gmail, this thread, etc. -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Circle-Of-Two	Posted - 2010.08.29 02:11:00 - [259] Which file did you download? If one of the installers you'll need to make sure it is mode 07xx for user you are trying to run it as. If you got one of the archives or from SVN you'll have to manual run several of the scripts from install/ to add the DB and/or tables. You'll need to check inc/common_paths.php and change the paths to match where you put stuff. You'll also need to copy config/yapeal-example.ini to config/yapeal.ini and change the stuff in it to match your install. After doing that you can just run yapeal.php and it should start filling you DB with data. I strongly suggest using the installer as it make installing much easier. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Circle-Of-Two	Posted - 2010.09.08 05:22:00 - [260] Yeah somehow the Windows installer has broken in a very bad way and I haven't figured out how to fix it but been working on a rewrite for it. I've just finished moving in RL and hope to start having a bit more time to work on stuff again. I would actually suggest trying the Alpha builds as they will soon be replacing the current Beta stuff as they have several improvements and bug fixes in them. As to what you need to do to have the tables added to your DB try running install/createMySQLTables.php first without any parameters to find out what you need to use then with the required ones. It should run without any problems for you and it will also leave the SQL it used to make the tables in cache/.sql files for you to look at if something goes wrong or you decide you need them for something else. I'd also suggest take a look at the website Wiki and issues both current and closed for some tips that might help with install problems. I'm currently working on a couple of issues with how Yapeal handles it's connections to the API servers that have come up in the Alpha and once I have them fixed and tested a little I'll have them up to be downloaded as well. -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. Circle-Of-Two	Posted - 2010.09.20 17:04:00 - [261] If 'changed' is NULL it'll use CURRENT_TIMESTAMP to fill it which is what it's suppose to do. Quote: Now I need to find the php file with the appropriate sql and modify that. Can't be done really since that SQL is gen in a common method from a class that is used for all upserts. Quote: 2. I'm also getting a MySQL error code 1366: That looks like a problem from trying to upgrade an old version of the data to the new and it didn't convert correctly. Try running the installer with a empty (no tables) DB and you shouldn't have any problems. I know I'm probably going to have to write a special upgrade SQL for going from the older tables in trunk to the newer ones but if you know a little bit about SQL you can usually look at the 2 versions and put something together to transfer the data. There should only be a few tables that will need extra attention. Also make sure you are using at least version 5.x of MySQL and 5.1 is better. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Circle-Of-Two	Posted - 2010.09.21 05:37:00 - [262] Edited by: Dragonaire on 21/09/2010 05:52:16 Your code does address the problem but not the cause. The error is actually caused by code I added to insert default values for optional fields and it of coarse puts CURRENT_TIMESTAMP in as default for 'changed' because that it's default which then is quoted by the code you found. The most correct fix would be to remove 'changed' from that table as it isn't an actual field from the API but a left over one that I originally added for use in the corp project that Yapeal grow out from. The only reason it wasn't removed before is it can be useful for checking when market orders have been updated and I had really forgotten it was still being added until this came up. FYI the code that is used to set all the defaults can be found in class/YapealQueryBuilder.php lines 117-119. Changing them to the following should fix the problem before it can happen. if (isset($col->has_default) && $col->has_default === TRUE && $col->default_value !== 'CURRENT_TIMESTAMP') { $this->defaults[$col->name] = $col->default_value; };// if isset $col->has_default ...
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.11.04 04:34:00 - [263] Hi everyone just thought I'd let everyone know I'm working on getting an updated version of Yapeal out for the changes to old APIs and the new ones. I'm having some issues with Google Code after they've made some changes too so look for some changes on how you get hold of the code in the near future as I'm working on stuff I hope will make maintaining and deploying Yapeal easier and better soon. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.11.06 19:48:00 - [264] Hi again thought I'd let everyone know I'll probably be delaying any releases until CCP can fix a few more of their bugs in the APIs as many of them right now are Foobared big time if you haven't noticed I would like to at least get some testing done with working APIs before putting anything out and having other people bug hunt for me In the mean time I'll be trying to finish up several enhancements I've been working on that I think will be useful to many and hopefully lead to other people being able to help with adding new APIs as they come out without having to wait always on me. Adding APIs now should be a simple matter of extending one PHP class and adding some data to a couple XML files so the tables are added to the database. Actually the process has been close to that simple for a while but I have made a few changes that should make it clearer what needs to be done IMHO anyway Expect that you'll need to do full backups of your database and probably a manual data import from many of the existing tables into the new empty database tables because of all the non-backwards compatible changes made both by CCP and by myself on some of the tables. When I get a chance I'll try to put together some kind of guide to what needs to be done to convert them but I've already got 3 times more things to do on the project than I have time for it as it is it seems For those so inclined you can checkout the cacheAPIs, httprequest, and alpha branches from the SVN as code from them will be merged into trunk going forward after a brief testing period in alpha and maybe through a few RC versions. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.11.12 06:47:00 - [265] Ok decided to put out the information on what's going to be happening with downloads for Yapeal. Since Google Code has decided to make some changes that makes it impossible to automate using downloads any more I decided I had to find another way to make them available My first idea was to try some of their other services and see if one of them would work. After looking at several and trying a couple I found none that could do what I wanted/needed. I started looking around and thought I should check out the changes that had been made by the competition SourceForge. Basically after looking around at all the changes I decided I liked what I saw. Now the question comes up if I should just move the whole project back over to SF or not. For those that didn't know Yapeal did start as a project on SF but was quickly moved over to Google Code because it seemed to have everything I needed and was easier to use at the time. After some testing I decided I did like Google Code's wiki and issue tracker better and so far the SVN is doing everything I needed but SF does allow me to automate (script) file uploads and do several things that just wasn't possible with the Download on Google any more. So in the end I've decided to leave the project at Google but host the downloads on SF and also start mirroring the SVN over manually from time to time which at some point I'll probably automate as well. So now the downloads that were on Google will now be found on SourceForge with several enhancements like having multiple folders for different branches i.e. trunk/, alpha/, etc. Since I had to do a fairly complete re-write of the admin scripts I use to build and upload the archives and installers, etc. I decided to make some other changes as well while I was at it. One that I think will be popular is I can now have copies of the developer document PDF and HTML files for the branches besides trunk/. Since often the other branch can have major code differences it should be helpful for anyone try to understand what's being worked on better. Another thing that the per branch folders makes possible is that each branch can now have installers and use the auto updater feature. This means that you can decided which level of stability of code to use with your application but still have Yapeal be able to check for new version and even allow setup of full autoupdating for when bug fixes are released without have the code go from an unstable branch that has a fix or feature you need to i.e. trunk/ code and start throwing a bunch of errors because of some non-backward compatible change that has been made in the branch to something. There will be some other benefits as well as I have a chance to setup and test them. So to the bottom line. If you want to get any of the archives you can now get them from https://sourceforge.net/projects/yapeal/files/ and pick the one that best matches the stability trunk/ alpha/ etc you want. If you want to use installer version for now stay with Google Code downloads as I'm still in the process of re-writing them and the ones on SF are incomplete at this time but the ones on Google are still available though really starting to show their age. You should only use them if something have happened to a current install of one of them and you need to get your application back up without any updates or changes. I'm trying to finish a re-write on the installers now and hope to have that finished Soon(tm) so everyone can convert over to SF for them as well. Once I have that done I'll be trying to fully automating the process so when I commit something to SVN the archives, installers, and docs also get built and uploaded. I'm out of space add more later. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.11.20 04:43:00 - [266] All the builds on GoogleCode are broken for several of the APIs that have changed and I have now hidden the download page there as it was really useless and just added confusion. My best advise right now is to make sure you have a real good backup or two for any data you want to keep and drop all the tables from your DB or make new one using the cacheAPIs branch code from SourceForge. Don't try any of the installers but instead use one of the archive (tar.bz2 or zip) downloads. I'm still trying to finish the rewrite on the installers to fix several issues with them. You have to run some of the script in install/ directory to setup the DB and it's tables then add any user/char/corps you need. After you are sure it's working try manually importing your old data. There have just been to many changes for the DB update system to figure it out. I've been extra busy in RL and trying to fix as many bugs at I can in Yapeal that I don't have time right now to write anything to help out with the conversion. If someone would like to help out writing some SQL to convert from trunk/ or the alpha installer version of the DB to the new one in cacheAPIs I really could use the help and will give you the credit (blame ) for it when I add it to the downloads if you want. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.12.03 21:38:00 - [267] Just a quick update to let everyone know I should have everything into the alpha branch now and would like to have people test it please. I would prefer to have it more tested before I move it to trunk/ but since trunk isn't very useable after all the API changes etc I'm going to be do so soon(tm) Only thing I may wait on is have some kind of instructions and path for those that need to convert their existing data over. Work is being done on that and I hope it'll be done within a few days with some help I'm getting with it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.12.11 04:46:00 - [268] There's some docs in the wiki from the web site you should find useful. You can also look at the Developer Guide PDF or tar.gz2 which is made from the DocBlocks in the code which should make somethings clearer than just reading them in the files themselves. If after having a look at them you have any questions on something contact me through my project owner E-mail on Google and I'll see if I can confuse you some more -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.12.13 00:57:00 - [269] Okay I finally decided not to wait any longer and have copied branches/alpha/ over to trunk/ It's not as tested as I might like but overall seems to be working well for most people that have been trying it. I'd like to thank everyone that helped try it and filed bug reports, etc. For those wanting to upgrade from the old trunk to the new you'll need to backup your config/yapeal.ini file and database before trying. I've also added a SQL conversion file that jmoerdyk has been working on. I added a couple changes and uploaded it to SourceForge in the trunk/ directory as yapeal-trunk-to-alpha.sql. It should convert the old trunk tables over to the new tables but as always make sure you have a couple of good backups of all your data as there aren't any guarantees it'll work right. If you have used the prefix feature from the installer in the past you'll need to manually edit the SQL file to make it work. Except if you really need your old data it is recommended you do a fresh install in an empty directory with a empty database as well. To setup Yapeal you'll need to copy config/yapeal-example.ini over to config/yapeal.ini and compare the settings in it and your old yapeal.ini and make any changes to them you think are needed. You'll notice several settings are now gone and a few new ones have appeared plus a couple have some addition allowed values. For most people you'll just need to change in the [Database] section your username, password, and maybe database settings everything else should work with the defaults but if you notice any of the others are different you'll have to decided if they need to be changed. The only other setting you may want to edit is log_level in the [Logging] section to set it as detailed in comments. After you have config/yapeal.ini edited to your liking you'll need to run a couple files you'll fine in install/ directory to make the database and the tables. The main files you'll want to run are install/createMySQLDatabase.php and install/createMySQLTables.php. For most Linux people you should be able to run them directly after setting them executable but if you don't want to do that or are installing on Windows you'll probably need to use something like this: path/to/where/php/is/php -f path/to/where/yapeal/is/install/createMySQLDatabase.php Windows: C:\path\to\where\php\is\php.exe -f C:\path/to/where/yapeal/is/install/createMySQLDatabase.php You'll have to add some command line parameters to both scripts to make them work but if you do the above with both of them they should show you some help text for what is needed. You don't have to use createMySQLDatabase.php if you have already made a new DB for Yapeal to use. If you are upgrading an existing DB use the above conversion SQL instead of this step. If everything goes right with the above you should have a work version of Yapeal that you can add some users/characters/corporations to and start testing/using. Some things to notice for long time users I've cut down on the noise level in all the log files meaning the will be empty most the time and shouldn't grow except when there is really something wrong going on. Yes even log/yapeal_notice.log is nearly silent now and can probably be left on even in production. This also means the only way to tell if Yapeal is actually doing something is to look for data being added and updated in the DB. Okay this has been a quick overview of what you'll need to do to upgrade/install and you'll probably need to look at the wiki on the project home or through some of the other docs like this thread for more help if something doesn't seem to work for you. One final note since the installers weren't working yet they have been deleted. Revision 1122 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.12.18 04:44:00 - [270] Sorry to hear about your raid dying and that I didn't get on to help you with your question but glad you figured it out. The scripts aren't very people friendly since they were made to be run by the installer and just had enough extra to let me test them too. I hope to have the installers working again soon but I know a lot of people won't or can't use them so I worked on the other stuff first. Just a FYI for everyone trying to use them if you run any of them without any parameters you'll get a short help that will give you what parameters you'll need to make them work. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.12.23 04:18:00 - [271] LuciferPhil check out http://code.google.com/p/yapeal/wiki/UsingClassUtilClasses and http://code.google.com/p/yapeal/wiki/UtilDatabaseTableDependences and look at how the isActive column effects which API Yapeal actually gets. You'll need to make sure it is on in UrilSections and for the users/char/corps you've added to the utilRegistered* tables. Also probably why you saw those files all on one line is you editor wasn't set for unix type line ends which are only \n not \r\n like windows usually uses. Andronette - Once you have the curl extension added to PHP you usually need to find a line that looks like ;extension=php_curl.dll in your php.ini file and remove the ";" so it is loaded. Make sure when you use phpinfo() you are not running it in a webpage which uses the CGI version of PHP but do it from the command line (CLI) which Yapeal uses. They often have different php.ini files they use by default as well so check that anytime something work with one and not the other. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.12.25 00:55:00 - [272] http://wiki.eve-id.net/APIv2_Corp_AssetList_XML that should have the extra info you'll need to make it work. You'll need one of the APIs to get that info so it's kind of related ;) -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.12.27 07:05:00 - [273] Edited by: Dragonaire on 27/12/2010 07:06:38 Look at post 582 here for a short guide on installing Yapeal. You have to do it manually for now until I've had a chance to re-write the installers. I've had people claim that it shouldn't need one and that a library shouldn't need to be configured but then someone like you comes along to prove them wrong once again. I've also now deleted the wiki pages you referenced as they were more confusing than helpful. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2010.12.30 14:21:00 - [274] First make sure you aren't trying to use (web server)CGI PHP to run Yapeal as it won't work Yapeal only runs with CLI PHP. Once you are sure that's not the problem check if for some reason changes to PHP's logging settings have been blocked. If you're using a hosted server they may have mis-configured something thinking they were making things more secure. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.06 05:04:00 - [275] Ok thought I'd update everyone on Yapeal again. Had some bugs reported mainly with trunk/. Several typos were found in the SQL upgrade script file which have been fixed. Some of those same typos were also in the SQL XML file and they have also been fixed. One more bug that was showing up with Windows was files like class/Section.php meaning Yapeal didn't do a lot other than throw lots of error Seems to have been cause by some changes to inheritance and parenting changes of some classes in SPL and their defaults in newer versions of PHP. Yapeal now is setting some settings to know working values which has fix the issue. revision 1134 -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.06 14:41:00 - [276] I'd suggest doing what everyone never seems to think is right and that is have it run every minute and don't use nice. The reason is when you don't let it run it just builds up stuff to do then when it does run it has to run harder for longer vs if you let it Yapeal has build in system to even out the load over time. It can take a day or two after you've started it for it to finish evening out the load. What it does is add a couple minutes of randomness to when it gets the APIs which over time spread out the load but it is hard limited to no more than 6 minutes so with you running it only every 3 minute that tends to regroup everything again making the work load stay higher. I've got other developers that were having the same problem with larger numbers of char/corp (hundred or even thousand of players) to try it and they all agree it does indeed work to reduce the peak workloads. Also I would say it's probably not Yapeal that is using the CPU but MySQL, network or storage load causing the issues you are seeing. In every case so far where I've worked with the developers have problems Yapeal itself was spending 99% of it's time waiting on either I/O (network or storage) or the MySQL server. Actual time spent in doing stuff was less than 1%. If you want some additional help with this contact me vs the project owner's email at Google. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.13 06:18:00 - [277] Sorry for the late reply seems to forums eat my first one The best source for docs on Yapeal is the developer guide which you can find in pdf, html.zip and html.tar.bz2 format in the downloads on SourceForge. IMHO the archive ones are better because they have link code pages where you can read about something and click a link to see the actual code. This thread and the wiki on google code also have some useful info you'll want to look at. Quote: ... struggling to actually do anything with the data because I don't know what Yapeal can do for me... You stated what Yapeal really does in the first part of the sentence but to quote the web site Quote: Used to get XML files from the EVE-Online API and store the results in a MySQL database. It takes care of getting the raw data from the APIs while dealing with the caching etc and then you just build your application like any other LAMP/WAMP project with a database that is 'Auto-magically' updated with new data as it becomes available. Hope that answered your question. On to some news about development in Yapeal. I've now add both a CHANGELOG and a new INSTALL.txt file that should be a big help for anyone doing an install from the archives or SVN. See the CHANGELOG for more details in the future beyond what ends up in the commit messages for the SVN. By using the new log more of the little changes and fixes should get logged that often got lost before because by the time everything was ready to commit to SVN some of them were forgotten about. revision 1137 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.15 23:39:00 - [278] ; Prefix to be added to all database table names. (required) ; Added for people that can only have one database where they are hosted. table_prefix="" You can find that setting in config/yapeal.ini it was made to be used just for what you are describing its also an optional parameter for the install/createMySQLTables.php script Hostname Username Password Database are required in install/createMySQLTables.php TablePrefix and XMLfile(s) are optional If XMLfile(s) is a list it needs to be inside quotes -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.17 07:19:00 - [279] There's been a bug fix done in trunk/ that hasn't made it yet into alpha is why you have the errors. Copying class/FilterFileFinder.php from your trunk/ install into the alpha one should fix it. For the best install instructions use the ones you'll find in INSTALL.txt as they work with Yapeal in it's current revision including all the branches though some of them may show a few more errors and their output can be a little different. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.19 12:54:00 - [280] I've put out what I believe is a fix in trunk/ for issue 65 and related problems people have been having. If you had the following errors please give it a try and let me know if this fixes it for you. ERROR: No section classes were found check path setting PHP Fatal error: Class 'FilesystemIterator' not found in ... on line 86 revision 1140 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.20 05:14:00 - [281] Those scripts expect the same XML you'd get from the API for accountCharacters. They were made to be used with the installer I had been using which could grab one simple API like that then pass it off to them to work with. They also need updated now to work with changes I made that moved graphics over to new table. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.21 04:55:00 - [282] Yeah they re-parented some of the classes/extensions in SPL so I'm going to have to keep working on it until it works with old versions and the new of PHP For any of you that haven't seen the other threads about WalletJournal they made some changes that have in effect disabled walking in Yapeal so I'll be looking into updating it in char and corp and I'm sure the same change was done to WalletTransactions as well. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.23 07:05:00 - [283] Or better yet try getting revision 1143 with the fix. I didn't actually get fixed put into svn before somehow BTW Cyril you fix breaks in the old version of PHP because the class and constants don't exist in older versions of PHP. it fails on $flags = FilesystemIterator::CURRENT_AS_FILEINFO line because of that like I posted in issue 66.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.25 11:13:00 - [284] Just found a nasty little bug in Yapeal dealing with caching for corp APIs not working right. Everyone should update to revision 1146 on trunk/. If you are trying to use one of the branches try running a diff on class/SectionCorp.php to see what you'll need to change. I've been working on updates for all the changes in the APIs since Incursion and hope to have some of it out soon. I want to at least have everything work right again then I'll worry about adding some of the new APIs. revision 1146 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.26 01:20:00 - [285] Yeah I'm still doing a little testing on some of the incursion stuff but I'm planning on merging some of it very soon. I need to finish some of it up plus I want to see if there's going to be anything in the patch Thursday that needs to be handled. After I get a chance to look at the patch notes I'll decide when to go ahead. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.27 04:42:00 - [286] Actually should just take a few setting changes since it ends up using cURL for all network traffic and cURL supports HTTPS already. I was trying to make some changes to let Yapeal use php sockets directly etc since some people don't have option to use cURL but never really got to far on it. I've never seen a real need to use HTTPS like most developers I'll end adding it if users ask for it I'm sure but as much as most people think everything in the APIs is of vast importance the reality is that ever most Eve players don't care, let alone someone else out side of Eve about how many corpses you're hiding in you hanger . -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.01.28 04:01:00 - [287] Fredrick Engly - If your line 86 doesn't look like this you aren't up to date: if (defined('FilesystemIterator::UNIX_PATHS')) { Also make sure you are using trunk/ as that fix has not been done on any of the branches yet. make sure you're at revision 1147 for the SVCN as that's the current. Let me know if you're still having problem after check those things and I'll look into it some more. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.02.05 20:36:00 - [288] The cachedUntil date/time doesn't matter to Yapeal so it isn't that as long as it's in the correct format YYYY-MM-DD HH:MM:SS just like all the other dates except a few CCP also using empty strings in Best thing to do when you start getting a lot of errors with an API like that is to check out the actual result sent and cached in either the files (cache/char/WlletTransactions.xml) or utilXMLCache table depending on which you are using (or both). If it looks right then it's something else if not delete cached XML from both locations. Do look at the times and make sure Yapeal hasn't got stuck and keeps trying to use an old one. There is a bug I haven't fully tracked down where it somehow get's hung up on the old XMLs and won't grab them again from API at times. It is rare but I've noticed it a few times during testing. It always seems to recover once both caches are cleared for the API. It maybe related to the bug reported in issue 67 which I think I have a fix for now and hope to get out for testing this weekend. It could also be related to another bug I found a few days ago having to do with how the hash was calculated that is used in the cache files names and database table which could cause some APIs to overwrite other APIs cache files and use the wrong cachedUntil times as well. I will be updating the SVN and archives with fixes for both later today so they can be tested. -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. SOUL CARTEL	Posted - 2011.02.06 21:48:00 - [289] Hi All I've been working on getting something out for incursion and the code needs some more testing so decided to add incursion branch to downloads on SF so a few more people might try it out and let me know if everything seems to work. I think I've also got issue 65 finally completely fixed for both old and newer version of PHP. I basically ended up doing feature detection like I was working in Javascript or something For those that want to give it a try there is a new branch where Johnathan Roark and I have been work been working on converting Yapeal to use HTTPS. You can find it in branches/https/. Be warned it's taken from trunk/ so will probably have some problems if you try any of the APIs that do walking like WalletJournal or WalletTransactions. If you try out trunk/ or any of the new branches make sure you read their CHANGELOGs to see what has changed in each of them. revision 1160 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2011.02.12 16:42:00 - [290] As you found alpha branch is currently broken. The trunk and the incursion branch are you're best bets with the incursion branch being preferred as it needs the testing and will soon be replacing the code currently in trunk. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. Everto Rex Regis	Posted - 2011.02.13 11:56:00 - [291] Either is ok I do like issues on site better in that they end up E-mailing me so I know there's something new to look at. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Everto Rex Regis	Posted - 2011.02.18 10:20:00 - [292] Hi all, After a few delays I've finally reintegrated the incursion branch back into trunk/. Make sure to read through the CHANGELOG as there's a few things existing user should do like clear their exist XML cache but there are no database changes to deal with this time if your trunk/ was already up to date. The changes have mostly to do with fixing walking for WalletJournal and WalletTransactions for characters and corporations. CCP seems to have some issues with how walking works in the APIs themselves but Yapeal should work with whatever it does get from them correctly. Several bugs like issue 65,66,67 seem to be fixed. Probably one of the biggest changes that will be noticed is Yapeal now uses HTTPS connections and unlike what I've heard about other API libraries Yapeal does actually check the certificates from the API servers so 'man-in-the-middle' attacks aren't possible now. I understand some other libraries have started using HTTPS connections but don't bother to check them which is kinda like using a new security door on your house and leaving the window wide open next to it As always reports of any problems are welcome either here or as an issue on the main GoogleCode site. revision 1164 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Everto Rex Regis	Posted - 2011.02.22 06:07:00 - [293] Since you brought it up yes there is a new update to XSDs since it seems AccountStatus.xsd wasn't allowing offer rowset to work correctly. There were of course a few other improvements made to all the XSDs while I was working on it in incursion branch as stated in the CHANGELOG. BTW Santa was very nice to me and it isn't even December thank you -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Everto Rex Regis	Posted - 2011.02.28 07:29:00 - [294] You might also try http://bitnami.org/stack/mampstack as I've had good luck using their WAMP stack and would expect the Mac one to be good too. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Everto Rex Regis	Posted - 2011.03.16 04:17:00 - [295] If you are writing an application you might also look at using class/util/Registered.php and the other classes there to manage the tables you'll need to make things work. In the README file you'll find some links to the wiki where you'll find more information on how everything works together. -- Finds camping stations from the inside much* easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Everto Rex Regis	Posted - 2011.04.07 15:01:00 - [296] Probably the last post on the old forums I've started a new thread on the new forums for Yapeal which you can find at https://forums.eveonline.com/default.aspx?g=posts&t=4266&find=unread -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Everto Rex Regis	Posted - 2011.04.18 04:59:00 - [297] The memory problem have already been solved by going to XMLReader soon after those blogs. Yapeal has been used in applications with 100s to 1000s of characters and/or corporations and memory isn't a problem. At least it's not for Yapeal but sometimes the DB has problems keeping up because of memory or I/O bandwidth problems -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. Everto Rex Regis	Posted - 2011.06.06 08:13:00 - [298] Hi all know it's been a little quiet for development lately but I've been having multiple computer issues and been working on another project related to Yapeal. Seems I missed any Dev Blogs about NPC corps now returning data for CorporationSheet so when someone brought it to my attention in issue 73 I made a change that now will let it work with them. Let me know if there are any other APIs that need to be updated because NPC data is now available for them as well. Fix is in SVN on GoogleCode and I'll try to get it pushed over to SourceForge soon. Now for a little background on the other project I've been working on. You can find it at https://sourceforge.net/projects/xmlschema/ As most of you know ADOdb is use in Yapeal and during the install it uses the ADOdb Data Dictionary Library from ADOdb to build the SQL needed to make the database tables from the XML files in install/. It has worked well generally but has a few quarks and 'features' to it that make doing some things like updates more difficult than it should be. It also lacked some features that would make it vastly more useful IMHO. To make a long story shorter a friend (Johnathan Roark) and I in the end ended up branch the old unmaintained project on SF and started a new one. Johnathan took on the job of rewriting the table extract code so it used DOM instead of the hand coded strings it had before so it could be more easily maintained. I took on the task of rewriting the rest of the code used to make the SQL from the XML. While we were at it I thought it would be a 'Good Idea' to also make a <schema version="0.4"/> with some of the new features that we had come up with. The first thing needed was to convert everything away from XML Parser which is based on James Clark's expat to something more programmer friendly like XML Reader which is used in Yapeal but to do so someone (Dragonaire) had to learn how XML Parser worked. For anyone else trying to do the same thing make it easier on yourself and just make your own code that takes your input XML and gives the right result as trying to do it like I did is NOT the best way but was needed for backwards compatibility. Okay to sum it up and not bore everyone anymore, do to backward compatibility and feature creep in the project what should have been at most a 1-2 month project has turned into a 6 month and counting one In the end I know it'll be worth it for how it will let Yapeal be more forgiving during installs and upgrades but does mean Yapeal will mostly be in bug fix only mode for a while longer. revision 1170 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2011.07.12 02:26:00 - [299] Hi, it seems there was a change to the WalletTransactions API that wasn't in the notes I've updated the cache//.xsd, install/corp.xml and install.char.xml files to reflect the new journalTransactionID field. You'll need to update your database using install\createMySQLTables.php as per step 8 in INSTALL.txt. I've added an updated cert file in config/eveonline.crt to see if that helps with the other APIs errors that people have been having. revision 1175 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax.	Posted - 2011.07.13 14:48:00 - [300] Quote: I know I have a slow connection, but not that slow ;) I also find it interesting to see the http instead of https, I see them on several API calls including Characters and ServerStatus which are all in the /server or /account API calls, maybe that has something to do with it? Thank you for noticing that Yapeal was still using HTTP instead of HTTPS on some calls that seems to be the root cause of all the errors that everyone has been having Seems I might need to take back some of the things I wrote about CPP and the even worse ones I'd been thinking as it was an error in Yapeal after all What was going on is because of Yapeal trying to use the same connection over and over again when it can but switching between HTTP then HTTPS or the other way around Yapeal was confusing the poor API servers I'm sure. Most the time they could adapt to the switch but once in a while either a packet gets drop while making switch some where on the Internet (UNKNOWN PROTOCOL) or they simple were busy enough they couldn't switch as fast as needed or were just plain confused (Operation too slow.) As to how everything didn't get converted to HTTPS I'm guessing it happened during the merge of the branch where I was testing HTTPS into trunk or right after that when something got reverted when it shouldn't have been either way I know who did it (ME) and they have been beaten severely for it I can assure you Quote: Failed to execute schema for util Not all files processed correctly Not sure why it does that, it sometimes happens to me too, but as long as DB and tables in util* get created it should be ok. If you want you can try running the cache/util.sql that is generated as well by script directly in MySQL just to make sure everything is all right. I believe in part I'm running up against some bug or limitation in ADOdb Data Dictionary. One reason a friend and I decided to branch the old project is to fix some know problems with it and try to add things to it to make it more useful for ourself in our other projects like Yapeal etc plus everyone else that might find it useful. Anyway everyone please upgrade to revision 1176 and let me know if that fixes the problems with connections. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax.	Posted - 2011.07.13 21:35:00 - [301] Not your fault I just missed it in all of my checking and no one else had noticed it. I know at one time I had changed all the APIs in trunk/ but somehow some of them reverted and I didn't catch it because I knew it had been changed I'm just glad it's fixed now. I'm glad you've found Yapeal useful and hopefully I'll have a chance soon to do some additions to it not just be in bug fix/maintenance mode. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.07.22 15:16:00 - [302] Think I know why you're getting that error and it has to do with bonusName length being 255 and using UTF-8 collate. I'll look into fix for it but something you can do manually is just convert it to ASCII as none of the current API use any characters outside that range. Here's a link describing the problem http://bugs.mysql.com/bug.php?id=4541 I might have notice this sooner but I've been trying out http://mariadb.org/ and http://www.tokutek.com/ and not running the standard MySQL version and they seem to have already fixed that bug. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.07.27 04:48:00 - [303] Simple way to know is look at which APIs have classes in class/api/ but you seem to have missed some info while looking at the wiki as well. I know it might be a little hard to find one named APIList but that was the best I could come up with sorry. Here's a link for you http://code.google.com/p/yapeal/wiki/APIList it might be a little out of date a few more probably work now but like I said take a look in class/api/ and it should give you a better idea. While you're looking at the wiki you might also try looking at the couple featured page called KeyFiles and UsingClassUtilClasses and you should be able to figure out why you may not be getting anything in your tables but just a couple hints here for you check your isActive columns in all the utilRegistered* tables and make sure the APIs are listed in utilSections as well. If that doesn't get you on the right track sent me an E-mail at my G-mail account which you can find from the website and I'll be more than happy to help you further. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.07.27 20:53:00 - [304] I had at least 5 people say they are going to write some install and setup instruction and I've only ever got a few step of it from them each time and I'm not good at writing that kind of docs I'm sorry. I see Yapeal from a much different way since I'm writing the code than someone just trying to use it. I've tried it myself and it never really seems to be very useful for people. I will highlight one more wiki page I missed before which may help clue you in on how everything in util* work together. UtilDatabaseTableDependences The best way to think of it is everything in util* tables is used for admin of the actual API tables. As to the API and user thing that was because with the old API system the keys belonged to the account/User and since it was the UserID and APikeys Yapeal needed to get the data from the API server the table got name after that. I want to let people have control over which of the account API Yapeal would retrieve so to make it similar to the other utilRegistered* tables I added the stuff there. I'll let you read the wiki page and I think you'll understand better how the tables work together. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.07.28 04:09:00 - [305] Actually the util* tables are going to be undergoing some changed because of the new custom API key system that CCP is rolling out in just over a month so I'm having to do some large changes in Yapeal and I'm hoping to normalize the tables while I'm at it so I'll be revisiting all the docs when that happens. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.08.01 16:35:00 - [306] Thanks Rex Golden glad you like it. Ok decided I'd update everyone on what's going on with Yapeal with the new custom keys stuff coming out sometime around the end of the month. I start working on the conversion when CCP Stillman announced the time frame etc in the Customizable API key update thread. Some parts of it are still in flux and it is a big change but after taking some time to understand it and make a few suggestions on changes to them I started working on the new tables and code to work with the new keys. I have a branch going with some working code in it but be warned its very much ALPHA and there's no documentation on how things work but account, eve, map, server APIs do seem to be working right now. For anyone that wants to try it and is okay with code that can crash without warning and take your data with it while having the possibly of your computer giving birth to strange things like hamsters here's a few pointers. The utilAccessMask table is the key to new activeAPIMask column that has replaced activeAPI in the util* tables. The utilRegisteredKey table is your new best friend. Yapeal has totally forgot what a userID, fullAPIKey, limitAPIKey is for. Try using this for proxy in utilSections table: https://apitest.eveonline.com/%section$s/%api$s.xml.aspx I'm sure there's more I could add but that should be enough for anyone that really should be trying out the new code as it now works. One last warning for anyone that hasn't thought of it. DO NOT TRY UPDATING EXIST DATABASE TO WORK WITH NEW BRANCH. First it'll probably not work and second to will totally trash your existing data. Use a new database to try it out with and make sure you change the settings in config/yapeal.ini so as not to interfere with any production version you may have on the same server. As usual report any bugs here or preferably through issues on website. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.08.07 15:30:00 - [307] Until after the conversion to custom keys is done and on Tranquility and any bugs from conversion in Yapeal are worked out I don't plan on doing anything else. As you said CCP is working on a fix which hopefully is include before or with custom keys so it's going to stay in wait and see mode for now. If they hold to the stated time-line we'll only have a little over 3 weeks before custom keys is out. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.08.15 05:33:00 - [308] Ok thought it was time for a little update on the progress I've made on conversion to custom keys. There is an ALPHA branch that is ready for anyone that is willing to try it available in branches/keys/. I've also upload archives to SourceForge as well in downloads under keys/. It's by no means ready for production server but it's unlikely to cause your server to have hamsters now I haven't really updated to much of the docs to reflect changes so plan on puzzling over the DB util* tables for a while to understand them and reading through the code a bit as I've tried to comment it as I've made changes. What ever you do DON'T TRY TO UPDATE AN EXISTING DATABASE USING install/createMySQLTables.php as it'll die in a VERY nasty way and probably that your data with it. Use a new database on a test server to try this branch with. IF you have to use the same server as your main server that is running trunk/ make sure to have good backups just in case you forgot to configure something right and it gets clobbered. That's it for now if you give it a try please report any bugs or errors you find on issue tracker from Google Code or here if you can't. revision 1187 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.08.20 04:20:00 - [309] Quote: That one looks like it wouldn't be too hard to add, its counterpart, tad more of a challenge. Atm I'm working on adding contracts. Dragonaire suckered me into it. Your idea to help plus it's been 3 different APIs you said you do before you finally did one before I give up on you doing it
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.08.20 04:26:00 - [310] Originally by: Johnathan Roark Originally by: Dragonaire Quote: That one looks like it wouldn't be too hard to add, its counterpart, tad more of a challenge. Atm I'm working on adding contracts. Dragonaire suckered me into it. Your idea to help plus it's been 3 different APIs you said you do before you finally did one before I give up on you doing it I never established a timeline for those! And you tired to sucker me into those ones as well. was your idea to add them

Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.08.20 19:43:00 - [311] Hi all just thought I'd put out an invitation out for any application developers that use Yapeal to join a chat channel where you can get some help on conversion to custom keys update. Others are welcome as well but things might not be as useful if you use another API library. Room: evephp Server: conference.eve-corporate.net Password: No password for now. I'd like to thank Johnathan Roark for letting us use his server for this. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.08.25 05:02:00 - [312] Ok I'd like to see Yapeal get some more testing before things go live so I'd like to invite anyone that is interested in helping out to try out the keys branch from SVN or in the downloads on SourceForge and give feedback on any problems or errors. I'll try to do some kind of quick guide to things that are different and how to use it with SISI test API server in next day or two as well but I'd really like anyone that has used Yapeal in the recent past or never to let me know where you get lost in trying to use it so I can try to cover anything I might not think of on my own. Make sure to check out the latest Yapeal blog as well at Peeling Yapeal for some info that you might find interesting and helpful. Sorry about the formating I did it in a hurry and don't have time to fix it right now You'll find a couple new APIs and there's a couple more being worked on as well that should be added very soon -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.08.31 05:08:00 - [313] Hi all, So by this point I was figuring on having the wiki updated with info about the new custom keys and how they work in Yapeal but I've really ran out of time to do that with RL and the short time frame give by CCP so I'll try to hit the highlights here and direct you to where you can find some more info too. First I'd like to thank Johnathan Roark for all his help on stuff. He and I have helped each other on our varies projects before but he eve has gone so far as to add the new contract API this time around and should finish off the other contract APIs in the near future once CCP either fixes a issue we found with them or I've had a chance to work with him on working around it. He also was both my Alpha and first Beta tester so he got to see the code when it was still very broken in some cases and provided the great feedback that I always get from him. As he pointed out in the post above me here it's best to drop all the tables in account* and util* from the database as they have had to undergo some major changes that can't be upgrade really. As always when upgrading the database you should have full backups of everything but none of the API table outside of account should have any large changes just a few minor fixes as usual when I notice something or someone else reports issues to me. You will notice a few more APIs should be active by default now when you first install Yapeal. I'm trying to have some of the ones I felt everyone was likely to use active now but haven't had a lot of time to really go over them and make a firm list yet so do give me some feedback on which ones you'd like to see. Ok so here a list of the big changes: New utilRegisteredKeys table - This replaces utilRegisteredUser in most ways and is the only Registered table that is always used. accountAPIKeyInfo table - This is the new table used to figure out key types and other info. accountCharacters - Merge with APIKeyInfo in effect as a rowset. The column names have changed to match the new source and no userID now. accountKeyBridge - Not really part of the APIs but it is the key to making connection between APIKeyInfo and Characters tables. util* - activeAPI is now activeAPIMask and instead of a list it is now a bitmap just like accessMask from APIKeyInfo. This has been expended on from what's in the APIs for the eve, map, and server sections utilAccessMask - Used to convert to and from new bitmap for masks. Should not need to use directly if using class/util/Registered.php classes Registered.php - These classes are provided to help other developers interface with Yapeal and internally too. If you have been currently using them only real change here is there is now a RegisteredKey instead of RegisteredUser. registered_mode setting - New setting found in config/yapeal-example.ini that should be checked out as it can have a large effect on how the char/ and corp/ sections work in Yapeal. Ok running out of space so here's some links to more info. http://www.eveonline.com/ingameboard.asp?a=topic&threadID=1554297 http://peelingyapeal.blogspot.com/ http://code.google.com/p/yapeal/source/browse/#svn%2Fbranches%2Fkeys Out of space hope those help. http://sourceforge.net/projects/yapeal/files/keys/Yapeal-developer-guide-keys.tar.bz2/download -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.09.03 18:59:00 - [314] Ok I've now update the Yapeal main page with info from my public API key. To understand what a public key is all about take a look at the page. While I'm posting I'll do a little update too. I'm still working on some of the error handling code mostly the part that tries to de-active keys/chars/corps etc when there something wrong with them or something. Some of you may have also seen that the notice log is a bit noisier then before because of some of the new changes to how keys work. I'm in the process of quieting it down again as well. As always let me know if you are seeing anything you don't understand in the logs or new so I can look into them. revision 1202 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.09.05 02:26:00 - [315] Unfortunately the docs are all very out of date because of the changes do to custom keys. But here's some tips on using it. The table you have to add stuff to is utilRegisteredKey. You'll need to look at registered_mode setting in config/yapeal.ini (make copy of yapeal-example.ini) to know if the other utilRegistered* tables are needed. For things you want to access the API the isActive column is important. It's in several of the util* tables and they do interact like the ones in utilSection are overall controls. Look through the featured wiki pages. They are out of date but as long as you think key where it says user it'll give you some idea how stuff works. I'll try to get the docs updated soon -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.09.05 21:35:00 - [316] If you are looking for the zip or tar.bz2 archives they are in keys folder on SourceForge. If you are looking for the correct place in the SVN try getting it from branches/keys/ instead of trunk/. BTW it's utilRegisteredKey not untilRegisteredKey but I'll assume that was a typo -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. PURgE Alliance	Posted - 2011.09.08 14:29:00 - [317] Ok going to try this again and move to the new forums. If you have questions or comments please post them there. New Yapeal Thread -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.