5
@ IrmtfanQuote:
As before i still think Xcube way of cloning modules (eg: in GIJ modules) is a better way. there is a back end (parent) and front end (child) and you just need to rename the folder name of the child to make a clone.
In this case you'll be sharing the module tables with all the other clones. If this is the purpose, then it's OK. But it won't be useful if you want to keep data separate from each other.
This method would also make separation difficult, e.g. if you want to take one clone and install it on a different Website. You will need to do extraction of data from all the tables.
But if there is a need to have the clones using the same tables of the original, then I believe SmartClone could be modified to do it.
Quote:
this way upgrading all current clones would be as simple as copy pasting one parent folder.
With SmartClone it is only one extra step - you copy the new files to the original module's directory (as you do with the D3 modules), and then re-run the SmartClone.
Quote:
Also only content modules should be clonable. some of them like protector should be unclonable.
Of course. It would be up to the module developer to provide the "clone" plugin for SmartClone.
@ sabahanQuote:
is there any list currently clonable module beside wfdownloads and smartfaq ?
There few more included in the /plugin directory. It will be up to the module developers to create a "SmartClone plugin" for their modules.
@ FlipseQuote:
Cloning this module is already very simple (rename the module and upload again), cloning it with the cloning module would be suburb.
There is nothing to clone with the Dummy module. SmartClone would be only creating a new directory and copy the files there.
