Troubles with &limit=recent in the URL

charm · November 30th, 2006, 06:08 AM

I have 'Recent photos' gallery which is shown on the top of the index page.

Links to the internal pages in this gallery looks as: http://www.zeno.ru/showphoto.php?pho...7&limit=recent

In the usual gallery links are in the next form:
http://www.zeno.ru/showphoto.php?photo=37687

Both links leads to the same page. But here is the next problem:
when user with rights of moderator trying to open the first link (with &limit=recent at the tail), he gets from the browser message that page can't be opened.

Users with usual rights has not experience this problem.

Chuck S · November 30th, 2006, 08:33 AM

I dont know what could be your issue there but is the exact message he reaches.

You could try ensuring you have the latest code 5.61 as I know there have been significant performance enhancements to certain scripts showing a photo or the member gallery since 5.3

Patrick@DC · December 15th, 2006, 03:17 PM

Quote:

Originally Posted by charm

I have 'Recent photos' gallery which is shown on the top of the index page.

Links to the internal pages in this gallery looks as: http://www.zeno.ru/showphoto.php?pho...7&limit=recent

In the usual gallery links are in the next form:
http://www.zeno.ru/showphoto.php?photo=37687

Both links leads to the same page. But here is the next problem:
when user with rights of moderator trying to open the first link (with &limit=recent at the tail), he gets from the browser message that page can't be opened.

Users with usual rights has not experience this problem.

Don't feel alone! I discovered this issue as well this morning.

I upgraded to vb 3.6.4 the other day, no real issues. That seems to have triggered it. I am still running photopost 5.21, but am upgrading to 5.62 this afternoon.

I created a dummy account, and the only user groups that have the "page cannot be displayed" issue are administrator, super-moderator or moderator group. The usergroup permissions within Photopost don't seem to be a contributor... as it happens no matter what is chosen.

Very strange.

But, before I spin my wheels on it I'm going to the latest version.

I would like to hear more about any changes you made prior to the issue.

Thanks!

charm · December 15th, 2006, 03:22 PM

Quote:

Originally Posted by Patrick@DC

I created a dummy account, and the only user groups that have the "page cannot be displayed" issue are administrator, super-moderator or moderator group. The usergroup permissions within Photopost don't seem to be a contributor... as it happens no matter what is chosen.

Actually now this issue is available for any visitor, even without login into the database.

I've not updated to 5.6 yet; hope it will help.

Patrick@DC · December 15th, 2006, 03:23 PM

Quote:

Originally Posted by charm

Actually now this issue is available for any visitor, even without login into the database.

I've not updated to 5.6 yet; hope it will help.

I'm upgrading at the moment. Stay tuned....

Patrick@DC · December 15th, 2006, 04:21 PM

Upgrading to 5.62 has resolved the issue completely.

charm · December 15th, 2006, 04:27 PM

Quote:

Originally Posted by Patrick@DC

Upgrading to 5.62 has resolved the issue completely.

Thank you, Patrick!
Definetly I had to devote my time to the update.
BTW, if it is not a secret, how large is your base? Number of photos, number of categories, number of users?

Patrick@DC · December 15th, 2006, 05:14 PM

Quote:

Originally Posted by charm

Thank you, Patrick!
Definetly I had to devote my time to the update.
BTW, if it is not a secret, how large is your base? Number of photos, number of categories, number of users?

I'll send you a PM.

charm · December 28th, 2006, 02:56 AM

The problem with &limit=recent parameter is that such URL calls the request to the whole database. If the images quantity is large (few tens of thousands), as in yours and mine cases, the request is too huge and produces abnormal delay for the database.
I think that developers can find more optimal method to proceed &limit=recent request.
The similar problem was in the displaying of the random pages.
Now I switched off 'Recent postings gallery' from index pages. It is not what I want from the database.

charm · December 28th, 2006, 04:23 AM

IMHO, it is possible to build 'Recent postings' gallery without the requesting to the ALL database. Just create small table 'recent photos' with, for example, 20 pages, and update it during new postings. Gallery of recent postings can be built by selecting of images from it, not from the whole database.

Chuck S · December 28th, 2006, 11:15 AM

Quote:

Originally Posted by charm

The problem with &limit=recent parameter is that such URL calls the request to the whole database. If the images quantity is large (few tens of thousands), as in yours and mine cases, the request is too huge and produces abnormal delay for the database.
I think that developers can find more optimal method to proceed &limit=recent request.

Correct and our later codes address this issue as Patrick states 5.62 completely fixed his issue