On Jul 21, 2011, at 2:24 PM, shortname wrote:
> so, is this a good way to modify stk templates adding own paragraphs in
> newBar:
>
> [@cms.newBar ...
> paragraph="${stk.asStringList(def.mainArea.paragraphs)},myCustomParagraph1,myCustomParagraph2"
> /]
I would not do this.
>
> If I make module or install third-party with custom stk paragraphs, should I
> go through stk templates adding them in this way?
> I thinks if I add paragraph name to
> /modules/standard-templating-kit/templates/stkHome/mainArea/paragraphs, this
> can help keep changes only in config tree, but this case magnolia error, when
> paragraph is outside of stk module configuration.
Either the default stkHome template is fine for you and then you can indeed add
your paragraphs there and then export that and have it bootstrapped on your
module installation or you can add install tasks to your module handler to add
such definitions to the path you show above, or you can create your own home
template that will extend default stkHome and make your changes in your home
template.
>
> and this make me confused. How in this case should I move magnolia author
> site with content from developing to production server?
you export everything what can be exported and put it in the mgnl-bootstrap
folder of your module. The configuration will be then bootstrapped once your
module gets installed. For things that you can't export you need to write
install tasks and put them in the ModuleVersionHandler class of your module.
> for example developing server use derby for jcr, but production will use
> postgresql. Compressing webapps folders and uploading it to production is one
> part of publish process. Second is relocating jcr database from derby to
> postgres? Is this manual works for this case:
> http://wiki.magnolia-cms.com/display/WIKI/Setting+up+Jackrabbit+PersistenceManager+%28prior+to+or+after+installation+of+Magnolia+CMS%29?
This manual is about configuration of persistence manager not about how to get
your content from dev to prod.
> Or better develop and debug modules/themes on developing server, then install
> fresh magnolia, customize it, and then start add real site content?
same way you develop your template and themes you can also develop your real
site content for the initial installation, or you can install w/o any content
and start writing it indeed on the prod author instance.
>
>>> 4. I try create own module with templates inside and have lost with module
>>> configuration. I download few modules source, and trying understand how to
>>> create config files like config.modules.*.xml in mgnl-bootstrap folder.
>>> Should I make them manually or some tools can be used for that. Or can I
>>> create my module settings in current magnolia config and just export it?
>> create all in your magnolia instance and export it.
> I saw jcr uid in this xml files like:
>
> <sv:property sv:name="jcr:uuid" sv:type="String">
> <sv:value>1b32f6eb-ba6d-410c-8a31-63ec7b89b020</sv:value>
> </sv:property>
>
> is this id unique for each models on different magnolia instances? I'm afraid
> if this id have duplicate on production instance, for example other custom
> module use same id (is this possible?), this will broke something.
UUIDs are unique per workspace, so it is actually possible to have content with
same uuid in website and in config for example.
If you are trying to import xml to an instance and there is a conflict between
UUIDs you can specify what you want to do in case of such confict (fail,
override, ignore ...)
HTH,
Jan
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
