Pages: 1 2 3 4 5 6 7 [8] 9 10 11 .. 11 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.12 18:10:15 -
[211] - 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.
|
Tiberius Zol
turaagaq GANOR INC.
44
|
Posted - 2014.12.12 18:22:38 -
[212] - Quote
still get the composer error... |
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.12 18:44:02 -
[213] - 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.
|
Tiberius Zol
turaagaq GANOR INC.
44
|
Posted - 2014.12.12 22:08:50 -
[214] - Quote
Dragonaire wrote: 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.
Thank you. This worked for me for both problems.
|
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.13 23:06:47 -
[215] - 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 -
[216] - 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.
|
Tiberius Zol
turaagaq GANOR INC.
44
|
Posted - 2014.12.15 09:15:39 -
[217] - Quote
Hm i got an error it i try to update the DB. Seems, as the script want to update: accountApiKeyInfo But in the DB is only a: accountAPIKeyInfo
I never changed the name. Which one is the right name? |
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.15 15:47:55 -
[218] - 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.
|
Tiberius Zol
turaagaq GANOR INC.
44
|
Posted - 2014.12.15 22:15:20 -
[219] - Quote
Dragonaire wrote:accountAPIKeyInfo is right I'll fix. One problem with doing most of my testing on Windows is it lower cases all table names and so doesn't care While I'm at it I push the new 'archive' versions of the older updates. Basically the sql/updates/ directory was getting kind of messy with over 20 update SQL files so I decided to condense them into monthly files for the past months that use name of the last update from that month. This has reduced the number down to 8 which is much easier to deal with. I may do some addition changes but I'm trying to do it in stages and keep it backward compatible as well so its kind of a WIP but do let me know of any problems you notice.
one more to fix charcorporateContactList should be charCorporateContactList (two times)
|
Dragonaire
Here there be Dragons
69
|
Posted - 2014.12.16 10:30:13 -
[220] - 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 -
[221] - 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 -
[222] - 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.
|
Tiberius Zol
turaagaq GANOR INC.
52
|
Posted - 2015.02.10 09:27:02 -
[223] - Quote
Hey man,
first of all, i want to thank you, that you still working on this. I tried to update yapeal yesterday and run in several problems:
First. The Procedure creates an error for me:
DatabaseUpdater::addDatabaseProcedure .CREATE PROCEDURE "yapeal"."AddOrModifyColumn"( IN param_database_name VARCHAR(100) CHARACTER SET utf8 COLLATE utf8_unicode_ci, IN param_table_name VARCHAR(100) CHARACTER SET utf8 COLLATE utf8_unicode_ci, IN param_column_name VARCHAR(100) CHARACTER SET utf8 COLLATE utf8_unicode_ci, IN param_column_details VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci) BEGIN IF NOT EXISTS(SELECT NULL FROM "information_schema"."COLUMNS" WHERE "COLUMN_NAME" COLLATE utf8_unicode_ci = param_column_name AND "TABLE_NAME" COLLATE utf8_unicode_ci = param_table_name AND "table_schema" COLLATE utf8_unicode_ci = param_database_name) THEN /* Create the full statement to execute */ SET @StatementToExecute = concat('ALTER TABLE "', param_database_name, '"."', param_table_name, '" ADD COLUMN "', param_column_name, '" ', param_column_details) ; /* Prepare and execute the statement that was built */ PREPARE DynamicStatement FROM @StatementToExecute; EXECUTE DynamicStatement; /* Cleanup the prepared statement */ DEALLOCATE PREPARE DynamicStatement; ELSE /* Create the full statement to execute */ SET @StatementToExecute = concat('ALTER TABLE "', param_database_name, '"."', param_table_name, '" MODIFY COLUMN "', param_column_name, '" ', param_column_details) ; /* Prepare and execute the statement that was built */ PREPARE DynamicStatement FROM @StatementToExecute; EXECUTE DynamicStatement; /* Cleanup the prepared statement */ DEALLOCATE PREPARE DynamicStatement; END IF; END Sql failed in DatabaseUpdater::addDatabaseProcedure on statement 1 with (42000) SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'COLLATE utf8_unicode_ci, IN param_table_name VARCHAR(100) CHARACTER SET ' at line 2
But in my understanding it was only for the three DropColumn statements. Everything after it works (i have run it manually after it).
Second: All my running CorpIndustryJobs have 1970-01-01 00:00:01 as completedDate and endDate.
Third: I found several Problems in the log: example:
[2015-02-10 10:08:29] yapeal.DEBUG: Started network retrieve for account/AccountStatus [] [] [2015-02-10 10:08:29] yapeal.INFO: Could NOT find /eve/yapealneu/lib/Database/Account/AccountStatus.xsl [] [] [2015-02-10 10:08:29] yapeal.DEBUG: Given XSL name /eve/yapealneu/lib/Database/common.xsl [] [] [2015-02-10 10:08:29] yapeal.DEBUG: Started XSD validating [] [] [2015-02-10 10:08:29] yapeal.DEBUG: Element 'Offers': This element is not expected. [] [] [2015-02-10 10:08:29] yapeal.WARNING: The data retrieved from Eve API account/AccountStatus for 3451731 is invalid [] []
Same for corpStarbaseDetail-
The most important thing for me is the industryJobs thing, as my industry tool doesn't work anymore. Any clue how to fix it?
Mr. Tibbers on twitter: @Mr_Tibbers
Mr. Tibbers Blog (german, but english posts incoming): www.eve-versum.de
|
Dragonaire
Here there be Dragons
71
|
Posted - 2015.02.11 02:47:26 -
[224] - 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 -
[225] - 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 -
[226] - 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.
|
Tiberius Zol
turaagaq GANOR INC.
52
|
Posted - 2015.02.14 11:10:46 -
[227] - Quote
As a short info. It's working again. Thx man. :)
Mr. Tibbers on twitter: @Mr_Tibbers
Mr. Tibbers Blog (german, but english posts incoming): www.eve-versum.de
|
Jahn Ntago
Association of Commonwealth Enterprises Nulli Secunda
66
|
Posted - 2015.02.15 09:48:37 -
[228] - Quote
Hello,
I seem to be having a new problem since 2.0.0 and remaining with the latest builds:
toons that leave a corporation remain in the corpMemberTracking table associated with that corp. In my case they are leaving a corp whose API I have to go to an NPC corp.
Any ideas? |
Dragonaire
Here there be Dragons
71
|
Posted - 2015.02.16 01:31:23 -
[229] - 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.
|
Jahn Ntago
Association of Commonwealth Enterprises Nulli Secunda
66
|
Posted - 2015.02.17 01:28:56 -
[230] - Quote
reserved... |
|
Dragonaire
Here there be Dragons
72
|
Posted - 2015.02.17 17:39:54 -
[231] - 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.
|
Jahn Ntago
Association of Commonwealth Enterprises Nulli Secunda
66
|
Posted - 2015.02.18 02:11:26 -
[232] - Quote
I ran the processing again this morning and it worked. Must have been a caching issue?
corpMemberTracking now works properly for me.
Thank you. |
Nick Partridge
Epsilon Inc
0
|
Posted - 2015.03.06 16:19:33 -
[233] - Quote
Any clues on the following error from the yapeal.log.
yapeal.WARNING: Failed to upsert data from Eve API corp/MemberTrackingLimited for 1542130595 {"exception":"[object] (PDOException(code: 22001): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'base' at row 21 at G:\\server\\WEB\\public_html\\eve_the-partridges_co_uk\\yapeal\\lib\\Database\\EveApiToolsTrait.php:111)" |
Mintoko
Taedium In Perpetuam
22
|
Posted - 2015.03.11 22:07:28 -
[234] - Quote
Nick Partridge wrote:Any clues on the following error from the yapeal.log.
yapeal.WARNING: Failed to upsert data from Eve API corp/MemberTrackingLimited for 1542130595 {"exception":"[object] (PDOException(code: 22001): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'base' at row 21 at G:\\server\\WEB\\public_html\\eve_the-partridges_co_uk\\yapeal\\lib\\Database\\EveApiToolsTrait.php:111)"
I was just about to report this myself. The column size for 'base' is too small. You can alter the table corpMemberTracking and change the base size to 100. |
Dragonaire
Here there be Dragons
73
|
Posted - 2015.03.12 05:08:30 -
[235] - 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 -
[236] - 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.
|
Cwittofur Cesaille
Wrecking Havoc Minning Corp Phoebe Freeport Republic
0
|
Posted - 2015.04.29 18:42:27 -
[237] - Quote
I stumbled upon yapeal while browsing for a new framework to use the API. I have been using custom code since then. It seems like Yapeal will handle everything I need it to do... however I feel stupid and have no idea where to get started. The old documentation doesn't seem overly helpful. I'm not completely new to PHP; but I'm new enough to be lost! (I'm a .NET Developer). If there is anyone who could give me some insight on how to create a *basic* site that'd be super helpful. I can hit the ground running from there. I'm just not sure how/where to start :) I have it installed on my server already and in my web site area (going to symlink once I know it's all set).
Thanks in advanced! |
Dragonaire
Here there be Dragons
75
|
Posted - 2015.05.06 21:03:19 -
[238] - 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.
|
Emma Otto
Mirai Industries
0
|
Posted - 2015.05.12 21:10:38 -
[239] - Quote
Thanks very much for this library. Like many others I'd started coding my own library to grab API data. But then I found this and you appear, at first glance, to have saved me so much time with your wonderful code!
Couple of questions:
1) I've added a corp API key but the corpDivisions and corpAccountBalance tables don't seem to be pulling in any data? 2) If I remove a key from the utilRegisteredKey table will this purge the data related to this key from the database on the next pull of data? |
Riley Masterson
Cloak and Daggers Fidelas Constans
1
|
Posted - 2015.05.29 01:50:36 -
[240] - Quote
Hi Emma.
I just noticed that a corp key seems to require an access mask or it will not pull data, if you're not supplying one that could be the issue. the documentation said somewhere that the column can be null but that appears to only be valid for character keys.
For the second, it has been my experience that removing the key does not purge data during the next update. |
|
|
|
|
Pages: 1 2 3 4 5 6 7 [8] 9 10 11 .. 11 :: one page |
First page | Previous page | Next page | Last page |