EVE Technology Lab

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.

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"

Also, if you need help with yapeal, I could try offer my help :)

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 ;)

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...

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

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.

UPDATE Never mind I setup Yapeal locally so I could test and see that CCP did add alliance and faction stuff which had been asked for by some other developers so will be updating Yapeal. Keep watching for it to show up in git.

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.

For composer use require: "yapeal/yapeal": "1.0.4"
or even better so you do NOT have to update it for stable version updates use require: "yapeal/yapeal": "~1.0"
To look at it on GitHub or grab it with Git the URL is: https://github.com/Dragonrun1/yapeal/tree/1.0.4

I'm look for some help also in updating the install instructions for Yapeal found in INSTALL.md. If someone would be so kind as to write up some new ones based on their experience it would be great. You can even find a new INSTALL.md issue for it.

As usual let me know if there's still problems but all the APIs I tests seem to be working right now.

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

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.