After Upgrade to Gallery 3-3.1.5- images not opening on mouse click

[A D]

Attached a screenshot. Before images opened when the default size display was clicked but not after upgrade. Logged in as Admin as well.

Andy

[A D]

It was just an upgrade from the previous G3 revival release ... probably 3.1.3.

http://outdoorclubjapan.com/photos/

[A D]

Wondering if Veiw Full Size was a module and it went in the server  bin when I deleted the old installation (didn't back up files this time).

The theme is still showing the view full size link though. In that case I might have something backed up on a dusty hard drive somewhere. Cannot find a mod for this searching online.

[A D]

It seems that a few hours later the veiw full size link has gone so I assume that was in the server cache, and it was a module.

At least it is performing to specifications and I will have to find the module again.

[mikt...@hotmail.com]

When you are logged in, hover over the bottom of a photo and in the box that pops up click permissions to see if view full size is checked. By default it is on but maybe somehow it got set to off

Tony

[A D]

Logged in, and hovering over a photos there is no box except just 'View Full Size'. I can only access permissions from the main gallery or each album page. They are all set to view full size for logged in registered users. Nothing was changed except the upgrade files but I might've lost a couple of extra modules.

[A D]

 The var folder was left untouched when upgrading - just like the instructions. Folder permissions are 0755 and file permissions 0644.

I can upload photos but now there is a red cross after upload is complete with a 500 error code, but when clicking 'Done' the photo displays in the gallery (not full size though) .

When trying to open a full size image in a new tab, I get this error message:

• Operating system: Linux 4.19.150-76.ELK.el6.x86_64
• Apache: Unknown
• PHP: 7.3.33
• MySQL: 5.6.41-84.1
• Server load: 0.03 0.01 0
• Graphics toolkit: imagemagick

Gallery stats

• Version: 3.0+ (branch master, build 434)
• Albums: 21
• Photos: 3097

Kohana_404_Exception [ Page Not Found ]: The page you requested, file_proxy/2012/120107yatsugatake004patrick.jpg, could not be found.

1. MODPATH/gallery/controllers/file_proxy.php[ 54 ]

   49 $compare_uri = url::file(ltrim($request_uri,'/')); 50 51 // Make sure that the request is for a file inside var 52 $offset = strpos(rawurldecode($compare_uri), $var_uri); 53 if ($offset !== 0) { 54 $e = new Kohana_404_Exception(); 55 $e->test_fail_code = 1; 56 throw $e; 57 } 58 59 // file_uri: albums/foo/bar.jpg

[Brad Dutton]

Are there permissions set on this album within gallery? Are you running apache or nginx?

[A D]

The previous post has all those details -  permission settings. Apache version I am not sure. It is a typical Bluehost share hosting account. Been running gallery on that for years back  since version 2.

Var folder was not touched - just deleted the rest, uploaded the new version and ran the update. This problem has not happened before.

[A D]

I just posted that the file permisions have not changed. Server settings were all in the previous post as well. The gallery user permissions are also in a post before that - set to view full size for logged in users - just not working though.

--
WHEN USING AN EMAIL PROGRAM to reply to this message, click REPLY TO LIST or REPLY TO ALL so your reply goes out to everyone in the group. If you click REPLY or REPLY TO SENDER Google will *only* send your reply to the original author (not recommended).
 
To post a NEW MESSAGE to the group, send an new email to:
gallery...@googlegroups.com
 
To view or sign in to this group on the web, use this URL:
https://groups.google.com/forum/#!forum/gallery-3-users
---
You received this message because you are subscribed to a topic in the Google Groups "Gallery 3 Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gallery-3-users/IYCsRxUazS0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gallery-3-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gallery-3-users/60d963d7-fa98-417a-a6cc-c2a63f07fcb9n%40googlegroups.com.

[Brad Dutton]

If you hover over the red cross on upload it usually shows an error message. Try looking there to determine the errors.

For the full size issue, what are the contents of .htaccess file in var/albums/2012/.htaccess? Did any URLs or paths change during this update? It seems like the gallery access check is referencing the wrong /file_proxy/ path. I would expect it to look like:

RewriteRule (.*) /photos/?kohana_uri=/file_proxy/$1 [L]

[J.R.]

:) ...a kind word aside to those who seek help from others (which is every one of us at one time or another):

