Category: Wiki Syntax (text area, parser, external wiki, etc)

Please see:
http://www.wikimatrix.org/wiki/feature:CREOLE%20support
http://www.wikicreole.org/wiki/TikiWikiCMSGroupware

Related:
http://dev.tiki.org/Why+Wiki+Syntax+is+Important
http://dev.tiki.org/tiki-index.php?page=2007-07-18+IRC+MediaWiki+discussion&highlight=creole
http://tiki.org/RFCWiki


Related:
*[wish1531|Wiki markup for icons]
*[wish1805|Universal Wiki Edit Button]
*[wish2102|Support some of the MediaWiki syntax that doesn't conflict with TikiWiki syntax]
*[wish1843|Infoboxes like MediaWiki/Wikipedia, but making use of trackers to be future-proof]
*[wish1220|MediaWiki import script]

Please go to "Syntax Examples" here:
http://www.wikimatrix.org/compare/TikiWiki-CMS-Groupware+MediaWiki

Please also see:
http://meta.wikimedia.org/wiki/Help:Wikitext_examples

Some syntax could be supported as it doesn't really conflict with the existing.

__Basic formatting markup__
{img src=images/code.png}%%% {CODE()}
You can ''italicize text'' by putting 2 apostrophes on each side.

3 apostrophes will '''embolden the text'''.

5 apostrophes will '''embolden''' and ''italicize''
'''''the text'''''.
{CODE}


__Signature/timestamp__
{img src=images/code.png}%%% {CODE()} You should "sign" your comments
on talk pages:
- Three tildes gives your
signature: ~~~
- Four tildes give your
signature plus date/time: ~~~~
- Five tildes gives the
date/time alone: ~~~~~ {CODE}

__Section headings__
{img src=images/code.png}%%% {CODE()} == Section headings ==

''Headings'' organize your writing into
sections.
The ''Wiki'' <u>ab</u>
##software can automatically
generate a [[table of contents]] from them.

=== Subsection ===
Using more "equals" (=) signs creates a subsection.

==== A smaller subsection ====

Don't skip levels,
like from two to four equals signs.

Start with 2 equals signs not 1
because 1 creates H1 tags
which should be reserved for page title. {CODE}


However, links & images could be more problematic.

Related:
*[wish1531|Wiki markup for icons]
*[wish1191|Wiki editing: Preview with diff, like Mediawiki]
*[wish1843|Infoboxes like MediaWiki/Wikipedia, but making use of trackers to be future-proof]
*[wish1781|Support for the Wiki creole markup (syntax)]
*[wish1220|MediaWiki import script]

It will be nice to allow the setting of limit of levels to show for maketoc:
{CODE()}
{maketoc maxlevel=2}
{CODE}
will cause only ! and !! headers to be shown, not !!!.

Syntax that should work inside a description term (the x in ";x:y") don't. This includes anything in a ':' in it even if it's nested within another syntax structure like a link or table. In a link, it's especially bad, since you can't use ~np~~np~~/np~ to fix it, e.g. you can't fix ~np~((a:b))~/np~. Also, ~np~~~color:x~~~/np~ doesn't work.

~pp~
!!!~np~;a:text~/np~
;a:text
works
%%%%%%%%%%%%
!!!~np~;~~red:a~~:text~/np~
;~~red:a~~:text
looks like ~np~;a:text~/np~
%%%%%%%%%%%%
!!!~np~;((a)):text~/np~
;((a)):text
works
%%%%%%%%%%%%
!!!~np~;((a:b)):text~/np~
;((a:b)):text
looks like ~np~;a:((a:b|b)):text~/np~
%%%%%%%%%%%%
!!!~np~;((a|b:c)):text~/np~
;((a|b:c)):text
looks like ~np~;b:((a|c)):text~/np~
%%%%%%%%%%%%
!!!~np~;((a|~np~b:c~/np~~/np~~np~)):text~/np~
;((a|~np~b:c~/np~)):text
works
%%%%%%%%%%%%
!!!~np~;__a__:text~/np~
;__a__:text
works
%%%%%%%%%%%%
!!!~np~;||a||:text~/np~
;||a||:text
works
%%%%%%%%%%%%
!!!~np~;||a:b||:text~/np~
;||a:b||:text
this just looks strange
~/pp~

I looked in the parser code, and it's pretty obvious why these bugs occur. The parser code, to put it bluntly, sucks. It uses regexps for most parsing instead of a proper context-free parser, so it's bound to have these types of bugs.

I'm trying to create a Content Template that indicates intention to use markdown, like shown on this page (for example): [https://markdownthemes.tiki.org/tiki-pagehistory.php?page=Markdown+Plain&source=0]
After I put the following code at the top of that Template
{CODE(theme="default")}{syntax type=markdown}{CODE}
and then Save the template, this code disappears after I re-open for editing.
If the template is used in a Wiki Page, the above code is also invisible.
Unfortunately, the content of the template only shows as a binary blob in the database, so it can't be edited directly and cleaned up.

t.o: page alias feature not working because some duplication exists (not prevented at edition time and feedback gone too quickly)

Reproduced here:
https://tiki.org/Community+Servers

alias added at the bottom was:
{CODE(colors="tiki")}
(alias(Servers))
{CODE}

When saving the page, some remarksbox is shown for less than a second reporting some duplication of the alias link, and the page is saved removing that remarksbox with the info. And I can't find where else in the t.o site that alias name is written.

Searching for "alias(Server" didn't bring the other page but dozens of pages.

In Tiki12, if I recall properly, if an alias link existed, you were not allowed to save your page, and you were told where that alias name was used already, so that you could at least go there and the duplication by hand before saving your page.

Table editor in wiki edit doesn't open anymore. It did work as expected in 15.x and 16.x

Page contents with this table here (even after updating 17.x to use svn r63071):
http://aspb.llavorspac.org/ASPB+Vehicles

However, I can't reproduce in the show.t.o instance, I don't know why. {sign user="xavi" datetime="2017-06-25T19:20:07+00:00"}

The TOC gets populated with some headings from plugins like trackerlist (probably should not as it seems to appear on wrong position at the top of the TOC).
---
affecting autotoc and standard maketoc, also in Tiki15. {sign user="xavi" datetime="2016-05-20T09:48:34+00:00"}

Well explained here:
http://twiki.org/cgi-bin/view/Plugins/ActionTrackerPlugin

We'd output in htask microformat
http://microformats.org/wiki/htask

And we'd need some sort of reporting. All tasks assigned to person X.

We currently usually do this with ((doc:trackers)). But doing it fully in the wiki would be more flexible in some contexts.

The system should be able to send email reminders at a certain date. This could be used as well to schedule actions / Email reminders as explained here:
http://www.youtube.com/watch?v=8XwyhSEqTs0

This is part of what is needed for ((Project management))

Similar to ((doc:PluginAnnotation)) for images.

This would make it easier for people to know who added what comment, when and to distinguish the main content, from notes.

Similar to ((doc:PluginMouseOver)), but should be easier to use.

Related:
{wish id=1409}

I have an issue where if I add the section heading toggle e.g. !-# or !+#, then they are lost after the next edit.

To replicate:

1. Create a new wiki page with a number of headings, toggle syntax and text. E.g. !-#Section 1, !-Section 2, etc.
2. Save and all is ok.
3. Edit page again.

When i go to source, all toggle tokens are missing from source e.g. + and - are removed from heading code. e.g. !-# is now !#

__Tikiwiki__ V6.1
__Firefox:__ 3.6.13

Using the "Colored Text" specifier in a Wiki link specifier like this:

~np~((Second Deletion List|~~red:__Unix Shared ID Deletion 2__~~))~/np~

results in the ~np~<SPAN>~/np~ tag being revealed instead of presenting text colored as specified. While not a critical item, we have just upgraded a site that has smattering of these throughout. It did work at one time obviously or they wouldn't be there now.

The link does still work and is not effected.

--Steve

The change text colour palette is blank:

{img type="fileId" fileId="483" thumb="y" noDrawIcon="n"}

Tested on the instance and confirmed.


~~#F00:Update:~~ Fixed on 48335. {sign user="Bsfez" datetime="2013-11-05T07:25:28+00:00"}

The text area is shown sometimes as hidden, when I open the page:
https://dev.tiki.org/tiki-editpage.php?page=Regressions+in+11x

(as user xavi, with admin rights).

Each time I open it again in a another browser program, then the page loads fine.
Codemirror is on in dev.t.o, but with highlighter mode set to "off but switchable".

This happens to me in either firefox or chromium, in several different computers (all of them with gnu/linux, in case this matters)

TW50B1 does not replace the {{itemId}} {{page}} {{user}}. I just displays all these without touching them.
See last section of
http://doc.tikiwiki.org/Advanced+Wiki+Syntax+usage+examples&structure=Documentation
which describes what should happen.

In certain instances when editing a page through the text editor (or creating a new blog post), with the wysiwyg-available available (though hidden) the smilies field is not displayed.

The problem is probably due to the fact that the variable $wysiwyg contains an 'n' if the editor is hidden while in some instances the value is NULL. This is probably because if the wysiwyg feature in admin-features is disabled then the $wysiwyg value is NULL, but if it is enabled but hidden the value is 'n'.

There is a conditional in templates/tiki-editpage.tpl that does not take this into account.

(The problem may be present in other versions as well)

{syntax type="tiki" editor="plain"}
Any occurrence of the string "<link" in a plugin of any case (for example, within a CODE block) is being replaced by the string "<link" (note case conversion) before being passed to the plugin as $data.

{syntax type="tiki" editor="plain"}
Hello Devs,

I did upgrade a site to 7.1 this weekend.

Using WYSIWYG/CKE I have the following prblem:

In some features of the Tiki 7.1 the output the editor is just the plain
HTML Source.

That means, not in Wikipages, but in the articles and in the calendar
events, there is not a nice text with formatting bold, italic, colors
and pictures etc, but only the plain HTML source code visible to the
website user/visitor.

The WYSIWYG/CKE editor works normal and I can see the content just
normal like ever, being in the editing mode. But when I save, I can just
see the source code, like it would be in codeplugin.

This affects as said articles and calendar (perhabs more, I will hope to
find out) but it does not affect wikipages by now.

And it affects existing articles and events aswell as newly edited.

(worked well in 6.x before)

Thx for reply and wish a nice sunday to all,
cheers
Torsten

See https://nextdev.tiki.org/File-a-bug

A backslash followed by 00 between non-parsing pre-formatted commands worked previously in tiki 1.8.5 but caused fatal memory errors / blank pages (even after memory increase to 64M) in tiki 1.9.2

Below is the exact line that caused the problem.
~pp~
#1 0x08071f28 in MJobSelectClass (J=0xd225858, ModifyJob=1 '\001', ModifyRM=1 '\001',
~/pp~

It is great that TikiWiki allows an administrator to customize the Custom Header of a given Website. This allows more personalization than the out of the box "Powered by TikiWiki" logo.

To extend this flexibility, it would be great if one could reference Wiki plugins - custom-built or native Tiki - in the header. As an example, a {RANDOMQUOTE} plugin similar to the simple PHP function on the attached page

http://php.about.com/od/finishedphp1/p/random_quote.htm

I know Christmas is a way's away, but this would be a great early gift!

When a wiki syntax field calls maketoc and the FADE plugin, the table of contents generated may contain bogus entries at the beginning. All the titles in the body of any call to FADE are taken into consideration by maketoc.

This bug is very similar to {wish id=5496}.

! Example

With the following field content, the TOC contains 2 headers, instead of just "Normal header":
{CODE(color="tiki")}
{maketoc}

! Normal header
This is a test page for the FADE plugin.

{FADE(label=Label)}
!! Header which should not be in the TOC
Lorem ipsum...
{FADE}
{CODE}

section_comments_parse does turn off wikisyntax in the comments, however, the editwiki_toolbar is still present

When using the TRACKER plugin with Tiki 2.2:
*I created a new tracker.
*In the tracker's description, I enabled the "Wiki parsed" option and included wiki syntax in the description.
*On a wiki page, I added the tracker with the TRACKER plugin
*I set the __showdesc=y__ option.

The description appeared, but was not wiki parsed.

This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers))