BTW, I just upgraded my site to PHP 7 with latest Piwigo and it seems to be working including gdThumb. I suspect there are corner case, so I am all ears
PS: $conf['show_php_errors'] = E_ALL ^ E_DEPRECATED; is indeed needed but for Admin Tools plugin
Last edited by Serge D (2016-03-26 01:00:38)
Offline
For now just feel a WARM WELCOME. It is good to see you around again. :D
Offline
version 1.2.27 has been published
+ Validated support for PIWIGO 2.8
+ Translation improvements: ES, DE, GR, EO, HU, KR, MN, PL, SI, TH, VN, CN, HK
+ Bootstrap CSS updated to 3.3.6
Last edited by Serge D (2016-04-06 19:03:19)
Offline
I'm still having issues with the "static menu" setting for "Main Menu Mode". The menu appears, but it overlaps album/photo thumbnails on the left-hand side of the screen instead of being in its own column like with 2.7.4. I've switched to "Popup Menu Closed" for now.
Last edited by windracer (2016-04-08 18:49:29)
Offline
I saw GDThumb had an upgrade as well so I have upped Greydragon and GDThumb a few moments ago.
Thanks Serge!
Will browse a round a bit before doing Piwigo 2.8.
Offline
Hey Serge. I'm using Piwigo 2.7.4 and Greydragon.
1) Are you aware that your theme is scaling the pictures, not displaying them to 100% ?
I usually use Firefox and I didn't observed nothing strange, but then I opened Chrome to check how my visitors view the gallery and observed something strange. Somehow my images lacked sharpness that I was used my images to have. I investigated with F12 and i discovered the problem.
Because you specify (inline) the image height and weight in the template code, and then you add 2px padding and 1px border in CSS, the image will be rescaled with 6pixels less, ending by being browser resized.
Probably Firefox apply more sharpening then Chrome when scaling the image and the effect isn't that obvious .
Maybe you should enter the image into a container and apply the padding and border to the container. In this way probably the image wont be scaled.
2) I'm using gdThumbs extension and I'm trying to add style to album thumbnails (border for example), to make easier for visitor to distinguish between thumbnails of album and pictures.
I have "album" class to subalbum thumbnails (actually to <li> element) only to when parent album contain both subalbums and pictures.
So I did not found a class/id to work only for album thumbnails.
Last edited by eliz82 (2016-05-05 09:09:04)
Offline
eliz82 wrote:
2) I'm using gdThumbs extension and I'm trying to add style to album thumbnails (border for example), to make easier for visitor to distinguish between thumbnails of album and pictures.
seems that "album" class is added by the gdthumb.js not by the theme. I have edited the gdthumb_cat.tpl and added a new class to <li> element. Now i can differentiate CSS between category and pictures. Something like this should be official.
Last edited by eliz82 (2016-05-07 13:30:13)
Offline
I forgot to write here but it seems this theme is NOT compatible with plugin "PWG stuff".
-If you add a "personal block" above the "main block" is OK.
-If you add a "picture block" (any type) under the "main block" the things become really messy.
The pictures <li><img> are moved from the <div> of the piwigo stuff and putted in the same <div> where category thumbnails are displayed. Also they are set an inline height attribute (the same as category thumbs).
I'm attaching a print screen.
I'm not sure where is the code who cause the problems but I'm assuming is something with GDthumb, some javascript trying to put masonry style to <li> <img> of the category thumbnails.
I think somehow PWG stuff is using the same classes/ids to their <div> , and GDthumb have some javascript that manipulates those classes. Because PWG stuff use the same classes the javascript is ending manipulating the wrong html elements.
Last edited by eliz82 (2016-05-25 09:50:22)
Offline
Found the problem to the PWG Stuff plugin incompatibility
plugins\PWG_Stuffs\theme\template\stuffs_thumbnails.tpl
this line is causing the confusion
<ul class="thumbnails stuffs_block_{$block.ID}" id="thumbnails">
the ID thumbnails is causing the problem
(to fix just rename the ID)
then the plugins\GDThumb\js\gdthumb.js
they are functions that search for "ul#thumbnails" elements
Last edited by eliz82 (2016-05-25 20:06:52)
Offline
Hi,
A very great theme, I like it !
I had the same problem as windracer.
windracer wrote:
I'm still having issues with the "static menu" setting for "Main Menu Mode". The menu appears, but it overlaps album/photo thumbnails on the left-hand side of the screen instead of being in its own column like with 2.7.4. I've switched to "Popup Menu Closed" for now.
I added this code in "custom css" and it seems to fix the problem
#menubar { position: static; }
Thanks, Valkann! That worked for me too.
Offline
Actually, that fixes the overlay problem, but for some reason the "static" menu won't stay static. It starts out closed, and I have to actually open it (as if it was in popup menu mode).
Offline
windracer wrote:
Actually, that fixes the overlay problem, but for some reason the "static" menu won't stay static. It starts out closed, and I have to actually open it (as if it was in popup menu mode).
I have make some change in the theme.menu.js
//2016-07-27 : We arrange so that the menu is always opened by modifying the behavior of the script function hideMenu(delay) { if ((p_animated_menu == "on") && (delay != 0)) { //jQuery("#menubar").fadeOut("fast"); jQuery("#menubar").fadeIn("fast"); } else { //jQuery("#menubar").hide(); jQuery("#menubar").show(); }
I did a child theme to implement these changes
Hope this can help you
Last edited by Valkann (2016-08-05 14:40:45)
Offline
Valkann wrote:
I have make some change in the theme.menu.js Hope this can help you
Thanks again, Valkann. That indeed makes the menu stay open, restoring the original "static" behavior. But the menu now can overlap the footer, which I don't recall it doing before the Piwigo upgrade. I guess I'll stick with the pop-up menu version for now still.
Offline