|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.24 22:21:00 -
[1] - Quote
Yet Another Php Eve Api Library also know as Yapeal which can be used to access the Eve Online API data and place it into a database.
Welcome to the new Yapeal forum thread.
I decided with all the changes that have been happening with Yapeal it was time to start a new one since 99% of the old one was of no use to anyone interest in the current version of Yapeal. The old version lasted over 5 years with all the updates to it but it's time to let it go and start looking to the future now.
You can find the old thread here. All 26 pages of it. The last couple pages might be useful to you for this version but I expect all the info you might have found there to end up here soon again 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
56
|
Posted - 2014.07.24 22:21:00 -
[2] - Quote
Reserved 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.25 04:40:00 -
[3] - Quote
Okay so basically though you might have PHP 5.4 installed for your webserver it doesn't seem to be in your path where composer can find it or it is finding a different version. Try running 'php --version' from cmd prompt and see if it sees the correct version if not you'll need to fix your path. Use 'env' if you are getting a different version and look at your PATH setting in there to see if there's a older version listed before PHP 5.4. You'll need to go in and fix it if it's wrong. You'll need t do web search for how to updated path for your version of Windows because there are some difference how you get to it depending on version used etc.
A neat tool I found for things like this is http://www.rapidee.com/en/about you might want to check it out.
Once you have the path set right so composer can find and use the correct version most if not all of your problems should be solved as you said. 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.25 16:42:00 -
[4] - Quote
Easiest way to get a good working yapeal.yaml is much like with the older version where you copy over the yapeal-example. * file and make any needed changes to it.
For getting help on any of the 'yc' command just run it without any parameters or options. For the individual commands themselves use 'yc help command'. To understand the new console commands in general look at the docs for the Symfony2 console as that is what's being used to create them.
The reason you were having problems run the 'yc D:I' command is it was made to be run from the root directory so needs to be run from 'yapeal' directory from your example. It does need some work to make it better as it was kind of hacked together in just a day or two but works well within it's limitations. The reason it was adding 'bin' in your case is anytime you give it a relative path it assume you want it to use the current working directory. This is common with many other CLI commands on all platforms. If you look in the bin/yc file you'll see where it gets the CWD and passes it on for the commands to use.
1. How do I refresh the API data for a single character? First I'll state that Yapeal is made to be run as a crontab or scheduled task EVERY minute to keep everything up to date. If you do run it this way even though no one seems to believe it it'll actually help increase your performance over all by NOT having all the APIs 'come due' so to say at the same time. The idea is you have a database that is always as up to date as the API server allows and you don't need do anything to make that happen in your application.
That being said the new version has been design to allow individual API classes to be called directly. This is mainly meant for things in your application like new account creation where you need something more interactive. It can also be used for cases where you want a single snapshot of the data and don't want to have it changing while looking at it.
To use Yapeal in this mode you'll be using the oneShot() method. This method is the same method that autoMagic() calls to do the actual work of getting the XML and putting it into the DB. I thought about trying to add a quick guide here on how to use oneShot() but it would be to long and the formating on the forums here sucks to put it kindly. I think its better to do this a wiki page so I'll try to put one together that should help everyone find their way on this new feature. 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.26 05:56:00 -
[5] - Quote
Tiberius Zol - If you do a data only export on most of the API tables they should import into the new ones okay. There are several APIs of course like IndustryJobs that have had a lot of changes to them which probably won't work without a lot of work. Also most of the old util Tables have had major changes to them. The only one that really matters there is utilRegisteredKey. If you delete the couple of columns that no longer exist on it you can export and import it as well. There is a outdated bin/sql/Update_1.0.4-1.1.x.sql file you may find some what useful but mostly not.
I can look into making a SQL file that would make the transfer easier but if there's only a couple of people needing to do so it might be just as easy to help them directly with problems and continue working more APIs than spend time on making something that will only be used a couple times.
As to which APIs have been done the best way to know is to look if there is an existing class for it in lib/Database/* directories. If you see a php and xsd file for it it's should be a working API but also have a look at the Database/TODO.md which I just updated. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.26 20:22:00 -
[6] - Quote
git update should work for you. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.29 20:39:00 -
[7] - Quote
Hi all so if you been paying attention to master branch you've seen a lot of bug fixing and several APIs added. In some cases APIs had been done on char/corp but not the other and the hole has now been filled.
I now need some input on which APIs people want to see done next so I've decided to try to get some. I'm calling it the 'Vote for your most needed API' campaign. I've added 'enhancement' issues for several of APIs on GitHub and I'd like to have people vote on their top 3 APIs they would like to see done next. I didn't add all of the missing APIs so if you want one that's not list please go ahead and add it since I was guessing at which ones people might want and part of the reason for the campaign is to let me know if I'm right. I plan on looking at the votes in about a week and no that doesn't mean I won't working on some other APIs this week just really need some feedback here.
Another thing that would help speed up getting some of the APIs done would be some helpers. I've had one person helping me a some of the APIs in Stephen but he got busy again in RL it seems so it's back to just me doing everything for now. So I'm looking for people that are interesting in learn more about Yapeal, the APIs, PHP, XML, or XSD to help with some of the APIs. This is also a good chance for people that really need an API done so they can finish their application they are write or hope to write with Yapeal to maybe get it a little sooner. Understand this isn't where I just throw an API at you and expect you to do it all by yourself though that cool if someone wants to try it but where I'm more of a mentor/QA/programmer available to help you as needed to make it work.
I'll also take help with re-doing/starting over on the Wiki or the include docs like CONFIG.md which I started but haven't got back to. Basically any place someone would like to do something just let me know so I can make sure not duping work.
Anyway as always thanks for use Yapeal. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.31 17:02:00 -
[8] - Quote
Yeah I didn't finish writing the CONFIG.md I'll try to get back to it and push it out. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.31 21:48:00 -
[9] - Quote
Okay finished off what I was doing with CONFIG.md and pushed it along with some other minor things I noticed while writing it. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.01 13:48:00 -
[10] - Quote
That wiki page is for the older version (1.0.x) of Yapeal which is no longer really supported since it doesn't work with all the changes to the Eve APIs that have happened. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
|
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.01 14:33:00 -
[11] - Quote
Kolb - At this time none of the old Util classes have been replaced. Some of them of course are no longer needed because the tables don't exist like utilRegisteredChar|Corp|Section. I will look at possible add something to manage the couple of other tables like utilEveApi and utilRegisteredKey which are at this time the only ones you'll need to make changes to. Everything that was done with the other tables can be manages with just these two now. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.02 17:13:00 -
[12] - Quote
Clean install is best. All the APIs are on by default so as long as the class for that API has been done it'll work. Make sure when you add your info to utilRegisteredKey that isActive = 1 or the only thing you will see is the account stuff since basically it's hardwired on for account/APIKeyInfo and account/Characters. If it still doesn't seem to be working check the log files. log/yapeal.log and log/error.log should be helpful. If there's no error.log file that's normal but if it exist there something more troubling going on. As always make sure the cache directory is writable.
Kolb - About the segfault are you sure you are using PHP 5.4? Try running 'php --version' to check. Also if you can copy it for us here so we can see it or better yet open issue on GitHub with it and any log files were I can take a look at what's going on should be able to figure it out.
As always it's a good idea to go back through the steps in INSTALL.md and CONFIG.md files and make sure you didn't miss something. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.03 17:22:00 -
[13] - Quote
Legedric Striker - You may have found a bug in the API actually because it's not suppose to matter if char is or has been in an alliance or faction it suppose to return some defaults like 0. I'll look at working around it as it'll probably effect any char that is in an NPC corporation since they don't have alliances or factions normally. I'll create an issue on GitHub and do a fix for it.
https://github.com/Dragonrun1/yapeal/issues/30 Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.03 17:28:00 -
[14] - Quote
So just looking at the voting so far it seems AssetList needs to be the next one I work on which somehow didn't surprise me as it both very useful in most application and of course one of the harder API to program which is why it's not done yet Do continue to vote if you haven't because after doing AssetList I'll need to decided on what to do next. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.03 19:18:00 -
[15] - Quote
Actual Yapeal does locking on a per API basis which allows multiple instances to run without stepping on each others toes just like it always has for a long time. AbstractCommonEveApi::gotApiLock() handles getting the lock. Using the database for locking is faster plus more cross platform compatible for what it needs. It also using transactions for all deletes and upsert so it makes sure multiple table APIs are updated correctly and keeps everything ACID. So you shouldn't need to do any extra locking in your crontab. You said it would cause weird behavior, have you actually experienced this or just assumed because you didn't see any locking that it would?
I'm a little puzzled by what you mean when you say 'delete APIs' maybe you can explain what you mean just a little more. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.03 20:33:00 -
[16] - Quote
Kolb - I would assume from the all default_time_zone warnings that you are using Ubuntu and they still haven't figured out like all the other distros how to set the time zone correctly in php.ini . You probably need to fix that yourself and I'll look at adding something into Yapeal to also take care of it for it's needs. I thought I already had it setting it but must not have made it in like I thought.
On the segfault looks like you're simple running out of memory with even less than 1000 row inserts so you might want to make sure your memory_limit is high enough in php.ini. 32MB should be enough but my current setting is 128MB here on my test machine. I've not done any really memory profiling on Yapeal this time but I've used best practices to keep it as small as possible with the limit of course being the size of the Eve API XML itself. One reason I limit individual upserts to under 1001 row is to try keeping memory use lower plus work around some limits with typical MySQL setups. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.04 16:09:00 -
[17] - Quote
So did a little more research on seg-faults in PHP and seem what's going on is you're hitting a bug in PHP itself or one of it's extensions. Based on the log messages just before it happens I'd say there are one of 2 possible things that can be causing it.
- The preg_replace() on line 91
- PDO prepare() or execute() on lines 97-99
Since the message the preg_replace() is creating is never shown it the most likely cause but there is a small chance that it doesn't get written to the log before PHP seg-faults and aborts the background OS I/O process. Easy way to find out is to just comment out lines 91-93 where it's creating and trying to log the message and see if it stops seg-faulting. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.04 23:31:00 -
[18] - Quote
No it's the preg_replace() causing the problem I'm sure. The default setting they use for pcre.backtrack_limit is only 100k chars and the string was trying to process I'm guessing is closer to 200k. you can try uncommenting them and increase the setting to say 1M and see if it works but I'll probably still push out another fix that just replaces it instead. I like the RegExp because it was a single line but easy enough to use something else.
https://github.com/Dragonrun1/yapeal/issues/31 Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.06 20:50:00 -
[19] - Quote
CCP is adding new char and corp Blueprints APIs which can be seen on test server now. I've adding them to Yapeal but set isActive=0 in utilEveApi for now until they get deployed to Tranquility.
Legedric Striker - Great to see you get it out for people to take a look and glad to hear you found Yapeal useful. I've took a quick look but not had time to actually try it but I'll try to get around to that soon. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.07 18:45:00 -
[20] - Quote
Could be that some of my changes to have Yapeal do a better job of reusing the FS cache aren't right yet I'll look at it again. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
|
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.08 04:21:00 -
[21] - Quote
Legedric Striker - Ok updated it should work correctly now. The problem I was having is when I first started writing the method I had $current and $now flipped in what they were set to and when I changed them to what they are now I didn't get them fully flipped in my mind as well so ended up with things backwards but thanks for figuring it out. I took a little different approach on minimum time which is more what I had in mind originally. It won't run into the problem you were having but still sets a minimum cache time like I was wanting. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.08 15:48:00 -
[22] - Quote
Tiberius Zol - Sorry you lost all the data without backups but there is a reason I called it init. I also clearly state in the instructions to make backups before starting. Something I will try to do going forward which I really have been mean to do is make an update SQL with just the changes. I'll have to come up with a naming system that make sense and is easy to understand as well but it is something that will be needed more and more as time goes on. I just had another idea how to do it as well that might be easier to maintain so give me a couple days and I'll see if it might work the way I think it could. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.09 22:15:00 -
[23] - Quote
Jack Haydn - Sound like your application needs to do a better job of check keys before they get added to utilRegisteredKeys but to why Yapeal doesn't delete 'bad' keys and just deactivates them is randomly the API servers will return error codes suggesting it's a bad key. If it actual did delete them every time the API reported a problem you'd very soon end up with no keys at all.
My suggestion is you have a crontab that check for deactivated keys and use oneShot() calls to APIKeyInfo to check the keys are still valid etc and decided what you want to do directly. Another reason Yapeal doesn't do it automatically is some sites might want to send eve-mail or do something else to let the site admin or user know there is a problem. By simple making it not active the problem can be corrected and reactivate it. I try NOT to decide how things like that have to be handled because that's not Yapeal job that's the application's job Yapeal just tries to keep things from happening like your IP from being banned. Now if you find something in the logs where it's not deactivating a key when it should be do let me know and I'll make sure it gets fixed.
What might be helpful to figure out why you ended up getting banned, which by the way is very hard to do, except if there's something true wrong with your app setup if we could see the log files. There should be no way Yapeal would be breaking any of the API caching rules which would cause this but if somehow it is I would have to see the log files to figure out where the error might be. I would suggest instead of trying to paste all or part of your log file here and fight the forum formatting etc that you put it on Pastebin or something like it and just include a link. If you prefer you can also E-mail it to me at the E-mail listed on GitHub just make sure you ID yourself so it doesn't end up in my junk bin . Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.10 05:41:00 -
[24] - Quote
delete from utilRegisteredKey where isActive = 0;
Now if you want to remove all the data from the API tables that is a little more complex and I can give you some pointers on that but if you are already selecting the data to show it in your application you know how to do it really. Just change your selects into deletes and you're done. All the joins etc will be the same or nearly the same and I'm sure you can figure it out.
Let me quote something from the main page of Yapeal here.
Quote:Yet Another Php Eve Api Library also know as Yapeal which can be used to access the Eve Online API data and place it into a database. I think it does that and I'll assume you did too or you wouldn't have used it. The idea of Yapeal is not to abstract everything database away for you but to simple have a auto-magically updating database so you don't have to deal with all the details of the XML. The original idea of Yapeal is the database is the interface that you should only need to deal with it. That has changed in some small ways but in the end I still use that as the guide to what is done and included in Yapeal. It is NOT Yapeal's job to handle everything related to the database because it really can't. Every application or even programmers writing the same application are going to do things differently and what might work great for one type of application or one programmer could bring tears to the eyes of another programmer. The code in some of the older versions of Yapeal and some of my other projects have been know to nearly do this at times actually for me when I look at them now
Think about what Yapeal does do and really how simple it is to work with.
- You have one small config file that is set and forget.
- You turn on and off which APIs it does anything with from a single column in one table (utilEveApi) isActive.
- You only have to add site user API key information to one table (utilRegistereedKeys) and Yapeal takes care of the details afterwards.
- If you need to stop Yapeal from getting some site user data once again there's only one table you need to work with utilRegisteredKey.
- Do a one time setup of a crontab or scheduled task on a preferred one minute timer.
- Yapeal goes to work making sure all the API data you have requested is as up to date as is allowed by the servers.
So in the end you only have two tables in the database your application has to manage so Yapeal can update over 100 tables for all your site users. I think that a pretty good deal.
Now with that said if you look I did start some work on a class to help manage the utilRegisteredKey table which you'll find in bin/ directory. It currently just helps you add a new key but I do plan on it being a more complete management tool for people to use on that table. If you want to add to it and share it with everybody please do as I'm not sure when I might get back to working on it as I have many other things to do in Yapeal and otherwise. I also would like to see something to help manage the utilEveApi table to make turning APIs on and off easier with a more OOP interface etc.
I do want to thank you for the feedback and ideas even if I probably wouldn't change Yapeal in the ways you want and as always thank you for using Yapeal.
Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.08.11 20:09:00 -
[25] - Quote
Just a quick note I've added corp/Facilities for those of you working with IndustryJobs. Note that I include an update SQL file in bin/sql/update/. It's mostly an early idea about doing this so will have some changes to it in the future but at least it can be used manually for now with edits until I develop the code to use it more directly. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
57
|
Posted - 2014.08.12 17:43:00 -
[26] - Quote
Kolb - Thanks for sharing just have a few suggestions.
- First instead of trying to manage the log files yourself look at logrotate it's made to handle that type of stuff and is what most people use.
- Instead of copying rows from one table to another you could look at replacing utilRegisteredKey with a view or change you app so it uses the keyID as a foreign key in your table. You might find CreateCustomTables.sql helpful here.
- Why check for the API server when Yapeal already does that? It's a waste of your time writing code to try replacing something Yapeal already handles.
- Once again THERE IS NO PROBLEM WITH MORE THEN ONE YAPEAL RUNNING AT THE SAME TIME IT WAS MADE TO DO SO. It does locking on a per API and keyID basis and no additional locking is needed or management is needed. If you want to have Yapeal NOT be able to keep up with increasing load continue NOT letting this happen and it'll get slower and slower with more users. Running Yapeal with the one minute crontab is basically a simple way to make it act like it's threaded which can't be done in a cross platform way at this time in PHP or I'd use it. Yapeal spends 99% of it's time waiting on either your network connection to get the XML or your database/ filesystem to store it.
In summary stop re-inventing the wheel. Stop try to second guessing over 5 years of Eve API development experience that has gone into Yapeal from me and others. Everything you are trying to do I've tried in Yapeal at some point in the past and if it's NOT there now there is a reason for it. The reason is usually I found a better way or it didn't work or even that it simple wasn't needed.
Just a suggestion try it my way. One of three things will happen.
- You'll find I'm right and it does work better then what you've been trying.
- You won't be able to measure any difference and my way is simpler.
- You find something in Yapeal that can be improved because you have tested it both ways and can show that and everyone benefits when I give you credit when adding it to Yapeal.
One final thing don't really take the above personally in anyway I've just been down this road a few times and needed to blow off some steam about it. I'm glad you want to improve things and help others and if you can show me I'm wrong on something that great as well. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
57
|
Posted - 2014.08.13 23:27:00 -
[27] - Quote
Make sure they aren't for the same POS the cache files are on a per KeyID/characterID basis. So if you have say 2 CEO keys or a CEO and Director key for the same corp you'll have 2 cache files but only one set of data in the DB. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
57
|
Posted - 2014.08.14 07:02:00 -
[28] - Quote
Tiberius Zol - Do all the POSes show in StarbaseList table? Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
57
|
Posted - 2014.08.14 19:00:00 -
[29] - Quote
Tiberius Zol - So it seems to be working here fine but I only have a single POS to work with. I'll go through some checks you can do to maybe narrow down where something might be breaking.
- If you look in cache/corp you should find a couple of StarbaseList*.xml files which list all the POSes you see in the DB table.
- You should see one StarbaseDetail*.xml for each POS as well.
- Looking at the StarbaseDetail*.xml files they should look something like http://pastebin.com/hVXtxk5Y. Notice if there is a 'fuel' element and make sure there are rows in it.
If all the above is good then you will next need to check log/yapeal.log and look for the messages on the POS stuff. Easy way to find them is do a find/search for 'Corp/Starbase'. Should see where StarbaseDetail calls StarbaseList to make sure it's up to date then processes each POS in turn. Make sure it doesn't report invalid XML when checking with XSD. Next it inserts the info into the 'corpStarbaseDetail', 'corpFuel', 'corpCombatSettings', and 'corpGeneralSettings' tables. Look for any exceptions especially having to do with the inserts. Also note how many rows it says for each table with fuel being the only one that should have more than a single row.
If you do find something in the log if you can put is up on Pastebin or some where I can take a look I'll try figuring out what's causing the issue. If you don't find anything when you look at the log you might still put it up somewhere where I can have a look at it as I might spot something that looks wrong to me still. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
57
|
Posted - 2014.08.15 20:35:00 -
[30] - Quote
Based on my post from yesterday I decided to start putting together a little guide to help people when trying to troubleshoot Yapeal. I don't know how useful it might be for people so ideas and feedback on how to improve it are welcome. Also like to hear ideas for how to continue on or does it need to continue? Anyway here the link: https://github.com/Dragonrun1/yapeal/wiki/Troubleshooting-Tips
Tiberius Zol - Thanks for report on WalletTransactions problem I started issue for it. https://github.com/Dragonrun1/yapeal/issues/33
I'm still looking at the other thing with Starbase but let's try one thing that might help on getting a little more complete log message for all you POSes. It looks as though corpStarbaseList for ownerID = 98067338 wasn't expired at the time you took that log so let's 'force' all the Starbase stuff to need refreshing at the same time. This may work better for you if you temporarily stop any crontabs etc and run Yapeal manually.
- Go into the utilCachedUntil table and delete all the StarbaseList and StarbaseDetails rows.
- You can also optional delete the cache files for them in cache/corp/ but Yapeal should use or replace them as needed.
- You might also find truncating the log/yapeal.log file useful.
- Now run Yapeal manually on CLI with something like 'php bin\yapeal.php'.
Once it finishes take a look once again at the tables that didn't seem to be updating and see if they changed also look at your log and see if it now shows anything different like trying to add the other POS that is missing. If you can Pastebin the section from the new log so I can compare it with to old one that would be great as well.
Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
|
Dragonaire
Here there be Dragons
57
|
Posted - 2014.08.19 20:23:00 -
[31] - Quote
Tiberius Zol - I've been looking at stuff for last couple days and just not seeing anything but I just pushed an update that will add into the XML via processing instruction a json copy of the arguments used when retrieving it from the API server which might help one of us figure out why you're have problems. I did setup a new test POS myself and everything seems to be working fine with the APIs. Try the update and clear the cachedUntil table and the FS cache and see if the XML with the new info makes a difference because without something more to work with not sure what I can do to help you Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
58
|
Posted - 2014.08.19 23:46:00 -
[32] - Quote
Tiberius Zol - You are correct it is a loop problem more that it's missing a loop. Person that worked on API hadn't done any of the more complex ones before and I missed it during QA also. We only had single POS to test with so it seemed to work. Now that I know where the problem is should have it fixed in a day or two at most. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
58
|
Posted - 2014.08.20 01:40:00 -
[33] - Quote
Tiberius Zol - Give the update to DatabaseDetails a try and see if it fixes your issue. https://github.com/Dragonrun1/yapeal/issues/35 Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
58
|
Posted - 2014.08.20 22:31:00 -
[34] - Quote
Just thought I say I've updated the crontab Setup page in the wiki if you need some more help with that. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
59
|
Posted - 2014.08.25 18:36:00 -
[35] - Quote
Hi all I just pushed something I've been working on for last couple weeks. I finished up the database updater system. You can try it out by running
'php bin\yc D:U'
It should be able to update any databases that have been manually updated to at least have the blueprint API tables. Note just like with install you may need additional privileges above what the normal Yapeal user needs. Something that's different with the update compared to the install is it uses MYSQL procedure so make sure the user you run it as can create, delete, and use them. Also as always make sure you have a current backup of your database before using it.
Just a little bit about how the updates work. The command starts out by grabbing your settings from config/yapeal.yaml. You can tell it to use a different config file you if you want or override any of the settings using command line options. The command then checks the current version of the database in the utilDatabaseVersion table if it exists and compares that to the sql files in bin/sql/updates/ directory. It will apply any of the sql files that have a version (name) greater then the current database version. They are applied in order and the utilDatabaseVersion table is updated. On the first run you will get a warning message about 'Could NOT get database version ...' which you can ignore as the table should be added for you automatically so you don't see the message again. I decided to use a date-timestamp for the versions vs something else like plain numbers which you might have seen during development. All but the first one are based on when I did commits to git with database updates but in the future they'll be based on when I do create the update sql on my development machine since I wouldn't have commit dates before doing the actual commits like I did this time.
Anyway hope this new tool makes it easier for everybody when updating Yapeal. As always you can ask any questions you have here and if you find a bug make sure to create the issue on GitHub.
Thank you for using Yapeal. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
59
|
Posted - 2014.08.25 19:41:00 -
[36] - Quote
Tiberius Zol - So are you seeing character names longer than 50 characters? Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
59
|
Posted - 2014.08.26 17:57:00 -
[37] - Quote
Tiberius Zol wrote:just for your information: i set the isActive flag for the Blueprint APis to 1 and it pulls stuff and write it to the table... BUT i have several (maybe all?) Corp BPs in the charBlueprint table Edit: yes.. all BPs, char and corp related are in the charBlueprints table. corpBlueprints table is empty. Edit2: found the error and fixed it manually: lib/Database/Corp/Blueprints.php Quote: $this->attributePreserveData( $xml, $columnDefaults, 'charBlueprints' );
must be Quote: $this->attributePreserveData( $xml, $columnDefaults, 'corpBlueprints' );
https://github.com/Dragonrun1/yapeal/issues/37 Fixed. Sorry thought I'd made change before I pushed.
Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
59
|
Posted - 2014.08.26 22:02:00 -
[38] - Quote
Tiberius Zol wrote:About the corpWalletTransaction stuff.
I truncated the table. after it i run yapeal again and found this on the yapeal.log:
[2014-08-26 16:44:49] yapeal.WARNING: Failed to upsert data from Eve API corp/WalletTransactions for 98067338 on account 1000 {"exception":"[object] (PDOException: SQLSTATE[HY000]: General error: 1364 Field 'characterName' doesn't have a default value at /htdocs/eve/yapealneu/lib/Database/EveApiToolsTrait.php:107)"} []
after set the characterName to NULL again the table get filled again.. but with characterID and characterName both NULL https://github.com/Dragonrun1/yapeal/issues/38 Fixed. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
60
|
Posted - 2014.08.27 16:00:00 -
[39] - Quote
Legedric Striker- You might want to read how the bufferSize works in the FingersCrossedHandler.
https://github.com/Seldaek/monolog#wrappers--special-handlers
It doesn't really limit the log overall size only how many lines it goes back in it's internal held log from when something triggers it. Fixing your other issue should keep it from writing anything to you logs which probably will help keep them from growing like they have been.
The CorporationRolesAt* tables in the database are set to only allow for ASCII characters since they are fixed by CCP but titles are done by players so it should allow all normal UTF-8 characters. It was an oversight on my part about the difference and I'll try to push out an update that should fix it for you today or tomorrow. If you want to try it now just change the charCorporationTitles table charset from ASCII to utf8 with utf8_unicode_ci collate and you should see the warnings go away.
On another note some of you might have noticed Yapeal does NOT seem to be remembering which updates it has done so reapplies them all when you run 'yc D:U'. There's really nothing wrong with this other than it can be slower and it really shouldn't be repeating something it already did. I think it has to do with a last minute change I made to updating the utilDatabaseVersion table but still tracking it down so look for a fix for this as well in the next day or two.
There also a bit of a issue with the corp/MemberTracking stuff which I seem to have a working fix for. I expect to push out sometime later today to fix it. I may wait and do all the fixes together or break them up into several so just keep watching for them.
As always thank you for using Yapeal, Dragonaire. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
60
|
Posted - 2014.08.28 15:29:00 -
[40] - Quote
Try changing it directly on the titleName column because changing it just on the table after the table is created doesn't always update existing columns Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
|
Dragonaire
Here there be Dragons
60
|
Posted - 2014.08.28 21:03:00 -
[41] - Quote
Okay think I've resolved all the issues I talking about in https://forums.eveonline.com/default.aspx?g=posts&m=4958262#post4958262 above. Also found another couple things and fixed them in the tables hopefully before anyone had run into them without realizing. Updating is now working as intended so applying the updates should be more streamlined going forward.
Hopefully with these fixes there will be less issues coming up and I can start spend more of my time on adding some of the missing APIs again but I think its important that the current APIs be as bug free as possible so keep the reports coming.
Resolved issues in last two days:
#37 corp/Blueprints using wrong table #38 corp/WalletTransactions not setting defaults for characterID and characterName #39 XSD for eve/CharacterInfo does NOT understand new corporationName field. #40 charCorporationTitles table allows only ASCII character titles #41 IndustryJobs tables installerName columns to short #42 yc Database:Update unnecessarily reapplies updates
Thanks for using Yapeal, Dragonaire.
Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
60
|
Posted - 2014.08.28 22:53:00 -
[42] - Quote
Tesla Ming Chent-Shi - There's probably some people that would really find that useful. Like with any project that uses Yapeal I'd be more than happy to help you figure out any missing details on how it works etc. I really don't know much about WP but I'm wondering how you'd handle the background automatic updating feature Yapeal uses or if you'd more be doing it as a one shot on a per page basis? I probably would have some other questions about it but I'll wait and let's see how much interest people have in the idea and what they might like to see etc. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
61
|
Posted - 2014.08.31 16:05:00 -
[43] - Quote
They have totally changed all the Industry stuff include what some of the column values mean so chances are you can't import them but the good news is the new IndustryHistory API will let you get the older jobs with the data updated by CCP so if you really need it as far back as they allow you can get it. You are really going to be limited in this case by what CCP has done. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
61
|
Posted - 2014.09.04 02:13:00 -
[44] - Quote
Okay got some good news that should make many people happy, the char/AssetList and corp/AssetList APIs are now done and active. Has been tested here on both char and Crop side and seems to be working right but only got it work about an hour ago so might still have a minor bug or two but figured everybody had been waiting so long for it I'd put it out as soon as I could. No DB changes so should be able to grab update and let Yapeal do it's thing.
Enjoy, Dragonaire Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
61
|
Posted - 2014.09.04 17:29:00 -
[45] - Quote
AmsTaFF Kreon - I think I'm understanding your question is does Yapeal just work with the Eve API servers to pull the data and put it into a database. Yes that's what it does. It does not have anything to do with the static data dump or SDD there are other tools for that. Most applications will need both to do the, as I put it, 'numbers to names part'. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
61
|
Posted - 2014.09.04 19:56:00 -
[46] - Quote
Okay some updates have been pushed to fixes some issues I came across. First like I figured there was a couple things incomplete on AssetList. It wasn't deleting the old orphaned records. Couple of the other newer APIs had to same issue and fixed them as well. I'll try to go through them all and make sure none of the other are doing the same thing.
For those of you that haven't paid attention Yapeal for a little while now is adding into the cached XML file what is called a 'processing instruction' generated by Yapeal. Think of it basically as a comment for an application in XML. Yapeal doesn't really use it in any way at this time but it can be a useful tool for me during troubleshooting. Current it's writing the API parameters being sent to the server with the vCode cut off so it's safe to just cut and paste to places if I should ask for it. Anyway to make a long story short it let me trace down a long standing thing I've been noticing that even with just one active corp key during testing I'd often end up with more than a single IndustryJobs cache file for example after running Yapeal manually a couple times. This probably wasn't noticeable if you have several keys but is with single key testing. Before I couldn't figure out what was causing it but now I know it's because left over parameters like accountKey from accountBalance or one of the other APIs that need extra parameters was not being reset between the different API calls. It came down to one miss placed line in one of the XML network classes in the end.
Anyway I've pushed the update to fix it but I highly recommend that everyone clear out your cache/*/*.xml files to get rid of the bad files and let Yapeal refresh the cache as needed. This could save you a lot of disk space as well since the are cases where you'd end up with as many as eight files instead of one per API/key combo after a few runs.
Next I'd like a little more input on which API everybody needs next. I'll go back through thread as well to look at the votes people already made but new people can have a chance to vote now or you can update your vote if you changed your mind.
As always thank you for using Yapeal, Dragonaire. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
61
|
Posted - 2014.09.05 17:10:00 -
[47] - Quote
Looks like another column that needs to be UTF-8 I'll look at changing it. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
61
|
Posted - 2014.09.07 01:01:00 -
[48] - Quote
Fixed some things I ran across with AccountBalance, and the Wallet stuff. Came to light while I was looking at some corp stuff. One small DB table update for the corp AccountBalance table to allow for the new mercenary stuff. Fix also should keep corp/AccountBalance from making a bunch of unneeded cache files so like before worth deleting all the cache/corp/AccountBalance*.xml files and Yapeal will recreate the ones it needs.
I haven't decided for sure which API to work on next but leaning towards corporationSheet to match up with characterSheet. Looking at making it useable with and without API key info so you can use it in your apps to grab public corp info with just the corporationID but not sure if I can make it work yet so stay tuned on that. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
61
|
Posted - 2014.09.09 00:55:00 -
[49] - Quote
Tesla Ming Chent-Shi - After the README.md, INSTALL.md, and CONFIG.md there really isn't much I've updated a couple of the pages in the wiki as well but since the database tables are the Yapeal API really it just a matter of looking for the info you need in them. If you are having a problem with something in particular asking your questions here in the forums is probably the best as either I or someone else should answer them and others can find them later as well when they have the same questions. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
61
|
Posted - 2014.09.09 02:22:00 -
[50] - Quote
Base way as an application programmer is to look at it is you have a database that just magically always has the most up to date data possible. You are right in that to make that happen you do need to have Yapeal running in a crontab which is outlined in one of the Wiki pages. I don't have direct instructions for Windows because you usually do it through the GUI which is much harder to explain without a lot of screen shots etc. Also each version of Windows is a little different and I'm not going to take the time to try figuring it out with each of them. Most people will use Yapeal on a Linux server anyway so I don't expect that to be much of a problem since they have crontab.
As to how often Yapeal should run in the background I'm always very clear about that. Yapeal should run every single minute to insure the lowest server load on both ends and the most up to date data. Yapeal internally manages which APIs are ready for refreshing from the Eve API servers and trying to second guess it on that just causes you more load and problems NOT less like everybody seems to think.
How to use Yapeal for things like site signup etc does take a little more work but not much as I made a utility class you can use to add the API key info into the right table which you can find in bin/UtilRegisterKey.php. After that or possibly before you can also use any of the API classes you'll find in lib/Database/*/ directories directly just like the main Yapeal class does or even just extend from it. You'll find it in lib/Yapeal.php. You can just ignore the AutoMagic() method or override it to do what you need. The code is the best documents you will ever find in any project on how something works so don't be afraid to poke around in it a little.
Just an additional hint for things like signups etc is to use the oneShot() method in the lib/Database/Account/APIKeyInfo class. It'll put the EVE API result info into the account database tables where you can check the mask and get the character and corp info you might need.
Hope this helps you get going or at least gives you some idea where to find out some more about some of the stuff. Remember the database is the interface everything else is just setup to make it work Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
|
Dragonaire
Here there be Dragons
61
|
Posted - 2014.09.10 20:08:00 -
[51] - Quote
Actually the quote marks are correct but I use ANSI mode in MySQL for all the SQL in Yapeal. What I probably do need to add into the class is the SQL to set that mode up first in a class where it's more likely to be used by others. I'll try to push out something to do that later today. If you look in lib/Configuration/Wiring::wireDatabase you'll see the exec() commands that is used in Yapeal to set the correct mode up right after the connection is created. You can add those into your code before passing it to utilRegisteredUser. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
61
|
Posted - 2014.09.10 22:39:00 -
[52] - Quote
Okay pushed out several bug fixes for things a couple of them include database updates so remember to do a 'php bin\yc D:U' to fit up the DB as well. You can see more about the issues fixed in https://github.com/Dragonrun1/yapeal/issues/50 https://github.com/Dragonrun1/yapeal/issues/51 https://github.com/Dragonrun1/yapeal/issues/52 https://github.com/Dragonrun1/yapeal/issues/53 https://github.com/Dragonrun1/yapeal/issues/54 Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.11 15:50:45 -
[53] - Quote
For those that may have been waiting for it corp/CorporationSheet is now finished and been pushed out. It can be used to get public corporation information by just using corporationID with oneShot() . Note that that API does have a quirk in that if you include a corporationID argument when requesting the XML you end up with just the public info vs if you just have the keyID and vCode you get the full info. Why? I have no idea really you can ask CCP on that one
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.12 15:24:16 -
[54] - Quote
Since it thinks it's invalid look for an InvalidCorporationSheet*.xml file but I'm thinking you got one of the WIP version of CorporationSheet.xsd that might have slipped out and not the final one so you probably should update Yapeal again to the current version and insure everything is correct. There should be a line in the XSD that looks something like this
xs:element type="eveNameType" name="allianceName" minOccurs="0" maxOccurs="1"
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
62
|
Posted - 2014.09.12 19:15:00 -
[55] - Quote
So looks like what is causing the problem is CCP decided to put the allianceName after the factionID instead with allianceID I'll look at making it either not care or update the order. You can try just moving the line in the XSD yourself and see if it fixes it for you. Finds camping stations from the inside much easier. Designer of Yapeal-á for the Eve API. Check out the Yapeal PHP API Library thread for more information. |
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.12 19:15:03 -
[56] - Quote
So looks like what is causing the problem is CCP decided to put the allianceName after the factionID instead with allianceID I'll look at making it either not care or update the order. You can try just moving the line in the XSD yourself and see if it fixes it for you.
https://github.com/Dragonrun1/yapeal/issues/55 CorporationSheet fails XSD verifying on allianceName resolved.
Try the update it should fix the issue on this and any other out of order elements.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.14 19:24:38 -
[57] - Quote
I've been known to just add Yapeal directly into the task scheduler on Windows a few times but a BAT file can make it a little easier. Just a little tip for Windows users in the trigger advanced settings under Repeat task every: you can edit the number so instead on the lowest being 5 minutes you can change it to 1 The list is just suggested values not the only ones allowed.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.23 15:41:19 -
[58] - Quote
Tesla Ming Chent-Shi - If you are looking for a list of the characters in a corporation that's the MemberTracking API and you'll find a table by that name as well. If you just want to know the number of people in the corporation is you can find that in the CorporationSheet if you have at least a limited key. You might want to take a look at https://neweden-dev.com/API to learn more about the actual available APIs. For APIs that have multiple rowsets or rowset like parts you'll find the data broke out into another table with the same name for example the logo part from the CorporationSheet API becomes the corpLogo table.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.23 21:08:29 -
[59] - Quote
Make sure the corp keys you have include MemberTracking in their mask. There are a couple of bits in the mask that control this API. One doesn't include as much details about the members location etc as the other which you can read more about on the MemberTracking API page from the above link. Some corporation are a bit touchy about including the more complete location Info I know or even the lesser API because it does give a lot more detail than their member might want available about their location even with the longish cache time used.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.24 04:17:29 -
[60] - Quote
Corporation member information isn't in CorporationSheet just the memberCount and memberLimit info is available from that API. To get the info about the actual members in the corp you need to use MemberTracking. I did push out some updates to Yapeal to fix an issue with the ceoName column as well today that I had forgotten to push out plus the other fixes to FactionName etc that Tiberius Zol found which could be causing you the same issue in CorporationSheet.
You should always make sure to update any time I put out updates to tables/APIs you are using since sometimes there can be additional small fixes that don't make it into the commit messages for things I notice while fixing the main issue I'm working on. I have been trying to always create a new issue for those things with its own commit but a lot of times I'll not do so when the fixes are inter-related and/or its only a couple of lines of code. A good example of something I usually don't include in the commit message since I decided to make Yapeal require PHP 5.4 is that as I make any changes in any of the PHP files in Yapeal I'm updating all of the arrays to use short syntax. Since this really doesn't effect how it works I don't usually feel that it needs to be included in the commit message. There can be other minor things like this as well from time to time that I don't expect to effect how Yapeal works.
I was a little unclear from your post if you were saying you CorporationSheet tables were empty or just the MemberTracking table which is a different API. Either way hopeful the above answered your question If not maybe you can try explain in a bit more detail what info your need and where you are looking for it so someone can help direct you to it.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.25 23:53:06 -
[61] - Quote
So I put out a few updates to Yapeal and I wanted to briefly go over them a little.
The first one is the new User-Agent header stuff. If you don't know anything about what the User-Agent header is you can read about it at http://en.wikipedia.org/wiki/User_agent. In the past Yapeal kind of allowed for a custom setting but it was added and implemented in a way that made it hard to use and as best I can tell never really was. I'm hoping that with the better design I used this time that everyone will find it easier and it will get used more this time around. Have a look at the config/yapeal-example.yaml for more info on the settings and let me know if anything is still unclear.
The other new thing is the stuff to do with corporationSheet and using corporationIDs found in some of the other APIs. The CorporationSheet API allows you to get the same public information that available in game using just the corporationID argument. There are now a couple of new API classes I added to take advantage of the corp info available in a couple of the existing APIs.
The first one is account/YapealCorporationSheet.php and uses the info from the accountCharacters table. To avoid conflicts with any exist corporation keys that might have the CorporationSheet API active they are filtered out so the less complete public info doesn't overwrite the detailed info from the regular API. This one is active by default as it adds little load and most apps should find the addition info useful.
The other new class/API is eve/YapealCorporationSheet.php. It uses corp info from the eveMemberCorporation table which is part of the eve/AllianceList API. This one is still considered experimental and is NOT active by default. On average in Eve there are ~13k corps in some kind of alliance and getting even just the public information on them adds a lot of load to Yapeal and the Eve API servers. I made the cache interval a day long as that should be often enough since corps are limited on how quickly they can leave and join alliances. Note that at this time the corp IDs are not filtered like with the other API so more detailed info can end up being overwritten but I plan on fixing that in the future. Note that during testing it's been taking up to 1.5 hours to run this API. I believe why it's taking so long for me is do to the high latency I have since I'm on the West Coast in the States and the servers are a 1/3 of the way around the world from me. It would be nice if someone in Europe which should have less latency would try it for me so I'll know for sure if that's really the issue I've been having. Anyway as I said this one is experimental still and I'd like to get some feedback on how it's working from people before I make any additional changes.
As always thank you for use Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.25 23:56:12 -
[62] - Quote
Tesla Ming Chent-Shi - I just notice the forums eat my reply to you it seems Have a look at post 142 above as it's about the same API and has info on what to look for.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.28 02:48:29 -
[63] - Quote
So added SkillInTraining API for anyone that uses it instead of the SkillQueue API. I'd like to thank Icy0ne for his work on it. It's actual very rare to have someone add code to Yapeal other than myself so it does mean a lot to me that someone took the time to do so. Also his work on a couple of the other APIs in his branch lead to me fixing a couple of the issues I've pushed out over the last couple of days.
As always thank you for using Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.30 08:49:05 -
[64] - Quote
HI all thought I'd let you know I've update the 'yc D:I' and 'yc D:U' commands. Probably the most noticeable change will be they now are better integrated with the rest of Yapeal and can be ran from directories other than the base directory. So where before you couldn't run them from the 'bin/' directory you can now.
The other thing I did while I was working on them is made them a little smarter so now some of the stuff that use to be in the SQL files can be removed. I updated the existing SQL files but no updating is needed to the tables etc.
The next time you run the 'yc D:U' command you should notice it being a bit faster as it no longer is adding and dropping the procedure over and over again for each file. This will probably be more noticeable when there are multiple update files to bring your database current.
As always thank you for using Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.10.02 14:38:50 -
[65] - Quote
Okay like to thank Xinryu for noticing and working with me while I figured out an issue with the corp/WalletJournal and Transactions. Seems it wouldn't update the cachedUntil date-time for non-faction warfare corporations and I'd never noticed it https://github.com/Dragonrun1/yapeal/issues/63
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.10.09 20:10:40 -
[66] - Quote
Ok I pushed out a couple fixes today for everyone. First one for char/ContactNotifications which was mostly typos that QA (me) missed The other was on the new char/SkillInTraining where Yapeal was modifying the cached XML in a way that made it invalid when it tried to get it from the filesystem.
Be aware there are some changes coming to char/CharacterSheet which will mean Yapeal will probably be broken until you update after its deployed. An update is in the works and I should have it deployed on the same day when it goes live on TQ. I'd deploy it sooner but since the changes are NOT going to be backwards compatible they have to wait. For anyone that missed the thread about the changes check out https://forums.eveonline.com/default.aspx?g=posts&t=378333&find=unread
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.10.20 03:35:13 -
[67] - Quote
Hi everyone just thought I'd let people know about some of the updates I been putting out over the last week or two. Mostly some small issues with some lesser used API like eve/CharacterInfo. I also did some refactoring on how Yapeal does it's XSL transforms which should help out with future Eve API changes since CCP is paying more attention to it again and seem that there is a full-time person in CCP FoxFour working on it and the CREST stuff which is great, but means things change more often which can cause more updates for me to do as well in Yapeal. The XSL changes should more future proof against any reordering of the XML etc that sometimes happens which breaks the XSDs. This mostly happened on Eve APIs that used a lot of elements instead of attributes in the rows.
After the last update I just finished Yapeal should now have all the updates it'll need for Phoebe which is expected Nov 4th. That of course is assuming there aren't any more made by FoxFour before then He have hinted he might look at a couple more things after getting back from the get together in Vegas which I was sad to miss
On some other sad news I will probably NOT have as much time to work on stuff in Yapeal do to RL issues so I will probably need someone to take over again and keep Yapeal going. I would like to have someone step forward now so I can help them get up to speed and give them access on GIthub etc so if I do end up NOT having any time they can keep everything going. This really needs to happen in the next day or two because after that I'm NOT sure I'll be where they can contact me. So please if you can help out let me know.
As always thank you for use Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.10.29 05:41:27 -
[68] - Quote
Hi everyone, So I been working on another little project over the last couple of days and while doing some testing using Yapeal version history I noticed that Yapeal is coming up on its 6th year here at the end of the month. Yapeal had existed for a few months as part of another corporation project before this and even as a separate project but the old Sourceforge SVN has long ago been deleted so records of the earlier code is probably lost now.
We do have the history starting from when I start working with some other developers on what was going to be a open source Eve API framework that everyone could use to make their own tools. Yapeal was going to be the core API library for the tool and one of the developers suggested that GoogleCode might be better place to do it than Sourceforge. I liked some of the features GoogleCode had at the time too so I moved Yapeal over. When I made that move there wasn't any good tools to import from one SVN into another so I simple created the new project and copied over the files and committed them. Yapeal has of course been host other places since then in several different versioning software (SVN, Mercurial, GIt) but I've been able to import the history from one to the other every since when I changed Yapeal over.
As I was saying Yapeal has been hosted on SF, GoogleCode, BitBucket (Not public), back to SF, and finally the move to GitHub. In most cases I made the move because either the new host offered one or more things I found useful or in one case (GoogleCode) they removed features that I needed and/or wanted. I probably would have moved directly from GC to GitHub but at the time I still didn't know enough about Git to see the advantage of using it vs Mercurial which Yapeal was using at the time.
For those of you that want to have a look at this very early version of Yapeal you can see it here.
A few things to notice is that even though it was called Yapeal there was no yapeal.php file yet you actually ran it using the backend/eve-api-pull.php file. One thing I just noticed while looking at that file is the old SVN revision number that would have come directly from the old SVN on SF since I hadn't set it up yet on GC to update.
$Revision: 20 $ $Date:: 2008-10-24 00:48:59 #$
The reason it was so low is I had just make Yapeal public on SF not more than a couple weeks before as I remember it. Before that I'd hosted on a private server either at my home or probably at a friend's place because he had a better internet connection and more HD space Just a few other things to notice is that Yapeal was mostly procedural code at this time with just a few classes being used. It only worked with about a dozen APIs from the eve, corp, and char sections. Most of the char APIs were very new since the eve and corp ones had been the main focus of development up to that time. It's worth looking through the Docs/User Guide/User Guide.xml file to get a bit of an overview on my vision for Yapeal etc. It's actually the source DocBook file for the HTML and PDF files that would have been included in the tgz and zip files that was the expected way for people to install it at the time. Unlike now where the developer tools are just included with Yapeal I actually had another separate project for all of the development stuff I also had to maintain etc.
What I notice when looking back on this original code is how many of the ideas that I had already developed about how to make things work already existed and can still be seen at least by me even today in it. There are also parts of it that just make me want to hide because some of the code has some really ugly hacks in it. I have to give myself a little credit though because I was working within the limits set by PHP 5.2 and this was really my first project written in PHP. I was in many case still learning about all the commands etc of PHP and first applying what I'd just learned in Yapeal. I think I'd first become interest in learning PHP only 6 months to a year before I start Yapeal and it was by far the biggest project I had ever done. Before this I had always been more into hardware than software and playing around with some JS for web pages.
Anyway I hope everyone has enjoyed the little trip with me down memory lane and here's to at least another 6 years for Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.10.29 17:30:20 -
[69] - Quote
So after StGoe reminded me that it didn't exist I've added an option to turn off the file system caching for the XML. The new default is for it to be off as that's probably the most useful for people at least in production. Also while I was at it I added a setting to allow you to change the name and location of the main cache directory with the default being its current location. If you just want to use the defaults you don't need to update your config/yapeal.yaml file although it wouldn't hurt to do so
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.11.04 03:14:34 -
[70] - Quote
So just finished pushing out an update that should have all the updates needed for Phoebe. Only real breaking things should be the changes to the CharacterSheet tables so if you use it make sure you don't do this update until the Eve update happens. I may have another small update after it comes out in case there are any differences that I couldn't test for on the test server or if CCP made any last minute updates etc
Make sure you've read https://developers.eveonline.com/ for all the API changes that might be affecting any tables you use. Basically for charCharacterSheet there some new columns and the charAttributeEnhancers table is gone and replaced by charImplants table that will also have the slot 6-10 implants as well. Also two new tables charJumpClones, and charJumpCloneImplants. There are a couple other changes to some other APIs but I've already deployed them as they didn't make any breaking changes just add a couple of new columns in tables and I set them as optional which I'll probably update sometime after this update to make them required as needed.
Let me know about any problems and I'll make sure to do updates to fix anything I missed.
As always thanks for using Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.11.04 15:47:37 -
[71] - Quote
Legedric Striker - that's normal for any API that haven't been implemented yet.
Tiberius Zol - Looks like some how you already have some invalid existing rows in your charCharacterSheet table. Probably the best way to handle it is to just truncate it and let Yapeal do it's thing to refill it. Might delete any characterSheet rows in utilCachedUntil to speed up the process.
The only reason I was updating that column is it was out of order and I didn't change it in any other way. DoB has always been a required column with no default value so you really shouldn't be getting an error there except if you have edit the row or found a way to import it without the DB giving the same error before and you worked around it
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.11.04 20:07:15 -
[72] - Quote
Some of you might have noticed a small problem with the cloneImplants stuff but I've already pushed an update. https://github.com/Dragonrun1/yapeal/issues/80
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
65
|
Posted - 2014.11.10 22:22:28 -
[73] - Quote
Norian Lonark - Since you have SSH access you have several options. If you are working on a new project or a major update to an existing one if you converted to using Composer for your dependances it's simple to add Yapeal as one of them. Another option since you can also get Yapeal as a zip file directly from Github is to get it that way and just unzip it where you need it. If you are using some kind of version control like Git you can also setup Yapeal as a subtree like I did with Pimple so you can import it and update stuff as bugs and other updates are done to Yapeal. Git has option to create a compress or uncompressed archive which can be sent over a SSH connection as well. Those are just the options I came up with off the top of my head
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
66
|
Posted - 2014.11.13 19:11:22 -
[74] - Quote
Thought I'd documented that some where but easiest way to manually start Yapeal or use it in a crontab etc is to use bin/yapeal.php. It works basically the same as the old yapeal.php did. There are also options to call any of the per API classes directly for one-shot type needs as that was one of the planned features to be added with this rewrite.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
66
|
Posted - 2014.11.16 19:40:22 -
[75] - Quote
Battle On - There really aren't any tutorial type docs like you are looking for. One reason for that is that I find it very hard to write anything useful to anyone new to Yapeal since I wrote 95+% of the code and have been work with it for over 6 years now. I just don't see it the way someone looking from outside does. In the past there has been a couple people that wrote about how to use the old version that I then edit and tried to maintain but so far no one has done the same thing for the current version. My suggestion on how to learn to use the individual API classes is to follow the code from bin/yapeal.php through lib/Yapeal.php and on to how the AutoMagic() calls oneShot() in the class you are interested in. It would be great if someone like you that is just learning to use Yapeal would write about it but so far no one has.
If after looking through stuff you still have questions you are welcome to ask on this thread or even contact me via E-mail etc. I'm also usually available on G-Talk and IRC when I'm at home near the computer. And for those that prefer talking to typing I can usually be talked into some voice comms as well if you really prefer that.
In other news I decided since I'm current not doing much new development work on Yapeal right now and the rate of bugs being reported is slowed down it was about time to do a tagged release so now you'll see a 2.0.0 version on GitHub and at Packagest as well if you look. I'd been thinking about doing this for at least a month but decided to wait until after Phoebe changes were merged into master and any needed fixes had been done.
As always thank you for using Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
66
|
Posted - 2014.11.17 20:23:30 -
[76] - Quote
Battle On - https://github.com/Dragonrun1/yapeal/issues/82 - fixed
Quote:First of all, when fetching with composer, it gives an error that "dragonrun1/file_path_normalizer" cannot be found in packagist. Probably because the version changed or something. I'd suggest looking into this. It's easily fixable by pulling it in manually, but it would be nice if it was included in de dependancy of yapeal.
Think it was because I was working on that class yesterday and did several commits in short order etc so it should be working right now. If it still seems to be giving trouble try deleting the composer.lock file and use composer update -o to have it recreate it. also worth having something like the include_once - die block from bin/bootstrap.php in your own code to take advantage of the great PSR-0/PSR-4 auto class loader that composer generates for you. I found the code some where in another composer package and added a few improvements/tweaks to it as well. You should be able to just drop it some where in your project and it'll manage finding the autoloader and than you don't have to worry about doing any more includes for classes etc.
Quote:Instead there is the bin/UtilRegisterKey class which needs and instance of PDO and in instance of CommenSqlQueries. However, i have no idea how to set these two up, since im not familliar with PDO (I'm used to using mysqli, or use a framework like Laravel which comes with eloquent, which handles everything for me) nor the CommenSqlQueries class.
CommonSqlQueries you'll find in lib/Database/ and is just a simple class I use to collect up all the SQL queries into. Just pass it the database name and table prefix you are using in the constructor. PDO isn't really that much different from mysqli and is probably what Laravel uses as well internally. I would suggest learning to use it instead of mysqli as in some future version of PHP mysqli is going away plus the PDO prepare statements, if used, can go a long ways towards preventing DB ejections which is near impossible without a lot of code with mysqli. If you have a look in lib/Configuration/Wiring::wireDatabase() and ::wireDefaults() you can see how PDO is setup normally in Yapeal but utilRegisterKey takes care of it's own init stuff so you just need to give it an active PDO and it'll take it from there.
Quote:Furthermore, it would be nice to have some kind of helper class/method that can give you these two instances based on the yapeal.yaml config file that you used earlier. This way, yapeal can live completely on its own without the user needing to make an own instance of PDO and such, but only needs to add the keys he needs and populate the database using bin/yapeal.php.
That already exists it's called lib/Yapeal.php. It was made to be extended as needed and used. Its only requirement is a working autoloader and a ContainerInterface compatible class. You can find info on the interface and the default class that Yapeal uses in lib/Container/PimpleContainer. It's basically a wrapper around Pimple 2.0 which you can find in subtree/Pimple/. I use a git subtree for Pimple instead of through Composer because most things are still using version 1.x and Composer errors out on the conflict when I do. You might also look at bin/yc and the lib/Console/Command classes to see some possible less complex ways to do things like reading yapeal.yaml and DB setup stuff. You should find that extending the Yapeal class is really easy as all the walking APIs stuff in contained in autoMagic() and can be ignored if you don't need it and just add your own methods to it for what you need. You will probably want to look at how autoMagic() grabs the DB info, calls the per API classes etc. I did a 10 minute quick example of how part of a signup check and registering might look like which you can find here that I made to show extending the Yapeal class. Maybe it'll give you some ideas how to do what you are trying to do.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
67
|
Posted - 2014.11.19 21:14:07 -
[77] - Quote
Battle On - More like that feature of using config outside of Yapeal directory was never implemented but I'll look at fixing that so it will look up and over to config directory for a config file as well like it says in the CONFIG.md.
https://github.com/Dragonrun1/yapeal/issues/83 Pushed an update that should work now if you can give it a try Battle On and let me know if it seems to work for you.
Just to make it clear how this works if you have both myApp/vendor/yapeal/config/yapeal.yaml and myApp/config/yapeal.yaml files then any settings in the later file overwrites any matching setting from the first file and they both overwrite any defaults set from Wiring::wireDefaults() . So for example if you have the following:
--- # myApp/vendor/yapeal/config/yapeal.yaml Yapeal: Database: database: yapeal1 userName: IAmADummy ...
and
--- # myApp/config/yapeal.yaml Yapeal: Database: database: yapeal2 ...
then the merged settings would be:
--- # myApp/vendor/yapeal/config/yapeal.yaml Yapeal: Database: database: yapeal2 userName: IAmADummy ...
and all other settings would use their defaults.
Sorry I didn't have it implemented before but in the thousand other things that went into re-writing Yapeal it just fell through the cracks
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
67
|
Posted - 2014.11.20 18:21:22 -
[78] - Quote
Battle On - it's set in Yapeal::wire() if it notices any 'vendor/' directory in the path.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
67
|
Posted - 2014.11.20 21:52:00 -
[79] - Quote
Added setting it in the 'yc' stuff as well. Note you will only see $dic['Yapeal.vendorParentDir'] if Yapeal has a parent vendor/ directory in its path. It should set it if you are doing something like
$yap = new Yapeal($dic); if (isset($dic['Yapeal.vendorParentDir'])){ print 'Parent = ' . $dic['Yapeal.vendorParentDir'] . PHP_EOL; } else { print 'Parent not set!' . PHP_EOL; }
You would need to use isset etc as $dic is not just a normal array but an instance of Pimple which in many ways can work as an array but doesn't always work well with things like var_dump().
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
67
|
Posted - 2014.11.26 22:13:21 -
[80] - Quote
Things like WalletJornal do build history but others like AssetList, or AccountBalance do NOT they are deleted and replaced on a per char/corp basis.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
|
Dragonaire
Here there be Dragons
68
|
Posted - 2014.11.27 00:58:14 -
[81] - Quote
Hi all I know it's been a while really since I added any new APIs so I decided to look at one that has been outstanding for a good long while and see about adding it. I decided MailBodies shouldn't be to hard to do so I did it. It did turn out a little more complex than I had expected because I forgot i was one of the irregular APIs that use rows with attributes and the element value but since it was only one of each I took a short cut there on how to deal with it.
A heads up for anyone using NOTICE level logging in production (btw WARNING is strongly recommended) you will start seeing some log lines about 'CachedUntil is excessively long was given ...' There isn't anything really wrong here just that Yapeal is noticing the 10 years cachedUntil time the API returns. I'll look into it some more and see if I can quiet it down some way if I get a chance.
In other news do to some RL issues I'm going to be having to move sometime in the next week to a month and not sure what kind of Internet connection I'll have or time to do anything so hopefully people that are already using Yapeal can step up and answer any questions on the forums here and I'll see if I can get someone to help with any bug fixing that might come up. One person does have access to Github and has some knowledge and experience with the code so he can probably deal with most things that might come up. He was even asking about if I had anything I want him to work on the other day in Yapeal since he has some time off work so maybe he'll get a couple of things done while I'm dealing with RL for a while .
As always thanks for using Yapeal, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
68
|
Posted - 2014.12.02 19:37:50 -
[82] - Quote
Thanks to Melikoth for spotting this: Issue 84
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
68
|
Posted - 2014.12.07 03:28:47 -
[83] - Quote
Jahn Ntago - Think you are confused about how it works which I was at first too The threshold keeps it from logging anything until the log message meets the threshold then it will log the prior 'bufferSize' worth of messages. It then continues to log all message regardless if log level until the end of the run. So with your settings on the first WARNING (300) level log message it'll continue to log from there plus a few before so you know what lead up to it. The question I would have is what is happening to cause Yapeal to log something with that high a level message?
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
68
|
Posted - 2014.12.09 20:47:13 -
[84] - Quote
Jahn Ntago - First glad you find Yapeal useful but just reading through your post I'm a bit confused by some of the partial log messages you gave.
Quote:yapeal.WARNING: Failed to upsert data from Eve API char/ContactList due to weird formatting of names: "Invalid datetime format: 1366" Considering there are no date or time columns in that API table I really don't see how you could get that error.
Quote:yapeal.WARNING: Failed to upsert data from Eve API account/APIKeyInfo for due to a "Syntax error or access violation: 1064" That would suggest some kind of SQL syntax error which though possible is very unlikely except if it's doing it for all keys but I got the impression from your post that wasn't the case.
Quote:yapeal.WARNING: Failed to upsert data from Eve API corp/CorporationSheet due to the schema not supporting REALLY big corporations (fixed by me) : "Numeric value out of range: 1264" Because of the mention of REALLY big corps I'm assuming you mean ones with lots of members. I do notice some possible issues with the 'memberCount' and 'memberLimit' that are probably do to some copying and pasting and not fully editing them afterwards which can probably be fixed but like the others since I don't have the complete log messages I can only guess that the changes I might make would fix it.
May I suggest you either give more complete info and log messages here or even better create each of these as an issue on GitHub so someone might have a chance to fix them for everyone instead of you having to 'customizing' Yapeal and in effect be maintaining your own private branch you would need to be constantly merge the main project into all the time as other issues are fixed there? If for some reason you feel some of the data within the log messages is to sensitive to post here or in a issue you can of course either mask with dummy data or directly E-mail it to me through my GitHub listed account and I'll take a look at it there.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
68
|
Posted - 2014.12.10 23:34:38 -
[85] - Quote
Push a couple fixes for some of the issues Jahn Ntago noticed. ContactList does NOT allow UTF-8 contactNames corpCorporationSheet does NOT allow for large membership.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.11 19:25:11 -
[86] - Quote
Tiberius Zol - I'm puzzled why you say you can't use composer as you can run it anywhere you can run Yapeal. All you need is PHP and the composer.phar file some where with access to a command line interface. The last part can even be some what optional if you have a public facing web server as well. You just need a web page that starts composer with the correct options in the right directory. Having file_path_normalizer as a separate package is no different than say monolog being a separate package that Yapeal also needs.
Legedric Striker - I wouldn't worry about it to much except if it keeps happening. Yapeal generally ignores the 'cachedUntil' DT from the XML if it way off and uses 'currentTime' plus the interval from 'utilEveApi'. Another thing that seems to happen a lot on days when CCP does updates is the API returns a lot of errors including ones that have 'retry after ...' and Yapeal is made to obey them any time it sees one but it'll self correct in all these cases normally within a day except if there really is a problem with your account or the key.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.11 22:17:36 -
[87] - Quote
https://github.com/Dragonrun1/yapeal/issues/87 Make sure you run yc D:U so the database table is updated.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.12 17:44:02 -
[88] - Quote
It gets the file names directly from the file system so they would be correct so something else going on.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.12 18:10:15 -
[89] - Quote
I would say try deleting all the files in bin/sql/updates and do a 'composer up -o' that should make it replace the files just in case they got messed up some how or something else in Yapeal is not right
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.12 18:44:02 -
[90] - Quote
Use of undefined constant STDIN - Make sure you are using cli version of PHP and NOT CGI etc as they don't have STDIN by default available.
The other error sounds like you did a find/replace that didn't just change the stuff in your code but also on everything in vendor as well. I've done this a couple times myself with IDE. Try just deleting the vendor/dragonrun1/file_path_normalizer directory and running composer again it should be able to update it without prompt then. This might also help with the other problem.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
|
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.13 23:06:47 -
[91] - Quote
Okay so been looking at the list of past issues and thinking about them a little and decided if I took the time and made one change to the whole database it would solve a lot of issues that keep coming up all the time. The issues are cause because some tables are created using ASCII character set and others UTF8. That general worked well in the past but as CCP has made things like character, corporation and alliance names etc more internationally compatible it has become a lot more of a problem. So I decided to just convert everything now and it should prevent many issues in the future for everyone especially me
https://github.com/Dragonrun1/yapeal/issues/89
Just update Yapeal and run 'yc D:U'. Note that it might take a little while to run depending on how much data you have in your database because it has to check/convert the existing char, varchar, text, etc columns for all 126 tables in Yapeal plus set the default for new columns on all the tables and the database as a whole.
As always thank you for using Yapeal, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.14 17:28:40 -
[92] - Quote
Figure out the other error Jahn Ntago was having and pushed out something that should fix it. Turned out to be an edge case of an API keyID for an account with no characters that APIKeyInfo wasn't handling well . https://github.com/Dragonrun1/yapeal/issues/90
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.15 15:47:55 -
[93] - Quote
accountAPIKeyInfo is right I'll fix.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.16 10:30:13 -
[94] - Quote
fixed
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
69
|
Posted - 2015.01.01 19:40:26 -
[95] - Quote
So thought some of you might find this interesting. One of my another small projects from GitHub that I use in Yapeal has been nominated for an award on the PHP Classes site. You can find more about the class here: http://www.phpclasses.org/package/8912.html
And you can also find out about voting for it or any of the other nominated classes here: http://www.phpclasses.org/vote.html
On other Yapeal news I've started a new experimental branch where I'll be working on new stuff. I'm basically going to use it as a play ground/testing area for some possible new ideas for Yapeal that may or may not be in future versions. You should expect it to be often broken and have a lot of WIP code but if your interested in seeing what the future of Yapeal might hold you're welcome to have a look and comment on GitHub. Do try to keep anything related to the experimental code on GitHub and not here so as not to confuse anyone read this thread. I may from time to time ask for input here but usually only when what I'm working on becomes a RC for next version of Yapeal.
Something I'm currently looking at adding an event system to Yapeal or even re-writing Yapeal itself to use a event-dispatch system. The reason I've been looking at this is that it would open up the possibility to have Yapeal run in a cloud which would let it scale much better for large sites. Anyway like I said some of you might find it interesting to follow what I'm doing in the experimental branch.
As always thank you for using Yapeal, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
71
|
Posted - 2015.02.07 02:23:22 -
[96] - Quote
Hi everyone so just realized it had been a while since I'd posted anything here so decided I better update everyone on some things I've been do with Yapeal. First Yapeal has moved again but not very far After experimenting with Github organizations I decided to go ahead and move Yapeal into its own. What does this mean for you you ask? Not much Github should auto redirect you to the new URL but you might make sure any browser bookmarks etc you have saved get updated as I think the forwarding end at some point.
Install - If you use composer you don't have to do anything I've already update Packagist so everything should just work If you use git directly you'll either need to update the remote repo info in Git or another option is to simply delete your current git directory for Yapeal and recreate it using the new info. Make sure you back up any config/yapeal.yaml and bin/sql/CreateCustomTables.sql files you might have there etc before you delete.
Updates - While I was at it I have done some maintenance type things on Yapeal based in part on stuff I've been work with in the experimental branch. First I've decided to go as fulled to PSR-1,2 standards as I can with Yapeal. As I've noted before version 2.0+ has generally been to PSR1 standards but now that more of the developer tools have started understand the PSR-2 stuff and I've got more comfortable with the way code should look when using it and I've also had a chance to use it on some of my other projects I decided it's time for Yapeal to change over as well. Note it doesn't really change how it runs but if you look at the code you may notice some difference in spacing and how the code wrap etc.
Something that may be more noticeable is I've converted all the files in Yapeal to use Linux (Unix) style line ends including the README.md etc. I the past to make them easier to access for people on Windows platforms I've kept them with Windows line endings but now that there are some many free editors out there that understand both I've decided to switch and make my life easier. Only people this might effect is anyone trying to use notepad etc on Windows trying to view them will see just one long line. I'm guessing anyone that going to be using Yapeal already has an editor that can handle this plus all of them can be view directly on GitHub as well.
Another new 'tool' I've been starting to use is SensioLabs Insight. I kind of have a love/hate thing going on with it mostly because it thinks Yapeal is really badly written It isn't but there are some things I have done that they don't think much of mostly in the code used by 'yc'. Like many PHP tools they assume the only thing people use PHP for is in webpages. I've submitted some bug reports etc to them to look at making it better in a few areas for console type apps as well. The main reason I decided to say something about it is I'll probably being doing some commits over the next few days to fix stuff it reports but I also thought I bring it to everyone's attention since I'm sure many of your apps are web based and it can be a neat tool to help you improve things.
You may notice I've delete the old PhpUnit test that were in tests/. They have been failing for a while because of some changes that were done to Yapeal a while back. I've basically been having to ignore travis on each commit complaining about them. I originally was going to fix them so left it going but I've decided that fix the existing tests and trying toaddd all the others that I should write for the over 100 classes in Yapeal was just to much. Don't get me wrong I think tests are great and I'm not happy about not having them but if you've even wrote PhpUnit tests you know they are the easiest thing to work with. PhpUnit is a great testing tool but for something like Yapeal I just have come to feel it's not a good match with all the DB and network code that Yapeal uses plus there are some other things reason as well that I'm not going into here. What I am looking at is switching to something like PhpSpec instead for at least any new code I add. I may also do a few specs and examples for the more critical stuff in the existing code as well if I rewrite it. Just a quick word on why I think PhpSpec might be a better match is it talks to the behavior of the code which is what is more important than the details of how the code goes about doing it. Both PhpUnit and PhpSpec let you test for the behavior but PS just makes it easier and it doesn't bog you down in a lot of setup details or let you start trying to check the internal state of class like I as least always seen to end up doing when using PU trying to make sure everything is good.
Okay I think that enough for one post and if you manage to read the whole thing your gate camp must be really boring and slow or the mining is in Eve for you.
I'll try not to go so long between post so they don't get as long hopefully.
As always thank you for using Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
71
|
Posted - 2015.02.11 02:47:26 -
[97] - Quote
Tiberius Zol - I think there is currently so kind of split going on between newer vs older versions of MariaDB and maybe also it and MySQL which is effecting stuff. Could you try running this show variables like "version" and let me know what you get back that might help me track it down more. I'm currently running '10.0.14-MariaDB' and in the process of updating to 10.0.16.
On the failing AccountStatus could you maybe send a copy of the XML as I don't have any example that have the offer part to use to update the XSD. Dummy IDs and names etc are fine just need to be able to see the structure. Just send it to my e-mail on GitHub is probably the easiest thing to do.
On the IndustryJobs stuff not sure why you might be having problems but you probably need to look for it in your log files and post that for me to have an idea. It sounds like you're getting the default values from the DB so somehow they are getting there from the XML might turn the file cache on and look at the actual XML and see if something looks off there as well.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
71
|
Posted - 2015.02.11 17:24:34 -
[98] - Quote
Okay sorry guys looks like in that last push I made a '!=' into a '===' by mistake instead of a '!==' which broke the attribute preserver stuff I just pushed the fix for it. Tiberius Zol this should fix what you noticed with the IndustryJobs and it was effecting other things to but just hadn't noticed it apparently
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
71
|
Posted - 2015.02.11 20:59:30 -
[99] - Quote
So on a better note that the last post I've added something that some of you will probably find useful if you deploy Yapeal in you app in some way. I the past you could have a bin/sql/CreateCustomTables.sql file to do additional DB setup like adding additional tables etc. The main problem with it is if you use composer to install Yapeal there was no easy way to put you file there so Yapeal would see it. I have now made it so Yapeal will also look in the config/ and if installed from composer into vendor/ it'll additional look for it in vendor/../config/ so it can be with any other per install config you do. So you can have it in the same directory with your yapeal.yaml file which should make it much easier to integrate with your app.
Something I'm probably going to do in the near future (next couple days possibly) is start move some stuff around to what I feel are better places for them. One of the first will probably be moving all the stuff currently in bin/sql over to lib/Sql/ instead. At the time I put them in bin it was simply because I need them somewhere else different than where they were in the old 1.x version of Yapeal and couldn't really think of a place I like at the time. Of course with time what was just a few basically static files used to do one time init of the DB and tables has grow into a full init and update system with a lot more files etc. There also some other Sql related stuff laying around other places in Yapeal that could stand a place of their own so I decided it was time to just go with the lib/Sql directory and that would also let me centralize some of the other stuff into a Yapeal/Sql namespace as well.
There are a couple other thing that I'd like to move and that the *.xsd and *xsl file that now are with the *php under lib/Database/*/ directories. Have them there is some what easier to work with when design things but gets very messy with the char and corp section because of the number of APIs. So look for them to be moved as well in the future.
None of this changes should really effect how you use Yapeal or anything, they will just mean you'll need to look for things in some different places as will I .
As always thank you for using Yapeal, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
71
|
Posted - 2015.02.16 01:31:23 -
[100] - Quote
Jahn Ntago - Sounds like there a missing clearing of the table per corp in that API that no one has notice before I'll see about fixing it.
https://github.com/Yapeal/yapeal/issues/93
See if that fixed it for you.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
|
Dragonaire
Here there be Dragons
72
|
Posted - 2015.02.17 17:39:54 -
[101] - Quote
Jahn Ntago - So I know its clearing all rows in the table and than applying the new info from the XML so I'm pretty sure its not an issue in Yapeal. I'm wondering how you are testing and if it's just something having to do with the cache times. MemberTracking uses a 6 hour cache so the XML can reflect them as still in the corp up to almost 12 hours after they leave a corp with bad timing. If you are still having problems with this please enable the XML filesystem cache so you have the XML for MemberTracking plus the other table's XML you that shows them as no longer in the corp so you can send them to me along with the log so I can try figuring out why it might still be happening. Also you should change the logging level so its including debug to get more details. You can E-mail everything to the one listed on GitHub and I'll take a look and see if I can figure out what is going on.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
73
|
Posted - 2015.03.12 05:08:30 -
[102] - Quote
https://github.com/Yapeal/yapeal/issues/94 fixed
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
74
|
Posted - 2015.04.23 19:33:03 -
[103] - Quote
Hi all give thought I'd let people I'm still around but been busy with work so not been working on Yapeal lately and it seems the last few changes I've made a couple months ago have largely killed most of the common bugs that get reported . Hopefully I'll have some time again to get back to some stuff I was working on in another couple months.
As always thank you for using Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.05.06 21:03:19 -
[104] - Quote
Sorry I haven't even been on the forums for a week because of stuff IRL. Using the new Yapeal and the old aren't that different in many ways you have Yapeal running in the background via crontab or task scheduler and it 'automagically' keeps the database updated. Just start php use bin/yapeal.php and it'll take care of everything else for you.
If you need to do something like verify an API key using Account/APIKeyInfo you can call the required class directly. You can find each per API class in lib/Database/ and use the oneShot() method for sign-in type stuff. In bin/ you'll find a UtilRegisterKey class that should help with add the required APIKey info to the DB tables needed for Yapeal's automatic stuff to work.
All the database and tables creation stuff is covered in the *.md files using the bin/yc console commands. The best way to understand how Yapeal works is to look at the code itself starting with the lib/Yapeal class which kicks off all the other stuff. You can see how it's called by looking in bin.yapeal.php which just insures the composer class autoload is started then creates and start the class passing it it's one required parameter.
If you have any other questions just post them here I shouldn't be away so long again and I or someone else should be able to help you out.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.06.05 17:16:21 -
[105] - Quote
Any docs that say the mask is optional is for the old 1.x version. 'activeAPIMask' in utilRegisteredKey is required to receive any API data for any API key now and has been since at least version 2.0.x.
Riley Masterson is correct removing the key record from utilRegisteredKey does not remove any of the of the data from the other tables if you need to do that you'll have to do it in your own code.
Remember also for any API the API key you are using must have the needed access active which means to get privileged info from some APIs like 'corpMemberTracking' it need to be from CEO or a Director since they are the only one with that level access. Yapeal logical ANDs together the 'accessMask' bitmap in accountAPIKeyInfo that comes from CCP with what you set in 'activeAPIMask' from utilRegisteredKey to decided which APIs are active from a given API key. This allows you to decrease which API info to get but not try to increase beyond what the API key allows and cause extra pointless errors from the API server.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.06.10 16:37:42 -
[106] - Quote
Legedric Striker - So probably was happening with the older version as well it just didn't do as good a job of logging what was going on. Since the event system that was planned hasn't been added to Yapeal yet you'll have to do a couple things to make it so Yapeal can handle this automatically for you. The easiest thing to do is extend from lib/Xml/GuzzleNetworkRetriever and add code to the catch RequestException code to inspect the returned error and handle the 403 errors. Probably not good idea to add all the code there but in another protected method but that the point where you can first intercept the normal process of just report the exception. The other thing you'll need to do is have Yapeal use your version of GuzzlwNetworkRetreiver instead of the default one. For that you just need to set 'Yapeal.Xml.Retriever' in the ContainerInterface $dic you pass to Yapeal class when it is called. The default is set in lib/Configuration/Wiring::wireRetriever() and you should be able to basically copy the code there and just change the class name in the new statement for retriever. Yapeal because of the if statement at the start of the method will not try overriding what you have set for 'Yapeal.Xml.Retriever'. If you need some additional help with this just Email and I'll help out as I can.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.06.10 18:24:35 -
[107] - Quote
I also just got to thinking about something and I don't think Yapeal checks the expires column from accountAPIKeyInfo table either before making the other API calls so that might be something that could be implemented as well. I'll look into it. That might help with at least some of them. Might also try just run query on DB to look for those yourself as well and it might help find some others that you might have missed.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.06.10 19:46:26 -
[108] - Quote
Legedric Striker - https://github.com/Yapeal/yapeal/issues/97 I've push a possible fix for this if you could give it a try and see if it clears up any remain API errors and let me know that would be helpful
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.06.11 19:01:36 -
[109] - Quote
You shouldn't be having timeout problems except if you are using the webserver SAPI version of PHP as the CLI SAPI ignores the timeout setting from php.ini. Normally the CLI version is at /usr/bin/php but usually if you just call bin/yapeal.php directly from your crontab it'll find it using env in the first line just like most scripts find bash or python etc.
I've also been thinking about adding back in the soft timeout timer like Yapeal had before. It got removed during the refactor for version 2.x but could be useful to have something like it again. Would prefer to make it configurable in yapeal.yaml if possible as well so if I get a chance I'll look at how I can add it back in.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.06.14 20:29:04 -
[110] - Quote
Hi all, so decided to rename the 'isActive' column in several of the util* tables to just 'active'. The old name was really a hold over from version 1.x and I'd been thinking about change it for a while. This will probably be most noticeable in utilRegisteredKey to most people. I haven't update any of the docs yet to reflect the change but will be doing that soon(tm).
Good news is I also have done some work on bin/UtilRegisteredKey class to make it more useful. It now acts as a more complete model for the table and can both read exist rows and do upserts. I also reduced the dependencies to just PDO which should make it easier to integrate into you own projects. The changes did break backwards compatibility but I think the benefit of the new abilities will out weight the pain. I don't expect to need to make any other changes to it now and it now is the recommend way to make changes to the table going forward.
I'll be looking at adding a class to help with interact with utilEveApi as well for those of you that turn APIs off etc. Let me know if there are any of the other util tables you like to see classes done for. Most of them actually are not used right now but I've left them in case the functionally gets implemented in the future.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.06.22 04:10:42 -
[111] - Quote
Mintoko - Look for something that's above the threshold that is triggering the logging. It only takes one WARNING to turn on logging for the rest of that run for all levels of logging.
Currently the only cache is filesystem as I never wrote the DB one for version 2.x. When I asked around no one seemed to be using it so with the limited developer time I have it lost out to other things. I've left in the tables for it so it can be added again by someone in the future. They would probably need some updates to be more inline with things but shouldn't be a lot. If you wanted to add it I'd be more than happy to merge it. Also would have a little time to answer questions via Email to help out.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.06.22 19:02:29 -
[112] - Quote
y default it print the proceeding 20 error messages when triggered and all following. I think I might know what is going on if you can try something for me we'll see if it'll fix it. In Database/common.xsd edit line 38 from
[xs:pattern value="[0-9]+(,\s?[0-9]+)*"/]
and change it to
[xs:pattern value="\s*[0-9]+(,\s?[0-9]+)*"/]
Replacing the starting '[' and ending ']' with '<' and '>' since CCP still can't get code tags to work right [;P] Just looking at the output from the reported error it I think maybe that the XML has some extra spaces in front of the list and the above change should allow for that. If that doesn't seem to fix it then if you can post to PasteBin or Email me one of the actual invalidMessageBodyXXX.xml file I'll look at it and see if I can figure out why it's failing. Either way let me know and I'll look at push out a fix to everyone.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.06.23 21:50:41 -
[113] - Quote
Ok leave it to CCP to mess up formatting I'll try pushing it out today for everyone.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.06.25 18:14:05 -
[114] - Quote
Mintoko - Actually to get that error requires that the XML from the API server is invalid. The current date-time in the XML is less than or equal to the cachedUntil date-time they gave which means they served stall data for you to use. If you look starting at line 255 in lib/Xml/FileCacheRetriever.php you see I'm comparing the times directly from the XML itself. I added that check because they had several APIs doing this and was trying to help them find the ones that did. If you'd file a bug report and go ahead and ref this post it would be great. Most of the APIs have been fixed now but looks like APIKeyInfo still has a problem. Hopefully CCP FoxFour will get a chance to look for it and fix it for us.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.06.25 22:25:11 -
[115] - Quote
https://github.com/Yapeal/yapeal/issues/98 Pushed fixed to master.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.07.02 23:41:12 -
[116] - Quote
Hi all, So after reading about the eve/CharacterAffiliation API in this blog post: https://developers.eveonline.com/blog/article/characteraffiliations-and-the-image-server I decided to go ahead and implement it. Do to the nature of the API and the expected use it is not run as part of the Yapeal::autoMagic() process but is available for anyone to use directly with oneShot() and to give everyone an example of how to do something like that I'm put the short bit of test code I wrote up on PasteBin for you all to have a look at. http://pastebin.com/hT3uc47f Its NOT pretty nor using the best coding practices but people often seem to have questions on how to use parts of Yapeal so thought seeing some working code might be useful.
Anyway hope someone finds the new API useful and as always thank you for using Yapeal, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.07.13 05:39:24 -
[117] - Quote
So looks like we have another new developer working on the Eve APIs again so some things are changing more quickly again I'll try to get to everything ASAP but if you notice any new errors popping up in your logs let me know so I can take a look at them.
https://github.com/Yapeal/yapeal/issues/99 fixed.
In other news I'm been working on a new developer related command I'll be adding to 'yc'. It automates/helps with all the things that are needed to add Eve APIs that have a simple rowset type structure to Yapeal. They are the most common API style so should prove very useful to me or anyone else wishing to add/update an API as CCP makes changes. I'll write more about it when I feel it's more useable and out of alpha development. I only start creating it a couple days ago but it's actually coming together nicely and I in part used it for the fix above.
As always thank you for using Yapeal, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.07.13 22:03:40 -
[118] - Quote
https://github.com/Yapeal/yapeal/issues/100 fixed https://github.com/Yapeal/yapeal/issues/101 fixed
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.07.20 15:09:31 -
[119] - Quote
Legedric Striker - Glad you can seem to reproduce it as that makes it much easier to try figuring it out Maybe they have changed the cache time on that API so I'll look into it. BTW the cache interval is stored in utilEveApi table so you can just update it there instead of having another script go through the other table for you. I just looked at it and for SkillQueue it's set to 15 min (900 sec) which should be right. I'm wondering if there's something going on with the currenttime in the XML that is throwing it off instead? Might look at those if you can and see if that what was causing it. I know the API was all kinds of screwed up after this last update but it sounds like you might have had this happening before that as well. Any more info you can find out on it that might help me narrow it down would be great.
Mintoko - Thanks for info I'll try getting the new columns they added to those APIs updated. I'm sorry I didn't ended up having as much time as planned to work on Yapeal before the update so I'd have a few more of them ready to go when the update came out but I'll get to them soon(tm) I expect I'll have the character ones done first since the contact one requires adding another table or tables I think but I'll have better idea once I get a look at the actual XML here on my end.
In other news made some progress on the experimental branch of Yapeal so hope to have it in available in an early alpha test for everyone to try out. I'm still trying to decide if I'll call it 2.1 or 3.0 but lending to 3.0 because some of the public interface is change enough to require it by semantic version standards.
As always thank you for using Yapeal, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.07.20 18:30:14 -
[120] - Quote
Okay kind what I was thinking if you can find an example where it's doing it might try bug report with copy of XML and maybe they can track down in their logs what's going on. Might just be one of the API server setup wrong or something and it'll help them figure it out as it's probably giving wrong current time but cachedUntil is still right in the XML.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.07.20 22:45:36 -
[121] - Quote
Okay think I got everything updated for the changes. Let me know if something still seems to be missing. Note that several tables have been added so make sure you run bin/yc D:U after installing the update so all the DB changes happen.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.07.21 15:46:07 -
[122] - Quote
Actual most of CharacterSheet is a collection of rowsets so that all looks fine it is just that that char doesn't have any corp roles etc which isn't that unusual. The unexpected row error does suggest something is off. Make sure you got the latest update I pushed out a couple of them yesterday. Also worth delete the XMLs in cache/ just to make sure it's not a bad XML that's messing stuff up from when the API was screwy. If after do that you still have the same error for the same ones if you could email me the part of your log just before and after the error (about 30 lines each side) and the Invalid XML file I'll take a look and see what's going on.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.07.29 15:55:44 -
[123] - Quote
Ramov Tinoga - Sounds like maybe I didn't get one of the tables added to the CreateCharTables.sql file that is in the update. I'll take a look and make sure I correct it. The way it is suppose to work is the update files act kind of like a diff between the DB version that you have and what the current Create*Tables.sql create on a new install would be like but seems like in this case the update is ahead of the create . You shouldn't have to do anything else if you aren't seeing any more warnings in the logs and I'll push the updated create out either today or tomorrow as I get time.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
75
|
Posted - 2015.07.29 16:56:28 -
[124] - Quote
https://github.com/Yapeal/yapeal/issues/102
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
76
|
Posted - 2015.09.18 17:59:01 -
[125] - Quote
Sona Arnst - Sorry for the late reply been busy and not checking the forums for last few days. All of the skipping messages is normal for an update it just means you already have a newer 'version' of the DB tables already. The first time you run the update when there has been a DB change it will do the one or two updates you need but skip any you have already done or for other reasons is unneeded (for example during new installs). All the update SQL file names are made up of the date and time they where created by me, so for example 201507132213 = 2015-07-13 at 10:13 pm GMT but your DB tables are already at 2015-07-20 at 10:10 pm GMT which if you look is the last one listed in the output.
If you do a fresh install and use 'php bin/yc D:I' it will also know it's at the current version. Yapeal tracks which 'version' of the DB tables is on using the utilDatabaseVersion table. Depending on how many times you done an update vs a new install you'll see one or more numbers in the table and the update always check for the highest one that it finds and adds a record for each update that it completes fully.
Hopefully my explanation help you better understand what's going on.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
76
|
Posted - 2015.10.01 18:08:41 -
[126] - Quote
Depends on the table but most are going to have corresponding ID columns or in the case of most of the char/corp/account tables you have the ownerID column which is based on those IDs so a simple 'delete * from yapeal.theTable where ownerID = id ' should remove anything with that ownerID
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
77
|
Posted - 2015.12.11 22:02:43 -
[127] - Quote
Mintoko wrote:'utilRegisteredKey' has a 'active' column and I thought that 'accountCharacters' at one time had one as well. A character on one of my accounts no longer exists and as long as the character is listed, attempts are made to pull from the API. I'd like to keep this character listed as it references other tables. Can an active column be added to 'accountCharacters' or is there something else I could do? 'accountCharacters' didn't have an active flag but before Yapeal had 'utilRegisteredChar' and 'Corp' tables and they had active flags that could be used but with the APIs moving to 'keyID' and 'vCode' those tables needed to be dropped since everything is based on the 'keyID' now and nothing else in the APIs.
You can do what you want to do you just need to find the row in 'accountKeyBridge' that is linking the keyID to the charID and remove it. The APIKeyInfo class that manages that tables does NOT delete any old rows so references don't break but you can do so as long as you insure everything you use refs to accountCharacters table only. Note that deleting rows in accountKeyBridge only works if the charID is no longer associated with the keyID which seems to be your case. If you look at the getActiveRegisteredCharacters() method in Sql/CommonSqlQueries class you'll see how Yapeal decides which char APIs it checks. getActiveRegisteredCorporations() methods does the same for corp APIs and they both use the accountKeyBridge table to select the list of IDs so deleting the correct row there in effect makes Yapeal ignore the old char/corp you want to keep around in the other tables.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
77
|
Posted - 2015.12.12 05:57:43 -
[128] - Quote
Legedric Striker - I have been on a bit of a break from doing anything with Yapeal but I just starting working on it again a few days ago so you should start seeing more activity again.
How Yapeal deals with APIs errors has changed over time from having a system to deactivate stuff in some cases to the current system of just logging them. The problem with the old error system was it didn't give developers any options about what should happen or really let they know that anything had even happened. What is needed is something that is easy for developers to interface with that lets you decide what, how, or if you want to handle things like API errors. I've looked at many different ways to make it easy to allow things like this and other stuff and in the end I decided that changing Yapeal to use an event based system for stuff would be best. The only real problem is to change to one requires once again a complete rewrite which takes a lot of time The additional thing I've run into is all the existing event systems (projects) I looked at had what I felt were fatal flaws or other issues that meant I couldn't use them in Yapeal. My solution was to make my own but I didn't want something that would only be useful in Yapeal since I believe in writing reusable open source code is important. For anyone that is interested you can see what I came up with at https://github.com/Dragonrun1/event-mediator.
I also decided that with this re-write I needed to see if I couldn't make the job easier since re-coding everything for over 100 DB tables and the required classes in Yapeal is really a kind of overwhelming task for a single person and from past experience I knew I would get little help doing it. There is also the fact that more APIs keep being add (which is great) but since Yapeal requires adding one or more classes, SQL, XSD, etc each time it can take a while for me to add them to Yapeal which is not great for anyone trying to use it. Even just a simple new rowset API involves a lot of manual work every when doing copy and paste and it's easy to make mistakes as you can see going through the commit history. What I've been working on is something that can automatically write most of the simpler API stuff and just leave the one off type APIs like charactersheet etc for me or someone else to write. Of course writing software to write other software can at times be a little challenging and some things that have been going on in my RL have unfortunately kept me busy and not able to get as much done as I would have liked .
Any way to cut this post off before it becomes even longer than it is you can follow the progress of the next version of Yapeal at https://github.com/Yapeal/yapeal-ng. I made it into another project for now to make it easier for me to work on while mobile etc when I have a chance. Understand it's very much broken and not really working but everyone is welcome to look at it and make comments and suggestions to improve it.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
77
|
Posted - 2015.12.23 07:41:53 -
[129] - Quote
Hi all, A little pre-holidays cheer for those of you trying out yapeal-ng. I've pushed all of the stuff I've been working on out for you to take a look at. It's still all Alpha quality and not for production yet but it does try to at least create stuff now and the normal retrieve and preserving works. Make sure you check your yapeal.yaml file as there are many changes to the settings in it. Only APIs the create stuff really works for are simple Rowset types so still a lot of work to do but at least you can start seeing how it'll work. You can also get a better idea how the new event stuff works.
Legedric Striker - You should take a look at the events and give me some ideas what kind of events you'd like to see for the API server errors and I'll look at adding them in. If the only ones that you want to deal with are the XML error ones processed in Xsd/Validator::ProcessEveApiXmlError() then triggering some events there shouldn't be hard that your app can then subscribe to. If not we'll need to look at the event system in Guzzle as well to see if it'll be possible to maybe add some kind of wrapper around them so they can be integrated.
Anyway as always thank you for using Yapeal and may your holidays be great, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
77
|
Posted - 2016.01.05 03:27:05 -
[130] - Quote
Pushed large update to yapeal-ng alpha for those following it. Please try out the new bin/yc E:C command and let me know how it's working for you. To make development easier I've changed it to only work with values only(Elements without attributes/children) or rowset type APIs or APIs that have both. This should cover most of the existing APIs (80%+) but not complex APIs like Char/CorpSheet or AssetList etc. I may in the future trying adding stuff to handle the more complex APIs but want to get the basic ones right before moving on. Note that it wouldn't overwrite exist files in the EveApi/Sql/Xsd directories so if you are want to see any change to the creator output files you'll need to delete anything from prior runs for the APIs you are looking at. Make sure you report any bugs or errors you notice. Please if you have access to lots of APIs keys it would be a big help if you could take some time to test thing as I've only got a couple to work with on from my own account and it's not very active so many of the APIs return basically empty results so it's easy to miss problems. I'm mostly looking at the create process itself but reports of problems when running Yapeal like normal on accounts with newly created API stuff is also welcome.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
|
Dragonaire
Here there be Dragons
78
|
Posted - 2016.02.02 03:32:59 -
[131] - Quote
Okay been doing a lot of work on Yapeal-ng and pushed out result of first mass create with the new 'yc E:C' command. Some of the SQL and XSD still need hand optimization but what APIs are there should be working. It is still not ready for production but it's ready to be tested by someone other then me for sure. I'd really like to hear from some developers that use the existing Yapeal with 10 or more API keys and hear your feedback. If you can test it in parallel against the same setup with a second DB you currently use and report any bugs or other things you notice like speedups/slowdowns etc it would be very helpful. Once I've completed the SQL/XSD optimization stuff I'll start work on the more complex APIs that can't be auto-created. I'll probably just be doing them by hand but may try to make things a little smarter so the command can do some of the heavy lifting but either way I'll get some of the more useful ones done like characterSheet etc which most people need for their apps once I'm sure all the bugs/issues are worked out using the simple APIs.
So to sum it up I need some testers for the first public Beta version before I can really continue on and be ready to start putting out any RC releases on the way to a production ready release.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
78
|
Posted - 2016.02.02 23:39:22 -
[132] - Quote
Actually it meant to deal with all of the APIs but because it acts more like a XML API to database converter than just a simple wrapper for a network library it makes dealing with some APIs easier. As an application developer which would you find easier to use some inconsistent raw data that you need to parse yourself or have generally well structured database tables full of the information you'll need so you just have to write the queries to extract what you are looking for? If the application you are making only needs stuff from a couple of the APIs all the existing API libraries do a good job and they all can work in any application but as the application grows more complex through adding more APIs etc the work load IMHO goes up much faster with the other libraries as they have a much lower level interface you are working with vs Yapeal where the database is the interface.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
80
|
Posted - 2016.02.27 06:32:57 -
[133] - Quote
Hi all just an update to let everyone know I haven't forgot about Yapeal just been busy with other things. For anyone that's interesting in understand more about how Yapeal-ng works you might look at some of the new docs I've been working on for one of my other projects Event-Mediator. I use some code from Yapeal-ng in the example since it uses Event-Mediator for the logging as in the example but the other place it's used is in the main event loop which is at the heart of Yapeal now. While write about Event-Mediator I got to thinking about some other stuff I can do to improve Yapeal as well so look for some upcoming updates there too.
That's all for now as always thanks for using Yapeal, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
80
|
Posted - 2016.05.17 16:17:00 -
[134] - Quote
Just wanted to let everyone know I've not forgotten about Yapeal but some RL issues like having to move have been getting in the way. I'm hoping to have more time in a couple of weeks.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
80
|
Posted - 2016.06.29 00:11:20 -
[135] - Quote
Just a quick bump and note to say I'm still working on Yapeal-ng.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
81
|
Posted - 2016.07.07 20:34:19 -
[136] - Quote
Couple new things for people to look at for Yapeal-ng. First Yapeal-ng now has it's own twitter account @Yapeal_ng so check it out. I just added a poll question there as well to get some feedback to decide on future road-map planning so please vote. Took a little break from regular programming as well to make some better/newer artwork to use with Yapeal-ng as well. You'll find what I have going on in new media/ directory that I just pushed out.
As always thanks for using Yapeal, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
82
|
Posted - 2016.07.10 05:22:46 -
[137] - Quote
Pushed out lots of changes to Yapeal-ng check them out also check out the new @Yapeal_ng on twiitter.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
84
|
Posted - 2016.07.18 14:31:55 -
[138] - Quote
Just to let everyone know that are following / waiting on me to complete Yapeal-ng I've decided to change the PHP requirement to version 7.0. The original Yapeal will continue to work with older versions and I have stopped development on it. If someone else is interested in picks up develop on it please contact me. I decided I'm tired of living in the past programming wise with the project so I'm not any more. I'm in the process of changing everything over to use scalar type hints and other things that should make the code safer and in some cases allows removing a lot of legacy code that was needed to maintain compatibility etc with older versions. Most of you can probably just switch to PHP 7.0 in your applications with no noticeable difference except it might run a little faster. There is lots of help available online if you have any problems. I also will try to make some time to help you if its related to Yapeal or Yapeal-ng as well.
As always thank you for using Yapeal-ng, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
86
|
Posted - 2016.07.19 05:14:42 -
[139] - Quote
Need to look in the util tables. utilEveApi has an active column to turn the APIs on or off Yapeal-ng wide then you add your API kayID etc to utilRegisteredKeys for the char, corp, or account key you have. There is also a active column as well as activeAPIMask value which is bool '&' with the mask from the key itself to allow you to turn things on or off on a pre-keyID basis. Those are really the only tables that an application will need to write to in most cases. Its sometimes useful to clear the utilcachedUntil table during development but generally not needed in production.
Yapeal and by proxy Yapeal-ng have been around long before CREST even existed so it uses keyID and vCode. There was an even old system from CCP which has since been dropped which is what Yapeal originally used before that. I believe you can get a keyID and vCode from CREST that can be used with the XML APIs but I don't have any experience with how it works etc since my direct experience with CREST has been limit plus they added the tie in with XML API only a little while back I believe.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
88
|
Posted - 2016.07.22 14:33:39 -
[140] - Quote
Small update I've been working on updating some of my other projects that Yapeal-ng uses for PHP 7.0 as well. Been slowed down a little by some needed updates from other outside tools there but still limping along getting it all updated so I can get back to working on Yapeal-ng instead.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
|
Dragonaire
Here there be Dragons
89
|
Posted - 2016.07.25 19:24:49 -
[141] - Quote
Updated one of the tools used by Yapeal-ng thought I'd let people know here as it can be useful for application developers as well. http://www.phpclasses.org/package/8912-PHP-Get-the-full-path-of-files-relative-to-root.html
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
89
|
Posted - 2016.08.02 19:47:04 -
[142] - Quote
Updated another tool used in Yapeal-ng for PHP 7.0+ thought I'd share it as well for anyone that might want to use it in their own applications. http://www.phpclasses.org/package/9568-PHP-Emit-and-listen-to-events-using-a-mediator-object.html
Currently WIP on doing updates for PHP 7.0+ in Yapeal-ng and a little refactoring that's needed to add on PHPSpec examples (tests) as well.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
89
|
Posted - 2016.08.13 07:18:47 -
[143] - Quote
Push a bunch more updates out for Yapeal-ng have a look in the commit messages for what's changes there are some BC breaks again mostly related to Sql settings and how database connection and queries are done. Also some changes to how config files are being processed but shouldn't break anything except if you where using some of the old features(bugs) that existed
Look for another thread I'll be posting about needing help with converting Yapeal-ng from being MySQL only to something more cross DB compatible you might be able to help with.
As always thanks for using Yapeal-ng, Dragonaire
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
89
|
Posted - 2016.08.24 18:36:00 -
[144] - Quote
You got one of my untested WIP pushes I'm in the process of pushing out some more stuff and fixes now. Just pushed 28 commit sure I fixed something in there and broke something new for you
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
89
|
Posted - 2016.08.29 17:43:13 -
[145] - Quote
Sorry been busy with other things so didn't get chance to check forums. [20160826 093947.768] yapeal.NOTICE: Element 'ancestry': This element is not expected. Expected is ( allianceID ). That's the line pointing to the problem I'll have to take a look at the XSD file and see what's going on probably didn't have AllianceID be optional I'm guessing.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
89
|
Posted - 2016.08.29 18:00:55 -
[146] - Quote
https://github.com/Yapeal/yapeal-ng/issues/5 This should fix it for you.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
Dragonaire
Here there be Dragons
89
|
Posted - 2016.11.03 21:50:58 -
[147] - Quote
Ping just to let everyone know I'm still alive and hopefully some side projects are getting wrapped up so I can spend more time on Yapeal again.
Finds camping stations from the inside much easier.
Designer of Yapeal for the Eve API.
Check out the Yapeal PHP API Library thread.
|
|
|
|