Enhanced Dynamic MoPics and Images stored in directories

[ridexbuilder]

Looking now...
Hmm bit unsure as to how that one crept in. It's intended for use where you have a stylised header to each of the boxes. If unused then...

  background-image:  url('images/box_header.jpg');

should be replaced with

/* background-image: url('images/box_header.jpg'); */

in all instances within dynamic_mopics.css

I'll grab some grub and have a think

[ridexbuilder]

New ALPHA release available, for developers/testers. Not advisable to be used in a live/production environment and should be considered as a preview only.
Highlights:

• Product Preview shows main image and any MoPics images (very similar to how the page will look to the end user) with Slimbox image popups.
• Product input page rearranged to put price related items together.
• Model number moved up into a more prominent position.
• Dimensions grouped together, using less screen 'real estate'.

Donations to the usual place. Though I guess 'Rep Power' is better than nothing.

[ridexbuilder]

Following a reply in a recent thread (albeit slightly out of context)

...or diverge from osCommerce so much as to break compatibility with the addons for osCommerce

One wonders whether I should stop further 'enhancements' and backport to osCommerce 2.2 - would certainly benefit one of my clients.

[michael_s]

No need to stop developing mods. They are mods, not core code. If someone decides to add this feature, it is their decision and has no bearing on the project as a whole.

No need to backport either. If it works in osCMax, it will work in osC with very little change. Remember that your mod is built to work with osCommerce + bts + dynamic mopics. As long as it works with that combo, there is no point in backporting, as those are required for the mod to work.

[ridexbuilder]

Product Preview of images stored in subdirectories now tested - moved to beta status.
USE WITH CAUTION - on a test/development site first!

[adatole]

I just can't seem to get Dynamic MoPics to work on my site. I've just loaded a fresh copy of 2.0.4, then the RC3 patch. Applied all database mods, etc. images, images_big and thumbs are all set to 777. I've got blahblah.jpg and blahblah_1.jpg in both images_big and thumbs (just in case). But still no love.

Promo Custom Branding :

This is hosted on bluehost, if it makes a difference.

ANY insight is welcome!

[ridexbuilder]

Take this product:
Wood Memo Pad Holder With Pen
/catalog/images/thumbs/pen-paper.jpg
That image is not a thumbnail - 500px × 333px (scaled to 100px × 66px)
It should be stored in /catalog/images/images_big/pen-paper.jpg with a resized 100x66px thumbnail stored in /catalog/images/thumbs/pen-paper.jpg

For a much easier time of it, grab the latest release (beta one). It'll auto-generate the images. Just go in and set the image sizes in Admin., Images, then upload your original photo, it'll do the rest. A perfect time to do this, given the few products already uploaded.

The only time that you'll need, for example, /catalog/images/thumbs/pen-paper_1.jpg and /catalog/images/images_big/pen-paper_1.jpg, is where you have an additional image to display. These will need to be sized correctly prior to uploading via FTP. This step will soon be surplus, if/when I get round to releasing the in-progress next major release.

EJ

[adatole]

I'm either confused, mis-configured, or both (likely both).

First, I *do* need additional images, so please help me understand how to proceed (the image_1.jpg, image_2.jpg files were in /images/thumbs already).

Based on your advice, I tried resizing the /thumbs pictures first, but it didn't make a difference.

Then I grabbed oscmax_V2.0.xEMRC5b2.zip and uploaded the whole thing to the site, over-writing the files that are there. I applied the SQL file although those were duplicate records, according to phpMyAdmin.

I still didn't have the "click to enlarge" option, nor did I have additional images. I figured that something is linked to actually ADDING the picture via the admin page (Catalog, Categories/Products). In editing an existing product (my intention was to re-upload the picture) I was greeted with this message:

Warning: require(additional_images.php) [function.require]: failed to open stream: No such file or directory in /home6/promocus/public_html/catalog/admin/categories.php on line 956

Fatal error: require() [function.require]: Failed opening required 'additional_images.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home6/promocus/public_html/catalog/admin/categories.php on line 956

Ever the optimist, I thought I'd *still* try to upload my picture. Alas and alak, there was no "save" or "submit" button to complete the process.

Because this *is* the start of the project and because I have a good copy of EasyPopulate (as well as a site backup), I'm willing to reload the system from scratch again. But please tell me which versions of OSCMax I should be downloading (2.0.4 or something else?) and which patches to apply. Also, should I be restoring from backup or is that introducing problems and I'd be better off going with EasyPopulate?

Thanks for the patient guidance and ongoing sense of humor!
- Leon

[ridexbuilder]

Tell you what, you done well to find beta2! I had to search for the filename to grab it. Weird.
Anyways... In my haste to upload the file, I gave you lot a sneak preview of what I was working on (and didn't want released), so in the notes for that release (presented here with better formatting):

Added in a file to cater for bug in specials.php.
Instant update removed from categories.php, to make more modular and simpler to implement.

Please remove lines 955-957 from admin/categories.php:
<!-- additional images //-->
<?php require('additional_images.php'); ?>;
<!-- additional images //-->

Not included in this version.

Apologies for that - I can never get the formatting correct in the Project Releases and should've replicated it here. Done now.

[ridexbuilder]

I'm either confused, mis-configured, or both (likely both).

That's me - always!

I applied the SQL file although those were duplicate records, according to phpMyAdmin.

- that would be down to the fact that you had already installed a previous release. You only need to apply any additional SQL statements, compared to the previous update (if any).

... But please tell me which versions of OSCMax I should be downloading (2.0.4 or something else?) and which patches to apply.

If you are using the 'standard' download of 2.0.4 and the aformentioned 'beta patch', then you're fine - there are other pseudo-development releases but for your purpose what you have should do the job.

... (my intention was to re-upload the picture) I was greeted with this message:...

Please try again, with the changes detailed in the previous post.

More to follow...
(Grabs a big gulp of caffeine)