open All Channels
seplocked EVE Technology Lab
blankseplocked Yapeal PHP API library (revision 1203 branches/keys/)
 
This thread is older than 90 days and has been locked due to inactivity.


 
Pages: first : previous : ... 6 7 8 9 [10] 11 12 13 14 ... : last (24)

Author Topic

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.08.21 04:38:00 - [271]
 

Don't know if it'll help you much with them but point them to this:
Quote:
Note: If you are using MySQL versions 4.1.3 or later it is strongly recommended that you use the mysqli extension instead.

from the docs for PHP 5 which you can find here and might also point out that mysql ext is in maintenance only mode now which is shown in the table at the bottom of that page and next step is to drop support for it. Hope that extra information can help you to get them to move out of the dark ages Wink

Sable Blitzmann
Minmatar
Massively Dynamic
Posted - 2009.08.23 02:47:00 - [272]
 

Edited by: Sable Blitzmann on 23/08/2009 03:27:47
I'm a bit confused...

I got Yapeal installed, and the databases have updated... But now what? I'm very new to the EVE API, but I was hoping to create a kind of character sheet on my local home server to get acquainted with it and then move on to a bigger community project.

Yapeal is a library of classes in OOP, correct? Which files should I include to pull the information that I need? I guess it's better to explain what I'm looking to do.

For example, I would like to register my character. I would put the userid and API key in two text fields, hit submit, and a new page should display asking which characters I would like to use. I select one, type in the password I would like to use to log into that character, hit submit, and then be taken to a page that displays some basic character information.

Basically, how would I incorporate Yapeal into a web application? I'm not asking anyone to make the application for me, rather to point me in the right direction on which file(s) have functions that can be included and used to pull different types of information. The problem I'm having with Yapeal is that it seems to only run from a terminal; thus, when I complete step one of the registration process (id and key) how would I exchange this information with Yapeal?

Sorry if this post is hard to understand. It's late and I always have trouble explaining things. Razz

Also: The installer gives me errors:
Quote:
Strict Standards: Declaration of dbTable::create() should be compatible with that of dbObject::create() in /home/ryan/public_html/dev/eve/yapeal-read-only/ext/ADOdb/adodb-xmlschema03.inc.php on line 642

Strict Standards: Declaration of dbIndex::create() should be compatible with that of dbObject::create() in /home/ryan/public_html/dev/eve/yapeal-read-only/ext/ADOdb/adodb-xmlschema03.inc.php on line 806

Strict Standards: Declaration of dbData::create() should be compatible with that of dbObject::create() in /home/ryan/public_html/dev/eve/yapeal-read-only/ext/ADOdb/adodb-xmlschema03.inc.php on line 1051

Strict Standards: Declaration of dbQuerySet::create() should be compatible with that of dbObject::create() in /home/ryan/public_html/dev/eve/yapeal-read-only/ext/ADOdb/adodb-xmlschema03.inc.php on line 1302


These are at the top of each step in setup.php... Also, wasn't this supposed to work well in the IGB? I get
Quote:
This setup can only be run in a normal browser and not the IGB. Press the link and you will be popped out of EVE and this setup will re-openned in a normal browser.


Maybe it's because I've already got a running setup? I'll do a fresh install and see...

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.08.23 04:49:00 - [273]
 

Think the problem is you don't understand what Yapeal does for you and how it works. I'll quote from the main page:
Quote:
Here's an extend explanation of what Yapeal does since it a little different then the other PHP API libraries people are using.

It not only grabs the data from the API for you but also saves the data into a MySQL database as well. It was made to be ran from a crontab job and works in the background to 'Auto-magically' as I call it, keep the database updated so all you have to do is work with the database tables not the API and XML. It was made to be set and forget once configured.


So basically it's grabbing the XML data from the Eve API and storing it into database tables for you and you get to write the application that takes the data from the tables and shows it to the web browser in some interesting way Wink

No part of Yapeal works with the IGB as other than the installer/test configurer nothing shows a webpage. There is a little code in all the PHP files now to show their source code in a web browser when passed ?viewSource=1 as part of their URL but that's so people can look at the files with source code highlighting not as any kind of normal operation.

Hopefully that makes things clearer for you. You might also take a look though the wiki as it has some additional information you will probably find useful.

Sable Blitzmann
Minmatar
Massively Dynamic
Posted - 2009.08.23 05:19:00 - [274]
 

Edited by: Sable Blitzmann on 23/08/2009 05:57:49
Edited by: Sable Blitzmann on 23/08/2009 05:53:26
Edited by: Sable Blitzmann on 23/08/2009 05:27:28
Edited by: Sable Blitzmann on 23/08/2009 05:22:07
The wiki and docs are few and far between, but I kinda understand now how Yapeal works. It it run on a schedule, and when it is, it updates everything in the database to their current true values, correct?

Great, that's awesome. However, I'm still having a little bit of trouble understanding how to initially create a user. I know you can manually add them to the database, but I would have thought there'd be an easier way to add the account to the database, and from that pull the characters, and from that register a character. I'm still trying to wrap my head around that part of the process. =)

Also, the IGB thing - I thought there was an installer version being released for the IGB, but I read through the topic more carefully and figured out that this is no longer the case.

Questions: What is a good time to schedule Yapeal? Once an hour? Once every 10 minutes? Every minute? And how fast is the updating if I use this in a community site where there's the potential of thousands of users being registered and updated? Will this put a heavy heavy load on my or CCP's server? Also, since you're not pulling data directly from CCP every time you access a characters info, but instead pull it from a local database, how accurate will that be (I'm sure that's dependent on how often I run the cron, yes?)?

I think this project is awesome by the way. Keep up the good work Very Happy

EDIT: I just foundt he installers test character thing. I assume this is what I'm looking, however, it has a bug. After I put in my API ID and API Key, i get this error:
Quote:
Error EVE API Server if Offline. Please try later.


The EVE api server is not offline, however. And there shouldn't be a problem with my server, because I've been able to update Yapeal and the databases and all the other API information (maps, corps, eve, etc)...

I'll look into this a bit, but I'd appreciate it if the author of that particular function looked over it since I'm not familiar with this project.

EDIT: Seems to be a cURL error. I enabled echo $result['curl_error'];, and this is what it gave me:
Quote:
Couldn't resolve host 'api.eve-online.com'

This stumps me, because I can ping api.eve-online.com just fine from the server...

I remember a while ago my server had problems resolving things used in cURL (just cURL for some reason, ping and whatnot was fine), but I don't understand why Yapeal can access the API site just fine yet the installer can't... Hmm...

Further testing: Running this in the terminal:
Quote:
curl -i "http://api.eve-online.com/account/Characters.xml.aspx?userID=myuserid&apiKey=myapikey"

Returned my character XML sheet like it should...

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.08.23 07:31:00 - [275]
 

Yapeal is made to be ran every minute in a crontab and keeps track of the cachedUntil times itself so it plays nice with the API servers. The data in the database will be update as often as the API allows with a tiny bit of randomness to help disperse bursts of calls to the APIs. As to if the API servers can handle thousands of accounts grabbing all that data that's a better question asked of CCP than of me.

You put your info into the utilRegistered* tables for any characters and/or corporations you want data for. We are currently working on some changes that should make managing available APIs etc in applications easier as all the settings will be in the DB instead of a mix of the DB and the ini file. The installer is last part that needs updated before it's released in the trunk so people can try it. The main programmer for the installer was busy in RL plus his MySQL server had crashed on him and needed re-installed Razz Hope to have new version out this weekend or this next week at latest.

Also look for future version to add a way to call APIs in an 'on demand' basis in addition to the current crontab system. Using that should scale much better for larger web applications while causing less loading of the API servers.

Sable Blitzmann
Minmatar
Massively Dynamic
Posted - 2009.08.23 07:55:00 - [276]
 

Originally by: Dragonaire
Yapeal is made to be ran every minute in a crontab and keeps track of the cachedUntil times itself so it plays nice with the API servers. The data in the database will be update as often as the API allows with a tiny bit of randomness to help disperse bursts of calls to the APIs. As to if the API servers can handle thousands of accounts grabbing all that data that's a better question asked of CCP than of me.


Well, the reason I ask about the server load is because of this: Lets say Yapeal runs every minute. Lets also assume Yapeal is running as a back-end to a web application that serves thousands of EVE's players. Within any given moment, those thousands of EVE players have changing values in their wallet and whatnot. It would seem that to keep the Yapeal database up to date it would have to update thousands of records (maybe more? Shocked) per minute. Now that sounds like a lot to me, but with computers, who knows. Maybe it's nothing. Very Happy

