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


 
Pages: first : previous : ... 13 14 15 16 [17] 18 19 20 21 ... : last (24)

Author Topic

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.03.13 08:57:00 - [481]
 

Ok thought it was time for a little update on stuff I've been working on. I'm currently still working on some cleanup on caching code and that's probably going to lead to some changes in the API fetching code as well. I'm try to go a bit slower on this so as to make sure not to break stuff in the process (Yes I'm using a branch this time Wink)
Something else I've been working on is cleaning up, adding to, and streamlining the new build stuff as I've gotten to know more about how Xinc and Phing work. Part of that has lead to having them build the Yapeal developer documentation also so it stays more up to date with the current revision. I've also changed it from being stored in docs/ directory where it had to be manually updated to being available as downloads in html and pdf formats. These are mostly useful for people working on making changes to Yapeal itself but application developers may find some of the information useful too.
Now that I've brought up the subject of documentation as most of you are aware there isn't much and what does exist needs some serious help. I've tried to write some docs but I've been finding it very hard write any that is really useful for someone try to develop an application and integrate Yapeal into it or build something around it depending on how you look view what you're doing Smile One thing that makes it hard for me is since I do know every line of code and how everything works it's hard for me to see Yapeal as an outsider would and not knowing what it does or can do for them. So what I need is some help from those that have been using Yapeal to share some of their experiences, tips, examples, etc. Things I'd like to really hear about are things that caused the most 'head scratching' when starting to use it.

revision 1024

Linaeon
Posted - 2010.03.14 05:43:00 - [482]
 

Something i dont understand here ::

theres many table is not d/l it is :
accountCharacters
charAccountBalances
etc etc

and i have upload my log here
please take a look is that anything wrong ??

http://eve-files.com/dl/218380

ps. permission denied already settle.

Thanks

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.03.14 06:13:00 - [483]
 

First thanks for trying Yapeal.
It looks like you're using an older version so first thing would be to update to the latest version 1024. Try using the installer from downloads if you can and select 'advanced' install which will have a few more pages to go through but most should have good defaults already just make sure when you get to the section part to make sure everything is on that you want. (accountCharacters will need account section and Characters API on). I've change the utilRegisteredUser table to reflect that the user has to be active to get those APIs I wrote about that change in my post 471
Hopefully I've covered enough so you can fix your problems but if not let me know.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.03.16 01:42:00 - [484]
 

Ok I finally decided to tag revision 1024 as version 1.0.0 Beta.

What does this mean?
It doesn't really change anything but it does mean that as a developer I believe it's mostly complete in what it does and has no major bugs anymore. You also notice when you look at download in the Summary it now says '***Beta*** ...' instead of '***Pre-Beta*** ...'Smile

Is development stopping?
No, but since it is mostly complete large scale changes to how it works or is used shouldn't happen for a while anyway (At least for a couple weeks to a monthWink).
Are you going to start on version 2.0?
Not really Yapeal will keep evolving much as it has and maybe at some point it'll make it to what could be call 'stable' and at that point I may decided to call it 2.0.

So what's being worked on now in Yapeal?
Everything Razz but main focus has shifted to cleaning up some of the code, looking at improving the installer, and maybe adding a couple more of the APIs. I've also been looking at ways to add a remote installer for people that don't have shell access with their ISPs but it hasn't even got to the testing stage just been looking at how others have try solving the issue.

Think that covers everything for now.

revision 1027

Tor Azgard
Posted - 2010.03.30 08:07:00 - [485]
 

Edited by: Tor Azgard on 30/03/2010 08:08:31
"Warning: The "yapeal" database exist but the user root does not have the required privileges to use it"

I also did a
GRANT ALL PRIVILEGES ON yapeal.* TO root @'%' IDENTIFIED BY '**********';
which gave me a:
Query OK, 0 rows affected (1.35 sec)


However, it still doesnt work.

When I removed the database yapeal, it worked. But then it couldnt insert any tables to it.. mainly because it dosent exist anymore, since I removed it.
bug?

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.03.30 15:48:00 - [486]
 

Try looking at the comments from issue 43 as the first couple apply even though you may not be try to use a remote DB server. I also believe there was someone else having similar problems that posted to this thread not long ago and I made some suggests for things to look at then too. You'll what to look over the last couple pages to find it.

Johnathan Walker
Caldari
Posted - 2010.03.30 17:43:00 - [487]
 

Hi Dragonaire,

After reviewing the data included in my post regarding excel, thought I'd give Yapeal a try... however:

Quote:
#!/usr/bin/php Notice: Yapeal version 1031 (beta) 2010-03-18 20:28:57 in /home/masqsor1/public_html/fvbe/yapeal/inc/common_backend.php on line 80 Fatal error: The required configuration file is missing in /home/masqsor1/public_html/fvbe/yapeal/inc/common_backend.php on line 109



Thoughts? I put in the username, databasename and password for the database I'm looking at using (it's empty at the moment)... Was I not supposed to use the example ini and rename to yapeal.ini when finished?

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.03.30 17:57:00 - [488]
 

