Category: Wiki Plugin (extends basic syntax)

I discovered an error in the PluginMatcher.php, which parses text of a wikipage and searches for opening and closing tags. Saving a file with these tags often gave the known error:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 77 bytes) in /usr/local/httpd/htdocs/tiki-6.2/lib/core/WikiParser/PluginMatcher.php on line 69

Looking at the size of the wiki-page (which was quite small), the problem was not in the memory_limit size in php.ini, which was set to 64MB.

Closing tags could not always be found (when it contained a nested tag), such that a cascade occurred (due to the recursive function call), resulting in an enormous amount of memory-use.

{syntax type="tiki" editor="plain"}
When you go to https://dev.tiki.org/Wishlist and first remove the "Open" status from the "Status:" field and then click to sort the results column by "Modified" you get an error 403 and feedback in a remarksbox:

{CODE()}Oops trackerId parameter must be present <!--//--><![CDATA[//><!-- // js 0 window.elementPlus = {"select":{"enabled":true,"clearable":true,"collapseTags":true,"maxCollapseTags":3,"filterable":true,"allowCreate":false,"ordering":true},"autocomplete":true}; //--><!]]>{CODE}

{img src="display3244" thumb="box"}

The preference "Except included plugins" no longer appears to work. Put another way, plugins listed in the preference are not indexed.

After clicking on the save button on a modal the user is redirected to the page "undefined".
This happen since Tiki21 and it is working fine in Tiki20.

Tested on : tiki-21.0.RC1

To reproduce:
#Login as Admin
#Enable trackers and button plugin
# Create a tracker with a few fields (in the fade I pasted the export for the tracker and the fields)
+ {FADE(label="Tracker export")}
[TRACKER]
adminOnlyViewEditItem = n
autoAssignCreatorGroup = n
autoAssignCreatorGroupDefault = n
autoAssignGroupItem = n
autoCopyGroup = n
autoCreateCategories = n
autoCreateGroup = n
defaultOrderDir = asc
defaultOrderKey = -1
defaultStatus = o
doNotShowEmptyField = n
fieldPrefix = contact
newItemStatus = o
oneUserItem = n
orderAttachments = created,hits,filesize
publishRSS = n
ratingOptions = -2,-1,0,1,2
saveAndComment = n
sectionFormat = flat
showAttachments = n
showComments = n
showCreated = n
showCreatedBy = n
showCreatedView = n
showLastComment = n
showLastModif = n
showLastModifBy = n
showLastModifView = n
showRatings = n
showStatus = n
showStatusAdminOnly = n
simpleEmail = n
useAttachments = n
useComments = n
useFormClasses = n
useRatings = n
userCanSeeOwn = n
userCanTakeOwnership = n
writerCanModify = n
writerCanRemove = n
writerGroupCanModify = n
writerGroupCanRemove = n
trackerId = 1
name = Contact
descriptionIsParsed = n
created = 1584087369
lastModif = 1584087369
{FADE}
+{FADE(label="Field Export")}
[FIELD1]
fieldId = 1
name = Name
permName = contactName
position = 10
type = t
options =
isMain = y
isTblVisible = y
isSearchable = n
isPublic = y
isHidden = n
isMandatory = y
description =
descriptionIsParsed = n
[FIELD2]
fieldId = 2
name = Country
permName = contactCountry
position = 20
type = y
options =
isMain = n
isTblVisible = n
isSearchable = n
isPublic = y
isHidden = n
isMandatory = n
description =
descriptionIsParsed = n
[FIELD3]
fieldId = 3
name = Date
permName = contactDate
position = 30
type = j
options =
isMain = n
isTblVisible = n
isSearchable = n
isPublic = y
isHidden = n
isMandatory = n
description =
descriptionIsParsed = n
[FIELD4]
fieldId = 4
name = Image
permName = contactImage
position = 40
type = FG
options = {"galleryId":0,"filter":"","count":0,"displayMode":"","displayParams":"","displayParamsForLists":"","displayOrder":"","deepGallerySearch":0,"replace":"n","browseGalleryId":0,"duplicateGalleryId":0,"indexGeometry":"","uploadInModal":"y","image_x":"","image_y":"","addDecriptionOnUpload":"n","requireTitle":"n"}
isMain = n
isTblVisible = n
isSearchable = n
isPublic = y
isHidden = n
isMandatory = n
description =
descriptionIsParsed = n
{FADE}
# Populate the tracker with a few items
# Edit a page and create a pluginList with an edit button
+ In my sample I used a table output __with fixed values for editing the item 1 only__ (pasted below)
+ I tested with a link and a button to be sure
+{FADE(label="PluginList content")}
{LIST()}
{filter field="tracker_id" content="1"}
{pagination max="1"}
{OUTPUT(template="table")}
{column field="reference_1" label="Name"}
{column field="reference_2" label="Country" mode=raw}
{column field="reference_3" label="Date"}
{column field="reference_4" label="Photo" mode=raw}
{column field="reference_5" label="link" mode=raw}
{column field="reference_6" label="button" mode=raw}
{OUTPUT}
{FORMAT(name="reference_1")}{display name="tracker_field_contactName"}{FORMAT}
{FORMAT(name="reference_2")}{display name="tracker_field_contactCountry" format=trackerrender}{FORMAT}
{FORMAT(name="reference_3")}{display name="tracker_field_contactDate" format=date}{FORMAT}
{FORMAT(name="reference_4")}{display name="tracker_field_contactImage" format=trackerrender}{FORMAT}
{FORMAT(name="reference_5")}<a href="tiki-tracker-update_item?trackerId=1&itemId=1&modal=1" class="btn btn-primary text-white click-modal">Edit</a>{FORMAT}
{FORMAT(name="reference_6")}{button href="tiki-tracker-update_item?trackerId=1&itemId=1&modal=1" _icon_name="edit" _class="btn btn-success text-white click-modal"}{FORMAT}
{LIST}
{FADE}

Your page should end with something like this:
{img fileId="1385" thumb="box"}

When you click on the link or the button you will have the "Update Item" modal.
*Close will bring back to the page (~~#090:GOOD~~)
*Preview won’t do nothing (~~#F90:I think it shouldn’t be here~~ don’t see how it will be used)
*Save will save but redirect the user to an "undefined" page (~~#F00:BROKEN~~)
+{img fileId="1386" thumb="box"}
+ Video : https://share.vidyard.com/watch/UCAew92XGPH4zHUQ3G2QbG?

Saving used to redirect to the page, same list, same result (if customSearch) in Tiki20.
Here a Tiki20 (using smarty template) with the same code for the button:
https://share.vidyard.com/watch/w8zwARp8C3X1aB4xFSiyma?

If you access https://dev.tiki.org/Tiki20#Open_or_Pending_Blockers_and_Regressions , there's a button to Expand that Table. It doesn't work, as it used to until a few days ago. So navigation in the table becomes very difficult. If you turn off jqDoubleScroll then the feature works fine.
{img fileId="1298" thumb="box"}

Plugin TrackerIf doesn't seem to accept nesting so far, and we need it to allow customization of the interface to edit data with Pretty Trackers.

*If field_1 is A
** if field_2 is not empty, display value of field_2
** if field_3 is not empty, display value of field_3
** if field_4 is not empty, display value of field_4
** ...
* if field_1 is B
** if field_10 is not empty, display value of field_10
** if field_11 is not empty, display value of field_11
** if field_12 is not empty, display value of field_12
** ...

{CODE(ln="1")}
{TRACKERIF(test="(f_1='A')", ignore='n')}
{TRACKERIF(test="(f_2 ='')", ignore='n')} {ELSE} {$f_2|output} {TRACKERIF}
{TRACKERIF(test="(f_3 ='')", ignore='n')} {ELSE} {$f_3|output} {TRACKERIF}
{TRACKERIF(test="(f_4 ='')", ignore='n')} {ELSE} {$f_4|output} {TRACKERIF}
{TRACKERIF}
{TRACKERIF(test="(f_1='B')", ignore='n')}
{TRACKERIF(test="(f_10 ='')", ignore='n')} {ELSE} {$f_10|output} {TRACKERIF}
{TRACKERIF(test="(f_11 ='')", ignore='n')} {ELSE} {$f_11|output} {TRACKERIF}
{TRACKERIF(test="(f_12 ='')", ignore='n')} {ELSE} {$f_12|output} {TRACKERIF}
{TRACKERIF}
{CODE}

Say I need to make a link such as:
{img src=images/code.png}%%% {CODE()}
[http://en.wikipedia.org/wiki/Argument_map|Argument map]
{CODE}

I could use an ((doc:external wiki)) link which is like this:

{img src=images/code.png}%%% {CODE()}
((wp:Argument map))
{CODE}

Even nicer would be an image (instead of {img src=img/icons/external_link.gif}) so the visitor knows he'll be sent to Wikipedia.

Also, would need:
*optional title: to explain what this site is about. (ex.: this is a sister community)
*option to open new window
these would be set centrally and you could override.


Perhaps the direction to take is to build with ((doc:plugin alias))

In my localhost trunk installations, I'm finding an extra period (.) appended to each footnote. This is true for pre-existing footnotes and newly added ones. I want to make a show instance to check trunk on another server.

When a page which calls the FADE plugin is printed via tiki-print.php, the call's body is not printed by default. To print the content in my Tiki 18 and 19 installs, once I am in tiki-print.php or tiki-print_article.php, I must cancel the automatic printing, click on the label, and then have the browser print. Having revealed from tiki-index.php does not suffice.

It is arguable how much of a bug this constitutes, but the fact the hidden content is quietly hidden when printing is in my opinion already a problem. I believe if the content is not printed, there should at least be a warning displayed, and ideally an offer to reveal hidden zones ("This page contains hidden zones. Should the content of these zones be printed?").

The current way to reveal the zones - to click in tiki-print.php - is very strange, since one would not expect tiki-print.php to be interactive.

New fade plugin is cool.
http://doc.tikiwiki.org/PluginFade

#If body is empty, plugin should not be clickable
#However, if there are line breaks in the body, the are no longer in the fade.
#Also, should have a setting, default to y for little icons:
{img src=images/code.png}%%% {CODE()}
[-] [+]
{CODE}

This is a huge problem

Not easy to solve. Would need ((WikiParser)) work?

Some phantom prefs are introduced in each version of Tiki, as devs add/change prefs but don't notice this. So before each major release (ex.: from 11.0 to 12.0, but not from 12.0 to 12.1), a complete check needs to be done, for all admin panels.

# Start with a fresh install (this is important because some of these issues could only happen once)
# Visit tiki-admin.php
# Activate all Preference Filters (Basic, Advanced, etc.)
# For each of the approx 50 panels on tiki-admin.php
## Activate or deactivate any checkbox (any pref really) on the page (only one per URL, no need to do it per tab).
## Confirm that the pref change is reported.
## If any ''other'' pref change is reported, figure out why and resolve.

I failed to produce this with fancytable:
||Item|Amount|Price per item|Total
Apple|3|1|3
Banana|2|3|6
|sum| | 9||

It's a common usecase, Excel solves this with SumProduct.

Or is it actually possible to solve this with the current implementation??

As of this morning 4/18/2011, fancytable and code plugins display their HTML.

See http://screencast.com/t/ZWJii6Abl for a screen shot.

I question revs 34013 and 34014

When the TRACKERITEMFIELD plugin is called trying to access a tracker item which does not exist, a fatal error like the following occurs:
{CODE()}
Fatal error: Call to a member function getConfiguration() on boolean in C:\xampp\htdocs\tiki\18\lib\core\Tracker\Item.php on line 200
Call Stack
# Time Memory Function Location
1 0.2009 192464 {main}( ) ..\route.php:0
2 0.2617 4607672 include( 'C:\xampp\htdocs\tiki\18\tiki-index.php' ) ..\route.php:306
3 0.5479 18560680 Tiki_Render_Lazy->__toString( ) ..\route.php:645
4 0.5479 18560712 call_user_func:{C:\xampp\htdocs\tiki\18\lib\core\Tiki\Render\Lazy.php:22} ( object(Closure)[521] ) ..\Lazy.php:22
5 0.5479 18560752 WikiRenderer->{closure:C:\xampp\htdocs\tiki\18\lib\wiki\renderlib.php:346-356}( ) ..\Lazy.php:22
6 0.5480 18560984 WikiLib->get_parse( string(16), bool, ??? ) ..\renderlib.php:349
7 0.5484 18565728 WikiLibOutput->__construct( array(34), string(58), array(3), string(1) ) ..\wikilib.php:802
8 0.5484 18566056 ParserLib->parse_data( string(58), array(3) ) ..\wikilib.php:2155
9 0.5485 18568760 ParserLib->parse_first( string(58), array(2), array(2), ??? ) ..\parserlib.php:1667
10 0.5537 18774536 ParserLib->plugin_execute( string(16), string(0), array(3), long, bool, ??? ) ..\parserlib.php:439
11 0.5562 18785784 wikiplugin_trackeritemfield( string(0), array(3), long ) ..\parserlib.php:1031
12 0.5670 20145512 Tracker_Item->canView( ) ..\wikiplugin_trackeritemfield.php:193
13 0.5670 20145664 Tracker_Item->canSeeOwn( ) ..\Item.php:88
{CODE}

Objects which contain such calls cannot be viewed, and reindexing for search is also broken.

This happens since {commit id=37583} and persists in trunk r68584.

There was a question in the forum (by freeman57) about how to let users use their webcams to record a video to insert in a wiki page, etc. After checking around, I came across a plugin for Wordpress that does this, using Kultura: [http://wordpress.org/extend/plugins/all-in-one-video-pack/]. It would be great if someone could do a Tiki version, or equivalent, of this plugin. There doesn't seem to be any installation needed in the server except for the plugin files.

Actually I think just a subset of what's in the Wordpress plugin would be needed. That plugin includes other video and audio display options along with a TinyMCE install, which wouldn't be needed for Tiki.

This would be a nice additional feature for sites and users and would tie in well with Kultura integration.

in plugin trackerlist and plugin trackerfilter (and maybe some others also) the filter fields is really ugly, mainly because the colon ":" is often displayed in a own line, ripping apart the field name and the filter field.

Well, just look at the screenshot, it's obvious.

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

{syntax type="tiki" editor="plain"}
{img fileId="3052" thumb="box"}
{img fileId="3053" thumb="box"}

Field selection is also not working when setting a tracker wikiplugin in a smarty template
{CODE()}
{wikiplugin _name=tracker trackerId="1" fields="3:4:5" tpl="contactForm.tpl" showmandatory="n"}{/wikiplugin}
{CODE}

In 2.0, Flash files (.flv) stored in the file directory don't play with the FLASH wikiplugin. The movie source url, etc., look ok in the page source, but still nothing displays. File gallery Flash files work with the FLOWPLAYER plugin, though.

The general translation behaviour for Tiki features is to allow translations of titles and other labels.
Page title, trackers (title, field names), categories and eventually to allow wiki syntax that allow the admin to set TR tags where it is needed (tracker description, wiki page content, etc...).
But not for Tiki file gallery. ??‍♂️

The translation of term(s) is found in tiki lang/../language.php or lang/../custom.php

Following the discussion in the comments the conclusion is:
1/ There are reasons for this as it may be unwanted to automatically translate terms of a file title (file name on import if none is specified).

2/ To allow translation of file title and file description it will made sense and easier to do it at the wiki plugin level, something like:
{CODE()}
{file type="gallery" fileId="1225" browserdisplay="y" translatetitle="y"}
{CODE}

There is no option to display the file description using the plugin and it is not necessary to add one.

Using Tiki I upload a file and I want to place it in a specific gallery.
Next time I upload a file, I want to "remember" where I uploaded.

Use case; For this tracker I use the img plugin.
# Click on the icon
# Click on the browse gallery icon
# On the explorer path => bug report => bsfez
# Click the upload button
# Drag the file (automatic upload)
# Insert the syntax on the item

Such a simple action than adding an image to an item = 6 clicks !!!
If we didn't used Explorer path and if automatic upload wasn't check it would have been 9 clicks !!!

Video added: {file type="gallery" fileId="2043" showicon="y"}

Features would be:

*Ability to select how many rows/columns for presentation
*Embeds photo, flash or just a link based on file type
*Clicking the image or link starts download of the file (if allowed)
*Ability to view full size image
*Ability to open a slide show

Would include last comments to each file. Related:
Comments to individual files in file gallery
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=719

After a basic PluginListExecute with editable filters, once we submit an action, we are redirected to the page where all filters are duplicated. See GIF below:

https://cl.ly/0698c9a23f29

Spreadsheets can be created directly through wiki SHEET plugin directly within wiki pages. this allows managing big tables visually, as well as having the data ready for producing graphs, etc. (see documentation for tikisheets at doc.tw.o, if needed)

However, when you create a sheet through a call to the SHEET plugin from the wiki page itself, there are 3 issues which need to be fixed:
# you need to know the id you want to assign it to,
# after that, tiki-sheets.php doesn't list it (even if the sheet is really created, and you can import data to it, and show it at the wiki pages, etc.).
# the sheet is not shown with the right css

Even if we have wysiwyg option available, I still think that is worth improving tiki sheets usability to be used directly from wiki pages, once those 3 previous issues are fixed.
---
Updated on Feb. 2, 2011, using trunk (7svn)
# Steps to reproduce the first issue
## Edit a wiki page
## Use the plugin helper to create a new sheet in that page. And since it's a new sheet, it doesn't have a sheetId yet, so that you leave all fields empty in the plugin helper for the pluginsheet
++ this will add this type of code in your wiki page:
++ {CODE()}{sheet}{CODE}
## Save the wiki page
++ you will see an empty sheet shown in place at that wiki page, with the button at the bottom to allow the user to "edit it" (so far, so good)
## Once you click in the edit sheet button, you end up in some url like this one:
++ http://localhost/tiki7trunk/tiki-view_sheets.php?sheetId=&parse=edit
++ which produces a WSOD (blank page).
*** In my case, I guess that this url should have been:
+++ http://localhost/tiki7trunk/tiki-view_sheets.php?sheetId=2&parse=edit
+++ since I had only one sheet previously created, with sheetId 1, so that the next one should be 2. However, this new url is still producing WSOD for me. (tiki caches cleared, just in case, repeated this step, and same WSOD)

The expected behavior is that the user is the user would be editing a blank new sheet with the url:
http://localhost/tiki7trunk/tiki-view_sheets.php?sheetId=2&parse=edit

and when the user saves that sheet, the new sheetId 2 exists, and the user is either sent back to the wiki page where he clicked at the button "edit sheet" (preferable option) or either sent to the corresponding tiki view sheet 2.

When a wiki page displays flash content through the flash wikiplugin, phplayers menus will appear under the flash content. This will happen even if the z-index property is properly set, because Flash renders on top of all DHTML layers.