|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Dragonaire
Corax. PURgE Alliance
7
|
Posted - 2011.09.08 14:20:00 -
[1] - Quote
Yapeal has now been in development for nearly three years and proven to be useful for many people in their Eve API applications and websites. For a description of what it does check out the project home page at GoogleCode.
Yapeal has now moved out of what I considered 'Alpha' into 'Beta' stage of development. For people use to Mircosoft's way of doing things Yapeal is now Win98 vs Win3.11 or Win95 (It actually works for more than 5 minutes
Yapeal is licensed under GNU LGPL 3
HOME PAGE http://code.google.com/p/yapeal/
You can find my public API key on the home page as well.
I have a blog for Yapeal called Peeling Yapeal that everyone is invited to follow as well.
It's now recommended that everyone uses the downloads of the non-installer versions which are available at: https://sourceforge.net/projects/yapeal/files/trunk/ CAK branch is in https://sourceforge.net/projects/yapeal/files/keys/ Yapeal is also still available through the SVN at: http://code.google.com/p/yapeal/source/checkout
For more information about Subversion see http://subversion.tigris.org/ Windows users may find http://tortoisesvn.tigris.org/ easier to use.
Please report any bugs you find in this thread or as as issue on the website.
You can contact me through the developer name from the project @ gmail.com Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. |
Dragonaire
Corax. PURgE Alliance
7
|
Posted - 2011.09.08 14:32:00 -
[2] - Quote
Here an extend explanation of what Yapeal does since it a little different then the other PHP API libraries people are using.
It doesn't only grab the data from the API for you but also saves the new data into a MySQL database for you. 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's made to be set and forget once configured.
Some features:
- Auto download of API data
- Auto updating of database tables
- Can be ran from crontab (preferred setup)
- Can be run from command-line for debugging or special needs
- Keeps track in the database of API cachedUntil times so it is API friendly even if ran every minute in crontab
- Does optional local caching of XML file from API
- Multiple corporations and multiple characters by just adding their information to database tables
Many other features but those are the main ones for now. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. |
Dragonaire
Corax. PURgE Alliance
7
|
Posted - 2011.09.09 06:19:00 -
[3] - Quote
Not really in the main Yapeal code as for some unknown reason CCP decide to put an API that requires key etc in eve section where none of the other APIs do. Until they fix that by putting it where it belongs in char section it can't be supported really. Having said that I will say that some work has been done to add what I call a retriever to Yapeal for stuff like during website sign up where you might just need one or two API calls without waiting on normal Yapeal crontab etc. I plan to make it more versatile when it comes to the parameters that you can have it pass to the APIs which should allow it to be used for some of the oddball APIs like CharacterInfo as well. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. |
Dragonaire
Corax. PURgE Alliance
7
|
Posted - 2011.09.11 06:58:00 -
[4] - Quote
I've been working on updating some of the wiki pages for CAK and have finished with the last of the featured ones. Take a look and if something doesn't seem to be clear or you find an error let me know.
In other news I'm looking to merge branches/keys/ over to trunk/ soon as I believe it is complete and there doesn't seem to be any bugs. I've already made a last tag from the current pre-CAK trunk/ just to have it as a reference for the future. There is some work being done on contracts that I'm hoping can be merged into keys soon and once it's been tested and reviewed a little the process to make branches/keys/ the new trunk/ will begin.
I've also had someone come up with an idea for how to work around the issues surrounding the IMHO misplaced /eve/CharacterInfo API. If it proves out the API should be added to the grow number of APIs Yapeal supports. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. |
Dragonaire
Corax. PURgE Alliance
8
|
Posted - 2011.09.13 03:17:00 -
[5] - Quote
I've been waiting to see if someone would finish the other couple contract APIs before releasing it (Looks at Roark) but doesn't look like that going to happen for a few more days anyway so I'll probably be merging what's been done into keys in the next day or two once it's been tested a little bit since QA (me) has found a couple problems and thought it might be a good idea Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
9
|
Posted - 2011.09.14 04:42:00 -
[6] - Quote
As Johnathan Roark said make a good backup or two then delete the util* and account* tables and run the script. There are only minor changes to the other tables that it should handle without problems. You can find some more complete instructions in INSTALL.txt just insert the above in the correct places.
Quote:Is there support yet for the new Contract API? Merge the contract branch into keys and uploaded some updated archives on SourceForge as well. Work on the other two contract APIs is in progress as well. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
9
|
Posted - 2011.09.15 04:30:00 -
[7] - Quote
Ok I've gone ahead and merged branches/keys into trunk/ It's as good as it was going to get in the near future and seems to be as bug free as can be without wider testing. enjoy.
revision 1228 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
9
|
Posted - 2011.09.15 21:08:00 -
[8] - Quote
You have the option to ignore it depending on your needs actually. Make sure you've read the updated http://code.google.com/p/yapeal/wiki/UtilDatabaseTableDependences and http://code.google.com/p/yapeal/wiki/UsingClassUtilClasses wiki pages as they have been updated in the last few days. You'll want to pay attention to the part about them being optional if registered_mode is set to that. Now to try to help out on understanding the table you asked about the classes use what are called magic methods to make the columns from the tables look like properties in the class. which makes setting and changing them very easy. You can also get them as well. There are also a couple methods addActiveAPI() and deleteActiveAPI() which let you just use the API names instead. To set the $corp->activeAPIMask directly you'll need to use a bitmap instead just like I show near the end there. Hopeful this little extra info will get you headed in the right way but if not I'll try to do a long explanation after work for you Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
10
|
Posted - 2011.09.16 15:29:00 -
[9] - Quote
Actually the Notice error you are getting might be part of the problem you're having as it's a bug that seem to have crape in with a bad cut and paste I've updated svn and archives to fix it.
Make sure you are using the archives (zip/bz2) or current svn from trunk/. If you are using archive check the revision in revision.php the YAPEAL_VERSION line will let you know which you are running. It should be 1231 or later. Also make sure if you do use archives you cleared out old version before unpacking the new one where you have it installed. Clear just the class/ directory should be enough but it doesn't hurt to backup your config/yapeal.ini file and wipe the whole thing if you still have problems. Also remember the RegisteredCorporation/Character tables can be totally empty when using registered_mode=optional like you are using but do make sure in utilSections that account row's isActive=1 or it'll come back to bite you later.
BTW you can also get the corporationID etc from the accountCharacters table just like Yapeal does for active keys Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
10
|
Posted - 2011.09.16 21:04:00 -
[10] - Quote
Yes you can have as many as your system can keep up with in a single DB. Everything is either keyed by keyID, characterID, corporationID in each table. If a column by those names don't exist in the XML I add an ownerID column with the correct type for the section of the API it's in. So for char section API it will be characterID etc Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
|
Dragonaire
Corax. PURgE Alliance
10
|
Posted - 2011.09.17 03:46:00 -
[11] - Quote
The only place in Yapeal that table was used was with some of the scripts in install/. They were used to interface with a GUI installer that I tried with it at one point but few people liked it or used it so it was dropped at least for now. The scripts still exist they are the addTestCharacter.php and addTestCorporation.php scripts. In the installer it would show you pictures of chars/corps to choose from on an account to add to the Yapeal database for testing. At one time the pictures were in the Registered tables but to streamline and normalize them I moved the pics to where they are now. Since they aren't really used in Yapeal you would be free to use them in your application if you want just keep in mind that at some point I may start using them in Yapeal for what they were made for so I would keep them just for character and corporation pictures. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
10
|
Posted - 2011.09.17 16:31:00 -
[12] - Quote
Your right there was an error in getSQLQuery(). Actually all 3 modes can use the same query so I'm dropping the switch. (Fixed in revision 1232)
I'm not seeing the notices and I believe those errors were cleared up in a revision of keys so I'm guess you're using an old version of it and not the latest trunk/. There are some errors popping up for some of the API that aren't implemented yet and I'll try to make some changes so Yapeal returns a different error message so it's clearer what is actually happening. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
10
|
Posted - 2011.09.17 18:31:00 -
[13] - Quote
Yeah database needs to be updated to get the changes made in util* tables etc
Did a couple more updates the install/*.xml tables that should make database updates work better. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
10
|
Posted - 2011.09.18 18:50:00 -
[14] - Quote
Ok been working on several things over last couple days like killing many bugs in the class/Registered* classes and issues when trying to do database updates with install/createMySQLTables.php. Read trunk/CHANGELOG for a more detailed info on what was changed.
revision 1235 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
11
|
Posted - 2011.09.30 07:28:00 -
[15] - Quote
In utilSections change activeAPIMask to 305 for eve section as that API is off by default. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
11
|
Posted - 2011.10.01 14:42:00 -
[16] - Quote
Make sure you read the INSTALL.txt file but if you still have some issues after that posting here or join the chat at
Server type: jabber (xmpp) Room: evephp Server: conference.eve-corporate.net Password: No password for now.
I'm in the room most of the time if not always at keyboard and there's usually a couple other people on there that also know Yapeal that are willing to help out. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
11
|
Posted - 2011.10.03 23:38:00 -
[17] - Quote
Only think I'll add to the above by Drapko Nitzhonot is utilRegisteredCorporation is totally optional when registered_mode="optional" in config/yapeal.ini which is the default now. You should only need to add your new key to utilRegisteredKey and make sure the corp row in utilSections has isActive=1. If one of the corp API tables doesn't seem to receive any data make sure the activeAPIMask values have the correct bit set for the missing API. You can figure out the mask you want by simply adding up the mask columns in utilAccessMask for the corp APIs you want. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
11
|
Posted - 2011.10.04 16:55:00 -
[18] - Quote
Start by reading http://code.google.com/p/yapeal/wiki/UtilDatabaseTableDependences from there the best thing is to look at the code in some of the classes and understand both the SQL queries and how the filtering in class/Section*.php works. The DocBlocks on ignoredFilter(), optionalFilter(), and requiredFilter() and other comments there should help.
Just to maybe help make things a little clearer Yapeal tries to be at least a little bit intelligent and use any info available from APIKeyInfo in addition to the utilRegistered* tables and won't do stuff with char/ and corp/ section APIs without some of it being available. I do allow you to shoot yourself in the foot by turning APIKeyInfo off but if you do you're on your own.
Also make sure you understand how many to many relationships (don't) work in databases. That's where accountKeyBridge comes in. It's job is to change the many to many relationships between accountAPIKeyInfo and accountCharacters into a couple of one to many relationships instead which the database can handle.
Quote:I'm trying to understand how to build a relationship so that I can Create-Reuse-Update-Delete all the CAK's used by an Account, Character or Corporation The above should help you with what you're trying to do but I believe you are also looking at relating multiple keys together in regards to some kind of 'user' account in your application which is beyond the scope of what Yapeal does. Yapeal really only understands keys and that they are sometimes related to characters, corporations, and their APIs nothing more. To manage keys as a group is totally up to the application developer which will probably mean you'll need to have a few database table of your own Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
11
|
Posted - 2011.10.05 04:14:00 -
[19] - Quote
Brought issue 76 back to life and have some new code for you to try as well which you can find in my post there. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
11
|
Posted - 2011.10.05 06:28:00 -
[20] - Quote
Only way to learn stuff is to ask questions so not a problem. Yapeal doesn't have any kind of frontend for getting the keys etc into it but does include classes you can use from class/util/*php to add them to it once you collect them. It should have all the APIs you need to get the other stuff you want once that's done. Make sure you read the wiki pages I pointed out a couple post back as they should be helpful to you as well. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
|
Dragonaire
Corax. PURgE Alliance
12
|
Posted - 2011.10.05 21:32:00 -
[21] - Quote
Okay decided to push out fixes for issue 86 and hopefully issue 76 as well.
revision 1243 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
13
|
Posted - 2011.10.10 17:17:00 -
[22] - Quote
Ok Thought I'd update everyone on some changes that I've finished in the last couple days which should make existing users happier and make it easier for people just getting start with Yapeal. They also should help decrease the number of times I get to explain some of the same things over and over again. That my hope anyway but we'll see if it works that way
First let me give a little history. There have been a couple tries at adding things to Yapeal to make it easier to install. There was one that used a series of web pages first which worked and was a great chance for someone that was relative new to PHP to and Yapeal get started on. After a few months they moved on to other projects I also didn't think a web front end installer for a command line tool like Yapeal was a good match but I did see where having some kind of instiller would be helpful so I worked on adding an installer that had both GUI and command line interfaces that worked cross platform on Linux, Windows, Mac, and several other Unix platforms.
No one but me seemed to like it and many long time users continued to install manually or use the web installer even though it wasn't really working correctly any more. The GUI had several problems with it most of which came down to me trying to have it do things it wasn't made to do and trying to do it in the same ways as the web installer had.
During the development of the GUI installer I found a need to write some scripts to let it do some stuff I need so I hack together a few PHP scripts for it to use on the back end. In the mean time the Web installer became totally unusable with the changes that had happened in Yapeal and I didn't have the time to update it and like I said I thought it was bad match anyway. I was also in the middle of a rewrite in the GUI installer at the same time so Yapeal was once again without a working installer.
One reason many of the developers using Yapeal didn't like the GUI installer or even the CLI version of it is they didn't have shell access on their hosting service but they did have crontab service so they could simple install it locally and copy it over and do a few database updates with phpMyAdmin which they also had access to. I suggested to a few of them when they said something about not have either the old web or new GUI installer to use locally to help out that they could use some of the back end scripts from the GUI to do stuff if they wanted and even finally wrote up a quick check list to help them remember the steps.
If this is starting to sound familiar that's because the current process used is basically the same now but I did improve on the instructions a little and started including them with Yapeal. What wasn't improved was the scripts since the plan was to one day go back and do an improved GUI installer.
So now it's been a while and some other projects demanded some attention so for the last 6 months to a year everyone has used the scripts I hack together for the GUI back end. During that time I've had many questions about installing Yapeal etc plus had feedback from developers using it that it would be nice if they didn't have to keep reentering the same information a couple times during updates.
Now pair the above with CAK coming out and I had to switch my attention back to Yapeal again for a while and deciding I could make it smarter and take advantage of some additional information that has been made available. Also during that time PHP 5.3 was released with many improvements and many hosting sites finally dropping the older versions of PHP when the PHP developer team stopped doing updates for them etc. One of the improvements with PHP 5.3 is the Windows CLI gained better support for command line parameter processing including using long versions which all of the other platforms had supported for a long time. So now it's possible to really design CLI scripts in PHP with all the features that have been available to every other shell or command line scripting language for a long time.
So what does all of this long history lesson have to do with this update? I'm glad you asked
I've updated the old hack together scripts used to install Yapeal currently into ones that are much more human friendly and even more intelligent then before. They now have actual parameters instead of just putting the settings needed after them in the right order to make them work. You can actually ask them for help with -h or --help and not just have to figure it out by trial and error from the error you got back if you entered something wrong. At the same time using the parameters has become largely unneeded with the other major change which is they can now use the same information that the rest of Yapeal does from config/yapeal.ini.
So now you can just download/extract Yapeal some where, edit one file, and then run a few simple scripts to setup the database and tables and have it ready to take your API information.
As always your feedback is welcome both good and bad as can be seen from the above history it's important in determining what improves in Yapeal even if it sometimes seems to take forever Also bug reports are always welcome as well even if the bugs themselves aren't. You can report them here or preferably as an issue on Google Code web site.
Fly safe and continue to camp those stations I'll be inside
revision 1246 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
14
|
Posted - 2011.10.17 21:33:00 -
[23] - Quote
Ok lots of updates and refactoring done on Yapeal in the last couple of days. Most interesting changes in no particular order:
- Yapeal now looks for and will use two new environmental settings. YAPEAL_BASE and YAPEAL_INI. If they are set they will used in place of the normal defaults.
- All the unused scripts in install/ have been removed. They were used by the old dead GUI installer and saw no reason to have them around still.
- The remaining scripts in install/ have been refactored to be much more human friendly.
- The install/ scripts now will look for their settings from an ini file in addition to the command line and the new environmental settings. They default to using the config/yapeal.ini file so if you've already edited it you shouldn't need to add any parameters to the command line when running them or use the YAPEAL_INI setting.
- yapeal.php has had most of the same updates as the install/ scripts as well.
- All the stuff that use to done in inc/common_backend.php has been moved into the other classes or yapeal.php and no longer exists. There is still some more work to do on this but everything works and has been greatly improved.
- Added new 'status' column to utilAccessMask table. This will be used to track the working status of each API in Yapeal. So now you can see which ones are working fully or not etc.
- Added a couple of new methods to trunk/class/util/AccessMask.php that will return section API masks or per section lists of APIs. This should satisfy Enhancement request from issue 82.
- Update the ActiveAPIMasks in utilSection to match all APIs with a status of COMPLETE.
I know there been some other changes like updating INSTALL.txt to reflect changes to the scripts in install/ but I wanted to give some instructions on doing this update since it could cause a few issues without some prep work.
- Stop any crontab or scheduled tasks.
- Backup your config/yapeal.ini somewhere just in case and it doesn't hurt to do a database backup as well but the changes there are minor over all and only to the utilAccessMask table.
- If you are using SVN export or one of the archives you need to clear out everything in install/ directory. A simple rm install/* should do for Linux or CTRL-A, SHIFT-DEL in Windows Explorer while in the directory.
- Clear out inc/ once again by doing rm inc/* should do or CTRL-A, SHIFT-DEL in Windows.
- Do the same for class/*, pics/*
- Download archive / svn up etc to get the latest version and install.
- If you backed up configyapeal.ini you can restore it now but it shouldn't have been clobbered by anything from above.
- Follow the updated instructions from INSTALL.txt. You should be able to skip steps 4, 5, and 6 but if you have any problems go back over them as well to check stuff. Don't forget to do step 8 as there is a database update.
- I like to clear out the old log files in log/ and run ./yapeal.php once manually at this point but it's optional and you can just restart crontab or scheduled task if you like.
You should not notice any changes to how Yapeal works but if you do please let me know.
revision 1250 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
14
|
Posted - 2011.10.18 05:20:00 -
[24] - Quote
Try putting all your settings into the config/yapeal.ini file and not using any parameters on the command line. Just from looking at the above messages you ran the first command and it checked out 'yapeal' database but then you try to install to a different one in the second command of 'myyapealdb' database. You need to be testing and installing to the same one. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
14
|
Posted - 2011.10.18 14:40:00 -
[25] - Quote
Just a guess for some reason MySQL has problems doing the TRUNCATE followed by the INSERT on those two tables. It seems to do it at random but more likely when you have something that is accessing the database at the same time as it's trying to update it. I've seen it when I've forgot to turn off crontab during testing myself but had it happen other times when I wasn't sure what caused it. Remember you can always run the cache/ADOdb/util.sql that createMySQLTables.php makes yourself which I think is what you've done. Usually when you do that it'll let you know which line is giving you problems.
Quote:I enabled mysql logging but I didn't see any error in queries. I have the log if you want to see it Sure It's worth a look just to see if I notice anything that might help track down why it does it. Send it to the project owner of Yapeal on GoogleCode which is a GMail account and I'll take a look through it.
Sounds like you finally got it to work for you just make sure utilAccessMask table has new 'status' column with data in it and you should be good. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
16
|
Posted - 2011.10.24 08:31:00 -
[26] - Quote
So I've been playing around with Mercurial while trying to help out on some stuff in EMK and kind of liked it. I can see where it might better match my work flow on Yapeal. Just thought I'd get some feedback from everyone to see what they think about changing from Subversion to Mercurial instead? I've also looked at Git in the past but never really liked it and found it harder to work with so I was surprised when I found working Hg very easy. Anyway like to hear get some feedback about switching. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
18
|
Posted - 2011.10.27 04:57:00 -
[27] - Quote
@Sable Blitzmann - Make sure you backup your config/yapeal.ini and then clear the directory where you are installing Yapeal too. The most common cause of that error is ending up with multiple copies of a file in different places when they are moved around in Yapeal. I try not to do that very often because of the issues it can cause but had to do so in one of the recent versions. Also make sure you run the database update as well. You can find out more about what needs to be cleared in the CHANGELOG. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
18
|
Posted - 2011.10.27 16:30:00 -
[28] - Quote
Did you export from either your local working copy or directly from the SVN because it looks like it's finding the same API twice which the only other time I've seen that is when someone was trying to use their working copy directly without export.
Now that you have a working copy you can export from it to where you plan on
running Yapeal.
svn export --force /path/to/my/wc/ /directory/where/yapeal/should/be/installed/
Let me know if that doesn't clear it up. I'm testing some other changes right now that should help with this problem as well. Once I'm sure there aren't any problems with the changes I'm looking at I'll let everyone know and have to update some of the docs to reflect the changes. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
18
|
Posted - 2011.10.27 22:30:00 -
[29] - Quote
It can use either or both keys but basically what happens is which key it selects to use first will get everything it can within time / mask limits and then when it gets to the other key if any of this APIs isn't done yet they will be handled. Read the comments in yapeal-example.ini for how registered_mode works in most cases you don't need to even use the utilRegisteredCharacter or corporation tables. There's also a few more notes in the class/SectionChar.php and class/SectionCorp.php file about how things work.
To better understand how to add/remove/etc chars and corps look through the wiki and the classes in class/util/ that should help make using the util* tables easier. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
18
|
Posted - 2011.10.28 22:28:00 -
[30] - Quote
Hadn't heard of it but I'll take a look. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
|
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.30 18:06:00 -
[31] - Quote
Generally just copying everything should work but if your host gives you ssh access it's usually better to install it and then just copy over your config/yapeal.ini and anything you need from the util* tables. The advantage to doing it this way is updates to Yapeal should be easier to do since you can just follow instructions from INSTALL.txt and don't have an extra copy step to get from your local machine to the host machine and maybe miss something. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.30 18:42:00 -
[32] - Quote
If you are talking about /eve/CharacterID.xml.aspx and /eve/CharacterName.xml.aspx they are really outside of the scope of what Yapeal does and it's unlikely I'll add support for them except maybe in some kind of util script if I find and need for it or a few extra days with nothing else to do
If you mean /eve/CharacterInfo.xml.aspx it would have already been done except CCP was stupid and put an API that requires apiKeys and vCodes in the eve section instead of where it belonged in char or account. You can get all the same information from the other APIs anyway so I've never seen why anyone would find it that useful as it is. I've got some ideas for changes to Yapeal that MAY in some distance future be able to overcome CCP's stupidity on the placement of this API but let's just say being able to support this API is going to be purely an afterthought in any changes. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.30 18:47:00 -
[33] - Quote
Quote:Also, could someone with more experience with yapeal help me to understand walking the wallet journal and transactions? also, I'm guessing it's the same principal with getting mail message bodies??? Yapeal should do this for you by default but CCP has made some changes in the past that may have broke it and I don't have enough activity on my chars to do any testing Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.30 18:53:00 -
[34] - Quote
Quote:Could you not make it possible to add a character ID to the utilRegisteredCharacter and get yapeal to download a charCharacterSheet for them? Yapeal doesn't even look at that table without a key in utilRegisteredKey so no that won't work.
Quote:Also off topic, CorpCorporationContactList should populate without the need for a corp key, it is available to every member of a corp regardless and yapeal should accommodate to that. All of the corp APIs have been changed to require a key from a director or the CEO and there is no way around that.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.30 19:01:00 -
[35] - Quote
Public access to the corp APIs has been turned off you have to have a corp key now to access them there isn't a way to bypass.
Or to put it another way NO and it can't be done
Is that clear enough? Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.30 19:27:00 -
[36] - Quote
Not really since that ability is going away when old keys do from what I understand and once again by design Yapeal expects to have keys etc for anything in account, char, or corp sections in the requests plus the database expect the full data you only get from having the keys.
Yapeal is a made to be used when you have the required keys etc not for just general random access to the APIs if that's what you need there are several other libraries for that but of course it's up to you then to parser the XML and put it in the database yourself too
Instead of just trying to say indirectly that Yapeal is doing something wrong why don't you learn how to use it correctly first. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.30 19:42:00 -
[37] - Quote
Miko Kiun wrote:Dragonaire wrote:If you are talking about /eve/CharacterID.xml.aspx and /eve/CharacterName.xml.aspx they are really outside of the scope of what Yapeal does and it's unlikely I'll add support for them except maybe in some kind of util script if I find and need for it or a few extra days with nothing else to do If you mean /eve/CharacterInfo.xml.aspx it would have already been done except CCP was stupid and put an API that requires apiKeys and vCodes in the eve section instead of where it belonged in char or account. You can get all the same information from the other APIs anyway so I've never seen why anyone would find it that useful as it is. I've got some ideas for changes to Yapeal that MAY in some distance future be able to overcome CCP's stupidity on the placement of this API but let's just say being able to support this API is going to be purely an afterthought in any changes. I'm confused, characterinfo doesn't require keys. https://api.eveonline.com/eve/CharacterInfo.xml.aspx?characterID=90338329Is corp history accessed somewhere else? I can't find it anywhere in the yapeal tables To get the full information from that API you do need the keys etc. I believe you need a key with at least the low access level to get the corp history info but I could be wrong as I've not looked at it since they added that to it and the examples on eve-id aren't really clear on that point.
The main thing is Yapeal doesn't currently support having APIs with and without parameters in the same section of the API as it now works so any API that doesn't follow the 'normal' pattern for a section can't be added at this time. As I've said in some of my other posts I've had some ideas on how to make changes that might lift that limitation but it will require basically a total rewrite of much of Yapeal so it's not something that can happen overnight.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.30 19:52:00 -
[38] - Quote
Quote:Okay, so to help me out then, when adding / updating data to the db does yapeal overwrite data if it finds any? For example if i created my own to add the data to the database would yapeal, if it ever got a key for such corp, replace it? If you put something into an API table that Yapeal works with it will overwrite it with the newer data yes. Some tables it truncates or deletes rows from before adding the new ones and others it just updates any overlapping existing data. So for things like the corpSheet it'll overwrite but an API like assetList it clears out the old data first. The easiest way to know which it does currently is to see if the per API class has a method named prepareTables() and see what queries it might be running. If an API doesn't have that method it's just overwriting the data.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.30 23:33:00 -
[39] - Quote
Miko Kiun wrote:corp history doesn't require a key, that link I posted previously shows that. I noticed that you have a CharacterInfo placeholder file, so I guess I'll play around with making something work to get corp history and store it in a table... One great thing with open source software is there is always that option of course and if you do come up with something that can be integrated back into Yapeal I'll be happy to look at it.
Miko Kiun wrote:I don't think that the walletjournal/transaction history is walking backwards. I know I have significantly more transactions in my journal than what is getting store in the database. It may not be working right as I said but I've been busy working on many other things and not having a lot of test accounts to work with which have more than half a dozen rows a week at most it's not easy to work on either. I will let you know that just because you have a lot of history that you can see in-game doesn't mean it will all be available through the APIs. CCP limits you to only walking back for the last week or so worth of rows. They use to allow more but with the latest changes they seem to have cut it down farther than before. So to put it another way you can't walk back to see that first frigate you bought when you started play Eve three years ago. To do that you would have had to started collecting it at the time to have it now.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.31 01:29:00 -
[40] - Quote
HI all thought it was time I post a little update on what I've been working on in Yapeal over the last week or so. Some of you may have already noticed it if you been looking at the web sites especially the subversion. For starters it's no longer a subversion repository but now uses Mercurial instead. You might wonder why the change and all I can say is I've been looking around at some of the newer distributed version control software like Git, Mercurial, etc because everyone seems to think they are better plus they say they have features that might be useful. I really looked at moving to Git but for me how it was an improvement over what Subversion had to offer I could never figure out. I never really looked at Mercurial because I never saw where it was really different from Git and so didn't see any reason to go with something that isn't used by many people from my experience anyway .
That changed after Callean Drevus decided to release the source code for EMT. He happens to use Hg (Mercurial) for his project and since he uses Yapeal in it I wanted to take a look and see if there was anything I could learn from how he was using it and improve on Yapeal or that I could suggest to him some things about using it more effectively in his project. Originally I only figured I'd checkout his code and maybe sent him a few Eve-mails or E-mail and maybe chat with him a little about stuff but while looking at the version of Yapeal he was using I noticed it was a little behind the current version. Since it needed updating I decided this might be a good time to really try out Hg and work with it. So I setup an account on Bitbucket and forked his project to try stuff out. You can see the fork here if you're interested.
https://bitbucket.org/Dragonaire/eve-marketeer/overview
So now I had my own sandbox to work on but no real idea how to do so with Hg. I did what I always do and started looking around at Bitbucket, Googling more about Hg, and looking at the man pages for Hg. While I was doing so I came across an interesting site about Mercurial called: Hg Init: a Mercurial tutorial which has a section just for people like me coming from a Subversion background. I don't know if the author is brilliant or if all the other reading I had done on the differences finally just came together when I read what he wrote but I decided I liked Hg and could finally see where it might be be better then Subversion for Yapeal.
I won't bore you with any more of the background reasoning that lead to me deciding to switch Yapeal from Subversion to Mercurial but that what I did a few days ago.
Continued in next post. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
|
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.31 01:46:00 -
[41] - Quote
... Continued
So how does this effect you is what you really want to know right?
If you use the archives not much. You might notice that instead of having one or more folders on SourceForge where you can download versions of Yapeal there is only one called archives/ with multiple versions in it. You may notice that the numbering system used for the versions has changed. With Subversion I had a nice simple number that increased every time I committed something to the repository but with a distributed version control system like Hg I don't have that anymore.
Old school three part numbering (1.0.2) doesn't really work well either or at least are very hard to manage automatically so I decided to go with a system based on the date and time I build the archives but make it looks more like the old school three part numbering system. Does it really matter to anyone? Not really the only time it'll probably be used is when I ask you what version you are using when reporting a issue or when you are wondering if you need to update your version. The only ones you'll probably ever really care about are the ones that have '-latest' in their names as they are of course the latest version you'll be wanting to upgrade to as features are added and bugs fixed. If you always make sure you are regularly updating to the latest version it doesn't really matter what the version number is.
If you use the repository to get Yapeal you'll have to use Mercurial or a GUI that understands it but if you only care about what use to appear in trunk/ before it'll be in default/tip which is what Hg defaults to when you clone it.
If you are like me and need to see everything because I am often working on several things like bug fixes and new features in branches they are still there for now but there are better ways to do things like that in Hg and you'll notice many of the current branches will disappear over time as I start taking advantage of them. A couple of them have already like admin/ and wiki/. Admin was where I kept stuff that was only used during development for things like making the archives etc. I've now done what I should have done before and moved them into a separate repository which is private at least for now since there really isn't anyone else doing releases or needing any of the other stuff that was found there. If / When needed I can make it public or give others access to it as well but there is no need to confuse everyone by having it there. The wiki move is because GoogleCode uses a separate Hg repository for it now. With Subversion it was part of the main one but now is on its own. I also decided to do a little cleanup and have moved pics/ out of the repos while I was at it and have them just as a download on SF instead. That last change with pics/ should make the download smaller but still make them available to anyone that needs them.
There are probably several other changes you might notice but they shouldn't really matter to anyone besides me. If you do notice something you used and can't find it now let me know and I'll tell you where it went to. I've got a full archive of everything in the old Subversion plus you'll find most everything in the Hg history since I did a full import of the tags, branches, and trunk to it.
One last thing that everyone will probably notice when they go to install or upgrade Yapeal is the README and INSTALL.txt now are named README.md and INSTALL.md. They are still basically plain text files but can be converted directly to HTML pages for display with the right software. They have been updated with the new instructions needed for working with the changes to Mercurial and the archives while I was at it
If you have any questions I'll help where I can. If you just have comments they are welcome as well.
version 11.303.0923 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.10.31 02:09:00 -
[42] - Quote
Quote:thanks for getting back to me so quickly. I have to say using it locally it is absolutely fantastic and taken my little project from being an absolute nightmare to something quite manageable (so far ). I would like to ask when copying the files to my host (as I think SSH access is a problem) which files / folders should I not copy i'm obviously thinking the install folder but are their any others that I should miss? You only need to copy the directory structure of cache/ and the *.xsd file but not the *.xml or *.sql files. install/ is optional but if you are having problems getting it to work you might need some of the scripts from it. They won't run with CGI by default but might still be modifiable to work with it should you need them. You don't need any log files in log/ either just the folder and the .htaccess file. Most directories have a .htaccess file in them so if you do happen to copy something you wish you hadn't no one should have access to them. I do still highly suggest you don't put it anywhere the web server can see it but with care it should be minimally secure to do so. Everything else you'll be needing.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.01 06:03:00 -
[43] - Quote
Quote:Warning: getopt(): No support for long options in this build in yapeal/inc/parseCommandLineOptions.php on line 82 Seems even in Linux support for long options was uncommon before 5.3 in PHP so I'll be looking at changing it so it only tries to use them with newer versions I guess on all platforms
Quote:everything seems to have updated in the sql database apart from the charindustryjobs (which is unfortunatly the main thing I am after If the other char APIs seem to be working and not the one you want make sure you didn't somehow turn it off in one of the masks.
Quote:Is the jabber room still used? I may not have set things up correctly, I'm being asked what settings I want to use to create the room, and I'm the only one there... Looks like the server died I've sent an E-mail to the owner to see if he can give it a poke. You can always try private IM on Gmail as well. Just try dragonrun1 there and you'll get me. Keep in mind I'm West Coast US and work an afternoon/evening shift that can make it hard to catch me for some people
Quote:WARNING: Could not prepare eveAllianceList API tables to accept new data for 0 No idea how you're getting that error. Yapeal doesn't use prepare SQL statements anywhere so only thing I can think of is you were trying to use them somewhere in your new code maybe?
Quote:EXCEPTION: Failed to get ADOFieldObjects for columns in YapealQueryBuilder Code: 4 I'm guessing you aren't passing the table name to the constructor for YapealQueryBuilder as the first parameter or maybe you're not passing in the correct DSN for connect in $dsn?
Do you have a preference on how you would like me to deliver this to you for your perusal???
If you can do it as pull request with Hg that would be great but I'm not sure I have that setup right yet else a unified diff would work sent to me via E-mail. The one other way would be just a copy all the files you've changed in an archive using zip or tar.gz etc. That last option might be the easiest overall and you can use the same E-mail account from above as well. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.01 22:04:00 -
[44] - Quote
Ah yeah there are a few there that are very large was something on the old thread about the packet size issue. Looks like you get it sorted out but the other way to fix it for anyone that can't make changes to their config file for MySQL is to lower the default number of records Yapeal tries to store at a time by changing YapealQueryBuilder::MAX_UPSERT from 1000 to something lower until you stop having problems. You want to keep it as high as possible to have less inserts so they are faster but small enough not to cause errors. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.02 04:34:00 -
[45] - Quote
Are there ways to get Yapeal to violate the cachedUntil time? Yes, simple delete the cachedUntil time from utilCachedUntil table and Yapeal will at least try to refresh the data from the cache. If you also clear the XML from the file and/or database cache it will even try to get it from the API server again and depending on the API you either get an API error with a new cachedUntil time that will be even farther into the future than if you had left it alone or the same data you already had once again with a new cachedUntil time that will also be farther into the future than if you'd left it alone.
Does it make sense to do either of these things? Not really.
Now if you are just wanting to have Yapeal grab the data for say a new char when they are signing up for an account you can add the key info to Yapeal and directly call it and it will get the data but it will do it along with trying to get anything else with an expired cachedUntil time. It shouldn't even cause any problems with your regular crontab job as Yapeal does use a very simple form of API locking so multiple copies don't try to both work on the same thing at the same time but since the order they will try to get the APIs is random there's no way to predict which of them actually ends up doing the work. I am looking at adding the ability in the future to be able to call APIs directly outside of the normal crontab way Yapeal does things but there are some other things that need to change before that is possible.
The best way to make sure everything is as up to date as possible is to add the accounts to it and run the crontab every minute. I've had several developer trying to run it less frequently and than complain it's overloading their systems. By design Yapeal tries to do as much work as it can every time it runs so the less often it is ran the more it has to do each time but if you let it work as often as possible it actually works to spread out globs of API calls by delaying some of them a couple minutes so only a few cachedUntil times expire each minute. None of them will be delayed more than 5 minutes because of hard limiting plus its heavily weighted to do them on time so the upper limit is rarely seen.
Hopefully that answered you question(s) and let's you understand how things work a little better. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.02 07:26:00 -
[46] - Quote
Wiki is outdated. What use to be in common_backend.php is now either moved to the classes the code should have been in or was moved to yapeal.php. Read through the CHANGELOG to see why etc. Lines 78, 79 are the ones for the autoloader in Yapeal.php but you'll want to look at some of the code before them to setup some of the environment you'll need. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.02 21:41:00 -
[47] - Quote
Yeah it has to read the config file or stuff doesn't work Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.03 14:14:00 -
[48] - Quote
@Norian Lonark - You could do what you are talking about but you would have to 'fix' the tables every time you updated Yapeal and it's database. The normal way to do what you want would be to add another table with the primary key from Yapeal's table as foreign key to your table with the other columns you need so they are linked. So for IndustryJobs you would have ownerID and jobID as the foreign key or even as you're primary key depending on what else you are adding then use a simple join in your queries. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.04 04:44:00 -
[49] - Quote
New version 11.307.2138 out. Made some changes to allow Yapeal to better work within MySQL server's max_packet_size limit. If you continue to have problems with 'Packet to big' try turning off xml caching in Yapeal. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.04 16:30:00 -
[50] - Quote
New version 11.308.0915 Since I don't have enough data to test some changes I'm trying with walking in the Wallet* API I'm pushing it out for anyone else to try. If you've been having problems with walking working give it a try and let me know if it's better. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
|
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.05 03:49:00 -
[51] - Quote
I understand it seems like a bit more work now but it has actually made it more useful because if you don't need some of the parts now you just don't call the function/methods or if you want to override something there's something with a name on it that helps you find what you need. In time it will be simplified once again but Yapeal needed to go through a transition here to get from the procedural code that was used a lot in this area to something more OOP. It has also let me reuse a lot of the same code for the scripts in install/ used to config Yapeal during installation too. Just think you only have to put your settings into config/yapeal.ini once and then can do all the setup and day to day run of it without reentering any of it again Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.07 04:15:00 -
[52] - Quote
Hi all got some more changes for everyone to try out this time I've overhauled all of the error and exception handling code. We can thank (blame ) Zaepho for the idea. Back in post 64 he talking about using log4php and I decided to check it out and liked what I saw. Then the fun part started, converting Yapeal to using it. As anyone that's done it knows making changes to your error and exception handling is often difficult since when things go wrong it's hard to figure it out since often you get nothing to look at. The changes actually ended up going smoother than I thought they might except for some problems during the final merging. I've done some testing but since Yapeal generally runs nearly error free for me I did most of the testing by introducing temp fake errors so there still might be a few problems hiding in the changes. It would probably be a good idea to do some testing of your own before going live but it should work without problems.
Log4php has a lot of options for where, how, and what is logged. Yapeal uses only a few of the addition features available but it does mean there have been more than a few changes to what you'll see so here a quick list of some things you may notice.
- Instead of just yapeal_error.log, and yapeal_warning.logs in log/ you will also find yapeal_info.log (replaces yapeal_notice.log), yapeal_debug.log, yapeal_fatal.log, and yapeal_trace.log. Not all of them are used yet in Yapeal but probably will be in the future.
- The logs are limited to 100KB in size and will keep one addition old log backup for each of them. As anyone that has seen Yapeal when the API server is having problems knows the logs can fill up fast so this should at least keep them from growing totally out of control. The days of 1.5GB log files per day are over
- Log entries format has some changes do to update. I tried to keep them as much like before but some things ended up having to be in a different order which shouldn't really matter.
- Several of the settings in the [Logging] section of config/yapeal.ini have been dropped and a couple others (log_level, log_locale) are now unused and reserved in case they are needed in the future.
- A new setting has been added to config/yapeal.ini called log_config. It can be used to point to a custom configuration file if needed just make sure you obey warnings found in config/logger.xml.
- There is also a new command line option -l, --log-config that can be use with yapeal.php.
- Yapeal will also use the environment variable YAPEAL_LOGGER which can be used to set the configuration file location. The priorities are from high to low the command line, yapeal's ini file, YAPEAL_LOGGER, and finally hardwired default that is set to config/logger.xml.
There are many other changes but those are the most visible ones.
Expect some additional changes and tweaks as Yapeal is adjusted to take advantage of having additional logging levels to work with. Suggestions are welcome as always.
version 11.310.1908 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.08 04:52:00 -
[53] - Quote
Yeah when I put out the changes for logging it reverted the changes for the Wallets I'll have that fixed tonight. I've got to remember to pull, merge, push not the other way around Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.08 16:29:00 -
[54] - Quote
What it should be doing is get one group with walking forward (no fromID) then use the oldest record from that one to walk back as far as it can which should be a month if CCP hasn't got that bugged. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.08 17:04:00 -
[55] - Quote
Limit is from CCP. They only allow the last month. Only way to have complete history since you started playing would be you started collecting it since then Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.10 17:48:00 -
[56] - Quote
So development and response times on bug reports maybe a little slower for the next week or two as I'm planning on spending most of my free time playing The Elder Scrolls V:Skyrim I've already get it preloaded and I'm just waiting for them to let me actually start playing tonight after work. I will try to check every day like usual before heading to work but I might forget too Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.20 23:37:00 -
[57] - Quote
The only APIs where there is a direct link from the key to ownerID is in account section. The eve, map, and server sections don't really have an owner so they default to 0. Char section APIs use the characterID and corp section uses the corporationID but since Yapeal can work with multiple keys for each there's really no direct link to the key used. To put it another way Yapeal doesn't care if there are one or multiple keys active for the same character or corporation and will use them in a random order when trying to retrieve the XML data from the API servers so there really isn't a way to say which key will be used.
If you enforce only one key of a type on a per character/corporation basis in your application you can then try to do a one to one mapping but watch out for account type keys as you actually have a one to many relationship with them.
Hope that helps you. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.21 10:32:00 -
[58] - Quote
Or maybe learn to use the accountApiKeyInfo, accountCharacters, and accountKeyBridge which really does the linking you were asking about there just isn't a real one to one link except as I said you enforce one in your application. You can do that with a few SQL queries on the exist info from the above tables. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.21 22:58:00 -
[59] - Quote
you can always truncate the tables and as long as you don't have that API active it won't refill. Yapeal actually does that on a few of the tables in eve, map etc so it can use inserts instead of upsert which is slower. If it's a table in account, char, or corp sections then you'll need to use the correct ownerID to do so. Here again at times Yapeal uses delete with ownerID to clear stuff out before inserting the new data with an example being assetList where upserts don't really work.
Now if the question is there something in Yapeal to help you do this? the answer is no it just does this things as need during it's own work updating APIs. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
19
|
Posted - 2011.11.21 23:00:00 -
[60] - Quote
@Bado Roul look in the config/yapeal.ini file for the cache settings you probably need to change. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
|
Dragonaire
Corax. PURgE Alliance
20
|
Posted - 2011.11.22 05:01:00 -
[61] - Quote
I haven't had a chance to really add any extra debug stuff to Yapeal since the change to new error logging code but you can try trace but it'll probably not have much interesting either but at least you'll know what all code it does run . Have you run install/checkForRequirements.php yet it might spot something that should help like the cache directory not being writable etc. Clear up any errors it might find and see if that helps. If doing those things doesn't seem to fix it let me know and I'll see what else I can come up with that might give us a clue to why it's not caching anything. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
20
|
Posted - 2011.11.22 18:12:00 -
[62] - Quote
I'll make a bet if you looked at what is using mast of your CPU it will turn out to be MySQL trying to put everything into the tables. Also it really is better to run Yapeal every minute as then it doesn't get behind and have to run for extended periods to catch up all the time. It has some built-in code to try evening out globs of APIs needing retrieved all at the same time that can't do it's job if ran infrequently. Everyone is always shooting themselves in the foot trying to out think me and Yapeal on that
It will be very busy for a while when you first start it as it does have to try getting all of the APIs for everything you have asked it to do but once that initial fill is done it should within a couple days only have an occasional spike when a couple of the larger APIs happen to need to be done at the same time.
Yapeal itself spends 99% of it's time waiting on either the API servers to give it the data it needs from the network or waiting on MySQL to finish storing the data in the database the code itself usually only takes a second or two at most to run and typically only is doing something for 1/4 of a second or less of the time it take to do an API. Disk I/O has been the most common limitation on how many keys it can handle on most shared hosts as they are usually setup for lots of reads but few writes to the file system but Yapeal spends 90% of it's time writing directly for cache or indirectly through database table inserts in MySQL.
Hopefully that helps you understand what's going on. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.11.25 18:15:00 -
[63] - Quote
As always make sure you are using the latest version and insure your config/yapeal.ini is up to date with any changes.
Try running it manually from command line might give you a few more clues also check that log files haven't filled up your disk space if you're using an older version before new logging system was added.
If all of that is good check that MySQL hasn't ran itself out of disk space with logs etc as I've seen some mis-configured ones if they use the defaults where they never clear out old logs etc when using ADDOdb instead of MyISAM like Yapeal does.
If after doing all of the above you still have problems try stopping any crontab/Scheduled Task of Yapeal and clearing out the API file and disk caches and the utilCachedUntil table then run Yapeal manually again and make sure the table refills right.
One last thing to check is if your API keys have expired.
If after all of the above it's still not work contact me via the project owner on Google Code at GMail. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.11.30 16:06:00 -
[64] - Quote
I would have been surprised if you didn't have lots of addRow() in trace consider it's called to store every single row (record) into the database that Yapeal does. Let me give an example with a very simple API like server/ServerStatus.
Once Yapeal decides the API needs to be updated it updates utilCachedUntil with new date-time with a short timeout in case something goes wrong on this update it can re-try in about 5 minutes. (BTW for this API that's it's normal cache time but on most APIs this is shorter than normal) It then tries to get the API data from the server. If it gets the data and you have database caching turned on it writes the XML to the utilXmlCache table and then does an upsert to the serverServerStatus table. Yapeal then figures out the new cachedUntil time it's going to use from XML (No it doesn't always use the one from XML directly because often the APIs lie about the true cache time and I got tired of all the errors) It then updates utilCachedUntil with the new date-time. So for just a single record API there are 3-4 writes to the database. 2-3 of those are overhead that don't change with the number of records that need to be updated.
Now let's think about an API like AssetList where there can be 1000s of rows of data for each of them addRow() is called. That's per char/corp as well so with just a dozen or so chars/corps you can easily end up with 10000 calls to it or more. The best way to get a good idea how many times it will be called look at how many rows (records) of data are in the all the API data tables plus the XML cache if you are using it and utilCachedUntil.
Now just to make something clear Yapeal doesn't actual store the data into the database on each call to addRow() it actually saves up the data and wraps up to 2000 of them by default into a single extended insert or upsert inside a database transaction to make them faster.
In all of the above I've ignored the selects that are needed on the database as well for Yapeal to do it's job. There are about six or so per API and do to the nature of them most can't be cached but for the ones that can Yapeal does some internal caching.
Let's now compare the number of writes Yapeal does to the database compared to say a blogging or forum site.
Let's say there are 10000 active people on the site and they are all quick readers and fast typists. They each take 5 seconds to read a post and 5 seconds to add their own and they are doing it constantly (Typical EVE General Discussion poster ). Lets guess each post causes three rows (records) in different tables to be written for each of them and it has to read from two tables to display one. So we have 10000 / 10 * 3 = 3000 rows being written each second and 10000 / 10 * 2 = 2000 reads. Now Yapeal can do that many writes on a single API for a single char/corp but a lot less reads. Most hosting site are setup at best to handle those type of loads and actually most of them are figuring on closer to 100 reads per write to the database since that's much more typical.
Given the above is it any wonder that when you start trying to add a few hundred or thousand users to Yapeal it's usually the database directly or indirectly via file I/O that can't keep up on most shared hosts or even a VPS? The above numbers are ignoring any overhead your applications might be adding which probably make up for some of the reads. The above numbers aren't going to be unique to Yapeal either but generally true for anything that tries to keep the all the API data in a database.
Anyway I hope that gives everyone a better idea of what you are truly asking of your poor server when working with the APIs Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.01 05:32:00 -
[65] - Quote
First I don't want you to think I was saying there was anything wrong with your VPS I actual think Linode is a great service. I mostly did the post to give everyone some data to work with to understand the differences in the load that API applications in general and Yapeal in particular have so they have something to work with when trying to scale up with them and might have had some baring on your problems since I didn't know how many chars or corps you were trying to run it with.
You are right 1001 inserts on corpWalletJournal doesn't look right at all. I would say somehow the exit conditions aren't right and my fail safe is kicking in at the 1000-1001 mark and keeping it from becoming an infinite loop It's interesting to me that only the Journal was effected as transactions use the same code with only minor diffs but I'll look into it now that I've got a better idea what's happening so thanks for the extra logging it really helps. I'm also wondering if you are seeing the same thing happen with the same 2 APIs in the char section by chance? Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.01 16:15:00 -
[66] - Quote
Ok I'll push out new version with fix then and we'll see how it goes. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.06 23:49:00 -
[67] - Quote
There where some docs about converting around the time Yapeal changed over which you'll on the old thread in the archives and some stuff in the CHANGELOG as well but the basic process is to backup everything up and drop all the tables outside of char* and corp* ones then do upgrade and the missing tables will be recreated. Or you can just make a new database following the install instructions then copy over the data from char and corp tables from the old database. There are enough changes to the account tables to cause problems and they'll refill automatically anyway you don't want to keep them.
If you need any more help let me know. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.07 04:58:00 -
[68] - Quote
That's because Windows doesn't think files ending in .php can be ran. Try it from command line and pass it to PHP by trying this:
php -f .\checkForRequirements.php
It should work right if you're PHP is setup correctly with that. Make sure you are following the instructions in INSTALL.md Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.07 06:24:00 -
[69] - Quote
Sounds like it's not finding you PHP either so yes you will need to have PHP installed to use it. Guess I thought it was pretty plain that a working local copy of PHP is a requirement for anything to work if you are going to try using it on your local computer
Edit : I'm really sorry if this comes across badly but what you are basically asking is "Do I really have to install the software needed to run your script?"
It was very hard not to answer that with something like this "No of course not you should instill Perl and Python and use them to write your own interpreter which converts it into Java code and run it that way"
Hopefully you understand I'm not really trying to be mean or anything but I just really never expect anyone to ask that question. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.07 14:55:00 -
[70] - Quote
Ok np I'd never heard of a portable version of xampp either but I'm glad to hear was mostly the question not being clear to me then you were really asking if PHP was needed. I don't know why but xampp never seems to work as well with Yapeal where as the BitNami WAMPStack always does. You can get it from http://bitnami.org/stack/wampstack. When I test Yapeal on Windows that's what I use and it always just seems to work Once in a while I do do some tweaks to a couple settings in the my.cnf file or in php.ini but it should really run without them they just seem to make a few things run smoother for my needs in testing. They are the same tweaks I usually make to the same settings in Linux so they aren't anything really special to make it work.
Anyway if you can finally get PHP working for you let me know if you have any more problems. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
|
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.08 05:39:00 -
[71] - Quote
I'm not aware of any changes to them but it wouldn't be the first time CCP made changes without telling us about them or I missed it. I didn't see it in the patch notes anyway I do think there was some changes to killlog but I haven't had any kills to look at yet to make the updates for them but I'll take a look at it this weekend and get it updated. Been busy with other things the last couple of weeks. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.09 04:26:00 -
[72] - Quote
sure I might spot the change with some addition examples faster Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.10 09:15:00 -
[73] - Quote
Ok should have fix for KillLog errors try out version 11.344.0112 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.11 01:30:00 -
[74] - Quote
So thanks to Satis Iqulenax for letting me have access to a couple new keys to do more testing then I've been able to lately and some stepping through code in WalletJournals etc I've fixed the last walking issues in journals and transactions now I think
I also finished the fix to killLog for singleton now it seems so give it a try.
Version 11.344.1722 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.14 05:32:00 -
[75] - Quote
Make sure the char section in utilSections has isActive=1 It sound like you did the rest right though you didn't say what your activeAPIMask value was but if it's NULL the one from sections will control it.
As to the wiki yes it is outdated on a lot of stuff but the UsingClassUtilClasses and UtilDatabaseTableDependences are still useful for understanding the things you're having trouble with and have been updated to the current way things work since I last wrote about them being outdated. If you have any other questions just ask I'm much better answering questions here than I ever have been trying to write about how to use stuff for new people in general Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.14 06:04:00 -
[76] - Quote
Most of them it should be able to handle on it's own if you stay within a couple versions of current version on the few times when I have to break it and you need to handle it manually I make sure to put something in the CHANGELOG plus say something about it here in the thread also with instructions on what to do or look out for. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.14 17:34:00 -
[77] - Quote
charContactList error about inWatchList sounds like CCP made a change to make it optional without telling anyone or its a new bug in their code with the same effect There is nothing in the blog when the API was added that says it can be optional and it really doesn't make sense for it to be so that needs to be followed up on with CCP. The blog that talks about the new API is here: http://www.eveonline.com/devblog.asp?a=blog&bid=757 I'll follow up with them on it but I'd like it if you'd also do a bug report on it so they get an example of the XML file that has the error.
The error about duplicate entry can only happen if somehow in your in game contact list you have the same character/corporation listed twice some how. If it isn't show something twice then there is a bug either in the API or the CCP database. I've had another report about duplicate entries in a different API which I know is a bug in their database so this could be the same thing happening here too. I'd follow up with CCP with a bug report on this too and let me know what they say as on the last one they initially responded they couldn't test it and the player would have to check it He followed up with them saying they had to fix it with some more info but as far as I know he has not heard back from them yet
Edit I've bug reported the inWatchList problem in bug ID 122907. If you could refer to it in you report it would be helpful. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.15 09:02:00 -
[78] - Quote
Szelene - Might actually get an ask if you did your own thread instead of using one that is about something else.
Spike Keikira - Give it a day the day after patches often the APIs do some strange things but if KillLogs still isn't working sometime after DT let me know and I'll look into it some more.
Controller Vrelk - That's one issue between Windows and Linux that Windows doesn't always track the case correctly The easiest way to fix it is to do a MySQL dump on the Windows machine and edit the table names before using it on the Linux one Yes it sucks trying to edit all 80+ table names. If you don't really need to transfer your data its much easier to just create the tables on Linux. Also there is a setting in MySQL's settings to have if use upper and lowercase on any platform it's just that they (MySQL) decided to default it differently on the two platforms even though Windows does normally keep the case just ignores it in most cases. You might try changing that settings so you have less issues in the future.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
21
|
Posted - 2011.12.15 17:21:00 -
[79] - Quote
Szelene - Since it's a thread about an EVE API library and your question isn't in even the right forum since it's not about it or even third party development then your chance are about zero here. You might try doing an actual search with something you heard about called Google or there's even s few search engine just for the Eve forums that work very well and it's just a guess but I'm sure someone else has asked your question before and you can find it if you look without even having to post. You'd probably even have a better chance having your question answered in one of the general threads then going out of your way to find one that has nothing to do with the Eve client but the API instead which is on the Eve website. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
23
|
Posted - 2011.12.17 17:29:00 -
[80] - Quote
Spike Keikira - First make sure you have the latest version of Yapeal since there have been a lot of changes to it lately. Next make sure you also ran install/createMySQLTables.php to update your DB. Next check that the chars/corps that are having problem haven't had their KillLog APIs deactivated. Finally if you are sure all of that is good clear the cache by deleting the KillLog xml files in cache/{char,corp}/ and the DB cache in utilXmlCache also in that order with any crontab/scheduled task stopped. Then try running Yapeal manually from the command line and see if you notice any more details in some error message that might help figure out what the problem is. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
|
Dragonaire
Corax. PURgE Alliance
23
|
Posted - 2011.12.17 20:11:00 -
[81] - Quote
If it won't cache to the database you should look at the cache/ADOdb/util.sql file and maybe try it manually to figure out what is wrong with your utilXmlCache table but glad you're making progress
There was someone working on the contract APIs but he has took a break from Eve it seems so someone is going to have to pick it up and finish it If someone is interested in finishing it let me know else it might be a little while before I have a chance to look into it. I believe there was some technical snag he was running into at the time because of something CCP had or hadn't done but I think they have ironed it out now. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
23
|
Posted - 2011.12.17 23:02:00 -
[82] - Quote
Ok I've been trying to catchup on a couple API changes that have been made over the last week or so and finally got the one for char/ContactList done. There have also been another change to KillLog plus some other improvements. Everyone really needs to update their database with install/createMySQLTable.php like it says to do in INSTALL.md when updating Yapeal it will save you a lot problems. It doesn't hurt to run it on every update since if there's no changes needed it doesn't really end up doing anything to the database.
In other news it looks like the issues with walking APIs not working have been fixed and a major source of slow down in Yapeal has also been killed in the process. Once again everyone should really update as it'll fix a major CPU usage spike that Yapeal had developed
version 11.351.1448 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
23
|
Posted - 2011.12.18 04:56:00 -
[83] - Quote
Quote:I'm running it from the command line, but it kept complaining about not being able to find the database password, which is logical, as there isn't any. So how does it work later while running it since Yapeal requires one then as well but it can be blank. You do know it can pull all the settings from your config/yapeal.ini file right without having to use the command parameters? Maybe you've missed it in this thread or in the CHANGELOG but the scripts in install and yapeal.php itself have had a overhaul that added some better command help etc. Might try createMySQLTables.php --help to see what is new.
Quote:It also seems to be trying to connect over a unix socket, which is never going to work, but I guess this has more to do with php than with yapeal, as it worked later. Yeah sounds like you were having some kind of database connection error there that cleared itself up. You might make sure the settings in my.cnf are right.
Quote:What sections is the script updating at the moment? It doesn't do that but in the help message it tells you the default order which is util, account, char, corp, eve, map, server. So it's in alphabetical order except for util because each of the other sections update tables in it so they have to exist first. You can also tell it to run just one or a couple by adding the optional --xml=util ... parameter.
Quote:What queries is it going to execute? It saves the queries it was trying to run into cache/ADOdb/*.sql one per section.
Quote:What is the result of the queries, and the result per section? The part of ADOdb used to run them doesn't really let you know just if it worked or not.
Edit: Also be nice to see you in chat again the evephp is gone until I find a new place to host it but I'm still around so convo me. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
23
|
Posted - 2011.12.18 07:37:00 -
[84] - Quote
Thanks to some work by Satis Iqulenax over the last week or so she has added the faction APIs to Yapeal the only problem is since neither she nor I have any character/corporations doing faction warfare we have no real way to test all of them So we're looking for some testers that are involved in faction warfare to do some testing for us on a test build and give some feedback. They should be all working as most of the code came from other know working code in Yapeal but typos happen If you are interested in helping out either Eve-Mail me or let me know in the thread here so we can get in contact with you and give instructions about the where and how to get the code that needs to be tested. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
23
|
Posted - 2011.12.18 17:29:00 -
[85] - Quote
you might try looking for the GSC first and use lvl or flag to find only the ones you want. Another idea is if you only want the GSCs that have items in them filter on rgt > lft+1. The remember part is easy just use a foreach loop it'll walk through the items returned in your outer queries. I think in part the mistake you are making is trying to think about how to do stuff only in SQL or only in PHP instead of use each of them where they make the most sense. Also to make your queries cleaner and faster try using between in SQL.
http://dev.mysql.com/doc/refman/5.1/en/comparison-operators.html#operator_between
So Quote:select * from charAssetList where lft>204 and rgt<315 where ownerID={MycharID}; -- Query #2 becomes select * from charAssetList where (lft between 205 and 314) and ownerID={MycharID};
You have to learn to think in a bit different way about how to get to what you want. Often times turning the problem and queries around will show you a better way. Always start by asking yourself what you want to get and see if there isn't a direct query that gets the items you're interested in then figure out where it happens to be. Hopefully that'll help you in using it more effectively. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
25
|
Posted - 2011.12.23 17:19:00 -
[86] - Quote
Yeah someone else was having problems with the log file paths as well a while back but it's easy enough to simply update config/logger.xml. When I get a chance I'm planning on looking into ways Yapeal can set it to use the same common paths that Yapeal uses but since it's an outside library now being use instead of code from Yapeal itself it's a bit more complicated Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
26
|
Posted - 2012.01.02 02:29:00 -
[87] - Quote
Hi everyone and Happy New Year So I've been working on a couple things in Yapeal and decided I should push them out to everyone.
First Ruziel reported a bug in Contracts API with how Yapeal handled ones that hadn't been accepted or completed yet. The API sends empty string value for 'dateAccepted' and 'dateCompleted' so it needs to be changed to a NULL for the insert/upsert. This seems to now be fixed now.
I've also been trying a new development tool PhpStorm that another developer told me about and I've been trying out some of it's features. Your can get it from http://www.jetbrains.com/phpstorm/ One of the things I've been trying out was a complete inspection of Yapeal with it's inspect code feature. I told different developer about it and he said he'd be scared what it would report if he used it on his own code I'll have to say when you get back a report with 8000+ things it found it wasn't much fun but after looking at it some I realized most of them were 'spelling' errors including name of variables etc. There were some actual spelling errors too in some of the comments and I fixed them but the other problems it found were a bit more interesting.
Most of the rest of the problems it found turned out to be in the other libraries I use like log4php, eac_httprequest, and ADOdb in ext/. I already know there were problems with ADOdb since every time I really take a look at it's code I shutter and get this overwhelming urge to either try fixing it or go hide somewhere because of all the problems that exist. It works very well and doesn't have any real 'bugs' as such but you can tell many people have handled it and it still has a lot of legacy code from the PHP4 days that it just hasn't been able to shake off yet. So the first thing was to exclude ext/ and a couple other things that are outside of Yapeal itself that I just use in development. So next I figured out how to filter out stuff I wasn't interested in for now like everything in ext/. So after filtering I only had a little over 2000 with 1800+ being spelling stuff which can largely be ignored but it still does look great yet for Yapeal. Some of the rest were pointing out the limits of the inspection feature itself in understanding dynamically building SQL and understanding how I'm using the magic functions like __get() and __set() in a couple places which isn't surprising since I've had to explain it to more than a few people that had never seen them used before in PHP
In the end after the manual filtering I did find several minor problems that needed fixing like not initializing some variables correctly, and some unused properties in some classes which were easy to fix. I also found a few places where I could simplify some if/else statements at the end of methods etc. There are some additional things I'll be looking into changing as well but they more about doing things in simpler ways or breaking up some of the more complex tasks which is something that is always an ongoing process in Yapeal anyway for me
Over all Yapeal was fairly clean which made me very happy
So you can get the new fully inspected version from the Mercurial or archives.
version 12.001.1845 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
26
|
Posted - 2012.01.03 06:35:00 -
[88] - Quote
Yeah it looks like I broke something trying to fix something else I'll try to get fix out in the morning after I've had some sleep and figure out how it broke and how to fix what I was trying to fix Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
26
|
Posted - 2012.01.03 17:46:00 -
[89] - Quote
Ok I pushed out a update that has remove the rest of the old legacy logging system that used observers so you shouldn't get that error anymore, just some new ones maybe Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
26
|
Posted - 2012.01.04 17:37:00 -
[90] - Quote
I'm sorry to say the person that was working on Contracts ran into some technical problems with ContractItems and ContractBids and then kind of drop out of Eve for a while and didn't finish them I've been busy with some other projects as well so I haven't looked into it to see what it would take to work around the issues he ran into yet. I think the main thing was CCP deciding to use a single mask for all three APIs and how Yapeal decides which APIs are do to be retrieved etc. I'll try to get to it when I have a couple other things out of the way. If you could add it as an issue so it reminds me that would be great as I have forgot it a couple times over the last few months with everything else I'm working on. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
|
Dragonaire
Corax. PURgE Alliance
26
|
Posted - 2012.01.04 18:36:00 -
[91] - Quote
I'll try to do that at least in the next few days for you. and maybe get XSDs made. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
26
|
Posted - 2012.01.04 23:32:00 -
[92] - Quote
You can also just do the last two tables in Drapko Nitzhonot's example as the Yapeal default is 'optional' for the data in the utilRegisteredCorporation table. Also you might want to look at a couple wiki pages that should help you better understand how to use it and how it works. http://code.google.com/p/yapeal/wiki/UsingClassUtilClasses and http://code.google.com/p/yapeal/wiki/UtilDatabaseTableDependences Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal forum thread |
Dragonaire
Corax. PURgE Alliance
27
|
Posted - 2012.01.09 17:18:00 -
[93] - Quote
Sorry for the late reply I missed your post just before mine.
Halonet wrote:Forgot to ask... Why you adding checks for running it on shell? I have webspace and db only. Comented check on yapeal.php, and now scripts runs on apache without any errors... Is there anything to be afraid using apache to start scripts? Yapeal is made to be ran by CLI not CGI version of PHP which you probably also have access to.There are a few technical reason why it needs CLI for example CGI does not allow parameters and has timeout timer set to 30 seconds on most common hosting sites which doesn't always give Yapeal the time it needs to do it's job. There use to be others but they are less of a problem now. There is another issue I avoid by adding those and that is people asking constantly why its not working when their try going to the files in their web browsers instead of reading how to run it. Everyone thinks anything done with PHP has to be web based which is really sad since it truly is a very good general scripting language.
I have largely made Yapeal to work with either by adding extra guard code around CLI only stuff so CGI can be used but that may change in future versions so once again CLI will be required. There are plans to add forking using PCNTL to Yapeal in the future for users with larger work loads where the single task structure starts runs out of gas because of network I/O and DB bandwidth issues. PCNTL can't be used with CGI so CLI will be needed then.
@Drapko Nitzhonot - I've not been able to get it to throw a fatal error on my system for some strange reason but I understand why it could so I fixed it. Mercurials updated and archives as well.
version 12.009.1652 Finds camping stations from the inside much easier. Designer of [url]http://code.google.com/p/yapeal/[/url] for Eve API. Check out the [url]https://forums.eveonline.com/default.aspx?g=posts&t=7540[/url] |
Dragonaire
Corax. PURgE Alliance
27
|
Posted - 2012.01.11 23:20:00 -
[94] - Quote
Callean Drevus wrote:Hey Dragonaire, I've just taken a look at my yap_accountAccountStatus table, and it's pretty messed up :P is it by any chance possible that a new item is created every time yapeal queries for this information? EMK certainly doesn't have 255.000 accounts... I've now added a primary key on keyID to keep it from doing things like this again, but I do not know if that's entirely correct. In addition, does yapeal EVER clean it's utilXmlCache table? Mine seems to be filling up like there's no tomorrow (15 GB?) There well be a accountStatus record for every key since the keyID is the only thing to work with in Account section.
no it doesn't clear the utilXmlCache table. It's been on the TODO list for a while but not very high so far. Think you've set a new record on the size though I'll look into at least making something that can be ran from a crontab to clear out anything over a set age maybe this weekend. File cache is the same way it never stops growing. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. PURgE Alliance
27
|
Posted - 2012.01.12 18:36:00 -
[95] - Quote
Actual most parts of Yapeal would work with PostgreSQL but there are a few places where some MySQL only stuff is used. Creating the tables come to mind plus the upsert method in YapealQueryBuilder. There are a few others I'm sure as well. Most all of them are inside methods where it could be updated without problems. The biggest issue right now for it would be some issues with how ADOSchema works which I'm working on another project to replace it. Once it is replaced it may open up Yapeal to make many changes to how it manages the database connection but for now it would be hard. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax.
27
|
Posted - 2012.01.12 22:48:00 -
[96] - Quote
KeyID is set to be the primary key on the table on mine and looking at the install/account.xml it also says it is so looks like something just not right with your table Did you run the install/createMySQLTables.php script when you were updating? Maybe you got old one where userID was key or something? Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax.
27
|
Posted - 2012.01.13 17:56:00 -
[97] - Quote
http://code.google.com/p/yapeal/wiki/KeyFiles http://code.google.com/p/yapeal/wiki/UsingClassUtilClasses Those should get you started but look through the other wiki pages that are link from those and the others.
But to get you started you need to put your keys etc into utilRegisteredKey table. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
27
|
Posted - 2012.01.15 07:48:00 -
[98] - Quote
Thanks Satis Iqulenax for the work you did on faction warfare stuff and the stuff you are working on for the wiki.
So it was also time for the annual update to the Yapeal copyright for the new year so I also pushed that out to the repos and archives while I was at it.
version 12.015.0739 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
27
|
Posted - 2012.01.15 21:08:00 -
[99] - Quote
Quote:In addition, does yapeal EVER clean it's utilXmlCache table? Mine seems to be filling up like there's no tomorrow (15 GB?) Ok I've added an ALPHA cache cleaning script for anyone that is interested in try it out. You can find it in install/cacheCleaner.php. It is made to be ran manually or from crontab/scheduled task. There is a new setting for it in [Cache] section which you'll find in config/ yapeal-example.ini you may want to adjust in your config/yapeal.ini depending on your needs. I would run it at least once manually if you have a large backlog of XML cached as it will put a large load on your server the first time through after that if you set it up to run about 4 times a day your load shouldn't be very high at all. I will be refining it some more as time goes on but I wanted some feedback on how it's working before adding anything more to it.
version 12.015.1701 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
30
|
Posted - 2012.01.23 15:36:00 -
[100] - Quote
It should try to fill it back in for you as it always tries to walk back as far as it can. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
|
Dragonaire
Corax. The Big Dirty
30
|
Posted - 2012.01.23 22:45:00 -
[101] - Quote
If you're talking about how to update Yapeal that is covered in INSTALL.md. You basically just install the new over the old except if some special instruction are posted here or in the CHANGELOG Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
30
|
Posted - 2012.01.24 15:40:00 -
[102] - Quote
Might try deleting the cache files and what's in you utilXmlCache so it tries getting everything again as Yapeal is designed to always walk back to get all the data as far back as the API allows. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
30
|
Posted - 2012.01.25 21:31:00 -
[103] - Quote
No La wrote:I tried that. I deleted all market journal cache files, deleted all entries from the charWalletJournal table from the 19th till now. After running yapeal, i end up with no data for the 20th, 21th and 22e. For the 23rd to now the data is there.
Seems yapeal only fetches the last 3 days. I just tried Yapeal on my test system and Yapeal was able to retrieve new transaction and journal entries for more than 2 weeks worth of backlogged data since it had last been run include ones for the days you are having problems with. I did identify some other problems that might be causing problems for everyone which is do to both changes CCP made to the APIs and a bug I introduced in the install/util.xml file.
When I made some changes to util.xml so it could work without having to make changes to everyone's my.cnf file to allow larger allowed packets. Some extra commas got missed when breaking up the single insert into multiple inserts which caused the SQL to have errors in it. I've now fixed the problem.
Additionally the bogus class/api/corp/corpCalendarEventAttendees.php API file that had somehow been added in error has been deleted. Everyone should insure they read the CHANGELOG when update Yapeal so the file is deleted completely and no longer causes errors.
version 12.025.1327 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
31
|
Posted - 2012.01.31 05:34:00 -
[104] - Quote
Astraeus Deltrynon wrote:Love your library, outstanding. I'm having a problem though, it installed perfectly but when I try to use "$regKey->store()" to insert a new API key, it gives me "Registered new API key" even if I give it a fake one, and it won't show up in the utilRegisteredKeys table. Actually it will store it in the utilRegisteredKey table but it in no way does Yapeal at the time you do $regKey->store() tries to validate what you add beyond insuring the required columns have something in them and are of a compatible type (integer, string, etc). As Satis Iqulenax pointed out you have to run the main yapeal.php file for it to try pulling anything from the APIs at which time it tries using your fake info and will report the error sent back from the API server and that Yapeal is deactivating that key in to the error logs.
Astraeus Deltrynon wrote:On a related note, if I try "$char->store()" to insert a new registered character, it goes in but the character name comes up as "null".
It seems almost like it's not getting data from the EVE API properly... The name is going to be blank if you haven't set it like Satis Iqulenax said above as well.
To put it simply Yapeal works on the GIGO (Garbage In = Garbage Out) principal but with the twist that it'll let you know by an error in the logs and and then deactivates things when it can figure it out there's some wrong with the info so does not keep trying to use the same GI over and over again. It's kind of like a 3 year old: It'll take what ever you give it and try what you said once then tells you it can't figure it out and want you to make it work right
Hope that the above helps and reading or re-reading the starter guide helps you understand how Yapeal works a little better.
If you have any more questions after the above please let me know.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
31
|
Posted - 2012.02.07 16:26:00 -
[105] - Quote
Yes in the APIKeyInfo API there's a 'type' field which returns 'account' which is known as 'all' when making or editing a key
Quote:Another question: If I want to get all information, I think I need to insert one all-characters key per account and one corporation key per corporation. What bits should I remove from activeAPIMask of corporation key to avoid duplicated data. Documentation mentions accountStatus but do I need to remove anything else? You are correct you'll only need one key to get information for all the characters on one account but one per corporation for the corp info. AccountStatus in managed internally to Yapeal and you don't need to worry about it. I'm not really sure where you got that you might need to turn off some of the APIs to avoid duplicate data between account, character and corporation keys. There can be a small bit of duplicate info in a couple of the database tables from the account section but as explained in the page it doesn't cause any problems or extra calls to the APIs etc so you really don't need to be concerned with it.
Quote:EDIT: It seems corporation key doesn't actually have accountStatus bit. Is there any duplicated information between corporation key and all-characters key? No there is no duplicate APIs between char and corp keys. Many APIs have both corp and char versions for example AssetList but the corp and char info does not overlap in any way.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
31
|
Posted - 2012.02.07 16:45:00 -
[106] - Quote
Ok guess I maybe should have added the rest of that thought which is ...any problems for anyone using it. Yapeal knows what it's doing and it isn't a problem for it but could cause some confusion for anyone trying to use it or readding that page it seems
EDIT: I've updated the page to make it a little clearer what I meant. I also wrote that when much of the CAK stuff was very new and thought there might be some other underlaying issues I hadn't worked out yet which I'm glad to say turned out to be non-issues and me just not having worked with them enough to understand some things Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
32
|
Posted - 2012.02.07 18:33:00 -
[107] - Quote
Since the CachedUntil time Yapeal uses is based on the cache interval it's what you need to use. The currentTime is used to figure out when to get the APIs since by and large CCP does things with the cachedUntil time reported by the API server that make it largely useless. There was I time when Yapeal used it but I got tired of all the bug reports and everyone got tired of all the APIs errors that were returned when Yapeal actually did what it said So now it uses the currentTime and cache interval to calculate then new cachedUntil time that end up in the table.
Just a bit of a warning don't think that the cachedUntil time has any bearing on how 'fresh' the data is. It something everybody that deals with the API has to learn is that there is no way to tell from the API when the actual data was updated it only tells you when you get it and when you can again.
I'll try to give you a quick example so you understand what's going on. Say two directors for a corp are pull the same API using two installs of Yapeal. One of them pulls say the WalletJournals and since it hasn't been request before CCP actually goes and grabs the data but they then cache it. Let's now say the other director request the WalletJournals as well but 10 minutes later. CCP sees they have the data cached so they return it from there but they only return the currentTime and when you should ask for the data again in cachedUntil based on the caching interval at best. They don't give you the actual time they well be refreshing their cache so as to prevent stampeding for it between the two applications requesting it. This is very important for server load for them especially with their DT which tends to force all the API calls to bunch up. So that means even though the second director's Yapeal could actually get new data 10 minutes soon if it knew it isn't give that knowledge so has to just use the cache interval.
I wouldn't even try to show any of that to the users of your application or would at most do what EveMon does and show when it will be updating it. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
32
|
Posted - 2012.02.08 00:09:00 -
[108] - Quote
you can do your selects from the table and limit them to the date of the last transaction you want to look at in all the tables and say that was the balance then but you would need to run at least one cache interval behind to be absolutely accurate. Since asset list is only every 6 hours you have to be at least that far behind but you could try rolling in any transactions from the information in WalletJournal/transactions as will but still be limited to their cache intervals Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
32
|
Posted - 2012.02.13 15:41:00 -
[109] - Quote
Just an update to let everyone know I've starting the process to migrate the Yapeal project over completely to SourceForge and as part of that process I've decided it's time to update the project on SourceForge to the new Beta style. https://sourceforge.net/apps/trac/sourceforge/ticket/24305
Work is underway to convert the wiki as it's the biggest issue to be solved but I've been experimenting with a process that seems to work. The process has some manual work to it so it'll take time. For now everything will continue to be on both sites but over the next few weeks expect more and more things to appear on SourceForge and to start see pages redirecting you from Google code to the new stuff on SourceForge.
Needless to say actual development work and bug fixing will be minimal until after the move is complete as there is only one of me and a part time helper working on the project right now Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
32
|
Posted - 2012.02.15 01:50:00 -
[110] - Quote
Read INSTALL.md and just follow the instructions like a new install. You can skip to step to make the DB but when you run the one to create the tables it will update the existing one with your data in place. As always make sure you have a good backup of the DB in case something goes wrong Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
|
Dragonaire
Corax. The Big Dirty
32
|
Posted - 2012.02.17 17:58:00 -
[111] - Quote
Just a quick note for everyone. All the Wiki pages have been converted, updated and moved over to SourceForge now. Check them out at https://sourceforge.net/p/yapeal/wiki/Home/ You'll also notice the Wiki tab at Google Code now redirects you to them. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
32
|
Posted - 2012.02.20 08:37:00 -
[112] - Quote
Ok everything for Yapeal can now be found on SourceForge.
For those of you that might have been cloning their Mercurial from Google Code you'll want to change to SourceForge as the one on Google isn't going to be updated in the future.
Also note for anyone else getting stuff from the SF site when the project was changed to SF Beta project all the URLs have changed so you'll either need to do a new clone of the project. Backup your config/ files and just wipe out your existing checkout and clone it again from the new URL. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
33
|
Posted - 2012.02.22 17:38:00 -
[113] - Quote
Mikokoel Is right sounds like you need to change your max_allowed_packet setting for MySQL. I would say yours is set below 1M or you are trying to run an older version of Yapeal before I put in some limits to the insert/upsert size that it uses. It now limits the size to 990k which is below the normal limit. You can find the constant that sets that at the bottom of class/YapealQueryBuilder.php. If you haven't yet you should read through the Starter Guide which on the Yapeal Settings page tells you more about changing the setting for MySQL. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
33
|
Posted - 2012.02.23 04:56:00 -
[114] - Quote
You can post to the wiki but you have to be authenticated (Be signed into SourceForge) to do so. General posts like that are moderated as well but I only set it up that way because of spambots so please do add any comments or suggestion etc you have and one of us will make it visible for everyone (Once I figure out how that works anyway ) I may decided to change to just authenticated in the future but still getting use to the new system and I decided being a little bit on the paranoid side might not be a bad thing to start with
Satis Iqulenax does deserve the credit for the writing on the Starter Guide I just acted as editor on it and did the translation of the Wiki syntax during the move. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
34
|
Posted - 2012.02.24 18:07:00 -
[115] - Quote
At some point the API server thought that key had the IndustryJobs API turned off so when Yapeal was told that it unset the key and/or corp's bit so you'll need to update them not the general ones used by all of Yapeal. Look at the utilRegisteredCorporation and utilRegisteredKey tables that are related to the key that stopped working as the bitmap in activeAPIMask doesn't have the IndustryJobs bit set. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
35
|
Posted - 2012.02.29 17:10:00 -
[116] - Quote
Quote:Would it make sense to have a field for desired and effective bit masks? This should allow for the desired mask to cover everything you want and effective to be updated via errors and the APIKeyInfo api. Effective would be used by all of the current classes. APIKeyInfo when processed would attempt to update the effective to be as close to the Desired as possible based on what the key itself supports. Could something like that maybe be implemented? Yes, but not everyone wants the keys to change either. If you want that effect Yapeal supplies the tools for you to do so in a way that makes sense to your application. BTW you can get most of the effect you are looking for by simply setting the masks in utilSections and utilRegisteredKey to what you want and once accountAPIKeyInfo updates it will block any APIs that aren't allowed. If Yapeal tries getting an API before it updates that isn't allowed it deactivates it when the API server returns an error saying its not allowed like what was happening above. I've designed Yapeal to report error and then try to keep from repeatedly telling you there's an error or wasting time on something that doesn't work. You then as the programmer/user get to decide when whatever was causing the error has been fixed and it can try again.
Quote:The new data was picked up nicely, but the old data, belonging to the first api that I deleted keeps showing up. Is there something I forgot about when deleting the api in order to clean up the rest of the database? You didn't delete the old data from the API tables. Deleting the keys doesn't have any effect on the API tables themselves when it comes to existing data but only effects what new data may be added. Additionally when you do a character move like you did it would be a good idea to update the accountCharacters and accountKeyBridge tables manually or in your application to break the link between the key and the old account etc as how Yapeal well react in this case is not really defined. It should do the right things after accountAPIKeyInfo updates for the key but you may get a few errors until that has happened. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
35
|
Posted - 2012.03.15 16:00:00 -
[117] - Quote
Drapko Nitzhonot - You have a couple options for the too slow errors.
- B!tch at CCP because their servers aren't responding in a timely matter to API requests for some reason.
- Change the error reporting level in Yapeal to 'warning' instead of 'info' inside the config/logger.xml file.
- Change the timeout value in Yapeal to try giving them more time. You can try this by changing the last line
const TIMEOUT = 45; in ext/eac_httprequest.class.php. This probably won't help as most times when the API doesn't response in the time given it's not going to respond at all
You also need to make sure there isn't another application trying to grab the same API information as they can conflict ending up with a race condition between them and the timeout errors.
Quote:Another issue is Yapeal stopped updating corpWalletTransactions about 10 days ago. I notice my activeAPIMask was changed from utilRegisteredKey. I haven't touch any API key or Yapeal config since last Yapeal update (January 26th), so I don't know what happend to change that key... maybe because I'm getting so many curl_error? Look for a line in your logs like this WARN: Deactivating Eve API: WalletTransactions for keyID: ****** as this API is no longer allowed by owner with this key I'll bet for what ever reason that Yapeal received an API error saying the key was not valid for that API and turned it off just like happened to The Magez above on IndustryJobs and the fix is the same as I gave to fix it. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
35
|
Posted - 2012.03.17 15:19:00 -
[118] - Quote
Drapko Nitzhonot wrote:I'm still getting cron emails after changing to "warn" level: Quote:curl_error: Operation too slow. Less than 10 bytes/sec transfered the last 12 seconds I'm getting this even there is no updates in log/ files. Sorry about that there seems there was some old debugging code left over in ext/eac_httprequest.curl.php which I hadn't noticed before which was directly printing out the errors on the CLI I've pushed out a change that fixes that plus a few other minor things.
I am concern though after looking more fully at the second log message you were getting that you are still running an older version as the line 106 reported in the error should be 100 instead. Make sure you are following the full instructions on how to instill and update Yapeal and not getting a mix of old and new versions etc.
version 12.077.0801 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.03.31 17:57:00 -
[119] - Quote
Kush Monster wrote:I'm sure this has been covered but your wiki goes into inserting data but it doesn't go into extracting data.
let's say I want to insert a key and then register the chars associated with that key.
How do I get a list of character id's associated with the api key?
I can do this with SQL but the point of using a library would be so that I don't have to. I'd suggest reading the project home page a little closer as part of the main idea with Yapeal is that the database is the API for people's applications. There are some classes in class/util/ to help manage the non-API tables that an application might need but there's no way I could ever come up with a set of classes that allow as much versatility to access the API data as what each developer can do for their own project with a simple wrapper class around the SQL queries they need.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.04.01 15:15:00 -
[120] - Quote
Check your cache settings in config/yapeal.ini as the default is 7 days so it will only clear files that are older than that. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
|
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.04.02 17:12:00 -
[121] - Quote
Gabba Cyno wrote:Is there a reason I have to run the yapeal.php 5-7 times in a row before it actually updates my database? I'd be checking the error logs to see what's going wrong myself. You might have to run it a couple times for it to prime the account section tables before you'll start seeing data in your char and corp section tables but I've never seen any cases where it was more than a couple as long as something isn't going wrong.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.04.03 17:01:00 -
[122] - Quote
Lluerssen wrote:Mega epic failed bug:
PHP 5.3.0 The prepend parameter was added.
Check your YapealAutoloader.php ;) huh since I'm not prepending anything your comment doesn't make any sense so maybe you can explain better what you're talking about.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.04.04 04:54:00 -
[123] - Quote
This is the bug report and it was fixed sometime in 2008. https://bugs.php.net/bug.php?id=42823 I'm not sure yet which version it got fixed in but you need to make sure you are using an up to date version in the 5.2.* series. I know the first version that talks about the new prepending option is with 5.3 but it's talking about a fix of the fix so it was added earlier. Given that it was put into the CVS in May I'm thinking it was added in version 5.2.6-8 which is about the version I was using at the time. Thank you for bring it to my attention though because I do need to update the minimum version of PHP Yapeal will run with. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.04.04 08:31:00 -
[124] - Quote
I like Bitbucket in many ways but some of the other things a project hosting site needs like bug tracking and a good wiki for docs etc they just don't have yet IMHO. When I started looking at how to improve the hosting for Yapeal GoogleCode, Bitbucket, and several others just didn't seem as good as what SF offers now. Yapeal start on SF but I moved it to Google Code because at the time they had better features but they then made changes so you couldn't use some things like downloads the way most projects use them and Github has started melting down under the load etc but in the mean time SF updated their stuff and now out do the rest and have a clear vision for how to continue to improve over the next few years which is more than I've seen with most of the other sites. At least that how I saw it Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.04.04 14:49:00 -
[125] - Quote
Actually you missed the point that it was added sometime in the 5.2.* series and additionally bug fixed in 5.3.0. The reason I say that is your the only one that has had problems with it and many people including me have used it with 5.2.* without problems plus the time frame when the bug was fixed. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.04.04 15:21:00 -
[126] - Quote
Yep those were some of the same reasons I didn't go with them. I changed the defaults on SF as well to require a little more than anonymous access to report bugs but since they also use openID etc almost anyone with an E-mail address can have logins there. I figure since people can still report bugs on this thread as well it's not really a problem either Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
41
|
Posted - 2012.04.27 16:13:00 -
[127] - Quote
Hi all decided I should push out a few fixes I've made. Most of them came from stuff found with some new inspections that have been added to PhpStorm 4.0.1. They added some better support for checking exceptions etc which found a few that I'd missed documenting plus a few parameter and return type problems. There was a few other minor bug fixes in the code mixed in I think from before as well but nothing that really broke stuff just not as well done as I'd like coding wise.
version 12.118.0900 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
41
|
Posted - 2012.05.09 06:00:00 -
[128] - Quote
Try running install/checkForRequirements.php and see if it picks up any more problems. Also make sure you didn't miss a step in INSTALL.md. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
44
|
Posted - 2012.06.03 19:38:00 -
[129] - Quote
Hi everybody, Thought it was time to let people know I'm still working on Yapeal etc. Development has slowed as other projects have been the priority lately but I'm still working on Yapeal from time to time as well. What has me especially doing an update now is something I read in another thread that got me to thinking about something in Yapeal. Historically Yapeal has had most of the API sections turned off do to many reasons like logs filling up with error messages when no characters/corporations were added to the utilRegistered* tables plus other issues but since none of those issues exist anymore I've decided to change the default so all sections are on by default going forward. This should also help many people when they first are trying out Yapeal since one of the more common questions is why their stuff doesn't work after adding data to the utilRegistered* tables. I'm not going to change which APIs are active in each section from the current defaults so you may still need to make those changes yourself in the masks.
There are a few other minor changes as well in the new version but they are mostly just comment updates.
version 12.155.1909 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
45
|
Posted - 2012.06.17 14:51:00 -
[130] - Quote
Quote:Is there a way to see the API cooldowns, when using yapeal? Look at utilCachedUntil table to see when it will next try to get the API.
Quote:Regarding ccp manual, corpwalltettransactions should have a cooldown of 15 Minutes, but it updates only after several hours. Think that's cause by changes CCP has been making for unified innovatory so you might try reporting it to them.
Quote:I haven't found any errorlog or something similar. I Sorry to hear it's running without an errors for you If it ever does have some errors you might try looking in log/ directory since that's where they get put.
Quote:Maybe yapeal stops updating after som sections fails do update? Shouldn't ever do that but also remember it expects to be ran every minute from a crontab or scheduled task.
Quote:This is really anoying. Sorry about that but maybe you should slow down just a little and try a little reading and things might be easier for you.
i'm using the standard yapeal.php for updateing the database.
BTW have you tried read the stuff in the Wiki a lot of your questions are answered there. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
|
Dragonaire
Corax. The Big Dirty
45
|
Posted - 2012.06.27 16:04:00 -
[131] - Quote
As always make sure you've backed up your data before trying to update it. To try figuring out what part of the SQL isn't working look in the cache/ADOdb/ directory and try running the SQL files you'll find there starting with util.sql. you can either run them directly with MySQL on the command line or through PhpMyAdmin. You can also look at the SQL in the files to have some idea what has changed but often the best way to find the differences is to run the script on a new empty DB and compare it with your current one.
As a general warning for everyone it's important to keep up with the current versions on Yapeal because though usually the individual updates rarely break anything and can be done automatically by the scripts upgrading over several versions can be more than they can handle and you'll end up having to do part of it manually. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
45
|
Posted - 2012.07.18 15:26:00 -
[132] - Quote
Thanks for letting me know last I'd checked CCP limited all names to 32 characters but I guess maybe they've changed that now. I'm wondering one thing with that name did it use any non-English characters by chance? Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
45
|
Posted - 2012.07.19 04:42:00 -
[133] - Quote
Sounds just like they have lifted the length limit I'll update Yapeal and push it out the next time I get a chance.
Your errors would seem to be your MySQL not being able to keep up or something. as both of your examples are for tables that only do small inserts. I'd check you MySQL config and make sure it's optimized for the system you have it running on. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
45
|
Posted - 2012.07.30 06:34:00 -
[134] - Quote
@Lluerssen First that's a very old tread from when they regularly reset the refIDs which no longer happens also if you pay attention Yapeal will include both records since ownerID, refID are used as the primary key so if you aren't seeing both of them in the Db it might be the query you are using to find them. If I understand right when you did a search you did end up seeing them both. In the char table ownerID is sent to the charID and in the corp one it's the corpID. The only time there can be a problem is when a char buys from their own sell order or the same for the corp. You still have a record but which one you'll get (buy or sell) can be random and due to no guarantee from the API on record ordering can change each time it's received
@Gilgamoth I'll try to update all of the name columns to be longer and push it out over the next couple of days.
Probably the best thing to do for the charSkillQueue error is to look at the XML and see what might be strange about it that causes the error. Also look for other errors just above it in the logs that start with either 'Row was missing required fields ...' or 'Row has extra unknown fields ...' which should give you some idea what's going wrong. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
46
|
Posted - 2012.07.31 05:25:00 -
[135] - Quote
Ok I've pushed out a new version that should have fixed the last of the char/corp name problems. Had a couple of other minor fixes as well.
version 12.213.0517
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.08.25 04:11:00 -
[136] - Quote
Sorry for the late replies but I wasn't feeling will for a couple days and computer also decided to act up and I ended up having to re-install OS so it took a couple days to get back on.
@Mikokoel - Glad to see you found a fix for the version problem. The reason 5.2.8 was picked is some of the code in Yapeal was running into a bug in PHP and there wasn't a real work around for it. I decided that since PHP 5.2.8 is now 2+ years out of date and two generation outdated that everyone really should be put pressure on their hosting service to update or finding a better one that actually cares about security etc as well
@Crassus Detlator - One area that Yapeal isn't as good at is in a sign-on scenario like you described. It is something I plan on improving but it will require a lot of re-writing on Yapeal to make happen which is never something to be undertaken lightly. Now to ways to minimize issues and make Yapeal sort of work in what you are doing. First I think the problem you are have trying to use exec etc is by default you will end up getting the CGI version of PHP and you need the CLI version. You need to find out the full path to it and use that when trying to call it from a web page which uses CGI. Now to getting Yapeal to only grab the API you need in a more timely matter. You have the option to have it use a different ini config file from by adding the -c or --config= option. How this helps you is by having a separate sign-in DB with only the account APIs active. Yapeal will still run in a batch mode like always but since these APIs are all small and you should only have info for new accounts that are just signing up it will grab the info from the APIs quickly. You just need to have you application check for records with a owner matching the suppled key and move them over to your main DB when they appear or as soon as the application user has decided on which one they want information about and delete them from the sign-in DB. Used this way Yapeal should seem no different then something that gets just a single user's records. One thing to remember is you can have multiple Yapeals running at the same time with a little thought and care and they can use different configurations. Hopefully that gives you an idea how to go about making it work for you doing something that it wasn't really made for but is possible with a little thinking outside the box. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.09.10 05:44:00 -
[137] - Quote
That's caused by API servers not working right not anything that can be done about it in Yapeal. Basically the API server is failing to continue connection after allow Yapeal to connect. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.09.10 16:07:00 -
[138] - Quote
Bluedisguise - You can't just add more rows to utilSections but need to change the activeAPIMask. The mask is a bitmap but you can make it with simple addition as well as by binary ORing them together like in the examples. So to get walletJournal and walletTransactions you use 3145728 for the activeAPIMask on the corp row.
Also you asked if there is anyway to just have everything on but that is the default mask used so you should be able to just leave everything alone and Yapeal will just work There was a time where most things were off by default but now they are turned on as both the API servers and Yapeal now handle it without any problems normally.
Drapko Nitzhonot - Make sure you changed it from info to warning not the other way around as you posted as that would be turning them on. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.09.10 21:17:00 -
[139] - Quote
Bluedisguise wrote:Oh goodness, I see now.
Any thoughts on why I am not getting any corporate contract data with the utilsections row:
46068159, 1, NULL, 3, corp
?
Right now the table 'corpcontracts' returns 0 rows. Make sure it's active in the API key you have. You can see the actual mask returned from the API for the key in the accountAPIKeyInfo table. Also make sure there are some active corp contracts as the API only returns current 'pending' contracts if I remember right. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.09.14 03:48:00 -
[140] - Quote
Drapko Nitzhonot - When I look at you error message it doesn't seem right as line 100 shouldn't be the one returned. It should give line 99 if anything. Here's what me lines 99-106 look like: $result = $this->con->post($url, $postList); if (!$this->con->success) { if (Logger::getLogger('yapeal')->isInfoEnabled()) { $mess = $this->con->error. ' for API ' . $url; Logger::getLogger('yapeal')->info($mess); }; return FALSE; };
If yours is different you might try following install instructions again as not everything was updated correctly it would seem. Also make sure you are changing the right line to turn info on and off. In config/logger.xml on line 124 you should change it from info to warn.
Bluedisguise - Might try clearing out the XML file in the cache and the DB cache at utilXmlCache in DB if you have it on. Sometimes for unknown reasons Yapeal will decided not to add stuff into the APIs but clearing the cache files seems to make it start working again Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
|
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.09.30 03:05:00 -
[141] - Quote
Somerset Mahm wrote:Hello!
I am (finally) running shiny latest Yapeal with CAK :P
Everything is working fine, but I have set the log level all the way to "debug" and I still am getting nothing in the logs at all. My config entry is:
log_config=YAPEAL_CONFIG "logger.xml"
Edit: after further troubleshooting, if I run Yapeal from the command line directly, I can get it to write to the files (if I intentionally make it error out). It doesn't write to them when run from cron, though. Yapeal actual now uses several different log files like log/yapeal_fatal.log, log/yapeal_error.log etc but generally you shouldn't see anything outside of error, warning, or info once in a while. By default Yapeal is very quiet if nothing is causing errors any more unlike it use to be where it could fill up it's logs in a day but now only does so on actual problems.
For not seeing anything when you are knowingly causing errors in crontab you probably need to check if cron is running with different user or something which doesn't have write access to where Yapeal is installed. You might try TEMPORALLY making the log directory world writable to see if that makes a difference. Also remember you need to manually edit paths in config/logger.xml if you are trying to move the log files from their default locations. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.10.13 08:32:00 -
[142] - Quote
Lluerssen wrote:Guys, what is best way, to check validity of api key? Check it with the http://wiki.eve-id.net/APIv2_Account_APIKeyInfo_XML API. Api server returns errors for bad keys and it can tell you what type and what API access the key provides.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.10.19 15:59:00 -
[143] - Quote
Just to let everyone know that might have seen some other API applications and tools that are breaking with CCP turning off HTTP and going to just HTTPS I changed Yapeal over months and months ago when they first announced the change so there should be no problems with it. Do report any bugs though just in case there is something some where along the line that was missed Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.10.28 10:23:00 -
[144] - Quote
Kivorno - Double check that all the tables were created correctly and also make sure you've followed the full install instructions. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.11.07 04:19:00 -
[145] - Quote
Skills API is one of the more complex ones to do and no one has finished it that started working on it including myself I've never really had anything where I needed it so I've never got very far with my tries. If you just want the list of skill names but not the full tree with what skills with levels you need for other skills that is available from the static data dump. If you want to work on it you are also welcome to do so. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.11.14 00:46:00 -
[146] - Quote
Crassus Detlator - Yapeal is for working with the Eve API not a one stop solution to everything Eve related so it doesn't deal with anything having to do with the SDD but they are usually both needed to make anything useful. I have thought about including parts of the SDD but what is useful to someone developing a killboard vs something for skill management are often very different and including any of it with Yapeal would just add stuff that isn't needed by everyone. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.11.14 00:52:00 -
[147] - Quote
Steven Trux - Make sure you've gone through all the steps in the install.md(test) file. I'm thinking you missed step where you test DB connection that you'll find in step 9. Also make sure you got everything and if you're updating from an old version that all the files updated correctly. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.11.15 16:29:00 -
[148] - Quote
Steven Trux wrote:Dragonaire wrote:Steven Trux - Make sure you've gone through all the steps in the install.md(test) file. I'm thinking you missed step where you test DB connection that you'll find in step 9. Also make sure you got everything and if you're updating from an old version that all the files updated correctly. Thanks for reply, but that's not the problem. Step 9 works just fine Still got the same error when running /install//createMySQLTables.php -s localhost -u YapealUser -p secret --database=yapeal If you haven't found it yet check out http://sourceforge.net/p/yapeal/wiki/StarterGuide/
You also shouldn't have to add any of the -s, -u etc part if you've got a config/yapeal.ini file setup. One other cause of major problems with the tables part is a bad my.cnf setting for max_allowed_packet. It needs to be at least 2M to generally not cause problems during install and while running Yapeal later.
Just on the off chance you really are missing something check that you have 2 files in ext/ADOdb/datadict/. I'm not sure if it's just a bad cut and paste from your error or if it really said 'datadict/datadict-.inc.php' which would be missing the 'mysql' part.
If none of those things correct your issue please E-mail me a copy of your exact error messages and any Yapeal log files and I'll take a look and see if there's a clue that's been missed. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.12.02 02:29:00 -
[149] - Quote
Sorry everyone been busy in RL with holidays etc. Glad you figured out what the issue was as I wasn't even aware anyone use anything but OpenSSL with cURL or I might have added checks for it. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
48
|
Posted - 2012.12.04 15:56:00 -
[150] - Quote
Quote:$this->options['CURLOPT_ENCODING'] = 'gzip';// allow gzip compression
It's been waiting on them for over a year Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
|
Dragonaire
Corax. The Big Dirty
50
|
Posted - 2013.01.06 18:43:00 -
[151] - Quote
Talos Katuma - You're right it should be. I started to work on the maintenance stuff but didn't get very far into it before I got busy with other things.
Gladi - Most of the other classes in class/util are there to make integrate Yapeal with your software easier but if you don't think you need them they can be ignored.
Thaddea - I'd be interested in looking at what you have done do contract me on SF. If you already did might try it a gain because I was deleting some SPam the other day and think I got some other stuff as well Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Corax. The Big Dirty
50
|
Posted - 2013.01.11 17:06:00 -
[152] - Quote
Yapeal actually calls the APIs in a random order so any bugs or API server errors don't end up block another API call and since it's hardwared into the code it can't be changed. The crontab should be ran every minute as I've stated multiple times since Yapeal manages work load internally to spend out the API calls to keep from cause API server spikes. If there's nothing for it to do it does cause any load on your server since it only does a few DB calls to check the cached times.
Wither you have the caching on or off is up to you as Yapeal doesn't need it but it can be useful when trying to track down errors. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Corax. The Big Dirty
50
|
Posted - 2013.05.28 14:13:00 -
[153] - Quote
As Everybody has probably noticed I've become very inactive in Eve over the last few months and having been updating Yapeal either. There are many reasons for this but in the end it doesn't matter much to most of you. Given that I don't see my interest level increasing in the near future I'd like to find someone to take over development and the day to day maintenance of Yapeal. If you are interest in taking over the project Eve-mail me and I'll also probably contact a couple of people I believe would be good at continue the project as well. It's hard to let the project go since I've worked on it for almost as long as I played Eve and actually spend more time on it then I did playing but it's really past time for me to step down and let someone else take the lead in moving forward. It's been fun and I've learn a lot both from working on Yapeal and from all of the other developers here on the forums. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
50
|
Posted - 2013.06.04 16:32:00 -
[154] - Quote
Ok so at least one of my account now only has a few days left on it and I don't plan on keeping it going and I may not keep the main one either so thought I better make one more post before it does too. None of the people I talked to were interest in keeping Yapeal going and no one else stepped forward on their own either so I expect development to stop completely now which it had mostly done already in the last few month since I haven't been doing anything. The good thing about is it's open source and host where it'll be available for a long time. I'd still welcome having someone else take over the project and be available to help consult on understand the inner works of Yapeal but have no interest in adding to it or rewriting it myself though it probably could use that again in areas.
Anyway thanks all of you who have help me along and been friends for years both in and out of game as a player and a developer with the Eve API over the last 6 years and maybe I'll see you all again someday flying around in EVE which is still one of the best games I've ever played. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
50
|
Posted - 2013.07.16 03:11:00 -
[155] - Quote
Erica Northman - See post 330 on this thread about possible cause as it's the most common cause of your error especially in Windows.
Tiberius Zol - The error in line 186 is when the script is trying to tell you it has finished without errors and since you are NOT using CLI it doesn't understand it.
Yapeal was made for CLI only because the normal CGI version is missing things it needs but as you've found by modifying it a little it will often work just without some features but I will say except if your host provider has gone out of their way to compile PHP themselves and said not to build CLI it would have been built by default and the PHP CLI is probably available you'll just have to do a little digging around.
Somerset Mahm - Your doing a great job and keep up the good work. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
52
|
Posted - 2013.10.07 06:42:00 -
[156] - Quote
Hi everyone just thought I'd let everyone know I pushed out a new version of Yapeal. No real changes to be had from what Somerset Mahm had put out. I updated the copyright and started adding stuff to Yapeal to work with Composer.
Does this mean your going to start working on Yapeal again, you might ask?Kind of. Let me explain.
Yapeal as it is now works of course though there are some problems with it do to API server changes I understand. Unfortunately it could be said that it's legacy code as used in the more Modern interpretations section even to me now after being away from it for a few months and I wrote 99% of it
So what I've decided to do is what I wasn't up to doing a few months ago, rewrite it, but this time starting really with a clean sheet but still keeping the better parts of the existing code. Since I'm basically starting over anyway I'm going to try writing the new version of Yapeal as though I was doing it for the first time with all of the knowledge I have now about write a PHP application/library unlike before when often the first time I tried something new it was in Yapeal to mixed results
What does this all mean? The version I tagged as yapeal-1.0.3 is the last expected version in the 1.0.x development chain that lead to it. There may be a few more bug fixes done if Somerset Mahm decided to keep it go and I'll help with some of those if needed but the main focus will be on working toward Yapeal 2 instead.
What to expect in Yapeal 2:
- Composer as main dependence tool / install method.
- Use common standards where a good one exists. Standards like the PSR-0 etc make for less work both for me and others in understand and using Yapeal.
- Use PHPUnit from the start. I thought about going with Extreme Programming but just haven't got my head fully around it, plus I don't see it working since I don't have a 'client' handy to work with.
- Move environment requirements forward. I.E. PHP 5.3, PDO etc to move away from legacy ways of doing stuff.
- Maintain some form of backward compatibility. Keep the simple CLI type interface for current users but make changes that allow a much easier integration of Yapeal into modern OOP projects that usually use mod_php on a web server.
- Many other things that I can't think of right now but I'll probably go into more in the future.
That's a short list and I'll be writing more about things as the project continues but on to another aspect of the changes.
How can I help? Glad you asked To make things work I'll need people trying out the new code as I release it. I also need ideas on what people would like to see changed or added to Yapeal as a core feature. Also I would find it useful to hear more about how people are currently use Yapeal and any problems they had to overcome or things they had to do to work around something they found lacking with Yapeal. I know some of these from reading many of the past forum posts but I'd still like to hear it directly from as many of you as I can because though many of you may have similar needs the way other person writes about it can provide extra insight for everyone and especially me.
You can also help by join me in writing the code. There's lots of work to be done and many part of that are still just ideas in my head but there is stuff that I need help with already, plus I work better when I have someone to bounce ideas off of and to look over my shoulder once in a while as well.
Ok that's it for now I'm off to bed and look forward to seeing everyone's comments. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.03.27 00:38:00 -
[157] - Quote
Hi all I've got a little time so thought I'd check in on things here again.
Zynen wrote:Apologies if this has been covered somewhere. After reading pieces of the wiki and half the pages in this thread I gave up :(
IGÇÖve built a few corp tools using Yapeal that only has our corp key in it. This works great!
We have another copy of Yapeal installed on a separate server that has all our member API keys. This takes 4-5 hours to run through all the keys/data.
What IGÇÖd like to do, is merge these two installs.
My question is, once I do that, will my corp API data be delayed because thereGÇÖs always a back log of member keys to roll through?
If the answer is yes, is it safe to run a second install of Yapeal on a separate database so they can update independently?
The corp stuff could be delayed though how much is hard to say you would just have to test. You could use the same DB for both copies of Yapeal you have running as well without to much of a problem using the 'table_prefix' option in the yapeal.ini so you can have separate util tables. Main thing is you'll want to do some testing to figure out where most of the delay is happening. Main areas that have shown up have been Network I/O, DB transaction limits, and / or Disk I/O limits which can seem to be DB limits without careful testing. Also remember that Yapeal is not a typical web app in that it uses a lot of incoming network I/O with little outgoing which is backwards to how most hosting is setup. The Reason for that is it's more of a client then a service at least as seen from outside.
Note that the idea of using 'table_prefix' might also help with the 4-5 hour runs on member keys as well but can make your queries to the DB a little harder as you'd have to merge from multiple tables. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.03.27 20:19:00 -
[158] - Quote
So pushed out update to repo for people to test. Mostly update to *.xml and *.xsds for Eve API changes that have been made. Just a warning there might be some other refactoring changes also mixed in that I was working on a few months ago so good backups and test server use only until you've tested it highly recommended as I'm not able to do any testing right now Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.04 22:07:00 -
[159] - Quote
Lluerssen wrote:Just updated to latest yapeal through hg.
> php -v PHP 5.4.26 (cli) (built: Mar 12 2014 12:15:56) Copyright (c) 1997-2014 The PHP Group Zend Engine v2.4.0, Copyright (c) 1998-2014 Zend Technologies
> php -f yapeal.php Could not find required auto class loader. Aborting ...
This is clean hg clone, with yapeal.ini moved from previous version.
If you instilled after my above post you got the broken version with some in progress alpha code so check that first. You might try grabbing the tagged version 1.0.3 with hg or rev 509 as anything after then is likely broken. I'll look into fixing the default branch again so it does NOT cause any more issues for people but I have to sort out which of the later changes I really did want to apply to the default branch. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.04 22:25:00 -
[160] - Quote
Zynen - Make sure you are using different yapeal.config files with correct settings for each database and are use the -c option with the one that is NOT using the default config/yapeal.ini. It might be a good idea to use -c with both installs so you end up with something like this:
php -f yapeal.php -c config/yapeal-corp.ini php -f yapeal.php -c config/yapeal-char.ini
Should help keep them straight plus if you do end up testing or trying to merge them later into a single setup it would be a bit easier maybe.
Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
|
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.05 08:29:00 -
[161] - Quote
Okay think I managed to fixed the stuff I broke in default branch. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.06 05:22:00 -
[162] - Quote
So my reg-exp script foo isn't the best but what I get from that is it looks for a line starting with "< schema" and finds the version attribute and extracts the value to be checked. I'm I missing something and why were you looking at ADOdb is it giving you an error when trying to use the install/*.xml files or something? Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.06 16:44:00 -
[163] - Quote
Lluerssen wrote:Wrong versions of schema causing line 161 of createMySQLTables.php return empty $sql; And this leads to "Failed to execute schema for util" & other files. Btw, i would use: http://regexr.com/38lre this pattern ) Don't forget to open substitution part to check for matches ;)
So you are trying to say I should make changes to ADOdb which is a project I don't control to fix an error you are having in Yapeal? Just an idea lets try to figure out why createMySQLTables.php does like the util.xml first I'm sure the version number has NOT changed in the files so that not the cause. My re-format of the XML might have but should NOT have. Just looked at a diff and found a couple things that my IDE did that probably cause the problem so I'll look at fixing it so it does NOT break things. Mainly it took out some spaces in the values like the <opt platform="mysql">ENGINE = InnoDB COLLATE = ascii_general_ci</opt> just before ENGINE which will cause it to fail. also re-arranged the attributes in the schema line which is probably what is what you are looking at. The version attribute get moved after the xmlns one which it shouldn't have done. Also line wrapped the <query> text which probably makes MySQL unhappy as well. I'll fix what it broke and push it out. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.06 18:10:00 -
[164] - Quote
So did push that should fix the problems with the XML files give it a try.
The include stuff has nothing to do with your include path etc. Those are there to insure you are running them directly in CLI and not trying to do a
include "config/createMySQLTable";
from another PHP file. If you look at some of the other files in class/ you'll notice they don't let you call them directly is they do need to be included or required. That's mostly there to protect against noobie mistake of think all PHP should be some where under their web root where the web server would allow it to be browsed to. If someone was to do that they get a error message instead. In the future I'll probably be dropping that since it's much more common now win all the PHP frameworks that they do not have their code in web root and people are more use to it being done that way.
Not surprised that Yapeal as is would fail PHP 5.5. The next version which I've start work on is going to require at least PHP 5.4 it looks like at this time. I've decided things like traits are just to useful to not use them and I expect that soon after PHP 5.5 is considered the current stable branch that PHP 5.3 will stop getting updated. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.06 23:41:00 -
[165] - Quote
Just a quick couple notes here. I'm looking at moving Yapeal development over to GitHub. SourceForge has done a good job of updating their stuff but they got behind GitHub early on and they just don't seem to be able to catch up. A good example of this is there is still no way to let Packagist receive automatic updates on commits. I've given SF a few months now and there still does NOT seem to be anything planned Those of you that followed the link have seen I already have Yapeal over there and now linked to this GitHub version of it. I'm looking at what I need to do to move the Wiki as well not that it got used a whole lot by me or anyone else I never really used the issue tracker on GoogleCode or with SF but I'm thinking I'm going to use the one on GitHub more so don't be surprised if bug reports here don't get replies to do bug report there in the future from me.
Look to hear feedback from everyone about moving both good and bad.
The stuff that's currently at SF will continue to be there and at least where I can I'm just going to have SF auto re-direct you to GitHub once the move is complete so links to the site don't break etc.
Just a couple pointers for anyone wanting to use the GitHub code. The new 1.0.x branch is what you want to use to keep up with bug fixes to the current code. Basically will just change from doing hg clone / pull to using git clone / pull using the new URL of course There is also a new 2.0.x branch where you can look in on or even better help out working on and shape the next version of Yapeal. Just a little warning nothing current is runnable there but hopeful parts of it will start coming together soon(tm).
Okay enough for now I'll get on with the other admin stuff I need to do so I can maybe get back to some coding later today Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.08 21:25:00 -
[166] - Quote
Eto Demerhzel - One of couple things could be going on with the first being CCP changed the API by adding new stuff to it etc. I do NOT think they have but been kind of out of the loop on API updates so possible. Easiest way for you to help figure it out is to make sure you have cache_output in config\yapeal.ini set to either "file" or "both" so Yapeal puts a copy in your cache\account\ directory. Look in that directory and find the *.xml file it saved there and open it and compare it to the one you'll find at http://wiki.eve-id.net/APIv2_Account_APIKeyInfo_XML. If there is any extra attributes than the ones shown in the < row line CCP made some changes and if you'll sent an E-mail directly to my github e-mail I'll take a look at it and see about updating Yapeal. If the file looks nothing like the example than it would also be helpful if you sent it to me.
If the XML looks fine than it's got to be something else and I'd look through the last page or two on this thread to see if there's an answer there. You might also try grabbing the current Yapeal 1.0.x version with composer or git from GitHub. I've pushed out a couple changes that you'll probably want as well from it though the changes shouldn't have really changed anything in the account section APIs just char, corp etc. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.16 17:33:00 -
[167] - Quote
So released v1.0.4 with the fixes for faction and alliance additions to the Eve APIs. Would have put it out a few days ago but had to get a better Windows development environment setup and did some work on another project. Also kind of forgot about it and did some work on some of the other development versions of Yapeal as well before I remembered.
As usual let me know if there's still problems but all the APIs I tests seem to be working right now. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.21 06:06:00 -
[168] - Quote
So I've created a new test branch where I'm doing a lot of clean up on Yapeal. it's the new 1.1.x one and I need some help testing. For anyone that has a test install for their app where they can give it a try and give feedback it would be very helpful. I've been doing what testing I can here and it's running error free but I have only my own keys to test with so not getting much of a workout. I moved almost everything around so you might have to poke around a little to see where things are but bin/ is only new directory really that you might need as config/ and yapeal.php are unmoved but not unchanged.
ADOdb is NOT died yet but I'm continuing to work in replacing it and Logger and the network connection stuff. Plan is to next replacing Logger with Monolog. There is nothing harder then trying to track down an error in what is suppose to report them during development and I'll need something very solid for the other changes to database and network connections.
Anyway please give the new stuff a try if you can and let me know if anything is broken or just doesn't seem to work. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.05.03 18:51:00 -
[169] - Quote
BoomBoss wrote:Hola,
Even though I have set max_allowed_packet=16M it is still giving me below error:
WARN: Insert/upsert failed for erm_serverServerStatus File: C:\yapeal\class\YapealQueryBuilder.php(425)
I am using the latest YAPEAL from sourceforge GitHub. Installed it today without any errors whatsoever.
Any ideas? Does it always break on ServerStatus? That one of the simplest APIs and hasn't changed for a long time. Might try turning on file caching and take a look at the XML and see if it has some different fields. You can find an example over on eve-id Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.05.24 17:44:00 -
[170] - Quote
I really know nothing about GDocs as only one I've ever looked at someone else made and that was a couple years ago so not much help there I'm afraid. I'd point you to http://wiki.eve-id.net/APIv2_Page_Index it usual has some addition (better) docs than what you find from CCP wiki. One thing I do notice is you have 2 x '&' which is incorrect. Other thing that doesn't look right to me but could be is I think it should be "/eveapi/result/key@accessMask". Notice no '/' between key and accessMask. My Xpath is a little rusty so yours might be correct. You might also just try "@accessMask" as there is only one and you shouldn't need the full path to find it.
You say you are getting errors but not what kind: Is it GDocs saying something is wrong? or API servers not understand what they are receiving?
In the end what I'll think you are going to find is your trying to make a speadsheet do a database's job which at some point will fail no matter what. One of the reasons I made Yapeal was to bridge the gap between the Eve Api XML and something that can actually handle the info (DB) so other developers can just worry about their application instead how to make it work. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
|
Dragonaire
Here there be Dragons
54
|
Posted - 2014.05.27 06:13:00 -
[171] - Quote
Good to hear it Zynen. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.05.31 20:10:00 -
[172] - Quote
So as most of you know have been working on updating Yapeal and part of that is a major re-factoring of all the code. I was kicking around some ideas with another developer and he made suggestion to have history of all the APIs. So as it is now the API data is either deleted and re-added on each API pull or the record is updated depending on some internal technical reasons but the end result is the same that basically there is only access to the most current version of the API data and no way to see how things might have changed.
Now since Yapeal is being changed in a major way which will already have some backward compatibility changes I decided to ask if this was something you guys would find useful? Understand the simple way to do it on the design part is to add an auto-incremental column to all the tables and make a few changes to the keys and indexes. The problem becomes finding the most current record in your queries on a per API and ownerID basis for you. Some other ideas were kicked around but the all were more complex and had other problems that we might or might not be able to overcome.
So to the questions: Would you like to see some kind of per API history feature added? Do you think it is worth adding know that probably all of your existing queries will need to be updated?
So let me know what you think and we'll look at it some more based in the feedback I get.
Also if anyone has some ideas on how to add the history but without the drawbacks of how I suggested it could be done please share it and if it works out to being a better way we'll be more than happy to try using it if everyone thinks it the way to go.
As always thanks for using Yapeal. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.02 03:10:00 -
[173] - Quote
True for some APIs doesn't really matter one that we talked about is AssetList where you'd maybe be able to do audits on where stuff goes etc. MarketOrders might be interesting to as you could see how quickly something is selling or coming in which might be useful. Might be a couple others as well. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.03 18:01:00 -
[174] - Quote
Ok understand and after looking into it some more we came to same conclusion plus how hard it was looking programming wise. Something else we MAY do is add an event system to Yapeal so people can tie in to things like API retrieved, pre-store etc if they want to to do other stuff but not at a point willing to say it will make in at this time. Not plan that they will be able to change anything just know what's going on and maybe some read-only access to data in the pipeline to allow people to do their own thing if they want. It has advantage that if you don't need it you can ignore it and doesn't change how you use Yapeal.
Anyway thanks for the feedback. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.11 17:15:00 -
[175] - Quote
Aquila Sagitta - Louis Vitton does have some good points that it helps to know what errors you are getting it also helps to know if you are having problem running yapeal.php itself or one of the install scripts and which version as well but I'll try to help anyway because the basic problem of how to do a empty parameter is the same on the command line. I'll use the install/createMySQLTables script in this example.
Windows: php -f install/createMySQLTables.php -u"YapealUser" -p ""
Notice the two double quotes for the password option. It's really the same idea as in the INI file. Helpfully that get's you past the problem you were having.
Jone Sad - I'll assume you really were trying to be helpful with a sense of humor about you suggestions but it didn't come across that way to anyone. If that was NOT your intent then please don't make those types of post here. I understand you may NOT like post about what you find easy and not related to Yapeal directly but my view on it is helping out someone trying to use Yapeal is always worth doing and when I think they could be better served getting addition help elsewhere I usually direct them to it.
In other news I'll be making an announcement about plans for Yapeal but I'll do it in a different post once I finish up something on my end later today. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.11 22:45:00 -
[176] - Quote
Okay so windows being extra pain here try php -f install/createMySQLTables.php -- -u"YapealUser" -p ""
Note added double dash after script name.
Also per the errors it's returning looks like you deleted or changed something you shouldn't have in the INI file for it to say problem with [Database]. Might try making a copy from the yapeal-example.ini file again and just edit it as needed. Main thing to watch for is no missing quotes and make sure to use double quotes NOT single quotes. Also since using Windows make sure you're not using MS Office etc for edits as it'll replace them with curly quotes which don't work. If you have to try using notepad or any of the many programmer friendly editors out there for free or paid. I current use PhpStorm for my IDE and Notepad++ for extra outside of project edits. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.12 00:35:00 -
[177] - Quote
Okay as I said have Announcement to make about Yapeal development etc.
Some of you might have notice I pushed out a new Tagged version today 1.0.5 and for those of you that read the commit message I expect this to be the last version in the 1.0.x series. All future development is going to be in what is currently know as the 1.1.x series but naming subject to change depending on if I think that semantic version rules require something different. Everyone should start now on getting ready for using the new version as I expect to have fairly complete versions out Soon (tm).
Backward compatibility breaks in 1.1.x:
- Uses PHP Namespaces so minimum version is PHP 5.3 but expected minimum is version 5.3.10 do to some PHP bugs.
- Yapeal uses mysqli instead of mysql for install scripts and PDO for main library. May be moving to PDO only in near future.
- INI config file going away to be replaced by Yaml instead. Other options may become available in the future but INI will NOT be one of them.
- Database changes. Most of these are cleanup on existing tables but several of the util* ones are being change/merge/deleted.
- Many 'That would be cool and someone might use them' minor features are being killed.
- Others I just can't think of right now.
Benefits/ improvements expected with 1.1.x:
- Direct one-shot API calling instead of just automated randomized scan mode. This can be used for thing like web site account sign-up and key verifying.
- Yapeal goes fully OOP. You'll still be able to run it from crontab etc and it is still expected to mostly be used this way but you'll now have option to call the main Yapeal class directly and the per API classes also with little work.
- Uses Composer and Packagist. If you also use Composer in your project this should make using it a one line addition to your composer.json.
- Console tools. Many of the existing scripts used during install and new ones being added will use symfony2/console which should make them much more user-friendly.
- Faster. May or may NOT be noticeable do to network and database operations but should be.
- Testable. Some of the new code already has PHPUnit tests and most should have some before final release.
- Others I just can't think of right now.
By no means are the lists complete but they should give you some idea what to expect. I will also add that changes to both lists are likely but only additions are expected to the first on the second it's more in flux as development is still ongoing. If you have ideas or code you think should be added to Yapeal please contact me as I'm open to suggestions on how to make it better and easier to use for everyone.
If you would like to help please contact me or try out the 1.1.x branch from GitHub. Areas I really need help in is testing as I only have access to a couple keys myself with mostly inactive chars. Bug reports from your testing with more data would be very helpful.
If you like to living on the edge try out the 1.1.x-WIP branch but be warned it's often broken and very incomplete as that's where I and another developer do our development work on the new stuff and often commit Work-In-Progress as the name implies.
Alright I'll end this here and sorry for the long post but had a lot of stuff I wanted to get out. As always thanks for using Yapeal. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.12 02:18:00 -
[178] - Quote
Okay actually looked at the code in testForMySQLDatabasePrivs.php and because of the way it test for the required settings it would NOT allow a empty password. All the other script I sure also would NOT allow it either so sorry I didn't check that part sooner but as my above post shows been busy with other Yapeal related stuff.
Guess the reason it's never really come up before is even on a local only install like with WAMP it doesn't normally let you create a user with a blank password as far as I know. PhpMyAdmin I know doesn't allow them. Easiest fix is just to give the user you want to use a password. Something like 'abc123' is fine if it's only being used for some local testing and behind a good firewall.
I actual use the default user and password from the example file during testing here locally all the time since I don't have anything in it but the public key and sometimes a couple others and nothing but Yapeal using the database. I also been known to dropping all the tables or whole databases several times a day during testing.
Anyway sorry for NOT checking the code sooner but I rarely look at the old code except once in a while to check how I did something before so I make sure to do it differently this time because I like new bugs Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.16 18:55:00 -
[179] - Quote
Tiberius Zol - Did a push to master branch give it a try and see if it fixes your issue. I added issue #14 on GitHub as well for it. I'll have some comment there about it. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.19 23:13:00 -
[180] - Quote
Not really if that's the only error message you get but make sure you updated the DB with the install/ script. You can take a look at the cached XML in cache/char/charCharacterSheetxxx.xml and see if you notice anything that doesn't seem the same as you find at http://wiki.eve-id.net/APIv2_Char_CharacterSheet_XML that might give a clue as well. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
|
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.21 05:32:00 -
[181] - Quote
No and should really only need to update the utilRegistered tables the other's get updated from the API itself and manual changes there could cause problems it's better to just delete info and clear utilCachedUntil so it can pull everything again. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.21 15:19:00 -
[182] - Quote
A copy of the CharacterSheet schema and the XML would be useful I would suggest E-Mailing link to me using one listed in my GibHub account and set them to expire in say a day. Other option is of course to just E-Mail them to me while your at it Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.26 17:57:00 -
[183] - Quote
Alright thought it was time for an update on things. I just did a large 209 commit merge into 1.1.x from the WIP branch with only one minor conflict I'm even more impressed with Git after that then I have been.
So I'll do a quick overview of what's working.
- Account section 3 of 3.
- Api section 1 of 1. New to Yapeal.
- Map section 4 of 4.
- Eve section 3.5 of 13. Faction War stuff not done yet could maybe be done but no way to test. CharacterInfo is WIP and new to Yapeal. Many of the APis in this section aren't something that Yapeal is made to do but at some point may include just to allow users to have a single interface to everything in the Eve APis.
- Char section 12 of 31 APIs. Things like AccountBalance, CharacterSheet, MarketOrders, Wallets are done. Some others like Industrial jobs could be but it just has a lot of columns to do you know Major missing here is AssetList.
- Corp Section 2 of 27. Most of the ones that are same as char section can be done just need some time.
- Server 0 of 1. Can be done just haven't got to it.
For the details on what is and isn't done take a look in the lib/Database/ directory for the GitHub 1.1.x branch.
So anyone that developing a new application it's strongly suggested that you develop against the new code vs the old 1.0.x versions as they are end of live and being depreciated as soon as I feel the new code is complete enough. Existing application can of course continue to use the old version but as it's not going to be receiving any updates and CCP seems to be continuing to make changes to the existing APIs and adding new ones you'll find that things will stop working or you can't add the newer stuff because data isn't available from Yapeal.
So I'm going to just add some somewhat random thoughts here I think would be of interest. First off the new code is faster. Yapeal has always been fast in that the code outside of network and database stuff took less than a quarter of a second to run here locally even on my older laptop. Now though with the move from ADOdb (May it die lonely and forgotten) to PDO the database access is much faster. I'm sure most of that has to do with go from most of the code being badly written PHP in ADOdb to using C code in PDO but also I have done a few things in Yapeal itself to take better advantage of things like transactions and prepare statements which can lead to quicker access.
Yapeal now does a much better job of reusing it's network connection as well which seems to have had a nice speed boost as well. Before Yapeal would re-use the network connection for say all the characters/corprations in one API call but didn't reuse it between different API calls in most cases which cause a lot of slow down. Now Yapeal truly uses just one connection for all the API calls when it is ran. The new network in Guzzle which it now uses IMHO is better too.
I haven't done any real benchmarking but to give you some idea using the same computer with all the current APIs active but need to do network refresh because their caches has expired Yapeal runs in ~20 seconds with my test keys vs the current master taking a little over a minute. Master of course has some additional APIs but just the feel with the new code on a couple of APIs seems much faster than the same thing with the older code.
Anyway think this post is long enough for now so please take a look at the new code and kick it's tires so to say a little and let me know what you think.
Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.27 17:33:00 -
[184] - Quote
Just something I got reminded of today and decided to make post about that everyone should probably take a look at. PHP 5.3 end of life Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.27 20:59:00 -
[185] - Quote
Okay been thinking about the above end of life on PHP 5.3 and thought I'd ask for some input from current users of Yapeal and other people interested in using it. You may have to do a little research with your hosting site for the answer.
If the next version of Yapeal required at least PHP 5.4 would anybody have problems with their site?
Main reason I'm asking is I would prefer with the current re-write to go ahead and make it for PHP 5.4 as there are some features that Yapeal can take advantage of if it's not going to cause to many problems for people. First thing that this would do is allow Yapeal to use PHP traits which because of both the design of Yapeal and the Eve APIs could be very useful.
Anyway would like to hear everyone's thoughts on this. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
55
|
Posted - 2014.07.10 15:37:00 -
[186] - Quote
Just a quick update for everyone. PHP5.4 will be required for the next version of Yapeal as some of the new language structures just make a huge difference on the amount of duplicate code needed. I've spent last week and a half or so on re-factoring a lot of stuff and now many of the class can have only a single method and maybe a single property vs 3-4 methods and several properties. The main thing that PHP 5.4 give is Traits which allows for a more horizontal sharing of code which better fits the APIs vs a parent-child inheritance PHP normally allows.
I'm going to try to get at least a good solid beta/RC version out before the new update to Eve comes out since it'll be making a lot of changes to industrial job and research stuff you'll need to be updating in your applications as well for those of you working with those things.
Anyway as always thank you for using Yapeal, Dragonaire Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.22 16:33:00 -
[187] - Quote
IndustryJobs ad History are out in WIP for testing but need to do some other updates to have corp ones ready as well. I'll be starting some short run jobs to have new test data but looks like they still have some issues at CCP that may cause a few issues too. https://forums.eveonline.com/default.aspx?g=posts&t=360020
I'm personally still downloading updated and should be able to try things out in an hour or less I hope. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.24 01:21:00 -
[188] - Quote
Lots of updates pushed today to 1.1.x-WIP branch including adding the corp versions of Industry stuff for people to try out. All the char versions seem to be working fine so I expect corp ones to be good as well. Fixed one typo (actually bad C/P) in createCorpTables.sql so make sure you update DB.
Just wanted to say something about a as yet to be documented feature of the bin\yc Database:Initialize command. The last thing it looks for is a bin/sql/CreateCustomTables.sql file. This can be used to automatically insert all your registered keys to save having to manually do so. I actually use this myself for that during testing. You can use it for other things as well as any SQL is generally allowed but I wouldn't try something like re-importing all of your tables data etc with it.
Please bug report anything that you find that's wrong and as always thank you for using Yapeal. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.24 18:57:00 -
[189] - Quote
Tiberius Zol - How you install composer is really just copying composer.phar into a directory where you can run it with php CLI so your web-provider doesn't even need to be involved. There are some addition things you can do with it but for simple install and updating that all you need really.
Legedric Striker & everyone - Like always integrating a new library into an existing project can be hard at times or very easy depending on the project. There some questions you need to ask yourself about your project and your plan for it.
I'll assume your project doesn't current use composer already since if it does Yapeal can be added with a single line in your composer.json file.
First question is do you want to use composer in your project? I highly recommend that you do consider doing so as it brings a lot of great stuff with it not the least of which is the easy of changing or adding new dependences and largely solving problems with people having outdated versions of them and your own project. It also comes with a very good optimized class autoloader.
It's requirements aren't that much really either you need to make sure you project uses namespaces and works with a PSR-0 or PSR-4 autoloader. If your project already meets those requirements a simple 'composer init' in the root directory and answering a few questions and your done. You also have the option of just making a composer.json file yourself. Putting your project on Packagest is optional but a good idea as well.
If for now you decided NOT to use Composer then simple add Yapeal using Git like you would any other project you find on Github. If you are using git in your own project I would suggest you look into using GIt's subtree commands to integrate Yapeal with it as it'll make Yapeal more seamless for you. I did that myself in Yapeal to be able to work around some issues using Pimple 2.x because most of the other dependences were made to work with 1.0.x so composer wouldn't resolve to a workable set. By putting it into a subtree I can still use it and everything else can use Pimple 1.0.x as needed. Once everything Yapeal uses converts to version 2.x I can simple drop the subtree and everything is in sync going forward.
Whatever you decided to do make sure you read the INSTALL.md in the 1.1.x-WIP branch as it's been updated with some info on how to install Yapeal including the ZIp file way if you need to.
Legedric Striker - I'll assume since you seem to be following the new INSTALL.md instructions you are using the 1.1.x-WIP branch but you said it reported "problems" but didn't give what kind of problems. I'd need to know what it's reporting to help you try to resolve what's going on. I also need to know if you are using the current WIP or one of the other branches. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.24 23:01:00 -
[190] - Quote
OK just to let everyone know here I've start a new forum thread for the current version of Yapeal which you can find at https://forums.eveonline.com/default.aspx?g=posts&t=360758
Since 99% of this thread is only of historical interest to any current users I thought it was time. I'll continue to monitor this thread for awhile but I do ask that all new posts about any of the 1.1.x stuff got to the new thread as that is all going to be part of version 2.0.x which is where all new development will be done for now on.
Legedric Striker - Try code from master as the other branches are gone now and the code merged there. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
|
|
|
|