Just an idea try the installer from download for windows and it should make the ini file for you and help you by make sure everything is set right and working.

Johnathan Walker
Caldari
Posted - 2010.03.30 18:20:00 - [489]
 

Originally by: Dragonaire
Just an idea try the installer from download for windows and it should make the ini file for you and help you by make sure everything is set right and working.



Sounds good! Dumb question though... how does one go about running an EXE on a shared host? Keeps telling me to download the file if I click on it, so I know there's something I'm clueless about.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.03.30 22:48:00 - [490]
 

If you have a shared windows host you are probably out of luck except if they give you remote desktop access (unlikely). If you're host is Linux on the other hand you can grab one of the Linux installer and use SSH connection to install it. If you have an old style host that thinks not giving you SSH access makes their servers more secure Rolling Eyes you'll have to follow instructions from either this thread or in some of the closed issues on the web site where I talk about how you can do a local install on any platform and make a few minor changes that depend how closely your local machine is to the configuration on the remote one.

On another matter for those of you that haven't been to the project web site in last couple of days or just didn't notice while you were there I've decided to start a new blog for Yapeal. I've named it Peeling Yapeal. I hope to cover things with it that people will find interesting and that I felt weren't being or couldn't be cover by this thread, in issues, or the Wiki from the project site either. I've written a couple posts already include the first couple from a series that will hopefully give some insight into how Yapeal works and some change that are coming. They probably will also give some insight into the process I go through when deciding on changes during development for Yapeal.

I'd like to invite anyone that has ideas for things you think are missing or you feel need to be cover but this thread, the wiki or issues just didn't feel like the right place to bring it up in the past to make comments on the blog and we'll see what I can do to address them through it.

Johnathan Walker
Caldari
Posted - 2010.03.31 00:58:00 - [491]
 

Originally by: Dragonaire
If you're host is Linux on the other hand you can grab one of the Linux installer and use SSH connection to install it.



I'm in luck; I do have SSH access. Thanks Dragonaire! :)

Qoi
Exert Force
Posted - 2010.03.31 20:20:00 - [492]
 