Originally by: Dragonaire
You put your info into the utilRegistered* tables for any characters and/or corporations you want data for. We are currently working on some changes that should make managing available APIs etc in applications easier as all the settings will be in the DB instead of a mix of the DB and the ini file. The installer is last part that needs updated before it's released in the trunk so people can try it. The main programmer for the installer was busy in RL plus his MySQL server had crashed on him and needed re-installed Razz Hope to have new version out this weekend or this next week at latest.


Thanks for the info; looking forward to testing out the new install.Laughing

Originally by: Dragonaire
Also look for future version to add a way to call APIs in an 'on demand' basis in addition to the current crontab system. Using that should scale much better for larger web applications while causing less loading of the API servers.


I think everyone would appreciate this. I've looked through the code and it seems like it wouldn't be too difficult to modify bits and pieces here and there so that you can easily include a lot of these classes right into webpage's and applications. For example, and from what I can tell, you already have the classes to call for API info from either fresh from the server or the database using YapealApiRequests(). Any ETA on when something like that would be available?

I really look forward to studying and breaking down this code. You've done a very good job with this cool project. It's been a while since I've been active in coding, and I think I'm gonna start my reintroduction with this Very Happy

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.08.23 15:01:00 - [277]
 

If you look through the revision history of Yapeal you'll see where it's gone from a completely procedural library to a nearly completely class based one over time as it has been refined. The changes that I'm currently working on will move it farther in that direction and will add some new or at least better refined options for proxy support and other things. All the changes are coming about because of some need that the development team has thought of, has come up during development in EMPA or one of our other projects, or been brought to our attention by someone using it. Some of the things that are being added to Yapeal now or are looking at adding are things that we said no to in the past. There have been many reasons for saying no to stuff in the past the main ones being:

  • The state and design of the code at that time just didn't support it

  • The main developer (me) didn't have time to do it

  • The problem wasn't explained well or more often mis-understood by the developers

  • Developer knowledge and backgrounds.


On that last point in my own case this was only my second PHP project though I've programmed in many other mostly procedural languages on projects before. For some of the other developers this was their first project ever in anything or at least in PHP. We have also had developers with more experience helping along the way too.

Time frame for the 'on demand' code is unknown at this time but is being developed by us for a designer of another project with a large community of Eve users (Thousands of users) as part of a re-coding project on their site. It'll be some time after the current changes we're working on as some of them are needed to make it work. So figure on any where from a week to a month or more depending how that project goes and when we get these current changes done.

Sable Blitzmann
Minmatar
Massively Dynamic
Posted - 2009.08.23 16:02:00 - [278]
 

Thank you for your helpful and thoughtful responses. =D

Can't wait to see what the devs come up with.

Sable Blitzmann
Minmatar
Massively Dynamic
Posted - 2009.08.25 19:30:00 - [279]
 

I have another question relating to SVN...Embarassed

I'm new to SVN, so i don't really know the mechanics. If I were to add my own notes to the source files, and then I updated to the latest revision using `svn up`, would I lose all my edits? Or will ASVN know to ignore my additions and just add yours?

Cadeyrn Gwrtheyrn
Posted - 2009.08.26 00:16:00 - [280]
 

Originally by: Sable Blitzmann
I have another question relating to SVN...Embarassed

I'm new to SVN, so i don't really know the mechanics. If I were to add my own notes to the source files, and then I updated to the latest revision using `svn up`, would I lose all my edits? Or will ASVN know to ignore my additions and just add yours?


It will try to merge the files, but don't count on it always working

Sable Blitzmann
Minmatar
Massively Dynamic
Posted - 2009.08.26 00:49:00 - [281]
 

lol, I thought that's what might happen. Thanks! Smile

Sable Blitzmann
Minmatar
Massively Dynamic
Posted - 2009.08.28 04:49:00 - [282]
 

Edited by: Sable Blitzmann on 28/08/2009 04:51:44
I'm still playing around with it. I finally got cURL working on my server so I've been testing a lot of things out. Question: the corp stuff only works if you are the CEO of said corp, correct? Because I put in my characters info AND my corps info into the appropriate util* tables, yet when I go to run yapeal.php, it returns errors.

I assume then that I must be CEO of that corp or have some sort of role (of which I do not have...), thus making the corp API's useless to regular corp members...

Do the character APIs export the characters role in his or her corp so that I can use that to narrow down what options are available for that character? For example, if a regular corp member without roles registered on the site, I do not want to insert anything into the utilRegisteredCorp table. If the corp accountant registers, I only want to enter into the `activeapi` column the API's that character can access.

Also, how does yapeal handle character deletions and role removals? If a character was removed from a role, will yapeal update the database to reflect this?

So many question, I know, but I'm very intrigued with this project.

Johnathan Roark
Caldari
The Graduates
Morsus Mihi
Posted - 2009.08.28 06:35:00 - [283]
 

Originally by: Sable Blitzmann
Edited by: Sable Blitzmann on 28/08/2009 04:51:44
I'm still playing around with it. I finally got cURL working on my server so I've been testing a lot of things out. Question: the corp stuff only works if you are the CEO of said corp, correct? Because I put in my characters info AND my corps info into the appropriate util* tables, yet when I go to run yapeal.php, it returns errors.

I assume then that I must be CEO of that corp or have some sort of role (of which I do not have...), thus making the corp API's useless to regular corp members...

Most of the corp APIs need the character to be either CEO or director. I think the only exception is corpMemberTracking which would just have missing data. I'm not positive how yapeal will treat the missing fields.

Originally by: Sable Blitzmann

Do the character APIs export the characters role in his or her corp so that I can use that to narrow down what options are available for that character? For example, if a regular corp member without roles registered on the site, I do not want to insert anything into the utilRegisteredCorp table. If the corp accountant registers, I only want to enter into the `activeapi` column the API's that character can access.


I am rather sure that is data only a director or ceo can get from the corpMemberTracking api. The easiest way would be to try an pull an api that only a director can get and see if it returns an error, 209 Character must be a Director or CEO.

Originally by: Sable Blitzmann

Also, how does yapeal handle character deletions and role removals? If a character was removed from a role, will yapeal update the database to reflect this?


Roles being changed should get updated. I am not sure what it would do for a character deletion.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.08.28 06:38:00 - [284]
 

Some corp APIs can be access with some of the other roles but basically you do need to use the CEO's or a director's full API key to access stuff and the best info for that is to look at info from eve-dev wiki and/or stuff at Chucker's site which are in the sticky above.

As it is now the roles aren't being updated correctly but that will be fixed when I do the next merge from the current branch I've been working on. There will also have some what more intelligent handling of some of the API errors so it can auto deactivate users, chars, corps, and their APIs. I'm hoping to merge the new stuff into trunk on Friday or at latest this weekend. When I do I'll try to post a good list of all the changes that have been made and bugs fixed.

Yes the roles are in the character sheet so you can see what roles and titles they may have in their corps.

M4g3ll4n
Sacred Templars
RED.OverLord
Posted - 2009.08.28 07:51:00 - [285]
 

Hi,

I have a short question regarding adding of corporation API keys. I would like to add the key of a director of a second corporation. How do I do this?

Just alter the yp_utilRegisteredCorporation table?

Thx in advance,
Mag

P.S.: Ypeal is a genious tool, as base for development of own API based applications.

Sable Blitzmann
Minmatar
Massively Dynamic
Posted - 2009.08.28 08:30:00 - [286]
 

Thanks for all the great work Dragon.

I do see one corp API that any corp member can access: `corpCorporationSheet` This just gets basic (and from what I can tell, public) details about the corp. So there is a reason to add a corp to the untiRegisteredCorps, even if that character doesn't have any roles. =)

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.08.28 18:14:00 - [287]
 

