Dynamic MoPics
for osCommerce Online Merchant v2.2
What does it do?
I absolutely loved the idea of the MoPics contribution, but adding 16
images in the admin section for each product grew rather tedious. I
noticed that all of my images followed a pattern, so I wrote this code.
Now only ONE image is needed to be defined in the admin. The rest of the
images will appear on the product_info.php page if they exsist.
Please not you do not have to follow my naming scheme. You can come up with
your own variations, as the script is flexible in that way. Mine is just an
example to follow. More on the naming scheme later. For now let's install it.
Legend: 
Download

Report
For those using MySQL5, the installation won't work. You'll find MySQL will report a SQL query error.
Use this sql file for a successfull installation.
This is not the full Dynamic Mopics contribution, just the import sql file.
Save your custommers bandwith showing thumbnails for the main pictures too!
What is this: In order to use this contrib. and to save on loading time, I make 2 images for every product. The large one for the pop-ups and a thumbnail for listings.
The problem is: even thou I have thumbnails for every main picture, OSCommerce would always take the big image and just resize it (only for main pictures, not for extra pics)
So I checked the code and found the places where it displays the image… and added the mopics tumbs directory to every path.
Now I have the thumb displayed and the popup still shows the large image, how’s that? =)
zip file contains a word document with the instructions. Only 3 text replacements needed!
This is NOT the full Dynamic Mopics contribution.
If you don’t have it already, download and install it first.
Based on Dynamic MoPics v.3.000
check it out at http://www.DominioGeek.com/catalog/
FTP Upload included in admin section (categories.php). Maybe someone can integrate this into an update. No full package.
Version 3.000 - Major Revision
====================
* Fixed bug when osCommerce's "Search Engine Friendly URLs" was enabled.
* User definable image pattern
* User definable counting method
* popup_image.php now pops up to the size of the larger image, rather than resizing after the image loads
* A link to popup the larger image is only shown if a larger image was found
* Images are laid out in an osCommerce style "box" now by default.
* Layout is CSS controlled
* Any type of image now supported.
* Image types are user definable
* Can be mixed (one product can have .gif, .jpg, .jpeg, and .png thumbs for example)
v2.2: Fixed code bug in pop_image.php where the window was not resizing.
Added support for older versions of osCommerce who use $product_info_values.
Moved configuration to admin. Cleaned up code in popup_image.php.
fixed a small error in the code logic, causing thumbs to link to their next in line rather than themselves.
Why jump to version 2.0? The code has been very much optimized for much much faster parsing time.
MAX_DISPLAY_THUMBS is now obsolete. you are only limited by how many extra thumbs u think you can handle making ;)
The display code will only be run based on how many extra thumbs it finds rather than MAX_DISPLAY_THUMBS.
*Note* if upgrading, just overwrite the popup_image and dynamic_mopics files
and make sure you have the same defines for configure.php
forgot to filter the popup_image.php in the last update...
fix for users whose main thumb is in the main catalog image dir
Just updated a few small text errors. Now also define the image type (jpg, gif, png, etc..) in configure
What does it do?
I absolutely loved the idea of the MoPics contribution, but adding 16
images in the admin section for each product grew rather tedious. I
noticed that all of my images followed a pattern, so I wrote this code.
Now only ONE image is needed to be defined in the admin. The rest of the
images will appear on the product_info.php page if they exsist.
Please not you do not have to follow my naming scheme. You can come up with
your own variations, as the script is flexible in that way. Mine is just an
example to follow. More on the naming scheme later. For now let's install it.