JCollection Homepage

It´s mee again.

I think this isn´t realy a bug, but still a problem on my side ( maybe for other users too ).

The default parameter for the shown items at one page on a category is set to 20 !

I don´t found any configurationparameter to change this value. When I look at my saved items on the frontside for the first time or even the cachetime has run out, it seems to me that the webservicerequests for all 20 amazonitems takes too long.

The result: The hole side is blank. When i hit the refresh botton in my webbrowser everything is shown.

Is there a parameter at my PHP/Apache-Configuration which i have to increase ?

Can i change the value from 20 to 10 items anywhere ?

Hi,
as far as I remember, JCollection uses the Joomla standard value for the number of items that are initially displayed (option "list length" in the global configuration) - but I haven't really tested if this does indeed work. I see the problem with the duration of the webservice request and the overwrite, but there is not really a good solution for that at the moment, I think caching like it is done at the moment is probably the best that can be done.
Thorsten.

Forgot about the Apache/PHP settings. Well, you could try to increase the maximum script execution time in your php.ini, but in the usual shared hosting environments this value is limited anyway.

tcriess wrote:
Hi,
as far as I remember, JCollection uses the Joomla standard value for the number of items that are initially displayed (option "list length" in the global configuration) - but I haven't really tested if this does indeed work.

You are right. This option controls the number of the shown items. THX again.

tcriess wrote:
I see the problem with the duration of the webservice request and the overwrite, but there is not really a good solution for that at the moment, I think caching like it is done at the moment is probably the best that can be done.

Sure, otherwise you must save the information in the database and you need to create some kind of trigger to initiate a refresh of the stored information from the webservice. Did you think about this solution ?

Hi,
just to clarify that point a bit, such a caching _is_ indeed done, the webservice is only called if the item information is too old (the individual times are hardcoded in at the moment using reasonable values, I believe for Amazon it is something like 30 minutes)! But the overwrite process is still quite time consuming since it must parse the XML data (no matter if it came directly from the webservice or from the database). The second caching step is then to cache the item information as it is displayed, so that the XML data does not have to be parsed again. The expiry for this caching is set to the standard Joomla value.
Best,
Thorsten.

So, I tried it with a list length of 10.

I still have the same problems. The side keeps completley empty at the first try.

My server runs on an virtuell host at 1&1. This Provider is normally known as one of the faster ones. I had never any performance issues before.

Maybe i must adjust the maximum script execution time. If this won´t help I have no further ideas.