If someone trying to help you asks for information, please do not reply with "I put that information in a previous post" -- simply provide the information requested. If you still have that previous post, just cut and paste the info into your current reply. People offering to help can't be expected to keep track of every recent post, or keep them on file . Asking them to go back and dig around for something you wrote earlier isn't a productive technique in a help forum. At the very least it slows down the process of getting a helpful reply.

-- J.R

[A D]

Brad Dutton

If you hover over the red cross on upload it usually shows an error message. Try looking there to determine the errors.

There is just 'server responded with 500 error - as I stated previously.

Brad Dutton

what are the contents of .htaccess file in var/albums/2012/.htaccess?

There is no htaccess file in that directory. Remember, the var folder was not touched during upgrade, yet it was working fine with the previous version.

The htaccess file in the var folder contains this:

<IfModule mod_rewrite.c> RewriteEngine On RewriteRule (.*) /photos/index.php?kohana_uri=/file_proxy/$1 [L] </IfModule> <IfModule !mod_rewrite.c> Order Deny,Allow Deny from All </IfModule>

J.R.

If someone trying to help you asks for information, please do not reply with "I put that information in a previous post"

I am sorry but I will not keep typing out or going back to search for details I already spent a lot of time adding. People just need to be considerate and read what was already posted and took time to collect.

[A D]

If this is a bug in the new version feel free to keep posting here. I will no longer use gallery 3. When it said revival on the gallery project site I thought that meant the whole project but with no theme or module updates and just essential bug fixes to keep the gallery going, These basic issues will most likely multiply and as you said in a previous post way back, Thereis no one else working on it.

 Good luck with the project but I want a stable basic release rather than each patch up job being another beta version.

[Sean Ster]

OP is being kinda a dick but I will help anyway. I updated to the latest git repo last night and had the same problems appear.

There is a change in modules/gallery/controllers/file_proxy.php where this line was added:

$compare_uri = url::file(ltrim($request_uri,'/'));

this changes the url under test

/gallery/var/albums/whatever.jpg

into

/gallery/gallery/var/albums/whatever.jpg

and then the next test fails:

// Make sure that the request is for a file inside var

This wasn't too difficult to locate. When logged in as an admin I tried to directly access a full size image url  and received a gallery page describing the exception that was thrown.

I'm not going to speculate if the /gallery/ in my url being tested is correct and that my .htaccess is set up properly. I barely understand what's going on. I just know what worked.

[Gwyneth Llewelyn]

Hm. That's interesting. Actually, quite a lot was changed on that file for 3.1.5, namely, what used to be a comparison with $request_uri is now being made with $compare_uri. So, how exactly did you fix the issue? 

[J.R.]

Thanks to everyone who's been working on this problem with Gallery version 3.1.5 -- but will someone please post in detail what the actual fix was, so that others can know how to deal with it? And I'm sure Brad wants to know about this as well. Also, Brad, I have a question: Is there a "beta" version of 3.1.5 available on GitHub that is *not* identical to the version of 3.1.5 available by clicking the link at  https://galleryrevival.com ?  I ask because I am still using the version downloaded from galleryrevival.com when 3.1.5 was first released and not seeing the "image not opening on mouse click" problem. However, my Gallery server is running PHP version 7.4.3 (build date Jun 7, 2022) -- so maybe that is why I'm not having the problem?

-- J.R.

--
WHEN USING AN EMAIL PROGRAM to reply to this message, click REPLY TO LIST or REPLY TO ALL so your reply goes out to everyone in the group. If you click REPLY or REPLY TO SENDER Google will *only* send your reply to the original author (not recommended).
 
To post a NEW MESSAGE to the group, send an new email to:
gallery...@googlegroups.com
 
To view or sign in to this group on the web, use this URL:
https://groups.google.com/forum/#!forum/gallery-3-users
---

You received this message because you are subscribed to the Google Groups "Gallery 3 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gallery-3-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gallery-3-users/2b1caef4-8a6d-4ab4-a0bf-acfa8f94f0e1n%40googlegroups.com.

[Sean Ster]

Hi. I fixed this issue in controllers/file_proxy.php (approx line 49/167) 

Comment out the existing line. Seems like a mistake if you follow the code comments above it. Maybe the intention was to only use ltrim to remove a leading slash if it exists.

#    $compare_uri = url::file(ltrim($request_uri,'/'));

instead set the compare uri to the request uri.

$compare_uri = $request_uri;

You can initially test to see if this is your problem by adding a couple of lines to print out the two values. Just remember to remove them later.

    echo $request_uri;
    echo "X";
    echo $compare_uri;