Category: Wiki Plugin (extends basic syntax)

Same as the [http://tantannoodles.com/toolkit/photo-album/|Flickr Photo Album for Wordpress], but for tikiwiki.

{syntax type="tiki" editor="plain"}
If you choose to use the flowplayer module, you are required to have Tikiwiki installed in the root of the domain.

ie: http://www.domain.com/tiki/tiki-index.php?page=Bob will not work, while
http://www.domain.com/tiki-index.php?page=Bob will work.

The cause for this seems to be that the lib/wiki-plugins/wikiplugin_flowplayer.php file is hard coded to work from the '/lib/flowplayer/' folder.

(Search words: flowplayer, tikiwiki, broken, no video, blank)

When the FOOTNOTEAREA plugin is called more than once for a single context, footnote numbers are duplicated. For example, if a single wiki page contains 2 footnotes and that each is displayed in its own footnote area, both notes have the number 1. Moreover, clicking on the second footnote reference brings to the first footnote's content.

When a page displays several footnote areas because it contains several objects, it is OK to re-use footnote numbers. For example, if reading a list of articles and 2 articles use footnotes, it would be bad to use different footnote numbers than the numbers which would be used if viewing the articles individually. It is good that each article is displayed with a footnote number 1.

Unfortunately the parser has no idea about context up to Tiki 19. In Tiki 19, the second footnote area displays both footnotes, as in Tiki 16 and below, so the first footnote is duplicated. In Tiki 17 to 18, each footnote is displayed just once, the problem is a conflict between these.

The duplicate footnote detection was lost at some point between Tiki 15 and tiki18.

For example
{CODE(colors="tiki" theme="default")}
Lorem ipsum dolor sit amet, pede reiciendis cras sapien, varius neque consectetuer tincidunt in ipsum, dui nec dis cras.{FOOTNOTE()}Wikipedia contributors. "George Nakashima." Wikipedia, The Free Encyclopedia. Wikipedia, The Free Encyclopedia, 3 Oct. 2017. Web.10 Oct. 2017{FOOTNOTE} Dui dapibus cras ligula, aliquam ligula. Sit eu euismod aliquam orci orci hendrerit, nullam morbi, et cursus, maecenas quisque blandit enim.{FOOTNOTE()}Wikipedia contributors. "George Nakashima." Wikipedia, The Free Encyclopedia. Wikipedia, The Free Encyclopedia, 3 Oct. 2017. Web.10 Oct. 2017{FOOTNOTE} Lacus sagittis dapibus sed, lorem lacus donec, fusce eros arcu rutrum adipiscing eget rutrum.
{CODE}
... displays:
Lorem ipsum dolor sit amet, pede reiciendis cras sapien, varius neque consectetuer tincidunt in ipsum, dui nec dis cras.{FOOTNOTE()}Wikipedia contributors. "George Nakashima." Wikipedia, The Free Encyclopedia. Wikipedia, The Free Encyclopedia, 3 Oct. 2017. Web.10 Oct. 2017{FOOTNOTE} Dui dapibus cras ligula, aliquam ligula. Sit eu euismod aliquam orci orci hendrerit, nullam morbi, et cursus, maecenas quisque blandit enim.{FOOTNOTE()}Wikipedia contributors. "George Nakashima." Wikipedia, The Free Encyclopedia. Wikipedia, The Free Encyclopedia, 3 Oct. 2017. Web.10 Oct. 2017{FOOTNOTE} Lacus sagittis dapibus sed, lorem lacus donec, fusce eros arcu rutrum adipiscing eget rutrum.
---
{footnotearea}
---

While it should be recognised that both footnotes are the same footnote, they show up separately :-(

This is how a lot of users went around the issues of -+sameas+- before -+sameastag+- was intruduced. This regression greaks sites upon upgrading to Tiki18.

The sameas parameter was removed in Tiki 18. Therefore, if one attempts to re-use footnote number x using
{CODE(theme="default")}{footnote sameas="x"}{CODE}
the plugin call will display "Error: Empty footnote" instead of a reference to the existing footnote with the number x.

For example,
{CODE(colors="tiki" theme="default")}
Lorem ipsum dolor sit amet, pede reiciendis cras sapien, varius neque consectetuer tincidunt in ipsum, dui nec dis cras.{FOOTNOTE()}Wikipedia contributors. "George Nakashima." Wikipedia, The Free Encyclopedia. Wikipedia, The Free Encyclopedia, 3 Oct. 2017. Web.10 Oct. 2017{FOOTNOTE} Dui dapibus cras ligula, aliquam ligula. Sit eu euismod aliquam orci orci hendrerit, nullam morbi, et cursus, maecenas quisque blandit enim.{footnote sameas="1"} Lacus sagittis dapibus sed, lorem lacus donec, fusce eros arcu rutrum adipiscing eget rutrum.
{CODE}
... displays:
Lorem ipsum dolor sit amet, pede reiciendis cras sapien, varius neque consectetuer tincidunt in ipsum, dui nec dis cras.{FOOTNOTE()}Wikipedia contributors. "George Nakashima." Wikipedia, The Free Encyclopedia. Wikipedia, The Free Encyclopedia, 3 Oct. 2017. Web.10 Oct. 2017{FOOTNOTE} Dui dapibus cras ligula, aliquam ligula. Sit eu euismod aliquam orci orci hendrerit, nullam morbi, et cursus, maecenas quisque blandit enim.{footnote sameas="1"} Lacus sagittis dapibus sed, lorem lacus donec, fusce eros arcu rutrum adipiscing eget rutrum.
---
{footnotearea}
---
You can also go to this page at https://doc.tiki.org/PluginFootnote and please see the "Would produce" example, the same issue occurs.

In Tiki21 it appears that the ~np~{footnote sameastag="widget"}~/np~ does not function in Tiki21.x
It does function in my Tiki18, I have not tested 19 and 20.

I will create a show instance.

Also you can see the live issue on my wiki at https://thepatriotwoodwiki.org/Glossary-of-Woodworking-Joints

See "Butt" for the original footnote tag, and see "Box" for the sameas tag not functioning.

Using the Footnote UI while editing, I can enter a footnote the first time only during a single editing session. If I try to use the Footnote UI a second time during the same editing session, the UI fails to open.
I have to save the first edit completely, then edit again, and use the Footnote UI to add an additional footnote.

So, the UI will only open once, per editing session.
Bug will be shown on "show instance".

Hello,

Due to the lack of direct support for footnotes in WikiSyntax, I've enabled footnote/footnotearea plugins in 18.2 and 19alpha installations, but it looks that footnotearea plugin is broken in 19.alpha release?

Here is the example code which I used:

{CODE(theme="default")}In Blume's outdated view, the Classic period of music{FOOTNOTE()}Sometimes dated from 1740 to 1828, from when C.P.E. Bach began service in the court of Frederick the Great to when Schubert died. {FOOTNOTE} used rhythm "with the finest nuance and sensibility,"{FOOTNOTE(tag="fblume")}Friedrich Blume, ''Classic and Romantic Music: a Comprehensive Survey'', trans. M.D. Herter Norton (New York: W.W. Norton and Co., Inc., 1970), p. 133.{FOOTNOTE} whereas Schubert and the Romantics often used rhythm in repetitive, stereotyped patterns."{FOOTNOTE()}''Ibid''.{FOOTNOTE} It is now recognized that those features of Schubert's work which give us such pleasure rest on a magnificently concieved and executed sense of tonal architecture.

Duplicate footnotes section:
This is to show examples of the -+sameas+- and -+sameastag+- parameters {FOOTNOTE(sameastag="1")}{FOOTNOTE} {FOOTNOTE(sameastag="fblume")}{FOOTNOTE} and check duplicates {FOOTNOTE()}''Ibid''.{FOOTNOTE} {FOOTNOTE(class="translator")}translator notes{FOOTNOTE} {FOOTNOTE(class="author")}author notes{FOOTNOTE}
%%%
%%%
{footnotearea}{CODE}

This is a regression from {commit id=66043}.

In corner cases, a footnote number in the footnote area will display alone on its line. The beginning of the note itself will go to the next line. There are 2 conditions needed for a footnote to be affected:
#it contains an HTML paragraph (<p>)
#it has a line long enough to wrap, as in the following:
{CODE(caption="Example" colors="tiki" theme="default")}Content{FOOTNOTE()}
Paragraph with at least one really long line which continues, continues, continues, continues, continues, continues, continues, continues, continues, continues, continues, continues, continues, continues, continues, continues, continues, continues...
*Dummy item in a list which makes the preceding paragraph a real paragraph
{FOOTNOTE}
{footnotearea}
{CODE}

This was caused by a switch to parse_data_plugin() in r61394. That being said, the previous situation was already not ideal. The footnote number is inside the horizontal space occupied by the footnote itself (data), so there is no real distinction between the footnote number and some number which would be at the beginning of a footnote. I believe each footnote should be displayed using 2 rectangles with equal height. The content of a footnote should be in a rectangle to the right of a small rectangle containing only the footnote's number. This would match [https://en.wikipedia.org/wiki/Wikipedia#References|Wikipedia's behavior]. wikiplugin_footnotearea.tpl could be modified accordingly, but adopting the HTML used by Wikipedia would require us to change behavior a bit.

At https://tiki.org/Consultants the field type Files, Display Mode = image show ^File not found.^ instead of the format parameter default content (default="" in this case).

{syntax type="tiki" editor="plain"}
At https://tiki.org/forumthread79408-Convert-between-file-storage-methods#threadId79409 I replied to a post inserting a image using the wiki plugin img. (toolbar insertion)

On save the image is not displayed.
If I edit the page, the image is visible on the preview.
I tried on different browsers

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

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

Made a new install of Tiki v3.2 on a Ubuntu 8.04.3 system as server (includes MySQL in version 5.0.51a-3ubuntu5.4).
Surfing at tiki-plugins.php produces the following error message:
{CODE(wrap="1",ln="0",ishtml="1")}<div class="cbox-data"><br>
<div class="simplebox error">
<div class="simplebox"><b>An error occured in a database query!</b></div><br>
<table class="form">
<tbody><tr class="heading"><td colspan="2">Context:</td></tr>
<tr class="formcolor"><td>File</td><td>tiki-plugins.php</td></tr>
<tr class="formcolor"><td>Url</td><td>tiki-plugins.php</td></tr>
<tr class="heading"><td colspan="2">Query:</td></tr>
<tr class="formcolor"><td colspan="2">
<tt>SELECT fingerprint, added_by, last_update, last_objectType, last_objectId FROM tiki_plugin_security WHERE status = 'pending' ORDER BY last_update DESC</tt>
</td></tr>
<tr class="heading"><td colspan="2">Values:</td></tr>
<tr class="heading"><td colspan="2">Message:</td></tr>
<tr class="formcolor"><td colspan="2"></td></tr>

<tr class="heading"><td colspan="2">Built query was probably:</td></tr>
<tr class="formcolor"><td colspan="2">SELECT fingerprint, added_by, last_update, last_objectType, last_objectId FROM tiki_plugin_security WHERE status = 'pending' ORDER BY last_update DESC</td></tr>
</tbody></table>
</div>
<br><br>
</div>
{CODE}
edit: Sorry, forgot to mention that this bug also affects the using of plugins. Using a plugin in a wiki page that needs approval produces the same error message. (Saw someone in [http://irc.tikiwiki.org/irclogger_log/tikiwiki?date=2009-10-02,Fri|the irc log] with this problem, which is also ===this=== bug, so I edit to clarify it.)

{syntax type="tiki" editor="plain"}
Using the [http://doc.tiki.org/PluginFtp&structure=Documentation|FTP Plugin], when you try to download a big file you'll encounter an error like this:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 59506688 bytes) in /home/myUser/public_html/lib/wiki-plugins/wikiplugin_ftp.php on line 65

In this case, I had tried to download a 56 MB file with a PHP memory_limit set to 128 MB on my hosting.

"Fullscreen Edit" is a new cool feature of 2.x

Quicktags are kept, but Wiki & Plugins Help are missing so it makes editing less enjoyable.

"Edit Summary" is missing as well. Maybe it's intentional?

When the GALLERIFFIC plugin is used in the WYSIWYG editor (full html) then the editor no longer opens - just the 'Loading' message forever. The plugin seems to run ok once it is in there ie it was there before an upgrade or put in new first time round - and you can also use the standard wiki editor ok.

Console errors shown when trying to load the editor are:

"TypeError: imageData is undefined
var index = imageData.index;

jquery....ffic.js (line 505)

which might have something to do with it


... just to confirm that this is still a bug at r 55993 Aug '15

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)]

((doc:PluginCode)) doesn't show colors for php code, as it should according to doc page:
[http://doc.tikiwiki.org/PluginCode]
Tried with param colors=>php or colors=>phpcode:
{CODE()}
{CODE(colors=>php)}
/** Return system defined temporary directory.
* In Unix, this is usually /tmp
* In Windows, this is usually c:\windows\temp or c:\winnt\temp
* \static
*/
function tempdir() {
static $tempdir;
<b>$tempdir = '../tmp';</b>
<b>/*</b> if (!$tempdir) {
$tempfile = tempnam(false,'');
$tempdir = dirname($tempfile);
@unlink($tempfile);
} <b>*/</b>
return $tempdir;
}
}
{CODE}
{CODE}

And it returned:
{CODE(colors=>php)}
/** Return system defined temporary directory.
* In Unix, this is usually /tmp
* In Windows, this is usually c:\windows\temp or c:\winnt\temp
* \static
*/
function tempdir() {
static $tempdir;
$tempdir = '../tmp';
/* if (!$tempdir) {
$tempfile = tempnam(false,'');
$tempdir = dirname($tempfile);
@unlink($tempfile);
} */
return $tempdir;
}

}
{CODE}

---
Update: RFE for plugincode:
Why not using "wrap=>1" as default param instead as "wrap=>0"?

This feature request is for a tool that would enable easy quoting and referencing of any content on a Tiki site, for example, to quote a forum post on a wiki page, or one blog post in another, etc.

Maybe it would be activated by clicking a switch in a module (side column), then selecting some text. Then in the referencing page, when you paste, it pastes not only the selected text but also wikiplugin syntax in which the text is the data and the url of the text's source as a parameter. The quote is displayed like a quote plugin output, and the source is displayed as a link.

The use case that started the thinking about this was a question about how to easily cite Tiki forum posts from a wiki page, without a lot of copying and pasting. Rather than hardcoding it to be forum and wiki specific, a global copy-paste site content referencing tool could be useful in other ways.

After clean installation on tiki-wiki 2.2 (2.1)
the gmap plugin does not work.

For example following string
{img src=images/code.png}%%% {CODE()} {GMAP(type=>page, width=>560, height=>350, controller=>large, mode=>normal)/} {CODE}
in wiki-page does not generate any html-code.

{syntax type="tiki" editor="plain"}
This has been seen on Tikiwiki 2.0 & 2.2: Trying to install the "googlecalendar" wikiplugin from "Admin mods" fails. A page appears stating "wiki-plugins/googlecalendar/wiki-plugins/wikiplugin_googlecalendar.php to impossible to copy".

This appears to be caused by a typo in the Packages/wikiplugins-googlecalendar.info.txt file on the line that states where to copy the plugin file to. There is no space between the source and destination paths and the "lib" directory the plugin should be copied to is missing.

{GOOGLEDOC(key=pXsHENf1bGGY92X1iEeJJI, type=sheet, name=docFrame1, width=400, height=500, align=middle, frameborder=0", marginheight=5, marginwidth=5, scrolling=yes, editLink=both)}
{GOOGLEDOC}

This bit of code is refusing to work for me on my Tiki Site. I have tried several different types of google docs with open viewing permissions without even getting a single one of them to display anything other then the code in text form on the page. I have the googledocs plugin enabled in the tiki admin controls as well.

Toggling highlighting shows that the code is being recognized for what it is despite it just coming up as text on the page. Any help getting this plugin working would be very much appreciated I am utterly stumped.

Group plugin is very cool to put conditional content on a wiki page.

However, it is only an if. There is no if/else.


Say I want to show a content X to people in a group and content Y to everyone else.

Maybe we could have a new parameter?: notgroups

{CODE()}
{GROUP(groups=>Anonymous)}text for anon{GROUP}
{CODE}

{CODE()}
{GROUP(groups=>notgroups=>Anonymous)}text for the others{GROUP}
{CODE}

Project to perform many of the functions of CRM using as many existing Tiki features as possible (dev notes).

When using Groupmail and the Webmail Inbox Module(Profile GroupMail) if you click on "TAKE" the label TAKE should change for your username and you should be redirected to a form to reply (from memories). It was working with Tiki18.

It is partially broken.
The CSS class change to reflect the status (from "read" to "replied") but the user name is not updated and it doesn’t open the webmail page to reply to the message.

While using the GUI for the plugin list and if I set any filter or option without "validating" by viewing the source nothing is saved.