minimally, to import a wiki page the following YAML syntax will suffice.
+
Minimally, to import a wiki page the following YAML syntax will suffice.
{CODE(example)}
{CODE(example)}
Lines: 43-46
Lines: 43-47
*__mind your spaces__ here each level of indentation is two spaces. (recommended). type and data are at the third level, name and content in the fourth.
*__mind your spaces__ here each level of indentation is two spaces. (recommended). type and data are at the third level, name and content in the fourth.
+
*Some Object Parameters belong to the __data__ section and others (type,ref,…) are above. The above parameters table does not make it obvious. You may need to experiment.
*__Re-import is ok__ (>=tikiwiki3.0) you can load a profile multiple times in the same wiki. It will ask if you want to ''Forget'' the install - this will not remove data imported. When you re-install a profile anything new will be added. In wiki pages, it's possible to replace & append (see above options)
*__Re-import is ok__ (>=tikiwiki3.0) you can load a profile multiple times in the same wiki. It will ask if you want to ''Forget'' the install - this will not remove data imported. When you re-install a profile anything new will be added. In wiki pages, it's possible to replace & append (see above options)
Lines: 48-51
Lines: 49-66
As of Tiki 6 onwards, ''wikiparsed:'' can be used to to get the ''parsed'' (HTML) output from a page, instead of the wiki mark-up. Used with tracker filter plugins and pretty tracker templates this can make tracker data available to be used in data channels.
As of Tiki 6 onwards, ''wikiparsed:'' can be used to to get the ''parsed'' (HTML) output from a page, instead of the wiki mark-up. Used with tracker filter plugins and pretty tracker templates this can make tracker data available to be used in data channels.
+
Another, more elaborate example follows. The template page named __template_greetings__ needs to exist to provide the content for the new page.