Edited by: Dragonaire on 30/08/2009 18:07:21
OK here is a mostly complete list of the changes in Yapeal.
  • All the Eve API classes have had some code cleanup done to them

  • New abstract classes were add and are used by all the Eve API classes now

  • The inc/pull*.php files have been replaced by new class/Section*.php files

  • Much of the code dealing with API sections in yapeal.php have been moved into the section files where it now belongs

  • Required memory footprint for Yapeal have been reduced by breaking up the larger API upserts into 1000 record pieces instead of one huge upsert. This should keep it's memory usage under 16MB. Let me know if not and we'll look at it some more

  • Most error and tracing log messages have been updated and should be shorter and more useful then before and not grow at such an alarming rateWink

  • Yapeal should make less connections to the MySQL database server by re-using existing connections which should make the DB admin much happier

  • Yapeal now uses SPL Iterators directly in many of the new/updated classes and in functions and methods where it didn't before

  • New utilSections table was added to database and some new fields were added to the utilRegistered* tables to support the new proxy config stuff

  • config/yapeal.ini has been change with many of the settings having been move into new utilSections table to make managing them in an application easier

  • Now each char/corp can have their own proxy setting as well as each API section can have it's own default that will be overridden by the individual char/corp ones

  • Yapeal is now more proactive when it come to dealing with Eve API errors by deactivating users, characters, corporations, or individual APIs of any of them as needed and logs an error message when doing so. Currently logging this as warning so that it is visible with default logging settings but may change to notice instead depending on feedback we receive from application developers

  • Yapeal now 'soft' limits how long it will run to approx. 5 minutes

  • SkillInTraning API has been added. It got missed somehow at time SkillQueue was being added and no one noticed Embarassed

  • Yapeal doesn't pretend to be Firefox when connecting to the Eve API servers/proxies anymore but uses an agent string something like: 'Yepeal/861beta (Linux i686) libcurl/7.19.0'

  • Many other changes that I'm sure I've forgotten as they had little effect outside Yapeal itself or were at least less memorable if it didSmile


Everyone should make a backup of their DB before updating to this revision of Yapeal, then make another one just to be sure Wink

Anyone run a revision of Yapeal before about revision 800 will probably have some problems upgrading because of all the changes to both the code and DB.

Everyone needs to run install/setup.php from a webbrowser and it should update the DB and config/yapeal.ini for you.

I will try to document the changes more on the weekend. For anyone that is really interested in understanding the code have a look at https://yapeal.googlecode.com/svn/docs/Developer Guide/phpDocs/ where you'll find two updated versions of phpDocs in HTML format.

revision 857

Sable Blitzmann
Minmatar
Massively Dynamic
Posted - 2009.08.28 19:42:00 - [288]
 

Edited by: Sable Blitzmann on 28/08/2009 19:43:04
EDIT: nvm.

Awesome stuff, btw

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.08.30 18:17:00 - [289]
 

Ok here's a list of some bugs that were fixed:
  • Sub-tables of CharacterSheet like rolesAt* and titles were not clearing old data. Now the old data is delete before adding new ones so no one just accumulates rolesRazz

  • Same type of fix was done on several other APIs that had same problem as above with accumulating stuff

  • Time out error exceptions, etc. from cURL were not being handled at all in the API files. They are now catching these exceptions correctly

Teavan
First CityWide Change Bank
Posted - 2009.08.31 14:17:00 - [290]
 

Is it typical to get "Expected before ref/trans ID = 0: wallet not previously loaded." issues when executing yapeal.php with a cron job? It successfully pulled the info on the first execution, and the time difference is not long enough, but I figured yapeal wouldn't try to pull something it knew should be cachedUntil.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.08.31 15:41:00 - [291]
 

Even if you obey the cachedUntil time sometimes you get that error it's a pain in the A$$ that the Eve API servers sometimes get behind on their accounting for which ones you've got already (I've added all kind of delays, etc to try minimize the number of errors) but sometimes you'll still get a few Razz You'll also get some of those errors if you stop and restart the MySQL server as the utilCachedUntil is stored in memory and is cleared every time you restart it. So to directly answer you question yes it normal to get a few of those from time to time but it should only do it once in a while usually when the API servers are under heavy load or having other issues.

Teavan
First CityWide Change Bank
Posted - 2009.08.31 16:01:00 - [292]
 

Thank Dragonaire ... nice piece of software, very much helped to jump start my latest project.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.08.31 16:34:00 - [293]
 

Just was going through my logs this morning and noticed some errors with the new exception code functions Razz Everyone should grab revision 867 BTW Teavan it could have been related to the extra error messages you were seeing as it was effecting updating the utiCachedUntil table.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.09.01 06:01:00 - [294]
 

How can something work without any errors for a week then after merging it into trunk it starts throwing all kind of errors and exceptions Mad Anyway give revision 870 it has the fixes.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.09.01 16:38:00 - [295]
 

Think I've finally fixed a long standing bug with KillLog, WalletJournal, and WalletTransactions walking code where it would throw mostly errors instead of working right. As goes with most errors of this type the fix was simple and easy to do once found Razz

revision 873

Teavan
First CityWide Change Bank
Posted - 2009.09.02 18:38:00 - [296]
 

Ok, a few things:

1.) I know I uploaded revision 870, yet when it runs it says 862. Forget to update something?

