Uploading mod question

[topaz44]

Anybody? If it was already posted, please show me the link. Sorry.

[swguy]

If it *can* be installed using an override, you should do so.
To see if overrides are supported in a directory, look for the subdirectory "classic." As of 1.3.7/1.3.8, you'll see it in

./includes/languages/classic
./includes/languages/english/classic
./includes/languages/english/extra_definitions/classic
./includes/languages/english/html_includes/classic
./includes/languages/english/modules/order_total/classic
./includes/languages/english/modules/payment/classic
./includes/languages/english/modules/shipping/classic
./includes/modules/classic
./includes/modules/sideboxes/classic
./includes/templates/classic


this means the directory can be overridden. Where you see "classsic," create your own subdirectory with the name of your own template. For instance, in templates, if your template is named "custom," if you are overriding a file in includes/modules, you would create

./includes/modules/custom/

and create the file there. Keep with this strategy, and your upgrade will be less painful.


and put

[topaz44]

Thanks. I have already created the custom folders. Now I know that if any new mod is to be uploaded, put them all in custom if possible.

[swguy]

Even if the mod author was careless and didn't do this, you should. It will make your upgrade experience easier and smoother.

[topaz44]

Thanks. Still struggling with image handler. All I am seeing in the support thread is problems after installation, not installation. Maybe my head is not there today.

[topaz44]

Well, that works now. Uploaded great on the first try.

[CJPinder]

Thanks. I have already created the custom folders. Now I know that if any new mod is to be uploaded, put them all in custom if possible.

Even if the mod author was careless and didn't do this, you should. It will make your upgrade experience easier and smoother.

Sometimes if a mod author has placed files in template_default it is because that is where they should go rather than carelessness. For example, my Checkout Amazon style mod has two files that need to be uploaded to template_default. The reason for this is that it creates two new pages and for each page there needs to be an associated template file. If the template file was only in the custom template folder the page would break if the user switched back to the Classic template for testing. By placing the template file in template_default the page will continue to work no matter which template the user switches to. To modify the template it should be copied to the custom folder first as per the normal procedure.

Regards,
Christian.

[swguy]

CJPinder, your point is well taken - I was thinking about existing files from the default installation that were being overridden, but your clarification is very helpful.

[swguy]

Thinking more about CJPinder's remarks, I'm having mixed feelings about this now ... introducing (say) a new module and placing it in

includes/modules/foo.php

rather than

includes/modules/custom/foo.php

does indeed mean it will work if you switch templates during a test. But how often does this actually happen? On the flip side, during an upgrade you can easily miss this file since it's not in a template folder - and who knows how long your site will be broken if you do. Now obviously you could put the default in includes/modules and put a second one in includes/modules/custom ... but what if someone else is making a change and carelessly doesn't bother looking in the template folder but just changes the one in includes/modules?

There are benefits to both approaches, I guess. Taking detailed notes and making good backups will help avoid (or at least minimize) problems. When I release a mod or contribution, I generally place new templatable files in template directories to reduce the number of files and to make further modifications easier - but YMMV.

Somewhere on my big fun list of things to do is "write an article explaining how to install a mod" and I guess I'll have to explain both points of view and the costs and benefits of each.

swguy