EVE Search - Yapeal PHP API library

Check My IP Information

All Channels

EVE Technology Lab

Yapeal PHP API library

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

Monitor this thread via RSS [?]

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 [15] 16 17 18 19 20 .. 24 :: one page

Author	Thread Statistics \| Show CCP posts - 0 post(s)
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.22 18:36:00 - [421] All char APIs do have a ownerID=charID and corp ones ownerID=corpID.The rest of the table are either admin tables for Yapeal (util) or general tables that don't have an owner really like the eve, map, server ones. The one from account is of course keyed to userID. Hope that helps if you need help with a particular table let us know and someone can give you an example I'm sure. You might also look back through the thread here as there is a lot of information on how things work in Yapeal in many of the posts as well plus in the wiki. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Lonestar Leo	Posted - 2009.12.23 11:20:00 - [422] Hi, I just tried your your library and it looks promising .) The installer didn't work: ./Yapeal-948-linux-x64-installer.bin Error: Error running /usr/local/include/php -f "/tmp/Yapeal/install/testForPHPVersion.php" : /bin/sh: /usr/local/include/php: Permission denied Press [Enter] to continue : I used the svn version then and that worked... only the mail api produces an sql error on inserting into the charMailMessages table.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.23 17:50:00 - [423] Try the latest SVN revision 949 for the problems with charMailMessages as it has a couple fixes. As to your problem with installer version it looks like you didn't point it at a CLI version of PHP but either a CGI version (though it should work now too) or just the directory where it could be found and not the actual program. I probably need to make the instructions clearer that it needs to be set to the actual program and not just path to it. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Lonestar Leo	Posted - 2009.12.24 08:51:00 - [424] it is still in the latest svn... the query was: insert into `yapealcharMailMessages` (`messageID`,`ownerID`,`read`,`senderID`,`sentDate`,`title`,`toCharacterIDs`,`toCorpOrAllianceID`,`toListIDs`) values (290720362,544714069,1,1001474112,'2009-12-18 07:33:00','Aw: Aw: xxx','544714069',,''), on duplicate key update `messageID`=values(`messageID`),`ownerID`=values(`ownerID`),`read`=values(`read`),`senderID`=values(`senderID`),`sentDate`=values(`sentDate`),`title`=values(`title`),`toCharacterIDs`=values(`toCharacterIDs`),`toCorpOrAllianceID`=values(`toCorpOrAllianceID`),`toListIDs`=values(`toListIDs`)
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2009.12.24 14:09:00 - [425] Make sure you run install/setup.php again at least also as there is a DB update that is needed to fix it as well as the update to the code. Have a look at http://code.google.com/p/yapeal/issues/detail?id=25 for more information. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.03 13:42:00 - [426] In trunk/: Implemented suggestion by gilgamoth from Issue 22 to set cachedUntil time to +6 hours on API error 902 and also 901. This should greatly reduce the amount of error spam when the API server is down which seems to have become all to common IMHO. Update handling of fullAPIKey and limitedAPIKey from utilRegisteredUser during API fetching. Now will use either with fullAPIKey having priority. Small change to the utilRegisteredUser table and some updates to the class/Section* files' SQL so they can use either key. Make sure at least one of the keys is set or expect some nasty error messages Alpha from Downloads: For those of you having problem during install with the DB tables not being added etc. Try selecting 'Advanced' install option and it should work. Seems one or more bugs have come up in 'Legacy' option since I've been working mostly on 'Advanced' option during development. I'll be looking in what needs fixed soon(tm) For those trying out Linux versions on some distros you may have notice it aborts with an error message before it even seems to get started This is caused by a error during initiation while trying to auto detect path to PHP and it's version. I have someone testing a fix for that now and plan to release updated version later today. Been making some progress on options to add test user/char/corp to utilRegistered* tables which is last feature I planned to add. Once that is done a general bug hunt and cleanup is planned which should lead to moving all the changes to trunk/ and the retirement of the old install system. revision 953 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Qoi New Eden Warriors	Posted - 2010.01.03 15:16:00 - [427] I'm using php 5.3 and yapeal revision 953. The corp AssetList contains 23633 Entries. When updating corpAssetList, i get this warnings: WARNING: Message: SimpleXMLElement::addAttribute(): Attribute already exists File: /home/niklas/yapeal/class/api/corpAssetList.php Line: 186 WARNING: Message: SimpleXMLElement::addAttribute(): Attribute already exists File: /home/niklas/yapeal/class/api/corpAssetList.php Line: 170 In total I get 302607 Warnings per yapeal run and yapeal takes 2.6 Gigabytes of Memory. The AssetList in the database seems to be okay. The callstack for the first warning is: editAssets(&$obj); editAssets(&$obj, 0, 2, 0); editAssets(&$obj, 0, 2, 0); editAssets(&$obj, 0, 32, 1); editAssets(&$obj, 0, 33, 1); editAssets(&$obj, &$obj, NULL, 2); With the last call leading to the warning - i don't think the second argument should be an object at all? (It's an simplexml object)
Scribbly	Posted - 2010.01.03 22:42:00 - [428] Hi there This is the best thing since sliced bread! One problem I am having is when inserting into charMailMessages, perhaps there is an extra ' in the mail message which is messing things up? I will investigate more One question...What is the method for upgrading to a newer version? At the moment I am deleting everything and reinstalling although this is becoming a bit of a pain as I am loosing all my history?
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.03 23:19:00 - [429] Qoi - Please try the new revision and see if it helps with some of your warning messages. If it doesn't clear them up please contact me through my G-Mail account which you can find by looking at the project owner for Yapeal and I'll have you give me some more details and try some things. Scribbly - Usually you can just install the new version right over the top of the old without any problems. If you're using the SVN version you probably need to run install/setup.php at least to let it update any change in the DB tables which BTW you don't have to clear like you've been doing as it can update them with the data in them. The new installer is also made to update the DB tables with data in them though there are some bugs right now that would probably make you have to use the 'Advanced' option. revision 954 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.04 05:40:00 - [430] New version of the 'Alpha' installer out which should have fixed the errors with Map section and the problem with auto-detecting PHP under Linux. 'Legacy' should work correctly now as well as 'Advanced'. revision 955 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Ramov Tinoga Tinoga Enterprises	Posted - 2010.01.06 11:15:00 - [431] Originally by: Dragonaire New version of the 'Alpha' installer out which should have fixed the errors with Map section and the problem with auto-detecting PHP under Linux. 'Legacy' should work correctly now as well as 'Advanced'. revision 955 I've installed the Yapeal-955-linux-x64-installer.bin (Advanced Setup) on my openSUSE 11.0_x64 and it worked fine once I gave the yapeal database user all rights on the yapeal database. I was a bit reluctant to update my old yapeal version manually, so the installer is really helpful and takes care of everything. -----
M4g3ll4n Circle of Shadows Black Swan.	Posted - 2010.01.08 13:36:00 - [432] Hi, at the moment I am running "Yapeal Revision: 940" on webspace (no dedicated server or vserver, etc). How is the best way (or are the steps) to update Yapeal to the actual Revision? Thanks in advance. Mag P.S.: Awesome tool! Circle of Shadows - Recruiting now www.eve-cos.info
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.08 15:40:00 - [433] How you upgrade Yapeal depends if you're using SVN or trying out the new installer version. With SVN you can use the normal 'svn up' to do it or 'svn export --force' if you use an export to keep from having .svn/ directories in web accessible locations on your server. For a somewhat more detail set of instructions that were written for Windows you can have a look at the Wiki With new installer you should find install/autoupdate-* file that you can run that works much like the installer and will check for newer versions and give you option to update to the newest revision. If you don't see autoupdate-* then you can also just grab the latest download and run it and it'll overwritten the existing install as well and then you should have the autoupdate-* to use in the future. In general updating Yapeal is mostly a matter of overwriting outdated files with new ones, adding any new ones, deleting unused ones, and then sometimes making updates to the database tables and ini file, all of which you can do manually but using svn and install/setup.php or the new installer are much easier and far less error prone of course -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.09 09:01:00 - [434] Ok a week later then expected but I've finished adding all the test user/character/corporation stuff to the new installer. It's ready to be used a bit more now. It's still not full production ready but if you make some good backups of your data it would be useful to give it a try. There have been a few changes to the util tables like adding CorporationName to the utilRegisteredCorporation table. Some things that the installer does that the old one didn't is it will add all your characters and their corps to the utilRegisteredCharacter/Corporation tables but only make the ones you select active. For more information about changes that were made look through the commit notes as well. revision 959 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.15 09:05:00 - [435] Ok did some clean up and bug fixing on the new installer. I've also enabled option for it to check for new updates on install so it can do the job of the autoupdater as well so you can always make sure you have to latest version revision 961 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Qoi New Eden Warriors	Posted - 2010.01.16 08:02:00 - [436] Edited by: Qoi on 16/01/2010 08:03:12 I was able to succesfully reproduce my problems on several systems (linux x64) with several php 5.3.X versions including HEAD and latest stable http://bugs.php.net/bug.php?id=50670 I optimized the code (it uses 70% less memory for CorpAssetList now with php 5.2.X) but still I get very high memory usage under php 5.3, i guess there is something terribly broken :/ To make that clear: it's php that is broken if you ask me, not your code
Xaroth Brook Minmatar BIG Libertas Fidelitas	Posted - 2010.01.19 11:31:00 - [437] Dragonaire, First of all, nice work so far, it was some getting used to due to not having that much information about it, but I got most of it working. One bit I didn't get working was this: If you have multiple characters belonging to the same corp, you can still only enter 1 item -per corp- in the utilRegisteredCorporation table.. as such, once there's already somebody in that list with limited view rights (say, normal member), you'll have to manually confirm that the character you are trying to add for that corp has more access than the one already in place, then replace the entry. how when you then remove that second character, adding the first could be possible with some logic, but then the system would again, try to load API sections it shouldn't be loading. a small proposed change for this: allow multiple character-corp entries (and linked as such, primary key on characterID or so), that each have their own activeAPI list. then, per corp check the list of characters (so you know which api key to use), and check which activeAPI they have set, start with the character that has the most (after verifying it works, obviously), if another character has access to a sheet that hasn't already been processed, use that character to retrieve the information as such you would end up with a relation like this: character - access Char1 - A B C D E Char2 - A B C D E F G H Char3 - A C D E F G H I J K L The system should then use Char3's key to retrieve A (not B as it doesn't have it) C-L .. after loading it should notice that B hasn't been loaded, and that Char2 (seeing it has the most lists available) has that.. 1+1=3, use Char2's access to Load B, and yer done. that way, if any of the characters gets removed at a later point, the system will remain functional (albeit less data being processed).. also, a new character added to the list with all access will be checked first to verify it's access, after which proper access will be used to pick up the remainder. It was like a baby, it landed on my lap and was helpless and totally defenseless. Then I shot it and bragged about it on a killboard.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.21 08:57:00 - [438] Quote: it was some getting used to due to not having that much information about it Yeah I know but I do try to document the code fairly well to help out. You can even do a SVN checkout of some auto built webpages for it from here. It's mostly made for Yapeal developers to use but there's stuff in that can be of use to everyone. Quote: If you have multiple characters belonging to the same corp, you can still only enter 1 item -per corp- in the utilRegisteredCorporation table.. as such, once there's already somebody in that list with limited view rights (say, normal member), you'll have to manually confirm that the character you are trying to add for that corp has more access than the one already in place, then replace the entry. The 'best' way to find the character to use is look at their roles in the corp from the character sheet API tables and select one that has 'Director' role and insert them into utilRegisteredCorporation. If none of the available characters have that role use the one that has to most roles that cover the API access you want. That's something best done/decided in the application code not Yapeal IMHO. Quote: allow multiple character-corp entries (and linked as such, primary key on characterID or so), that each have their own activeAPI list. The problem you run into trying to having more than one entry in utilRegisteredCorporation for a corp is you could end up trying to pull the same API more than once and the 'second' one to do so will always receive an error from the servers and cause un-needed increase in server load plus risk chance of having you IP banned from API from not obeying the cache timer -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Trader Hek Contingency.	Posted - 2010.01.22 16:50:00 - [439] I checked out the latest from svn and tried to install. I recieved a failure on importing char.xml during install. I had to edit /install/char.xml LINE 634 From : <field name="`remainderPoints`" type="F" size="52"> To: <field name="`remainderPoints`" type="F" size="5.2">
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.22 21:27:00 - [440] Yeah sorry about that ended up committing something to trunk instead being in a branch to test it You'll probably find that WalletJournal for characters fails also I'm going to revert the changes to it and just have the new Research API added until I work out my bugs with the Journal. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.

Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.24 23:41:00 - [441] Ok sorry took this long but had a couple other things going on in RL that kept me from getting the corrected update for Dominion 1.1 patch out. The new charReseach API should be working now and charWalletJournal updated with new tax columns. As always let me know if something isn't working I should have updates merged into installer downloads later or by tomorrow at latest. revision 968 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.01.31 05:10:00 - [442] Minor update to let Yapeal be run with CGI instead of CLI which should make it a little easier to use with some web hosts. Limited testing but worked for me To use it from CGI you may need to change the first line in yapeal.php to read #!/usr/bin/php-cgi -Cq on Linux/BSD. The path maybe different on your system but that one should work for most people. I'll merge trunk into branch I use for installer version after a little feed back from people using it with CGI then release update for them as well. If you want to try it out you can copy the updated yapeal.php, /inc/common_backend.php, and /class/YapealAutoLoad.php from trunk/ and see how it goes. For anyone that's been having problems running Yapeal from php 5.3 or latter you may need to change your php.ini file to allow 64MB memory as PHP now does proper accounting for memory use by it's extensions so you now have to deal with how much memory things like MySQLi and SimpleXML are truly using. So far in testing 55MB was highest I've seen reported but 64MB would be a nice round computer number to use revision 970 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
KtoJest Minmatar Silkroad Partners	Posted - 2010.01.31 11:12:00 - [443] hi- just got into 'nested sets'. thanx for the examples. Caveat Emptor -a trader's blog
Roomsy	Posted - 2010.02.01 21:00:00 - [444] Hi I think i'm being a complete numpty here but what is the password that your asked for at the end of the /install/setup.php web based setup? The DB password doesn't work and I can't seem to find a default password anywhere. I did the setup by using the latest svn 971, created a new db and user with full permissions. The database is populated but I can't log in.
Roomsy	Posted - 2010.02.01 22:13:00 - [445] Originally by: Roomsy Hi I think i'm being a complete numpty here but what is the password that your asked for at the end of the /install/setup.php web based setup? The DB password doesn't work and I can't seem to find a default password anywhere. I did the setup by using the latest svn 971, created a new db and user with full permissions. The database is populated but I can't log in. ok, seems I.E 8 jumps the page where you set the password.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.02 22:22:00 - [446] Ok finally got around to making a change to how Yapeal figures out the required and optional column types for ADOdb during table inserts. This change should have no effect on application developers but should make updating and adding new APIs easier in the future. Before the developer was required to put together the list manually for each table when adding a new API now ADOdb can figure it out for itself from the DB table This change has already highlight one minor bug in the StarbaseDetails tables that was missed with sovereign changes. I have a few days off and plan on looking into high memory use that has shown up with switch to PHP 5.3. I've tracked it down to the allianceList API but could also effect some of the other large APIs as well. I'll be trying out some different coding in a branch to see what I can do to reduce usage. I probably won't be updating the downloads with what I've been working on until after I finish one or two more of these type of changes but once they are in trunk/ I'm merge them out to that branch again and release update for them. I had a report of the autoupdater not working right and need to look into what changes I can do to make it work smoother before continue with work to merge that branch back into trunk/ as well. trunk revision 973, download revision 969 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.07 10:49:00 - [447] Ok added feature to Yapeal that I've wanted to do for a long time and just never seemed to get around to. You can now have XML cache to the database instead of or in addition to files in cache directories To enable the new caching you'll need to update config/yapeal.ini in the [Cache] section by changing cache_output="file" to either "both" or "database" depend on if you want to use database caching in addition to files or instead of. The XML cached in the database if valid and not expired has priority over the files during fetch so keep that in mind if you decide to use both and wonder why changes in the cache files during testing don't seem have any effect trunk revision 981, download revision 969 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.14 04:50:00 - [448] Ok I've finally finished what I can do for now on reducing memory usage in Yapeal and seem to have cut it in half at least for now from over 50MB down to 21MB or so in my testing. Farther cuts will have to wait until I can do some in-depth code profiling and tracing. That brings me to something else I've done. All the old tracing stuff have been removed to make way for an improved system that will probably be based on Xdebug instead. The time frame for adding the new code to do that is unknown at this time as changing over to the new install system and totally removing the old one is next planned thing to got finished. I have ideas for several things I'd like to add to or change with new installer but which of those get done before merge is still not decided yet but most will probably be put on hold until after merge. revision 986 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Dragonaire Caldari Corax. New Eden Retail Federation	Posted - 2010.02.14 10:26:00 - [449] I've updated the downloads to latest merge from trunk/ trunk revision 986, download revision 987 -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
Mahoosiv	Posted - 2010.02.14 13:32:00 - [450] Probably numpty time, but I have installed the Linux version via ssh and it reports back just fine, db tables all created and so forth, i can even run yapeal from the command line and no errors. However despite installing in 3 diff locations, no setup.php file is created/found in the install dir. Is this a feature or is something not correct? Mahoo



Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 [15] 16 17 18 19 20 .. 24 :: one page
First page \| Previous page \| Next page \| Last page

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