I remember this issue... but I remember also i could not reproduce the error..
As i just did a fresh install on my localhost.. (to also test something else)
I just looked into it.. and still could not reproduce...
if i understand you correctly, I tried following..
Fresh install
2 users Admin and Tester
I did not change anything in category configuration so I have:
Main Category --> Main Album
Admin uploads 10 images, Tester uploads 5 images (all to Main Album)
Filmstrip is set to 0 (disabled)
Now I login as tester and start browsing
Quote:
Originally Posted by cory_booth 
You won't see this error as an administrator, only a regular user browsing another user's gallery.
|
As user "Tester" I go to one of Administrator's images and click on: (View all of Administrator's images)
I get the page of his images, click on the first one-
From the browseimage page the link to the image is:
h ttp://localhost/site/gallery/showimage.php?i=13&catid=member&imageuser=1
I then click on the Next link
Link is: h ttp://localhost/site/gallery/showimage.php?i=13&goto=next&c=member&imageuser=1
and so on.. all links are working...
Am I doing something different than you are?
Have you any hacks installed?
Luc
PS: I remember in the betaforum, I could reproduce the error when adding a wrong link manually,... but cant remember what it was..
What I suspect is that some hack is setting the userid to something thus triggering the error...
because the $userid should be empty anyway...
Therefor you can safely remove those lines of code without loosing any functionallity!!!
to test this... add following line of code above
if ($userid)
echo $userid; exit;
now when you click a next link... you should get a blank page...
if not, (you get a white page with number) you would have to search through the plugins which one is adding the userid...
but if I were you, i just stick to the working fix.. by removing those lines..
Other possibility.. you have some error on your browseimage.php... so that the first link when you go to showimage is allready wrong.. having userid instead of imageuser!!! in that case its a completely different problem..
Luc