In some cases it it makes more sense if there is no default gallery node per user. Can this be controlled by a config option?
In some cases it it makes more sense if there is no default gallery node per user. Can this be controlled by a config option?
Comments
Comment #1
greg.harveyI could pull it out of the hook_install and have a "generate default content types" button in admin instead. My concern would be novice users might not understand the necessary steps, but I guess I could make it really obvious, e.g. present users with the generate options on the first step of a two-step admin form?
Ideally you would interrupt the installation process and ask, but I don't think that's possible.
Comment #2
kirilius commentedThe button would solve this problem I believe.
In my case I don't quite like the default gallery's name, because it seems to imply that all new galleries will be added INSIDE it ;-) I would prefer to let the users create whatever galleries they need.
Comment #3
greg.harveyOption to override the default title would be another good feature.
Actually, galleries are not inside galleries. There is a flat structure - all galleries are on the same level. User's can edit their default gallery name (if you permit them with the node module's "edit own cck_gallery" permission). Also, if you want to *enforce* one gallery per user and not editable, then this is also achieved with node module permissions, which is quite nice.
Comment #4
mojzis commentedI am voting for "the button" :-).
Indeed, I think quite a few things from what it does during install might be optional / "editable" (such as the default node types) - so it would probably end up as a form rather than a button.
BTW - from a "philosophical point of view" I think we are getting to an era where modules as they were wont be the same ... (sounds pathetic :) is anyone aware about anything beeing prepared for the new CCK / Views based modules ?
Comment #5
greg.harveyModule obsolete, no further dev will be done.