Image Scaling

[gjh42]

It would be possible to have two unrelated products in different categories with the same name, but one product linked into two categories still has only one product id. So the product id prefix would work, though I still think it's better to alert to conflicts and allow user discretion.

[DivaVocals]

It would be possible to have two unrelated products in different categories with the same name, but one product linked into two categories still has only one product id. So the product id prefix would work, though I still think it's better to alert to conflicts and allow user discretion.

I agree...

[niccol]

So, we are talking about the upload modifier section.

And we are talking about the renaming part of that.

So, how about:

• There is an admin switch to turn renaming on and off.
• There is an admin selection of the renaming filter.
• There is a simple ( for a developer ) way of adding new renaming filters
• As standard there is at the minimum a 'hard rename' renaming filter

The hard rename would

• rename to a sanitised version of the product name
• put everything in lowercase
• add the product id at the start of the name

Other renaming filters could do whatever developers wanted to do. Up to them. Their risks.

If renaming was being used the user would be advised if there was still a naming conflict and be given the chance of supplying an alternative name.

[niccol]

Of course, renaming is another one where it needs to be considered if we hope to create a retro-active renaming. So, does it need the ability to rename existing images?

Hmmm, that is possible but slightly scary the potential for disaster is pretty big. Someone adds a dubious filter and then goes for bulk rename and all their images disappear. Not good.

Perhaps with this and any other bulk changes you need to copy the files and then have an 'accept these changes or rollback' page. That would be a bit tedious because you also need to store all the previous image names for writing back into the database.

[niccol]

OK. Version 0.2 of the image scaler.

It does :
-- image scaling
-- additional image uploading
-- variant uploading
-- admin setting for all kinds of stuff
-- client side clean-up with an admin switch
-- admin side clean-up with an admin switch
-- clean-up just deletes files that haven't been touched for a while
-- you can set the maximum number of files to be deleted in one go to spread the load around a bit

It doesn't
-- categorise the files into directories as Nigel suggested yet. But I have a bit of a plan for the next version
-- do any of the things that I regard as 'upload modification'. Renaming, size limiting, watermarking and sharpness.

Install is just a rename of admin and an upload. Just make sure that you are logged in and not about to be logged out. The installer won't play nice if the first page it sees is the login page.

Uninstall. There is a file to upload in a separate directory in the zip. It is just the same old auto_loader file with an uninstall flag set. It will roll back the database changes and delete the files that were uploaded.

Only one core file is over-written which is application_bottom.ph which I don't think will cause you any problems. It is not deleted on uninstall but the new version won't cause problems anyway.

Let me know

Nick

[DivaVocals]

Awesome.. something to play with this weekend..

OK. Version 0.2 of the image scaler.

It does :
-- image scaling
-- additional image uploading
-- variant uploading
-- admin setting for all kinds of stuff
-- client side clean-up with an admin switch
-- admin side clean-up with an admin switch
-- clean-up just deletes files that haven't been touched for a while
-- you can set the maximum number of files to be deleted in one go to spread the load around a bit

It doesn't
-- categorise the files into directories as Nigel suggested yet. But I have a bit of a plan for the next version
-- do any of the things that I regard as 'upload modification'. Renaming, size limiting, watermarking and sharpness.

Install is just a rename of admin and an upload. Just make sure that you are logged in and not about to be logged out. The installer won't play nice if the first page it sees is the login page.

Uninstall. There is a file to upload in a separate directory in the zip. It is just the same old auto_loader file with an uninstall flag set. It will roll back the database changes and delete the files that were uploaded.

Only one core file is over-written which is application_bottom.ph which I don't think will cause you any problems. It is not deleted on uninstall but the new version won't cause problems anyway.

Let me know

Nick

[niccol]

version 0.3

just a few display changes. I haven't tested this one so much but it shouldn't need it. If it causes issues then try version 0.2.

This one just has a nice method of selecting products and lets you hide some of the information if you aren't interested in it.

[discoverytdi]

version 0.3

just a few display changes. I haven't tested this one so much but it shouldn't need it. If it causes issues then try version 0.2.

This one just has a nice method of selecting products and lets you hide some of the information if you aren't interested in it.

is this right no admin folder found it's in the uninstall folder is that right can you check it for me

[niccol]

Darn. It is the 'control' folder in that version.

I'll upload another with the correct naming :-)

Thanks for pointing it out.

[discoverytdi]

Darn. It is the 'control' folder in that version.

I'll upload another with the correct naming :-)

Thanks for pointing it out.

no prob just didn't want to try it and have a thunderbolt wizz out of my pc