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

It should get 1.1 but it is omitted for the first heading section on the page, e.g.:
{CODE()}!!# Introduction - A Historical Context{CODE}
on the https://dev.tiki.org/Hello-World

Or you can see the bug here:
https://tiki.org/201911-TAG-Meeting
(the "Who" section should have 1.1)

Anchors are seriously screwed up in Tiki. There are a couple of issues. I've dug into the subject thoroughly and summarized my findings here:

http://volker-wysk.de/tiki/Anchors%20in%20Tiki.html

When URL is entered in a parenthesis it takes the closing one and includes it in the external link:

(E.g. Google -- https://google.com/)

The expected result would be that the ")" is not included as part of the link.

With a simple wiki page that uses the standard wiki editor the drop down menus for font colours and background colours are blank.

Occurs in 12.x at r49095

The editor settings when this occurs are:
Full WYSIWYG editor
BUT Wiki syntax is NOT used
Content is parsed like a wiki page

A show instance has been created which shows this bug/regression

fixed commit id=49334 - thanks jonny

A blank line out of a paragraph should not start a new paragraph (as in 4.2). If feature_wiki_paragraph_formatting_add_br is on, an empty line is created on top of the new paragraph.
It comes from lib/tikilib.php line 6838ff
} elseif (!$in_paragraph && !$contains_block) {
// If not in paragraph, first non-blank line; start a paragraph; if not start of div created by plugins
$data .= "<p>";
...

in the comment it is stated that the paragraph should only begin at first NON-BLANK line

The Full Screen edit button is visible in my quicktags list, even though I have the __Allow fullscreen edit__ option disabled.

Like Wikipedia



In a more advanced form, the references could be kept in trackers, as Tiki would be a
[http://info.tikiwiki.org/Use+Cases#Bibliography_D_|Bibliography Management System].


Related:
[wish1769|Bibliography management system (references)]

This is an RSS feed:
http://sourceforge.net/export/rss2_projsummary.php?group_id=64258


It's not the traditional way of using RSS but it can be very useful :-) It permits us to get up to date info (Ex.: number of devs, number of downloads, etc.) from SourceForge, using RSS. We can then publish on http://info.tikiwiki.org/



This idea could be used for serving ads.
http://en.wikipedia.org/wiki/Ad_serving

This is also in the same idea as:
http://dev.tikiwiki.org/Connect
http://tikiwiki.org/Viral+Tiki

Two immediate uses
# Manage the footer of all *.tikiwiki.org sites from one place
# Permit to push news & calls to action (Current version of Tiki, vote for Tiki in an Award, new release, etc)


Tiki5 as of now:
http://tikiwiki.org/tiki-index_raw.php?page=rsstest

Tiki4 as of now:
http://info.tikiwiki.org/tiki-index_raw.php?page=DeployWikiPageContentAsRSS



Related
{wish id=1396}

Not totally sure if this is feature request, bug, or lack of knowledge. Basically I need some way of supporting maketoc with WYSIWYG pages.

~np~When using three hyphens (---) you get a horizontal rule in v3.0 Beta 3, but if you use more than three hyphens (i.e. ---- ----- or ---------), you will not get a horizontal rule on the page. Greater than three hyphens was valid in version 2.x of TikiWiki to create a horizontal rule.~/np~

I got a strange problem when writing a text in square brackets (in trunk):

~np~[[These brackets] should stay~/np~

should result in the output
~np~[These brackets] should stay~/np~
but they produce
~np~<a class="wiki" href="These brackets" rel="">These brackets</a> should stay~/np~
It works as expected in 5.0

Since Tiki 19, a collapsible section (generated with a heading that starts with a minus or plus sign, [https://doc.tiki.org/tiki-index.php?page=Wiki%20Syntax#Quick_reference_-_basic_text_formatting|as documented]) effectively ends at the first heading of the same level or above in the pages it includes (with the INCLUDE plugin).

For example, if page Parent has {CODE(caption="this code" colors="tiki" theme="default")}!Section 1
Direct content

!+Collapsed section
Direct content
{include page="Help"}

! Last section
Direct content{CODE}

...while page Help has{CODE(caption="the following source" colors="tiki" theme="default")}!For Support Please Contact

support@company.com
(555) 123-4567{CODE}
...then the "For Support Please Contact" section always shows, regardless of the toggle control's state. Clicking on "+" only reveals "Direct content".


I am categorizing this ticket in Bug::Regression because this is a regression, but this is arguably not a bug.

This issue is a regression from {commit id=66644} and therefore affects Tiki 19. That commit essentially reverted {commit id=48937} (2013-12-03, on the Tiki 12 branch), so Tiki 11 and before also have the same issue.

Note that this is the second back-and-forth on this, after {commit id=29321} was reverted by {commit id=33993}.

When creating a horizontal rule previous version of Tiki wiki 2.x allow you to use multiple hyphens (>3).

~np~i.e. "---------------" in 2.x version would produce the same horizonttal rule as: "---"~/np~

~np~In 3.0 Beta 3 the only valid horizontal rule creator is three hyphens (---), not more than three hyphens.~/np~

Using H5P Collage, when the file is inserted into page using for example:

{CODE(theme="default")}{h5p fileId="32"}{CODE}

The collage looks fine, but when the page is cached, the images fly out of the constrained area and convert to full size images.

Please see show instance.

{syntax type="tiki" editor="plain"}
I try to submit a wiki page with html text.
The submit never finish and I have a message :

Fatal error: require_once() [function.require]: Failed opening required 'lib/htmlpurifier/HTMLPurifier.auto.php' (include_path='/htdocs/public/www/lib/pear:.:/usr/local/lib/php:/htdocs/public/www/lib/core/lib:/htdocs/public/www/') in /htdocs/public/www/lib/htmlpurifier_tiki/HTMLPurifier.tiki.php on line 19

I don't understand because all php page are ok.

Compare https://themes.tiki.org/Shapely and https://nextthemes.dev9.evoludata.com/Shapely . The page uses the trackerlist plugin to display theme information but at the nextthemes site the source is displaying, including HTML syntax, etc.

HTML is turned on for wiki pages and is on for the Shapely page.

This problem doesn't happen at all Tiki master (upcoming Tiki 25) sites, though.

There are --2-- 1 issue--s-- of icons alignment for ISO (safari) you can see at https://tiki.org/Wishlist-Triage-Team

* social network alignment
* --translation action button--

{img fileId="1623" thumb="box"}

{img fileId="1624" thumb="box"}

You may need to be logged in to see the issue.

~~#F00:Update~~ : The translation icon I now properly aligned on Safari.

just like this ((text中文))

it can't be parsed correctly as a page referer.

{syntax type="tiki" editor="plain"}
If you click on an Edit Section button, the Switch Editor button is not available when you are editing.

__ Describe precisely what you did (how to reproduce).__
I attempted to place images with captions side by side in a wiki page, with the params as:

{CODE()}{img type="fileId" fileId="id" thumb="box" desc="Test Caption" responsive="n"} {img type="fileId" fileId="id" thumb="box" desc="Test Caption" responsive="n"}{CODE}

__ Describe exactly the faulty consequences.__
When images are placed side by side, with as thumb, responsive n, and caption added, they will not place side by side, but will only place over and under.

__ Explain what you expected instead of the faulty consequences. __
I expected to view the images side by side, with captions below the images.

Tiki's wiki syntax provides no equivalent of the HTML blockquote tags. Most (if not all) of the major literary stylebooks require that quotations longer than 2 lines be set forth as a separate paragraph indented ''on both sides'' and single spaced. In the judicial setting, this is universally required by court rules.

The [http://tikiwiki.org/tiki-index.php?page=RFCWiki|RFCWiki draft] specifies support for this syntax feature in section 4.13.1 as follows:

A block indent is created by using the minus (-) with the greater character (>) at the beginning of the line. The number of minus characters defines the indentation.

Example:
-> Block indent level 1
--> Block indent level 2

The material quoted above should, of course, be blockquoted. :-)

This may seem surprising, but this is a very important feature to us. We are preparing an integrated free and open source solution for law offices. We want to use Tiki as one foundation of that solution. But legal professionals are going to howl if they can't have their indented quotations.

1. The {include page=“name”} command is tremendously useful for naive wiki users who add content. It lets them create macros and re-use them at will.

So I suggest that this might deserve an alias {macro } and deserve a description in the wiki syntax help.

Also a slight simplification. If there is no ‘page=”name”’ text but there is {macro “name”} then use “name” anyway.

Any user could do {macro “myheader”} at the top and {macro “myfooter”} at the bottom and {macro “myusualrant”} wherever they want. They just have to make an orphan wiki page for each macro they want.

2. This is so useful and flexible that you might deprecate the “apply content template” thing on the Properties tab. It is hardly any easier to use, and it allows the user to choose only one macro at the beginning. It should keep working for the users who have already used it, but there’s no particular reason for anyone to use it again.

3. To really put the icing on the cake, you might let admins have two macros for each user page, one at the top and one at the bottom. These should not be visible when the user edits the page. So for each page category, the admin could decorate it a special way. Some might automatically get polls or other info visible. Or dancing bunnies, or whatever. It lets admins customize user wiki pages without coding, in ways that are hard to do without coding now. Without annoying users with the displayed calls on their edit pages which they might edit wrongly.

No indent
: One indent
:: Two indents

Please see:
http://www.mediawiki.org/wiki/Help:Formatting

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

{syntax type="tiki" editor="plain"}
If I create a table using the WYSIWYG Editor and click on the __Source__ button, the generated code is using HTML code like this:

<table>
<tbody>
<tr>
<td></td>
</tr>
</tbody>
</table>

Instead of the real Wiki Syntax for tables ([http://doc.tiki.org/Wiki-Syntax+Tables]).

I guess a "HTML->Wiki Syntax Translation" setting must be missing.

As an example, I found out a MediaWiki WYSIWYG CKEditor that does this same translation just fine. Maybe you could check out the code:

[http://www.mediawiki.org/wiki/Extension:WYSIWYG|Extension Homepage]
[http://sourceforge.net/projects/halo-extension/files/SMWHalo%201.5.3_b36/MediaWiki%20extensions/wysiwyg-1.4.1_3.zip/download|Download]
[http://smwdemo.ontoprise.com/index.php/WYSIWYG_Sandbox|Online demo]

Thanks a lot!