Image Handler 4 (for v1.5.x) Support Thread

Just to clarify/please confirm:

1. the install process copies the mod files into the site, overwriting the original files and making no backups.
2. the uninstall process copies vanilla 1.5 files into the site.

the auto-install is supposed to take care of this (removing old deprecated IH image settings and properly registering the IH4 menu)

The instructions say

You MUST do a complete uninstall of the hacked up version of Image Handler3

I found no mention that the IH4 installer cleans up old db entries.

The first quote from Diva refers to situations where folks install IH4 into a zc150 store that contains remnants of really old (thus the reference to "deprecated") versions of IH. Sometimes when folks upgrade from an earlier version of ZC, they forget to uninstall their outdated mods first, or do partial uninstalls and miss some of the files, and that is what she was referring to there.

The second quote, from the IH4 instructions, refers to a hacked up and totally unsupported version of IH3 (vs. deprecated code from fully supported previous versions of IH).

This instruction was included in the readme so that folks who chose to randomly edit IH3 to make it work with ZC150 without regard to full functionality and/or security would be able to upgrade to IH4 without issue.

Hope that clears it up for you :smile:

torvista:

Just to clarify/please confirm:

1. the install process copies the mod files into the site, overwriting the original files and making no backups.
2. the uninstall process copies vanilla 1.5 files into the site.

1. False

2. False

The IH4 auto-install process installs IH4 mod files to the cart. Some of those mod files overwrite core files. The auto installer automatically makes backups of those files, which it restores during uninstall.

Regarding Installation - As stated clearly in the readme install instructions...if you or another mod has made any changes to those files (and it lists what those files are), then you must merge those changes into their IH4 counterparts prior to uploading/installing IH4.

In other words, when you install, the auto-installer makes backups of the exact file you have in place at the time of the install, but will not incorporate any changes you've made into it's new IH version. You have to do that manually just as you've always had to do.

Regarding Uninstall - As stated clearly in the readme uninstall instructions...if you or another mod has made any changes to those files since the time that IH4 was installed, then you'll need to make a copy of those changes and put them back in to the file(s) after uninstall.

In other words, the uninstaller will restore the original file you had in place at the time of install. This would only be a vanilla file if the file was vanilla to begin with at the time of install. Further, if you've made changes since, you will need to manually add those changes back into the file after uninstall just as you've always had to.

For example, if you're using both IH4 and Zen Lightbox, you would need to reinstall the Zen Lightbox version of the file these two mods share after uninstalling IH4. (This is also in the readme).

The only thing that has changed with the auto-installer is that the install/uninstall process is done for you (i.e. file are overwritten and the SQL is automatically installed). Everything you used to do manually (file merges and actual uploading) you still will have to do for yourself.

The same rules apply here as have always applied - **always make backups of files that you change. **

**All of what she said just above this post.. :laugh:
**

ScriptJunkie:

The same rules apply here as have always applied - **always make backups of files that you change. **

Sometimes I get the impression that the word "backup" for some people means a lot of work... When it's actually quit easy if you just have to deal with some files. Just copy/rename them from eg. my_file.php to my_file_ORIGINAL.bak or something like that and leave it in the server/folder. Than you always have a backup and you always know where to find it. Works great for me.

And from what I have seen and understand, this is what the auto-installer is exactly doing the same when files get overwritten :thumbsup:

Precisely, the installer just does what a human being would do if they were doing the install.
-- it finds the current template and does that appropriate renaming
-- if it is going to overwrite a file then it creates a separate version of the overwritten file on the server with a different name.
-- it runs some sql statements that used to be run when you clicked 'install' ( it needs to do this without a 'install' button because of the changes in the structure of 1.5)

The uninstaller is a bit different in that reverting to versions of core files is hard to manage when subsequent changes have been made. There is some discussion about how best to do this. Until Zen has a proper plugin architecture then this is going to be an issue. I am not speaking out of turn here because I know that the developers, more than anyone, know that this is needed and are working on it.

In most cases the uninstaller will work just fine. In cases where there have been other changes to those three core files then some thought may be necessary. In this case we are effectively talking about lightbox mods that interact with IH so have basically created a 'joint' package with IH. Removing a section of that 'joint' package is always going to be a bit interesting. Kind of like making a chocolate chip cookie and then taking the chips out without messing with the rest of the cookie.

