When creating or editing a post, your users can open a popup window that will show them pictures in the chosen gallery or albums. Now also supports attachments: Reuse what you uploaded! A click on the picture inserts it into the editor.
Works with
vBulletin 3.7.x and 3.8.x, vB Blog (probably anything that uses the vB editor)
Upload the contents of folder "UPLOAD" to your forum root. Note how the folder structure in this folder mirrors the folder structure in your forum root, so every file will be in the right place.
a) If you intend to use only the vBulletin forums albums, proceed to step 4.
b) If you intend to use any other gallery product, see "Product configuration" in second post.
Install the product.
a) If you are using Template Modification System (TMS), you're done.
b) If not, do the template modifications explained in template_edits.txt manually.
Basic Configuration
if you're using only vB albums, everything is done via AdminCP->Options->Photo-Popup
Decide there how many rows and columns the popup table will have, what gallery products to use, which insert options you want to allow, activate code mode on a usergroup permission basis, or activate debug mode
Just reimport the product-xml-file, overwriting the old version, and reupload the photo-popup.php.
Please check in config_file_versions.txt whether the config file for one of the products you use has been changed since last update.
If the config file for one of your products has been updated, upload it from config files folder to your includes directory. Don't forget to take note of any any changes and settings in the old file and adapt the new one accordingly, if necessary.
Support and debugging
Ill help whenever I find the time. Before asking, please activate debug mode and post the information given there (especially under "Code". Please try the two links given - do they look "normal" and do they work? Debug information is only shown to Administrators (usergroup 6). Always state the products you use, including the software versions. Also read the infromation in the second post of this thread.
Hopes for the future
World peace, happiness, health and lot's of money
Version history
Version 3.5
new: supports attachments
new config file for CND Garage > 2.x
Version 3.4 / 3.4.1: Album dropdown not populated if using mysqli,Photopost not saving medium sized images, Fix for PHP 5.3.0 related bug (bugfixes)
Version 3.3 new/updated config file vBGallery (bugfixes); session-handling fixed; workaround for vbseo problem with Firefox in WYSIWYG editor
Important: template edits have to be redone!In every manually done template edit find: photo_popup.php?e=$editorid and replace with photo_popup.php?$session[sessionurl]e=$editorid
Version 3.2 new/updated product config file vBGallery (bugfixes), some additional error checking and error messages, debug information enhanced
Version 3.1 new/updated product config files: cnd garage (thanks to wottech for cooperation), photoplog categories, photoplog albums, photoplog, vBGallery; some additional cookie error checking; error checking in AdminCP removed; bugfixes from this thread.
Version 3.0 code reorganisation: implemeting of new galleries made easier by outsourcing of the relevant settings and database queries into seperate config files; new feature: support for vBGallery and Photoplog (lite?) added; minor bugfixes
3.0.1 Important bugfix if you are using vB albums: wrong database query in config file. To fix this, it's enough to reupload photo_popup_config_albums.
2.2 New feature: 2 plugins to show correct location and activity in "who's online". Bugfix: Bit of unphrased German removed from template (in pagenav dropdown). For upgrade from 2.1 just import product file, no uploads necessary.
2.1 New feature: Code mode. Lets you see the corresponding bb- or html-code instead of sending the image to the editor. If your browser allows that, the code is also copied to clipboard. Bugfix: Fixed a problem where pagination misbehaved when working with vB albums
2.0 New feature: Support for quickreply and quickedit!
1.4 New feature: Three new insert-options: thumbnail, medium and original image not linked themselves, but with a link to the gallery/album in the line below. This should be especially interesting for the users of the image resizer mod.
1.3 feature improvement/bugfix: default popup size is now determined before opening, not after (window.resize method causing issues in Firefox). Auto-close of the popup now using the YUI Event Listener; the needed library is already part of vB's standard distribution. New feature: title bar with "close this window"-link.
1.2 new feature: popup closes after editing is completed; smaller changes in Layout
1.1 new feature:set popup window size, to go with your table settings; minor bugfixes
1.0 Initial release
Development and bugfix releases for config files
If the need arises, there will be development or bugfix releases of config files between official releases of this mod. The zip file attached to this post will always be up to date. At the moment, there are no development/bugfix-releases.
Bug fixed: When using mysqli, the albums dropdown did not get populated from the database.
Bug fixed: Photopost Pro will not save medium sized images (smart!) if the original is smaller than the medium. The mod will now check whether there is a medium sized image. If not, it will use the original image for all medium sized options.
Update is strongly recommended if you use Photopost Pro and/or mysqli.
If you use PP, please remember to take note of your settings in your old config file and do them accordingly in the new one.
Upload folder, too, as stated in the upgrade instructions in the first post. If you are using PP, you have to upload the config file from the config files folder, too.
Let me know what products you use with this mod! I started a little poll over in community lounge. Please spare a second and tell me how you use this mod. Thank you
I see that this is supposed to work in all browsers. I have members that can't use it in Chrome and Opera. What settings should I tell them to adjust to get it to work?
Since it works for me in both browsers and your error description gives no information whatsoever on the nature of the error: no, I can't tell you what to tell your users.