Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Drupal 6 version is cooking quietly, I give it a hand few evenings a week. So far I have left some things to do:
* Convert ajax commenting , testing it. As it appears to me, comments module functions has been changed, Last time I started to work with it, I got "Call to undefined function comment_edit()". Must explore it`s functions again;
* compare d5 and d6, take a look at functions that are not ported yet:
* prog_gallery_user($op, &$edit, &$user, $category = NULL)
// link to user's gallery in his profile
* prog_gallery_block($op = 'list', $delta = 0, $edit = array())
// blocks aren't ported at all, this means theme`ing, blocks code, settings
* Image nodeapi modification with all links from galleries etc. implementation of image node attributes.
i have an update: recently it got almost all abilities from d5 version except commenting. If that`s fine, I could remove commenting part and create d6- dev release for testing.
okay, there it is, a drupal 6 version of prog_gallery. I spent >40 minutes while trying to understand how to properly make 6x-dev branch, but finally I made it and there is a cvs snapshot for download on project page.
So what`s inside the box?
+ Almost all features have been ported. What`s not ported is listed below.
+ database is backwards compatible with d5 version
+ commenting works, I dug into comment module functions... but it really needs some testing.
- views 1.x support is not ported. (maybe it is movable 1:1, whoever deals with views, must check out)
- watermarking option + admin setting is not ported (watermark module itself is not ported to d6)
+ lightbox2 integration is new to D6 version. optional dependency. Ideas of better lightbox2 integration are welcome.
- There is still code optimisation needed, because I have not red Drupal API line by line - function by function, I find that I have wrote like 4 lines instead of using one built-in function (like drupal_to_js, drupal_add_js, js basePath)
it wouldn't work on my install without it. There also appears to be something strange going on when it is showing My galleries. On my install it has an empty box next to the gallery image with the file name below the box not the image. I figure it is just something in the css.
By The way I really like this module, I've been playing around with it for a few days. There are a lot of things I would like to add to it for the application I intend to use it for. I just haven't figured out the the best way to go about it yet.
Thanks
The reason why there is an empty box, which actually is gallery, is one of following:
- the gallery is empty
- it has no thumbnails
- it isn`t published
The name You see there is actual name of gallery, you can change it by clicking on it and choosing "edit" tab. You can add pictures in "content" tab.
the "<?php" issue was fixed yesterday and I believe it is on dev snapshot already.
Bravo! This looks like the best Gallery For Drupal, period! Will the D6 version support views2 and CCK? What about a simple prev/next links next to each image?
thanks for your hard work. now i know what module that pdf I found on scribd is!
Thank you, i guess views2 is doable (I hope PROG team will give a hand with this). Which gallery parts would you want to see exported as CCK fields? How do You see that? Please, open new ticket if You really want deeper brainstorm with these topics.
Why would it be "way better". I see this opinion a lot on do, but do you people actually have any arguments for saying so? As far as I know the official plan is to keep image.module, but internally swap the storage to filefield resp. imagefield, so for modules depending on image.module nothing would change (except some api calls probably).
It's just not right to have to install image when your site is already using imagefield and cck. CCK gives way more flexibility for development and theming, especially with imagecache.
Image.module gives you the exact same flexibility in both development and theming. You just access different variables in the node object. Of course you are free to use imagecache with it, I do so on two pages of mine without any problems. In my opinion it's actually the better choice, because you can _rely_ on stuff with image.module. You know the name of the content type, you know that there will be exactly ONE image stored in it, etc.
couzinhub: this would have exactly nothing to do with imagecache. Filefield gained this feature recently, but there is no release version that supports it. There is a patch waiting in the queue of image module to do the same, but it's not yet commited. If you want to do it, apply that patch.
but in the end of the day - PROG Gallery will stick with image nodes, at least till 7th version of drupal will knock out the door and demand to come in.
What I`d be happy about is some real Drupal knowledge You guys have, with open tickets here. As an example I`d pick up and internationalization ticket where I just didn`t know how l18n internationalization works.
Comments
Comment #1
mikgreen commentedThere will be a D6 version, but not until a couple of months from now.
We need to get D5 release feature ready and stable at first.
Comment #2
Anonymous (not verified) commentedAwesome, thanks !
Comment #3
portait commentedAny news on a drupal 6 version?
Comment #4
Jānis Bebrītis commentedDrupal 6 version is cooking quietly, I give it a hand few evenings a week. So far I have left some things to do:
* Convert ajax commenting , testing it. As it appears to me, comments module functions has been changed, Last time I started to work with it, I got "Call to undefined function comment_edit()". Must explore it`s functions again;
* compare d5 and d6, take a look at functions that are not ported yet:
* prog_gallery_user($op, &$edit, &$user, $category = NULL)
// link to user's gallery in his profile
* prog_gallery_block($op = 'list', $delta = 0, $edit = array())
// blocks aren't ported at all, this means theme`ing, blocks code, settings
* Image nodeapi modification with all links from galleries etc. implementation of image node attributes.
* lightbox2 integration. optional dependency, http://drupal.org/node/144488
* code optimisation
I think it will be ready to test in February or so if no other big jobs are gonna show up.
Comment #5
portait commentedThanks for the update
Comment #6
aaron1234nz commentedIn my opinion, this is the best gallery available for Drupal. I'm keen to put this on a D6 site. If you need a hand let me know.
Comment #7
Jānis Bebrītis commentedwow, thanks a lot! it's very nice to hear this.
Comment #8
sedat44 commentedsubscribing
Comment #9
drupal999 commentedsubscribing
Comment #10
mishoboss commentedThis gallery is exactly what I need. It's just perfect!
I'm waiting desperately for the Drupal 6 version.
Comment #11
Jānis Bebrītis commentedi have an update: recently it got almost all abilities from d5 version except commenting. If that`s fine, I could remove commenting part and create d6- dev release for testing.
Comment #12
mishoboss commentedIt's OK for me. It will be nice to release it for testing :)
Thanks and keep the good work. This is the perfect gallery module!
Comment #13
Jānis Bebrītis commentedokay, there it is, a drupal 6 version of prog_gallery. I spent >40 minutes while trying to understand how to properly make 6x-dev branch, but finally I made it and there is a cvs snapshot for download on project page.
So what`s inside the box?
+ Almost all features have been ported. What`s not ported is listed below.
+ database is backwards compatible with d5 version
+ commenting works, I dug into comment module functions... but it really needs some testing.
- views 1.x support is not ported. (maybe it is movable 1:1, whoever deals with views, must check out)
- watermarking option + admin setting is not ported (watermark module itself is not ported to d6)
+ lightbox2 integration is new to D6 version. optional dependency. Ideas of better lightbox2 integration are welcome.
- There is still code optimisation needed, because I have not red Drupal API line by line - function by function, I find that I have wrote like 4 lines instead of using one built-in function (like drupal_to_js, drupal_add_js, js basePath)
Additionally I want to remind that there`s new swfupload version (2.20beta5 (change-set at http://swfupload.org/forum/news/1195 ) and I packed it for download at http://stuff.prog.lv/prog_gallery/files/swfupload_custompack.zip ).
If something doesn`t work, please open new issue with specific problem.
Thank you all for patience and good word, I`ll try to support module as much as I can.
Comment #14
Jānis Bebrītis commentedComment #15
kareed commentedThe install file is missing the php. First line is <? should be <?php
Comment #16
Jānis Bebrītis commentedas far as I know, it is not strictly required like many other things, but will be done asap, thanks!
Comment #17
kareed commentedit wouldn't work on my install without it. There also appears to be something strange going on when it is showing My galleries. On my install it has an empty box next to the gallery image with the file name below the box not the image. I figure it is just something in the css.
By The way I really like this module, I've been playing around with it for a few days. There are a lot of things I would like to add to it for the application I intend to use it for. I just haven't figured out the the best way to go about it yet.
Thanks
Comment #18
Jānis Bebrītis commentedThe reason why there is an empty box, which actually is gallery, is one of following:
- the gallery is empty
- it has no thumbnails
- it isn`t published
The name You see there is actual name of gallery, you can change it by clicking on it and choosing "edit" tab. You can add pictures in "content" tab.
the "<?php" issue was fixed yesterday and I believe it is on dev snapshot already.
Comment #19
jjjames commentedBravo! This looks like the best Gallery For Drupal, period! Will the D6 version support views2 and CCK? What about a simple prev/next links next to each image?
thanks for your hard work. now i know what module that pdf I found on scribd is!
Comment #20
Jānis Bebrītis commentedThank you, i guess views2 is doable (I hope PROG team will give a hand with this). Which gallery parts would you want to see exported as CCK fields? How do You see that? Please, open new ticket if You really want deeper brainstorm with these topics.
Comment #21
jjjames commentedI misunderstood the CCK... it already supports the CCK ImageField correct?!
thx
Comment #22
Jānis Bebrītis commentedumm, not sure about this, Prog gallery is based on Image module, not ImageField module.
Comment #23
jjjames commentedOhhh...Interesting! I was under the impression that the image module was being phased out? It's hard to keep up with the fast pace of Drupal!
Comment #24
Anonymous (not verified) commentedIndeed, it would way better if Prog Gallery were using imagefield instead of image. Would that be a hard transition ?
Comment #25
scroogie commentedWhy would it be "way better". I see this opinion a lot on do, but do you people actually have any arguments for saying so? As far as I know the official plan is to keep image.module, but internally swap the storage to filefield resp. imagefield, so for modules depending on image.module nothing would change (except some api calls probably).
Comment #26
Anonymous (not verified) commentedIt's just not right to have to install image when your site is already using imagefield and cck. CCK gives way more flexibility for development and theming, especially with imagecache.
Comment #27
scroogie commentedImage.module gives you the exact same flexibility in both development and theming. You just access different variables in the node object. Of course you are free to use imagecache with it, I do so on two pages of mine without any problems. In my opinion it's actually the better choice, because you can _rely_ on stuff with image.module. You know the name of the content type, you know that there will be exactly ONE image stored in it, etc.
Comment #28
Jānis Bebrītis commentedbtw, while we are talking about images.. is there any option to store image files using subfolders instead of putting them all in one?
Comment #29
Anonymous (not verified) commentedThere is with imagefield and imagecache :)
Comment #30
scroogie commentedcouzinhub: this would have exactly nothing to do with imagecache. Filefield gained this feature recently, but there is no release version that supports it. There is a patch waiting in the queue of image module to do the same, but it's not yet commited. If you want to do it, apply that patch.
Comment #31
Anonymous (not verified) commentedEasy, it wasn't meant to upset you.
Comment #32
Jānis Bebrītis commentedbut in the end of the day - PROG Gallery will stick with image nodes, at least till 7th version of drupal will knock out the door and demand to come in.
Partially because this requires fundamental redesign and I really don`t have such time (for next 4 months or so). I`m trying to fix small issues and my challenge is internationalization issue ( #372717: Doesn't work with Internationalization ) and comments ( #386954: Comments not working ).
What I`d be happy about is some real Drupal knowledge You guys have, with open tickets here. As an example I`d pick up and internationalization ticket where I just didn`t know how l18n internationalization works.
/cheers, Janis