Hi Guys,

I get this in the message stack....```
Image Handler files all exist in correct positions in the directory structure.
CORE FILE OVERWRITE : /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/modules/category_product_listing.php was NOT overwritten.
CORE FILE OVERWRITE : /hsphere/local/home/wctest/test-waycool.com.au/includes/modules/pages/popup_image/header_php.php was NOT overwritten.
CORE FILE OVERWRITE : /hsphere/local/home/wctest/test-waycool.com.au/includes/modules/pages/popup_image_additional/header_php.php was NOT overwritten.
TEMPLATE FILE CREATE : /hsphere/local/home/wctest/test-waycool.com.au/includes/modules/strong/additional_images.phpwas NOT created.
TEMPLATE FILE CREATE : /hsphere/local/home/wctest/test-waycool.com.au/includes/modules/strong/main_product_image.phpwas NOT created.
TEMPLATE FILE CREATE : /hsphere/local/home/wctest/test-waycool.com.au/includes/templates/strong/css/style_imagehover.csswas NOT created.
TEMPLATE FILE CREATE : /hsphere/local/home/wctest/test-waycool.com.au/includes/templates/strong/jscript/jscript_imagehover.jswas NOT created.
TEMPLATE FILE CREATE : /hsphere/local/home/wctest/test-waycool.com.au/includes/templates/strong/popup_image_additional/tpl_main_page.phpwas NOT created.
The auto-loader YOURADMIN/includes/auto_loaders/config.image_handler.php has not been deleted. For Image Handler to work you must delete this file manually.
Image Handler has been successfully installed

I think I followed the instructions but I can't find reference to these errors in the readme. I think I need to manually do stuff that the auto installer missed???

@gruntree
Yes, in principle. I would really like to see the site if that is possible. Can you message me with the URL?
And I'll talk you through how to get this to work.

I've just tried to do an uninstall and get the following. But I'll PM you the site details.

I tried unistalling and I get more message stack errors.
Makes me think there is some permission or cofig problem because the installer doesn't appear to be working...

 ROLLBACK : /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/modules/category_product_listing.php was NOT rolled back.  
 ROLLBACK : /hsphere/local/home/wctest/test-waycool.com.au/includes/modules/pages/popup_image/header_php.php was NOT rolled back.  
 ROLLBACK : /hsphere/local/home/wctest/test-waycool.com.au/includes/modules/pages/popup_image_additional/header_php.php was NOT rolled back.  
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/bmz_cache/.htaccess 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/classes/bmz_gif_info.class.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/classes/bmz_image_handler.class.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/extra_configures/bmz_image_handler_conf.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/extra_configures/bmz_io_conf.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/functions/extra_functions/functions_bmz_image_handler.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/functions/extra_functions/functions_bmz_io.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/image_handler.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/ih_manager.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/init_includes/init_image_handler.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/images/checkpattern.gif 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/images/icon_image_handler.gif 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/images/ih-test.gif 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/images/ih-test.jpg 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/images/ih-test.png 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/extra_configures/bmz_image_handler_conf.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/extra_configures/bmz_io_conf.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/extra_datafiles/image_handler.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/functions/extra_functions/functions_bmz_image_handler.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/functions/extra_functions/functions_bmz_io.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/languages/english/extra_definitions/bmz_image_handler.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/languages/english/extra_definitions/bmz_language_admin.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/backoffice/includes/modules/category_product_listing.DEFAULT.php.bak 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/modules/pages/popup_image/header_php.DEFAULT.php.bak 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/modules/pages/popup_image_additional/header_php.DEFAULT.php.bak 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/modules/IH_INSTALL/additional_images.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/modules/IH_INSTALL/main_product_image.php 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/templates/IH_INSTALL/css/style_imagehover.css 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/templates/IH_INSTALL/css/style_imagehover.css 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/templates/IH_INSTALL/jscript/jscript_imagehover.js 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/templates/IH_INSTALL/jscript/jscript_imagehover.js 
 not deleted - /hsphere/local/home/wctest/test-waycool.com.au/includes/templates/IH_INSTALL/popup_image_additional/tpl_main_page.php 
 Image Handler has been uninstalled. 
 Image Handler creates back up versions of certain files when it is installed before overwriting them. These files have been left in position for reference. They may be deleted but will not effect the functioning of the shop if you leave them in place. 

I'm working on a test version of this site which is pretty much a newly launched 1.5 install

I have emailed you. Once we sort this out then I'll post again with a solution.

Installing this module some issues have come to light. I was hoping these could be addressed.

1. The very fact that this module installs/writes files and installer functions/files are not removed post successful installation is not secure.

I would think that anyone installing this module could certainly and more safely run an SQL patch.

2. The creating of filenames which have no associated function, such as .bak is a vulnerability and PCI fail.

There is no need for this as certainly we do not want to be overwriting existing template files anyhow. Detailed merging instructions should likely be included in the place of the "installer"

Additionally, this thread is not listed in the documentation and should be added, as the instructions for using the installer are quite complicated.... More so than just installing the module without it would be.

I find it troubling that once installed even, deletion of these .bak files disables the module.

I am not trying to beat anyone up, but clearly this module is something shop owners need and always have needed... However, it makes no sense to take PCI certified software and in one shot make it vulnerable and PCI fail.

I would be willing to help out as I can, but I lack the GD/IMageMagick skills to port this to 1.5.0.

~Melanie

mprough:

1. The very fact that this module installs/writes files and installer functions/files are not removed post successful installation is not secure.The install function was INDEED written to "clean up" after the install and it most certainly does remove the auto-installer files. (there's posts in this support thread discussing this behavior) Is this not occurring for you??? If not you will need to provide more details.

mprough:

I would think that anyone installing this module could certainly and more safely run an SQL patch.Historically this app has never used an external SQL file for install or uninstall. We wanted to maintain this level of transparency with the new version..

mprough:

2. The creating of filenames which have no associated function, such as .bak is a vulnerability and PCI fail.Already aware of this and it there is already a planned modification to address this in the next version..

mprough:

There is no need for this as certainly we do not want to be overwriting existing template files anyhow. Detailed merging instructions should likely be included in the place of the "installer"The 3 override files being overwritten are not files typically overwritten by any other add-ons -- with the exception of the two popular lightbox add-ons.. For many shopowners this is the only modification made to the 3 core files that this add-on overridess.

Nevertheless, we have no plans to replace the auto-installer simply because of this. File merging is covered in the advanced section of the install instructions. We will however be revisiting changes to the main install instructions in the next release (which should be the next day or two).

mprough:

Additionally, this thread is not listed in the documentation and should be added, as the instructions for using the installer are quite complicated.... More so than just installing the module without it would be.Chicken/egg scenario.. The support thread was created after the add-on was submitted. So there's no way I COULD HAVE included the link to the support thread in the readme..

For the record, there's a TON of add-ons that don't provide links to the support thread in their readme files AT ALL let alone a link to the support thread in the add-on description.

That all said, the plan all along was to update the readme with the next release to include this information..

mprough:

I find it troubling that once installed even, deletion of these .bak files disables the module.Not one person in testing reported anything close to this as an issue, and I can't replicate this particular behavior.. I will test again tonight to see if this bears out.. In the meantime, more details would be appreciated..

No, init_image_handler (below) is not removed.

Historically this app has never used an external SQL file for install or uninstall. We wanted to maintain this level of transparency with the new version..

Correct, but it hadn't the ability to make directories and write file before either... which is a whole new ballgame.

deletion of the .bak file was reported to me by a colleague, first the other day.... I only had time to mess around with it today, but she was correct. delete the files and the module is disabled.

Wasn't beating you up re the thread... but none the less should have been present as I was already instructed as well =) How would I possibly know you knew that?

New Installation Instructions for Advanced Users

This set of instructions is for those who are familiar with Zen Cart and addon installations. If you need more detail than is provided, please scroll up to the Installation for Beginner/Intermediate Users section.
As always, back up your database & store.
Rename the YOUR_ADMIN folder. Do not rename, remove, or relocate any of the other files or folders. Doing so may cause the auto-installer to fail.
Make any file merges that may be necessary. Some filepaths and files have changed. Please use the filemap below to assist you.

IH4 Installation Package Files
	
Maps to These Files in Your Store
/YOUR_ADMIN/includes/modules/category_product_listing_IH4.php 	/YOUR_ADMIN/includes/modules/category_product_listing.php
/includes/modules/pages/popup_image/header_php_IH4.php 	/includes/modules/pages/popup_image/header_php.php
/includes/modules/pages/popup_image_additional/header_php_IH4.php 	/includes/modules/pages/popup_image_additional/header_php.php
/includes/modules/IH_INSTALL/additional_images.php 	/includes/modules/YOUR_TEMPLATE/additional_images.php
/includes/modules/IH_INSTALL/main_product_image.php 	/includes/modules/YOUR_TEMPLATE/main_product_image.php
/includes/templates/IH_INSTALL/popup_image_additional/tpl_main_page.php 	/includes/templates/YOUR_TEMPLATE/popup_image_additional/tpl_main_page.php

Log in to your store's admin. If you forget to do this before you upload your files, Image Handler4 will still install, but you won't see the message confirming successful install.
Upload the files to your server & then click any link in your admin to see the success message in your message stack
In Admin > Configuration > Images, set "IH resize images" to "yes" and configure as desired

If you are using Fual Slimbox or Zen Lightbox with Image Handler4 you MUST follow the instructions in the "Misc" tab regarding using either of these mods with Image Handler4.

Cannot install without the .bak files and even then although installed was not functioning. I actually did this 5 times.
My servers will not even allow the creation/storage of .bak files unless a mime type is created... as it should be according to the PCi guys.

I just want to be able to use this and install it myself w/o creating issues. It is a very good module, but I think the installer needs to be rethought and the manual installation needs attention as many PCI compliant server cannot make .bak files, cannot use the mkdir in that way as it sets the permissions incorrectly... it will additionally never work on Win, not that I care about Win :lamo:

    // make  override directories if needed
    @mkdir(DIR_FS_CATALOG.'includes/modules/'.$current_template, 0755);
    @mkdir(DIR_FS_CATALOG.'includes/templates/'.$current_template.'/css', 0755);
    @mkdir(DIR_FS_CATALOG.'includes/templates/'.$current_template.'/jscript', 0755);
    @mkdir(DIR_FS_CATALOG.'includes/templates/'.$current_template.'/popup_image_additional', 0755);

    // new files or non-core files
    // these are deleted on uninstall
     $files = array(
            DIR_FS_CATALOG.'bmz_cache/.htaccess',
            DIR_FS_CATALOG.'images/watermark.png',
            DIR_FS_CATALOG.'images/large/watermark_LRG.png',
            DIR_FS_CATALOG.'images/medium/watermark_MED.png',
            DIR_FS_CATALOG.'includes/classes/bmz_gif_info.class.php',
            DIR_FS_CATALOG.'includes/classes/bmz_image_handler.class.php',
            DIR_FS_CATALOG.'includes/extra_configures/bmz_image_handler_conf.php',
            DIR_FS_CATALOG.'includes/extra_configures/bmz_io_conf.php',
            DIR_FS_CATALOG.'includes/functions/extra_functions/functions_bmz_image_handler.php',
            DIR_FS_CATALOG.'includes/functions/extra_functions/functions_bmz_io.php',
            DIR_FS_ADMIN.'image_handler.php',
            DIR_FS_ADMIN.'includes/ih_manager.php',
            DIR_FS_ADMIN.'includes/init_includes/init_image_handler.php',
            DIR_FS_ADMIN.'includes/auto_loaders/config.image_handler.php',
            DIR_FS_ADMIN.'images/checkpattern.gif',
            DIR_FS_ADMIN.'images/icon_image_handler.gif',
            DIR_FS_ADMIN.'images/ih-test.gif',
            DIR_FS_ADMIN.'images/ih-test.jpg',
            DIR_FS_ADMIN.'images/ih-test.png',
            DIR_FS_ADMIN.'includes/extra_configures/bmz_image_handler_conf.php',
            DIR_FS_ADMIN.'includes/extra_configures/bmz_io_conf.php',
            DIR_FS_ADMIN.'includes/extra_datafiles/image_handler.php',
            DIR_FS_ADMIN.'includes/functions/extra_functions/functions_bmz_image_handler.php',
            DIR_FS_ADMIN.'includes/functions/extra_functions/functions_bmz_io.php',
            DIR_FS_ADMIN.'includes/languages/english/extra_definitions/bmz_image_handler.php',
            DIR_FS_ADMIN.'includes/languages/english/extra_definitions/bmz_language_admin.php',
            DIR_FS_ADMIN.'includes/modules/category_product_listing.DEFAULT.php.bak',
            DIR_FS_CATALOG.'includes/modules/pages/popup_image/header_php.DEFAULT.php.bak',
            DIR_FS_CATALOG.'includes/modules/pages/popup_image_additional/header_php.DEFAULT.php.bak'
             );

    // core files with overwrite
    // these are rolled back to Zen Default on uninstalll - the .bak file is left in place
    // files arranged in array (file_to_replace,file_to_replace_with)
    // file_to_replace will be resaved as file_to_replace.bak
    $core_files = array(
            array(DIR_FS_ADMIN.'includes/modules/category_product_listing.php',DIR_FS_ADMIN.'includes/modules/category_product_listing_IH4.php'),
            array(DIR_FS_CATALOG.'includes/modules/pages/popup_image/header_php.php',DIR_FS_CATALOG.'includes/modules/pages/popup_image/header_php_IH4.php'),
            array(DIR_FS_CATALOG.'includes/modules/pages/popup_image_additional/header_php.php',DIR_FS_CATALOG.'includes/modules/pages/popup_image_additional/header_php_IH4.php'),
            );

    // core files for rollback on uninstall 
    // not used on install
    // files arranged in array (file_to_replace,file_to_replace_with)
    // file_to_replace will be resaved as file_to_replace.bak
    $rollback_files = array(
            array(DIR_FS_ADMIN.'includes/modules/category_product_listing.php',DIR_FS_ADMIN.'includes/modules/category_product_listing.DEFAULT.php.bak'),
            array(DIR_FS_CATALOG.'includes/modules/pages/popup_image/header_php.php',DIR_FS_CATALOG.'includes/modules/pages/popup_image/header_php.DEFAULT.php.bak'),
            array(DIR_FS_CATALOG.'includes/modules/pages/popup_image_additional/header_php.php',DIR_FS_CATALOG.'includes/modules/pages/popup_image_additional/header_php.DEFAULT.php.bak'),
            );



    // template files
    // these are deleted on uninstall - the .bak file is left in place
    // files arranged in array (file_to_replace,file_to_replace_with)
    // file_to_replace will be resaved as file_to_replace.bak
    $template_files = array(
            array(DIR_FS_CATALOG.'includes/modules/'.$current_template.'/additional_images.php',DIR_FS_CATALOG.'includes/modules/IH_INSTALL/additional_images.php'),
            array(DIR_FS_CATALOG.'includes/modules/'.$current_template.'/main_product_image.php',DIR_FS_CATALOG.'includes/modules/IH_INSTALL/main_product_image.php'),
            array(DIR_FS_CATALOG.'includes/templates/'.$current_template.'/css/style_imagehover.css',DIR_FS_CATALOG.'includes/templates/IH_INSTALL/css/style_imagehover.css'),
            array(DIR_FS_CATALOG.'includes/templates/'.$current_template.'/jscript/jscript_imagehover.js',DIR_FS_CATALOG.'includes/templates/IH_INSTALL/jscript/jscript_imagehover.js'),
            array(DIR_FS_CATALOG.'includes/templates/'.$current_template.'/popup_image_additional/tpl_main_page.php',DIR_FS_CATALOG.'includes/templates/IH_INSTALL/popup_image_additional/tpl_main_page.php')
            );

mprough:

No, init_image_handler (below) is not removed.But the auto-loader file which executes it is.

mprough:

Correct, but it hadn't the ability to make directories and write file before either... which is a whole new ballgame.Not that new since the code that creates the files and directories in the bmz_cache folder writes directories and files too..

mprough:

deletion of the .bak file was reported to me by a colleague, first the other day.... I only had time to mess around with it today, but she was correct. delete the files and the module is disabled. if you delete them BEFORE you install the add-on then no you're right.. the install won't work. You can easily delete the .BAK files created by the install in the template directories with no issues whatsoever.

mprough:

Wasn't beating you up re the thread... but none the less should have been present as I was already instructed as well =) How would I possibly know you knew that? Wasn't expecting you to know at all nor was I feeling beat up.. I was simply responding to your inquiry about the .BAK files to let you know I'd been made aware of the issue and it will be addressed in the next update.

mprough:

Cannot install without the .bak files and even then although installed was not functioning. I actually did this 5 times.
My servers will not even allow the creation/storage of .bak files unless a mime type is created... as it should be according to the PCi guys. Again.. got it, and will be addressed in the next release..

mprough:

I just want to be able to use this and install it myself w/o creating issues. It is a very good module, but I think the installer needs to be rethought and the manual installation needs attention as many PCI compliant server cannot make .bak files, cannot use the mkdir in that way as it sets the permissions incorrectly... it will additionally never work on Win, not that I care about Win :lamo:Well I don't believe the installer truly requires a LOT of re-thinking.. The changes we need to make are fairly simple to implement, and are being addressed..

Hello, before complaining I must say thanks for the excellent addon. Used version 3 successfully on 1.38 for quite awhile, thanks.

I installed a fresh version of zencart 1.5. Imported older database from 1.38 store still online and all bmz_cache directories and images. I installed a fresh copy of Image Handler 4 then a fresh copy of zen_lightbox keeping zen_lightbox's additional_images.php. The first time I hover over an image a space of 100px's or so is created above my page and the image is displayed there. The space stays and each mouseover creates the image there not where it should be. The only other addon or change beside css files and such is zen_lightbox and its working fine. I've double checked files and am stumped, any helps appreciated, thanks

My screwup, Image Handlers back on top :) thanks again for all the addons you've written and shared.

@Melanie

Just my thoughts:

Delete of installer:
traditionally, IH has had an installer. It ran on a function that was triggered by the 'install' button. That function stayed in place after it ran. This is just the same. The installer functions stay in place but they are just not actioned. I am not sure that I completely understand your argument against this. Many modules on many platforms do not delete there install functions.

BAK files
Yes, this is going to be changed.
I think that there is a bit of a misunderstanding between you and Diva about this. There are BAK files in the original upload package. They are basically files that are going to be moved during the install or uninstall and are uploaded as BAK files. If those files are deleted prior to upload then the installer will not run as it checks that the files are uploaded correctly before continuing. There are also BAK files that are created when a file is overwritten. If you delete these then you should have no problems.
In general, the BAK suffix was a mistake and will be changed.
Actually, the file checking part of the installer is a part that I would be most reluctant to see removed. So many 'errors' are created by files be uploaded incorrectly that a quick check of this before install is finalised seems like a good idea.

Complication
Well, i think that you are just wrong here. The install procedure is to log in to zen admin, change the name of admin in the package, upload the files, refresh a page in admin. Takes me under a minute. But that is just my opinion.

Backing up Template files
Well, I know what you mean. But the idea is not that the file merging should not happen. Evidently the file merging needs to happen. The concept is more that part of the install should have a backup involved. So, for instance, if someone hadn't done the file merging there would still be a record of their previous file state. I can't honestly see why backing up a file is a problem.

File Handling in General.
Well, yes there is a different ballgame when you start moving files on the server. There are arguments for and against here. I understand that you are strongly on one side of that. Again, the support threads show that most errors are created by people putting files in the wrong places. The file handling does two things:
-- creates backup versions of overwritten files
-- puts the template files in the right place
Is your argument against either or both of these or just the concept of doing this programatically rather than manually?

OK,
I now have the admin functionality of IH4 working after installing the rolled back version you sent me Nicol.

What I don't have is the additional images showing at all in the shop.

Not sure why though.... I tried switching back to the clasic template but still no joy. Am I missing something stupid here???
URL:http://d2262519.i225.quadrahosting.com.au/index.php?main_page=product_info&cPath=50_2&products_id=2

OK guys,

I ditched the test site and had to have a go at my live site because there were real problems with the images.

I'm happy to report that IH4 is now working perfectly on my site!

Thanks very much to all the guys who work on this fantastic Mod. I would hate to have to run a Zen store without it!

ndg_uk:

Found it in the admin configure.php file

All working fine

Thanks for your help

I am having the same problem. :blink: Could someone give me the path to the adim.comfigure.php and what was altered.