• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

When a new web Foo is created from a template web _Bar only data/_Bar is copied to Foo but not pub/_Bar and templates/_Bar. This hinders deploying TWikiApplications that way and needs a shell access and copy the needed folders by hand.


IMHO templates/web is a very very bad idea, so I don't think it should be copied (you should use templates in topics instead). Copying pub is definitiely an issue. CC
But if I want to have an application specific print view I have to overload view.print.tmpl, view.print.pattern.tmpl and view.print.nat.tmpl. Same holds for view.rss.tmpl etc. Status quo is that we don't have the templates in the web space. So overloading templates in templates/web is current BestPractice. MD
Current practice, yes. Best practice, no.

Yes, you have to overload them; but the right way to do that (IMHO) is to use a cover. Tying templates to content is a major mistake. Example: I have a set of templates defined for the "Fred" web. I create the "Joe" web and want to re-use the templates. My only choice is to copy the templates subdirectory. If I had used a skin, all I have to do is define the skin in the new web.

Further, I would like to take over subdirectories of the templates directory for skins (e.g. templates/pattern, templates/classic etc)

But that is beside the point. The error here is that pub directories are not copied on web creation, which is in line with Cairo but nevertheless really crap.

CC

Call it crap or whatever you like, it is a missing functionality. Pub should be copied as stated in TWiki:Codev.ScriptToCreateNewWebWithAttachments.

-- PTh

however, this is an enhancement, as TWiki has never done it previously. in that respect, it would be reasonable to suggest it should be deferred, due to the testing load that it might produce (and notably, as no-ones ever considered it important enough to actually implement)

sorry

-- SD

A whole raft of features probably got missed because their Proposed For: field was empty rather than being set to DakarRelease.

Attachment updating is a particularly sore omission.

-- MC

Deferring it since it is to late in the game and might introduce new bugs.

-- PTh

Undeferred, post Dakar CC


Hmmm. According to the code, attachments are copied. And it works - I just tested it.

Discarding.

CC

ItemTemplate
Summary creating a new web does not copy templates and attachments
ReportedBy MichaelDaum
SVN Range

AppliesTo Engine
Component

Priority Enhancement
CurrentState No Action Required
WaitingFor

TargetRelease major
Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r13 - 2006-02-17 - MichaelDaum
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback