« July 2011»
M T W T F S S
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31

[blog...]

23.07.2011
19:46

Using chgallery as Image Gallery in TYPO3 with Shadowbox

chgallery settings
chgallery additional options
chgallery in action

"Could you please add a simple image gallery to the website!"

 

This requirement of customers sounds easy but with TYPO3 the developer gets nervose and starts to search the TER if there is any new, maybe perfect image gallery. But there is ... none :-(

 

With wordpress you need maximum 5 minutes to install e.g. ?NextGEN Gallery where you have everything you like: gallery, albums, categories, lightbox, sorting...

 

Back to TYPO3 you first have to decide: Do I use DAM (Digital Asset Management) or is it necessary to install the whole DAM for a simple gallery? With DAM, I use e.g. ce_gallery. Of course, I had to patch it to make it work, like I want, but you have to patch all TYPO3 galleries to fit your needs.

 

But now, I wanted to avoid DAM. And I tried the following three galleries:

 

 

YAG is for sure the most impressive extension in development and uses all modern programming technologies. But it is HUGE. Why do I need >50 classes and 10 MB of source code for showing some images? And that's not all. Some more extensions are necessary: of course fluid and extbase and pt_tools and pt_extbase.

My main problem was the flash uploader which seems to make stupid file permissions on one of the servers. That's why I dropped this solution. Also the plenty of exceptions in the logfile made no impression of a trustable pice of software. Lets wait some months and have a look again!

What is quite nice: YAG comes with its own lightbox. And you can install themes, other lightbox and configure a lot.

 

chgallery still uses the ereg()-function in the wizard for the image titles. That's why I deleted it immediately an tried wt_gallery.

 

With wt_gallery, you have to install wt_doorman and you're done. But... currently I forgot why I didn't like it.

 

At the end, I choose chgallery with pmkshadowbox. The configuration is easy if you don't make the mistake to check "?Use Single view" in the Gallery view. In this case the lightbox-code is removed and you have to add another plugin to the same page with the Single view inside. It took some hours to figure this out and finally, I debugged the source code to understand the configuration.

 

My template setup-configuration for chgallery is now the following:

 

 

# enable lightbox (pmks-shadowbox) in gallery view of chgallery
plugin.tx_chgallery_pi1.gallery.image {
file {
width = 100c
height = 100c
}
imageLinkWrap = 1
imageLinkWrap {
enable = 1

typolink {
title.field= tx_chgalleryTitle

parameter.override.cObject = IMG_RESOURCE
parameter.override.cObject {
file.import.data = TSFE:lastImageInfo|origFile
file.maxW = 800
file.maxH = 600

stdWrap.postUserFunc = user_replaceSpaces
}

# used lightbox is pmkslimbox
ATagParams = rel="lightbox"
ATagParams.override = rel="lightbox[presentlb{field:uid}]"
ATagParams.insertData = 1


}
}
}

plugin.tx_chgallery_pi1.single.image < plugin.tx_chgallery_pi1.gallery.image


Now you can add perfectlightbox or any other lightbox-clone as extension to your site. Usually you have to include the static template of the choosen extension. I choose pmkshadowbox.


Alexander Bigga
Tags: typo3, gallery
Views: 1568
  •  
  • 1 Comment(s)
  •  
Michael Knoll
02.09.2011
00:27
yag-gallery.de

Hi Alexander,

thanks for your critics on our extension (YAG-Gallery). We are happy about any feedback we can get and try to improve our software with every release.

First of all, let me explain our approach on writing a new gallery extension for TYPO3:

1. We wanted to make something easy to maintain and use. Therefore we implemented a full-featured backend module that lets you manage your galleries, albums and images easily.

2. We wanted to use modern MVC paradigms, that's why we used extbase.

3. We wanted to be extendable and wanted to create a gallery that can be personalized easily. Therefore we created a theming concept.

4. We wanted to come up with a variety of importers for different purposes. That's why we have flash-upload, directory import and zip upload.

5. We have many new features to come on current development branches, that's the main reason why we use pt_extlist for example.

Those are 5 reasons why we came up with about a hundred classes and 10MB of extension size at the end. Please mind, that 4MB of those 10MB are documentation!

Concerning your problems with the extension:

1. You can now set the file-permissions set by the flash uploader within TypoScript.

2. If you have the log entries written by YAG, it would be really nice, if you could send them to us - we are really into improving the extension and any problems are welcome!


Getting some user-feedback over the past couple of months, we have the impression, that users like the simplicity of using YAG and that it's quite stable at the moment. If you give it another try and let us know if there are any problems, we will shure get them fixed.

Regards

Michael

Your comment

Notify me when someone adds another comment to this post

back

[ 26.02.2013 ]