Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 [16] 17 18 .. 18 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Somerset Mahm
Cognitive Distortion
226
|
Posted - 2014.01.21 23:11:00 -
[451] - Quote
Zynen wrote:Thanks for making and maintaining yapeal! Question - I'm looking at this API Call - http://wiki.eve-id.net/APIv2_Corp_StarbaseDetail_XMLAnd I can't find the data anywhere in Yapeal. I see corpStarbaseDetail, where I think it should be. But it's nearly a mirror of corpStarbaseList. I don't see any of the combat settings, etc. Can anyone tell me where to find corpStarbaseDetail information in Yapeal? I checked SourceForge Issues, but I didn't see it listed. So perhaps I'm just missing something.
They get extracted into several sibling tables. For example combat settings for POSes are in corpCombatSettings, and there is a posID field that you can reference. SOMER Blink Microlotteries that finish in minutes! Running for over 2 years :) |
Zynen
0
|
Posted - 2014.01.22 02:54:00 -
[452] - Quote
Somerset Mahm wrote:
They get extracted into several sibling tables. For example combat settings for POSes are in corpCombatSettings, and there is a posID field that you can reference.
Much appreciated! |
Umnumun
Fweddit I Whip My Slaves Back and Forth
3
|
Posted - 2014.01.22 06:55:00 -
[453] - Quote
Drapko Nitzhonot wrote: Actually I have utilRegisteredCharacter and utilRegisteredCorporation empty. I track Characters and Corps with only utilRegisteredKey table.
Hmm okay. I have this in the utilRegisteredKey table and it doesn't add a new key. Feel free to point out how wrong I am....
http://pastebin.com/1pF7hBut |
Umnumun
Fweddit I Whip My Slaves Back and Forth
3
|
Posted - 2014.01.22 10:05:00 -
[454] - Quote
Ok nevermind. I'm very special. Solved my issue. |
Zynen
0
|
Posted - 2014.03.12 05:31:00 -
[455] - Quote
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? |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.03.27 00:38:00 -
[456] - 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 -
[457] - 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. |
Lluerssen
Cthulhus Corsairs
15
|
Posted - 2014.04.04 05:40:00 -
[458] - Quote
Just update 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. Sister of EvE:-áhttp://SisterOfEvE.ru/ Loot History Analyzer:-áhttp://SisterOfEvE.ru/loot_history/ |
Zynen
0
|
Posted - 2014.04.04 08:09:00 -
[459] - Quote
I successfully installed a second install of Yapeal, and up until a few days ago everything has been working great.
yapeal Corp = My Corporation Key only yapeal Member = All my member's keys
My corp install (the one with only my corp key) will no longer pull API data from the key.
I suspect the notice below could have something to do with it?
Quote:INFO: No corporations for corp section File: /var/www/yapCorp/class/SectionCorp.php(82)
- The corp key works in EveHQ fine. So the key is good.
- I created a new key, just in case. That one works in EveHQ, but not Yapeal just like the original one.
- I cleared the cache (was database, switched it to file to see if that would help, but still the same problem)
- I've done a fresh install of Yapeal latest (1.03) including database tables.
- I have my key in utilRegisteredKey
- I have my corp in utilRegisteredCorporation (tried with, and without. Was working before with it)
- My IP is not banned @ CCP
- If it helps, I'm on Ubuntu 12.04 at the moment
The only data that's populating is the non-key tables. For example, mapSovereignty, eveAllianceList, etc.
When I turned on TRACE in the yapeal.ini file, I occasionally see these on the Member install. And for a while, constantly on the Corp install. Since the fresh Corp install however, I haven't seen them.
I'm at a loss at what else to check. I haven't messed with the install since I confirmed it was working after the second (Member) install. (That was around March 13th or 14th)
Any advice/direction would be appreciated. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.04 22:07:00 -
[460] - 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 -
[461] - 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 -
[462] - 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. |
Lluerssen
Cthulhus Corsairs
15
|
Posted - 2014.04.06 05:01:00 -
[463] - Quote
Additionally there is error with RegExp.
adodb checking xml version using /< schema.*?( version="([^"]*)")?.*?>/
but file have
schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="0.3" xsi:noNamespaceSchemaLocation="xmlschema03.xsd" Sister of EvE:-áhttp://SisterOfEvE.ru/ Loot History Analyzer:-áhttp://SisterOfEvE.ru/loot_history/ |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.06 05:22:00 -
[464] - 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. |
Lluerssen
Cthulhus Corsairs
15
|
Posted - 2014.04.06 14:55:00 -
[465] - Quote
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 ;) Sister of EvE:-áhttp://SisterOfEvE.ru/ Loot History Analyzer:-áhttp://SisterOfEvE.ru/loot_history/ |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.06 16:44:00 -
[466] - 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. |
Lluerssen
Cthulhus Corsairs
15
|
Posted - 2014.04.06 17:25:00 -
[467] - Quote
Yeah, you're write, especially because it came from "wrap lines at" option in your IDE :)
And also found new trouble.
> php -f checkForRequirements.php createMySQLTables.php must be called directly and can not be included.
var_dump(get_included_files());
array(2) { [0] => string(68) "/Users/bp/Documents/Projects/yapeal/install/checkForRequirements.php" [1] => string(41) "/opt/local/var/db/php55/pear/pear-ini.php" }
Are you going to say, that i should remove pear from auto include? )
And, because you already said that you want to get away from ADOdb, and it's uberly outdated... why should you care about changing adodb?
P.S. 5.5.6 totally fails with yapeal installation... Sister of EvE:-áhttp://SisterOfEvE.ru/ Loot History Analyzer:-áhttp://SisterOfEvE.ru/loot_history/ |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.06 18:10:00 -
[468] - 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 -
[469] - 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. |
Eto Demerhzel
Science and Trade Institute Caldari State
0
|
Posted - 2014.04.07 22:01:00 -
[470] - Quote
hi,
I'm really a noob here, but i try to config yapeal.. So, i have setup all the needed, follow instruction in install.md, and all goes well.. i think.. i have using the file i find on Fuzzy website, and follow the instruction https://www.fuzzwork.co.uk/resources/xamppyapealInstall.txt to put my ApiKey. (my first step in learning php and all that stuff, it's to made a page for adding all my chars^^). When i check the utilRegistredKey table, i have my keyid, vcode and api mask..
But when a try to run yapeal in cli "php -f yapeal.php" i have this
Quote:WARN: Caching invalid API XML for account/APIKeyInfo File: .../yapeal-1.0.3/class/YapealApiCache.php(192)
follow by this, but i think it's normal because the first step fail
Quote:INFO: No corporations for corp section File: .../yapeal-1.0.3/class/SectionCorp.php(82) 2014-04-07 21:35:00.881 INFO: No characters for char section File: .../yapeal-1.0.3/class/SectionChar.php(82)
and.. nothing in accountAPIKeyInfo accountCharacters accountKeyBridge
so.. i don't understand what i do wrong.. ??
(english is not my primary langage) |
|
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.08 21:25:00 -
[471] - 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. |
Eto Demerhzel
Science and Trade Institute Caldari State
0
|
Posted - 2014.04.08 23:33:00 -
[472] - Quote
hi,
I have send you a mail on github.. |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.04.16 17:33:00 -
[473] - 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 -
[474] - 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. |
BoomBoss
Common Sense Ltd Nulli Secunda
14
|
Posted - 2014.04.26 21:51:00 -
[475] - Quote
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. Installed it today without any errors whatsoever.
Any ideas? |
Madam Mika
xXx Serenity Dead Space Syndicate
0
|
Posted - 2014.04.27 04:41:00 -
[476] - Quote
Dragonaire, Im glad to see this is still active in the Eve Community!!! |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.05.03 18:51:00 -
[477] - 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. |
jsmb
Bullets And Tears
0
|
Posted - 2014.05.24 17:01:00 -
[478] - Quote
I have a question not pertaining to this, I am trying to pull the accessmask from eve so i am using
https://api.eveonline.com/account/APIKeyInfo.xml.aspx?keyID=XXX&&vCode=XXX
if i put that into my browser i can see the eveapi -> result -> key @ accessMask
I am trying to import it into a google doc spreadsheet so importxml("https://api.eveonline.com/account/APIKeyInfo.xml.aspx?keyID=XXX&&vCode=XXX", "/eveapi/result/key/@accessMask") but i get errors any chance you might now why? |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.05.24 17:44:00 -
[479] - 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. |
Zynen
0
|
Posted - 2014.05.26 21:31:00 -
[480] - Quote
Dragonaire wrote: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.
1.0.4 fixed all of my issues! |
|
|
|
|
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 [16] 17 18 .. 18 :: one page |
First page | Previous page | Next page | Last page |