2.) I can't say for sure it is yapeal, but after an hour or so I can't seem to run yapeal manually, it never finishes. When running it with a crontab every 10 minutes, the entire system would get locked up within 24 hours. Any ideas on what to check? I checked the yapeal_error.log file and it is blank.

3.) Has work already begun on a Corp_MemberSecurity interface? I'd like access to the roles for my project and I can handle writing the file for yapeal if it is necessary, but I don't want to waste my time if its already in the works.

I apologize if any of this has been answered before.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.09.03 16:12:00 - [297]
 

Edited by: Dragonaire on 03/09/2009 16:24:11
I haven't been changing yapeal.php that's why the revision number doesn't change. That's cause by way svn works I'll have to remember to make minor change to it so it'll update too once in a while Wink As to the locking up problem I don't know why you're having problem as I've been running it even minute in crontab for several days without any problems. I would suggest you setup your crontab correctly by having it run every minute.
* * * * * /path/to/yapeal/yapeal.php
By not letting it run every minute you're keeping it from doing part of it's job correctly which is pulling the APIs by the cachedUntil times and also it tries to even out server load over time with some randomness which also won't work as well with running it only every 10 minutes.

To get more error logging to see what's going on try these settings in config/yapeal.ini:
cache_xml=TRUE
log_level=E_ALL|E_STRICT
trace_active=TRUE
trace_level=2
trace_sections=YAPEAL_TRACE_ALL

That should give you a LOT more logging that may point to where the problem is.

As far as I know no one is work on MemberSercurity if you want to work on it send an E-Mail to the project manager's G-Mail with your G-Mail account and I'll add you to project and we'll setup a branch where you can work on it in the svn.

revision 878

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2009.09.04 15:22:00 - [298]
 

An issue has been reported with the MemberTracking API in issue 20 only storing the last corp member for each corporation. Thanks for the error report Matthew. You can read about the fix in the issue.

I've also corrected an error that was leaving all the Eve API error XML files in the main cache/ instead of cache/{section}/.

Revision 880

Garo Hertee
Posted - 2009.09.05 17:00:00 - [299]
 

What a fantastically useful library. Thanks Dragonaire. Having set it up and got it running, I hit issue 20. I came on here to report it only to find it had already been fixed. Very nice.

Elnar Khad
Minmatar
Legion of the Locust
Posted - 2009.09.06 16:38:00 - [300]
 

Let me say, thank you to everyone who has worked on this project. It is very well thought out and will be very useful.
I'm coming up against a wall during setup of the scripts. I have followed the windows version of the setup and most things seem to be working. It is correctly pulling down server, map and alliance information, and pulling the characters out of my accounts correctly. The only things that are not getting put into the database are the items that I put into the "ActiveAPI" fields in the utilregisteredcharacter and utilregisteredcorporation tables. Per the instructions, it should be "char" or "corp" and then the name of the api, so I'm putting in items like:
Quote:
charAccountBalance charAssetList charCharacterSheet charIndustryJobs charKillLog charMarketOrders charSkillInTraining charSkillQueue charStandings charWalletJournal charWalletTransactions corpAccountBalance corpAssetList corpCorporationSheet corpDivisions corpWalletDivisions corpLogo corpIndustryJobs corpKillLog corpAttackers corpItems corpVictim corpMarketOrders corpMemberTracking corpStandings corpStarbaseDetail corpCombatSettings corpFuel corpGeneralSettings corpStarbaseList corpWalletJournal corpWalletTransactions


I am not seeing any errors in the logs, and the yapeal/cache/char and corp folders are not getting xml documents.

I've been staring at this for days and I don't see what I'm doing wrong. Any ideas?
Thanks,
Elnar


Pages: first : previous : ... 6 7 8 9 [10] 11 12 13 14 ... : last (24)

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only