Loading...
 
Skip to main content

Option: "Content is parsed like wiki page" leads to unwanted problems

  • Tracker item actions
Trackers
Items
Status
Open
Subject
Option: "Content is parsed like wiki page" leads to unwanted problems
Version
14.x
Category
  • Usability
Feature
WYSIWYG (What You See is What You Get)
Resolution status
Partially solved
Submitted by
GriessbreiLP
Lastmod by
Philippe Cloutier
Rating
(0)
Description

If you uncheck the option:
Content is parsed like wiki page

some features of the tiki wiki will not work anymore.


Our case:
We have many code examples where we, for example, have arrays like you have them in javascript with square brackets. ["array"]

When wiki syntax is parsed, the square brackets are interpreted as a wiki link, which is not the case.

The solution:
we solved the problem with the option "Content is parsed like wiki page". We unchecked it, so wiki syntax is not interpreted.

Side effect:
Now, if we try to insert an image from the file gallery, tiki wiki inserts it as a wiki image with the wiki syntax. That won't work, obviously.

Another feature that won't work anymore is the codemirror plugin. The plugin inserts wiki syntax too.

My opinion:
All features that use wiki syntax have to check, if this option is set. If it is not checked, than they have to insert html. I mean, if the file gallery inserts a simple img html tag, it would simply work, the same for codemirror.

Solution

Seems to work for me using one of the following:

  1. No parse tags
    [array]

  2. PluginCode
    Copy to clipboard
    [array]
Importance
9
Easy to solve?
4
Priority
36
Demonstrate Bug on Tiki 19+
Demonstrate Bug (older Tiki versions)
Ticket ID
5732
Created
Wednesday 14 October, 2015 09:08:15 UTC
by GriessbreiLP
LastModif
Friday 05 January, 2018 20:59:43 UTC


Show PHP error messages