Hey Dragonaire, thanks for your great library (I've been using it for quite some time now). Very Happy
I like to keep my yapeal up to date with svn (as i think that's way easier than any installer/whatever stuff), however there are some files that are under version control but keep getting changed by the library itself, namely:
M log/yapeal_warning.log
M log/yapeal_strict.log
M log/yapeal_error.log
M log/yapeal_trace.log
M log/yapeal_notice.log

which makes it very impractical to use svn diff on my working copy.
I tried svn:ignore and deleting them (which sort of fixes the issue), but could you perhaps remove them from version control? If anyone else tries to commit something, it's not a good idea to have his logs with all the API Keys under version control, i think ;)

Keep on the great work, i'll read your blog now Wink

Johnathan Roark
Caldari
The Graduates
Morsus Mihi
Posted - 2010.03.31 22:12:00 - [493]
 

Originally by: Qoi
Hey Dragonaire, thanks for your great library (I've been using it for quite some time now). Very Happy
I like to keep my yapeal up to date with svn (as i think that's way easier than any installer/whatever stuff), however there are some files that are under version control but keep getting changed by the library itself, namely:
M log/yapeal_warning.log
M log/yapeal_strict.log
M log/yapeal_error.log
M log/yapeal_trace.log
M log/yapeal_notice.log

which makes it very impractical to use svn diff on my working copy.
I tried svn:ignore and deleting them (which sort of fixes the issue), but could you perhaps remove them from version control? If anyone else tries to commit something, it's not a good idea to have his logs with all the API Keys under version control, i think ;)

Keep on the great work, i'll read your blog now Wink


I'm guessing your actually using a working copy to run your yapeal install? Those files should only change when a branch is merged into the trunk. What I suggest doing is keeping two copies, one for syncing with svn, another for live. Then export the diff files out and update your copy that way. Something else to watch for is database updates. SVN wont update your database.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.03.31 23:04:00 - [494]
 

Qoi - Glad to hear you like and have been using it for a while. I'll just let you know how I work with Yapeal and maybe you can try doing something similar and they won't cause you any problems anymore. I have a working copy in a location where I do my edits then when I wish to try it out I do an export:
svn export --force /my/wc/ /my/test/location/
Doing it that way allows helps insure I don't end up with any of my passwords or logs in the commit like has been know to happen a few times in the past Rolling Eyes you'll notice it doesn't overwrite my config/yapeal.ini and does overwrite the log/yapeal_*.log files saving me doing it manually. The only time I need to do any extra work would be when I delete or move files around in the SVN. That isn't hard either as a simple rm -R /my/test/location/*.php followed by an export cleans it up nicely for me Smile One of the original reasons for including the log files was to have them there so you can insure they had the correct permissions before Yapeal looks at them and try to write to them. It use to check each file to insure they were writable but I think now it's been changed and just requires the directory be writable and may not check each file. One other reason was to insure the directory was created when using archives (zip, tar.gz, etc) as some of them will ignore any directory that is empty and not make them when you expand them. That was the reason for adding dummy.txt to all the cache/*/ directories you see as well Wink So there's some background on why it was done like it is now.

Now back to things you can do, first you could use the export method I do and not run from you're WC which is not a good idea to start with BTW as you've seen it causes problems Wink and yes I know some of the old documentation had an example doing that (I didn't write it) Razz
Another option is to use a different name for you log files by changing them in your config/yapeal.ini and you just end up with a couple extra empty unused log files Smile

There one more option be it's more for me then you and that's to check if Yapeal still checks the permissions on all the log file directly or not. If it doesn't I could probably just add a dummy.txt file instead and not have the log files in the SVN any more. I'll just have to remember to clear them myself during testing Wink which isn't a big deal as I have to do that now when testing the installer since it doesn't overwrite them if they already exist.

Qoi
Exert Force
Posted - 2010.03.31 23:50:00 - [495]
 

Edited by: Qoi on 31/03/2010 23:49:59
Uhm, i've worked with subversion quite some time now - thanks you for pointing out that there is an export subcommand Shocked It's really useful, now that i know that it exists Smile

As i run yapeal with cron and i get emails every time it does any output, is there any way to supress this Notice:
Quote:

Notice: Yapeal version svnversion (beta) builddate in yapeal/inc/common_backend.php on line 80


Without changing the code (i always comment out that line, so i don't get hammered with emails). I didn't set E_NOTICE in the yapeal.ini log_level directive, changing error_reporting on the command line does nothing. Of course it's not a big deal, but if i overlook something then please give me a hint :)

Another thing i always have to change is the shebang line in revision.php ( #!/usr/bin/php ) - i think it's there by mistake (Line 43: "Only let this code be included or required not ran directly.") - and it adds a line of output which cron then happily emails to me.

I will from now on diff the latest changes (to look if i need some database updates) and then export, i think that's really a better solution, thanks for pointing that out.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.04.01 00:36:00 - [496]
 

Ok now that you know about svn export I may have fixed Yapeal so you don't need it Wink there are of course the other benefits still.

After looking at it I've decided I could remove the logs from the SVN and while I was at it I fixed revision.php as well. I thought that had already been done a while back when I noticed it be apparently it didn't get changed.

To also help with the extra emails you can try adding the follow line as the first one in your crontab:
MAILTO=""
That should silent any crontab emails in most Linux distros.

Johnathan Roark
Caldari
The Graduates
Morsus Mihi
Posted - 2010.04.01 01:19:00 - [497]
 

Originally by: Dragonaire
Ok now that you know about svn export I may have fixed Yapeal so you don't need it Wink there are of course the other benefits still.

After looking at it I've decided I could remove the logs from the SVN and while I was at it I fixed revision.php as well. I thought that had already been done a while back when I noticed it be apparently it didn't get changed.

To also help with the extra emails you can try adding the follow line as the first one in your crontab:
MAILTO=""
That should silent any crontab emails in most Linux distros.


I use
*/60 * * * * /path/to/yapeal/yapeal.php &> /dev/null

directs any output to the NULL device :)

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.04.05 01:15:00 - [498]
 

Thought I'd let everyone know I've fixed a few minor bugs lately which most people wouldn't notice but became KOS once I found them like they all should Evil or Very Mad

For those of you that missed it I did an interview for KaarBaak about Yapeal which you can find at http://evemetagaming.blogspot.com/. She's done a couple others now which I found interesting to read myself about some other projects/applications that people are working on.

I'll be finishing off my series from the PeelingYapeal blog soon as well but in writing it it got me to thinking about some things and I decided to try out a few ideas to make Yapeal work better. Most of them are about memory usage which is of course what the posts were about Wink but I've also been looking at making Yapeal scale better for people that want to use it with say a few hundreds or thousands of accounts ;)

That's it for now.

Revision 1043

Gracelia
Caldari
Posted - 2010.04.06 02:41:00 - [499]
 

Installs just fine and got set up with the database. However when I try to run yapeal.php from the command line I get this

"Notice: Yapeal version 1043 (beta) 2010-04-05 00:38:06 in /home/matt/Yapeal/inc/common_backend.php on line 80"

Johnathan Roark
Caldari
The Graduates
Morsus Mihi
Posted - 2010.04.06 02:58:00 - [500]
 

Originally by: Gracelia
Installs just fine and got set up with the database. However when I try to run yapeal.php from the command line I get this

"Notice: Yapeal version 1043 (beta) 2010-04-05 00:38:06 in /home/matt/Yapeal/inc/common_backend.php on line 80"


That's normal, ignore it.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.04.06 04:09:00 - [501]
 

I found the old post I did about this a long time ago and decided to update it a little and make it into wiki page.
http://code.google.com/p/yapeal/wiki/UnderstandingErrorLogs

Bubba XXX
Posted - 2010.04.15 00:23:00 - [502]
 

I run an older version of Yapeal on MOSSO, which means only FTP Access. About once a year, I decide to update yapeal to the latest version, but I can never find instructions on how to do so. Lots of installers. Is there a document on how to update Yapeal manually via FTP only access that I've missed? If not, could we get one?

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.04.15 06:46:00 - [503]
 

Bubba XXX - It not going to be easy if you are using a version that old. best way to start would be to export your data from your server to a local machine. Install Yapeal on the local machine with an installer and if you're lucky the database will upgrade correctly for you. Once you're sure that has worked you can transfer Yapeal over ftp to your server and update the database there from your local machine using a backup from it. The more similar the local machine is to your server the more likely it is it'll all work. Make sure you use 'advanced' install so you get a chance to make changes to all the settings.

Hopefully that helps and I would suggest you upgrade more often as there are often many changes to Yapeal both to fix bugs and added features. The older the version the harder it'll always be to update.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.05.01 04:03:00 - [504]
 

Ok thought it was time to give everyone a little update. I've started a new job so that's been taking up more of my time lately but I've been working on converting all the APIs over to using XMLReader as I outlined in my blog posts. I believe all the APIs that Yapeal had before have been converted and are working now plus I've add a few new ones along the way too Smile I'm having some issues right now with downloads at GoogleCode but I hope that will be fixed soon and I'll be able to upload some test installers and other files for people to start trying out. Some of the changes I've decided/had to make will require some manual changes to the database tables in util. This should have little impact on most users that have been using the newer class/util/*.php files and the classes they contain to interact with the tables. I'll give more information once I've done a little more testing and the download issues are solved.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.05.07 14:31:00 - [505]
 

Ok I put the Alpha test version of the installers that use XMLReader up in downloads I've not had a chance to test them so BACKUP YOUR DATABASE and current install of Yapeal before trying it. You'll need to delete your existing tables or make a new database to try it out as I haven't upload the manual conversion SQL you'd need to update existing one. Let me know if there's any problems with it and yes this is **ALPHAware**

Gouverneur
Posted - 2010.05.13 18:39:00 - [506]
 

Hi, so, I've just uploaded the Contents of Yapeal.tar.bz2 to my Site(there is no CLI-Binary available afaik, CGI only). Updated the ini-File and updated the Files because my Hoster requires .php5-Ending for PHP5 Files.

yapeal.php5 runs without errors, but the DB is still empty.
createMySQLDatabase.php5 seems to miss Arguments and is trying to create error-log:
Quote:
Warning: fwrite(): supplied argument is not a valid stream resource in /kunden/aocc.de/webseiten/gouv/eve/yapeal/install/createMySQLDatabase.php5 on line 53

Warning: fwrite(): supplied argument is not a valid stream resource in /kunden/aocc.de/webseiten/gouv/eve/yapeal/install/createMySQLDatabase.php5 on line 54


Well, how am I supposed to install Yapeal / create the DB-Tables without CLI?
Did some search but didnt find anything usefull yet. Oh, I've got SSH-Access btw.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.05.14 01:01:00 - [507]
 

The installer should work with CGI as well from SSH you just need to tell it where it is just like you would with CLI. You shouldn't need to change the suffix on the files either since you aren't running anything with the web server which is where that requirement usually comes from.

Gouverneur
Posted - 2010.05.14 05:37:00 - [508]
 

Edited by: Gouverneur on 14/05/2010 05:50:47
Thanks for a Reply. I've made some Progress and got another Problem here:
Yapeal Installer doesnt accept my Path: /usr/local/bin/php.5 -c /usr/local/php5/php.ini
Yes, it is the Path to the php5-Binary, but it throws out a zend-error if run without specifying alternate ini-path :/
Is there any way around this?

Edit: the ini-file is not the Problem, the Directory I've put Yapeal-Installer had a php.ini from PHP4 in it.
But even in a nother Dir. I'm still getting the same error:
Quote:

Where can the CLI version of PHP be found? [/usr/bin/php]: /usr/local/bin/php.5

Warning: Error running /usr/local/bin/php.5 -f
'/tmp/Yapeal/install/testForPHPVersion.php' : child process exited abnormally

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2010.05.14 07:04:00 - [509]
 

You might look at the /tmp/bitrock*.log file and see if there's any more info on why it's failing on some systems it could be in /var/tmp/. I'd also try a few test from command line to make sure there aren't any other issues with PHP config. Some things to try.
/usr/local/bin/php.5 -v

Check this really is PHP version 5.2.1 or greater.
/usr/local/bin/php.5 -m

Make sure all the required extensions (modules) are included in PHP.

If it seems it's using a php.ini file that's wrong when entering the command to use try adding the extra parameter to yours to it. Example:
Where can the CLI version of PHP be found? [/usr/bin/php]: /usr/local/bin/php.5 -c /usr/local/php5/php.ini

Since it'll use simple string append of the commands in the installer that should work without problems.
You might also find out where the CGI is putting it's log files as it might shed some light on why it's failing as well. If you need some help understanding any of the log files from anything you can E-mail them to me at my G-mail. You can find it (figure it out) from project owner.
Hopefully you'll be able to figure out from doing some of the above tests what is causing it to fail.

Gouverneur
Posted - 2010.05.14 14:07:00 - [510]
 

Originally by: Dragonaire
/tmp/bitrock*.log file
I'm not allowed to list in /tmp and have no access to /var/
Quote:
/usr/local/bin/php.5 -v

Yeah, I tried it before, it works very well - Version 5.2.11, Zend 2.2.0.
All required Modules listed on the Projectpage are installed.

Quote:
/usr/local/bin/php.5 -c /usr/local/php5/php.ini

Installer doesnt accept that Line, because it's 'not a file'. It doesnt matter in my case anymore, I just need to launch Installer in another Directory.

I've experimented a bit and found out, that all the test*.php's in /tmp/Yapeal/install seem to work(no more 'abnormally exiting') after removing these Lines:
if (basename(__FILE__) != basename($_SERVER['PHP_SELF'])) {
$mess = 'Including of ' . $argv[0] . ' is not allowed' . PHP_EOL;
fwrite(STDERR, $mess);
fwrite(STDOUT, 'error');
exit(1);
};
I've edited the Files in a second ssh-Window while Installer was waiting for Input in first Window.

But I've got tired of editing at
Error running /usr/local/bin/php.5  -f
"/tmp/Yapeal/install/getCorporationOptions.php" "/tmp/Yapeal/characters.xml" :
child process exited abnormally
.
Well, Is there anything wrong with those lines I removed? Guess I'm missing some Privileges again, huh?


Pages: first : previous : ... 13 14 15 16 [17] 18 19 20 21 ... : last (24)

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


 


The new forums are live

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

These forums are archived and read-only