Category: Wiki Plugin (extends basic syntax)

Plugin Convene is "Always" editable and can’t be locked even when meeting is decided.

Sample is our Roundtable that people keep to edit after time is fixed and this lead to confusion.

It is easy technically (I think) complicate practically.

Who has right to edit the page can always change it so it must some kind of Warning or...

I tested Trunk on my Ipad (IOS11 Safari).
The login popup for a default install is outside the screen (landscape and portrait).

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

With this Wiki-plugin it's very easy to subscribe to Mailman mailinglists. You can determine if you want to put a Name field or only the input for the email address. The plugin might need some polish, esp. in the smarty template but works fine so far.

Make a basic working example of Tour (to end up in a learning tiki profile, for instance)

I tried with some basic copy pasting of current info in https://doc.tiki.org/PluginTour and it didn't fully work for me.

See the issue reproduced here:
https://demo.tiki.org/trunk/tiki-index.php?page=HomePage
and
https://demo.tiki.org/trunk/tiki-index.php?page=Tour2


{CODE(caption="Homepage contents")}
{TOUR(title="Welcome to the tour" prev="-1")}Here's the start of a tour.{TOUR}

foo1

{TOUR(title="A Jumbotron")}Use a jumbotron to make an area for special intro information, etc.{TOUR}

foo2

{TOUR(element="#module_1 .panel-heading" title="This is a module heading.")}This is a module.{TOUR}

foo3

{TOUR(path="Tour2")}The next step is on page 2.{TOUR}

foo4

{TOUR(next="-1")}This is the last step of the tour.{TOUR}
{CODE}

And contents in Page "Tour2":
{CODE(caption="Tour2 contents")}
{TOUR(title="Welcome to the tour" prev="-1")}Here's the start of Page 2 in the tour.{TOUR}

foo10

{TOUR(title="A Jumbotron")}Use a jumbotron to make an area for special intro information, etc.{TOUR}

foo11

{TOUR(next="-1")}This is the last step of the tour.{TOUR}
{CODE}

Issues:
!!# "This is a module" instead of start of Tour
Visiting https://demo.tiki.org/trunk/tiki-index.php?page=HomePage shows then content related to "This is a module", and not the content set as the start of the Tour, according to the documentation.

!!# I can't see the jumbotron content

!!# I can't see the info about "The next step is on page 2"
when that info was expected to be seen, the page was redirected to page 2 ("Tour2", in this case)

!!# In page2 (Tour2) no tour is shown


Probably, issues just due to only partial documentation available about how to properly set up a tour with this plugin? {sign user="xavi" datetime="2016-01-11T08:50:41+00:00"}

make plugin pivottable look and feel (3rd party css) adapt to currently chosen theme style
See it explained in the following screencast:

{mediaplayer src="https://seeds4c.org/tiki-download_file.php?fileId=465&display=y" type="webm"}

maketoc is often used in a div like this:

{CODE()}{DIV(float=>right,width="200px")}^{maketoc}^{DIV}{CODE}


How about making a param for this?
{CODE()}{maketoc float=left}{CODE}

Upgraded Tik 9.3 to Tiki 12.2 in our test environment. We have a few wiki pages where we use PluginInclude to incorporate portions of other pages into another wiki page (mainly because the combined page ends up being too long for the database to store). The included text contains section headings that are nested to the proper levels. However, the maketoc plugin on the main page produces a mangled table of contents (all the included section headings are listed before the ones on the main page). Under 9.3, this worked as expected -- the included headings are listed in the proper place inline with those from the containing page. Note this behavior appears to be present in the version running doc.tiki.org as can be seen at http://doc.tiki.org/PluginMaketoc?structure=HomePage+Plugins. Notice that the Example section shows what the maketoc output for the current page would look like and the "Related Pages" heading is out of place.

! Example
Assuming that "HomePage" contains titles, a page with the following source would suffice to demonstrate the bug:
{CODE(colors="tiki" theme="default")}
{maketoc}

! Main section 1
Dummy content

! Main section 2
{include page="HomePage"}{CODE}

The bug can be observed on [http://user-11727-5496.show.tikiwiki.org/tiki-index.php?page=Issue5496|this test page].

This is a regression from Tiki 12.1, due to [https://sourceforge.net/p/tikiwiki/code/48937/|revision 48937].

A small collection of related issues with maketoc:

^{maketoc} -=Maketoc issues=-^
!!! ''TOC and heading type sizes''
* This is an issue that seems to crop up repeatedly on tw.o. Users would like to be able to easily control type size of both the TOC itself and headings created by maketoc. Type size for both seems to be theme-dependent now, with many themes using very large type size for headings, some with a type size for TOC entries that is too small for users with only slight vision loss. It would be a Good Thing if TOC and heading type sizes could easily be set globally, per object type, and by category, with switches available to vary those settings on a per page or object basis.
!!! TOC and heading character attributes
* It would help reduce inconsisistencies in TOC and heading character attributes (as in this tracker item) if the attributes could be set globally, per object type, and by category, with TOC switches available to vary those settings on a per page or object basis. However, the ability to manipulate emphasis within a single TOC/heading entry should be retained, so that for example, a single word could be italicized in a TOC/heading entry.
!!! Vertical linespacing between headings and text
* Under some themes, vertical linespacing between text and headings is too much for taste, or as in the theme affecting this tracker item, too small for taste. This is another setting that should be unleashed from the themes and made easily selectable by a Tiki admin through global, category, and object type settings, with switches for per page or object variation.
!!! ''Backlinks from headings.''
* Links from the TOC to headings are now 1-way. For larger pages, maketoc would be much more user friendly for those viewing pages if clicking on a heading would take you back to the TOC.
!!! Outline numbering.
* TOC formatting and heading formatting would be friendlier to the eye if both could be assigned numbering schemes such as 1., 1.1, 1.1.1, 1.2 or I., A., 1., a., II, etc. Settings might be implemented as described for ''TOC and heading formatting.'' If developed, this might be implemented for lists as well.
!!! Headings indentation.
* Many power users in the word processing and outliners worlds expect headings to inherit the indentations of the corresponding TOC entry. This would help break up the visual clutter that happens when many headings are close together vertically as a result of short text elements separating them, as in this tracker item (but it is far worse when there are subtopics and corresponding subheadings). Settings might be implemented as described for ''TOC and heading formatting.''
!!! Text indentation
* Many people used to word processors' outlining or stand-alone outliners expect text to be left-indented one tab more than its heading. Relevant settings might be implemented as described for ''TOC and heading formatting.''
!!! Associated features
* Display current settings in editor, change current settings from editor. Make changes to settings made from the editor apply only to the object being edited, so that users do not accidentally apply per object settings to other objects. Admins should have option to disable deviations from admin-set settings.
* maketoc is commonly used in conjunction with list features. Any changes to maketoc should not unintentionally impact the list feature and ''vice versa.''
* Need to ensure that all enhancements suggested render correctly when Tiki objects are exported as PDF.
!!! Future options
* Future options might be kept open by maintaining compatability between Tiki objects containing maketoc elements and various formats used by outliners such as OPML, XOXO, OML, or OpenDocument XML. (See corresponding Wikipedia articles.) E.g., it might be feasible at some point to directly export an outline file to Tiki where it is imported as a wiki or blog page and ''vice versa.''

See ((doc:maketoc))

Related: {wish id=1045}


dev.tw.o has too many items on the menu. Using ((doc:Module MenuPage)), so we would need CSS menu or Phplayersmenu.

But if so, we lose the version history, ease of contribution of a menu in wiki wage.

How about the best of both worlds?

Perhaps a menu using a special code around the hierarchy (with bullet points), it can be caught and used by css menu.

In an updated Tiki25 using ElasticSearch I have a customSearch that displays orders.
When I receive a payment I use a button to create a payment item (in a different tracker) and set a relation between the 2 items (order <-> payment).

On Tiki25 the operation is completed and the initial item (the order item) is at the same place in my customSearch results.

---

On the same Tiki (same database and same server) using Tiki26 and Manticore I have a different behavior.

After saving the payment item and going back to the results page the initial order item it is related to is gone.😳
I refreshed the index but still couldn't find it.

In the trackers payments and orders I can see the items exist so the operation was completed.
However the placement of the item I just related another item to has been changed in the customSearch results.

This item (order item) has been moved to the end of the results list after I related to this item another item from a different tracker.

It shouldn't, I have a sort filter here based on order item date `{sort mode="tracker_field_productsboughtDate_ndesc"}`.

{mediaplayer src="display2103"}

On a Tiki 26 I have a plugin List that displays results using a smarty template where I have another wikiplugin list embedded.
This plugin has a filter to match a date with a fields that have a list of dates (2023-07-23, 2023-07-24, ...) using "multivalue".

With ElasticSearch (the originaly used search engine) the results are displayed, no error.

With MySQL full-text Search (used to test only) the results are displayed, no error.

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

With Manticore Search the results are displayed after a long error that start with:
"Fatal error rendering template file /home/tsaharoniki26/public_html/themes/templates/holidays_camps_childrenList_inner_days.tpl
TypeError: strpos(): Argument #1 ($haystack) must be of type string, array given in /home/tsaharoniki26/public_html/lib/core/Search/MySql/FieldQueryBuilder.php:24
Stack trace:"


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

I tried to point a finger on something and change/simplify the plugins that displays such results.
In the last wikiplugin list I this filter.
`{filter field="tracker_field_productsboughtHolidays_text" multivalue="{/literal}{$row.tracker_field_holidaycampsDayDay}{literal}"}`

It's the only "multivalue" filter I have for this page.
If I change "multivalue" for "content" or "exact" no error is displayed.

Layer of a map is not displayed when the tracker used for the searchlayer parameter contain an item link or an underscore.

''Note: Underscore are added automatically when you have a number in or at the end of a tracker field. IE : If your tracker field name is "Name 2" then the permname automatically created will be "name_2".

I had hard time to find what it is exactly so I set 5 samples to demonstrate on the instance.

When the MAP plugin is used in the WYSIWYG editor (full HTML usage) and an already configured plugin is opened in the edit screen (by double clicking the grey box to open up the Plugin Editor) the parameters that were set for the 'centre' parameter have been moved and added to the end of the 'height' parameter with some other characters inserted in between

An example of a corrupted 'height' field is:

400¢er=-1.734241247177124,51.421028334349295,14

which should be 400 and to which the centre parameters

-1.734241247177124,51.421028334349295,14

have been added with the additional ¢er= characters added in between

This does not happen happen when the plugin editor is opened direct from the wiki page by clicking its edit icon and it obviously does not apply when the standard wiki editor is used.

FIXED with r46190 - thanks jonny

Hello!

I'm wondering to know if it is possible to put ((Markdown)) support on TikiWiki roadmap. As many of you know, Markdown is a syntax widely supported by many CMS, text editors, JS and PHP libraries and other Wiki services.

There are even some e-mail plugins, like ((https://markdown-here.com/|Markdown Here)), that allow users to write e-mails on Markdown language and the convert to HTML before sending emails.

Some ""competitors"" allow Markdown support as a plugin, like:

* WordPress - https://br.wordpress.org/plugins/wp-markdown/
* Joomla - https://extensions.joomla.org/extension/ace-x-markdown-editor/
* Drupal - https://www.drupal.org/project/markdown
* Plone - https://docs.plone.org/adapt-and-extend/config/markup.html
* Magento - https://github.com/SchumacherFM/Magento-Markdown
* Jekyll - https://jekyllrb.com/ (AFAIK, this one is used on Github pages)
* Octopress - http://octopress.org/ (I used this one for a long time)

Also, some other frameworks have extensions for markdown:

* Symphony - http://symphonyextensions.com/extensions/markdown/
* Django - https://github.com/agusmakmun/django-markdown-editor
* CodeIgniter - https://github.com/jonlabelle/ci-markdown
* Rails - https://github.com/vmg/redcarpet

So, as Markdown became familiar for a lot of non-technical users, I bet supporting Markdown is a good move for Tiki and also, it may turn easy migrating from other platform using Markdown to TikiWiki.

Hi,

I am working on a few datamanagement projects these days and look deeper and deeper to the boundaries of the Tracker feature and the Trackerlist Plugin.

Walper (Wolfgang) has a huge pro datamanagement in his company aswell and is committing very helpful additions and is doing high quality fixes to existing bumping features.

Now it appears (actually original idea from Wolfgang), that on the output side using Trackerlist, we face some strict limitations, which could be easily solved with a master and slave setup.

Tracker should be interlinkt on the output base (wikipages, trackerlist or list plugins) to provide some kind of "issue reports", "case reports" etc. where trackerlist output is conditionally interlinked similar to dynamic list inside the tracker.

__basic idea: __

Have two or more trackerlist on a wikipage (optionally paginated or so). the master is on top.

Filter content on the top tracker and dynamically get the related content (to the issue or to the case) viewed below.

In my example use case I see, that it would be important to have the option to print the interlinked output together, for example to print out a full overview of a case to have it physically when the responsible person goes to a court hearing. In Wolfgangs use case it might be mor a report for the customer or so to send out as pdf.

At this point I only did a rough sketch and appreciate ideas and input by other users and devs.
Not my sketched technical solution is what I am focussing on, but instead the idea of the workflow and a good UI/UX for aswell site developers and end users.

Thx for any ideas and help from coders.
I am seing more and more that data management would be one crucial killer feature in context of a better respectively a successful marketing of our "beast" Tiki.

Best regards to all community members,
Torsten

Create ((PluginMeta)) as described in the subject.

You can use the plugin meta tag (https://doc.tiki.org/PluginMetaTag) to set a content for a meta tag on a Tiki object.
However this will be added as a new metatag in the -+head+- keeping any other value you may have set (admin, control panel same meta tag or automatic feature).

For exemple:
#I have at tiki-admin.php?page=metatags in the field description : "My very general description".
#In a wiki page about Tiki and I would like to have specific description for this page.
I set the following plugin
{CODE()}
{metatag name="description" content="Tiki is the best"}
{CODE}

After saving, if I check the page -+head+- the description "My very general description" is still there and I can see a second metatag for description with "Tiki is the best".

Results of having meta tag duplication (twice description meta tag) are unclear.
From page validation point of view it seems to be forbidden and bad.
From SEO (Google) point of view it is unclear if the second tag will ignored, will replace the first one or will be considered as an extension of the first one. This because it seems it depends of the meta tag (robot = extension, keywords = not used anymore, description = unsure ?, etc).

Each meta tag nature is different and Google may change its rules at any time.

So, to use the plugin meta tag, it should be advised to remove the "global" values for a meta tag which leave ALL the pages (object) without this meta tag.
Thus I have now to set the meta tag plugin on every pages (or objects). ?

It would make much better sense in real life to have the "admin" meta tags used by default and have the "plugin" meta tags used if they exist.

Also, as side effect it forbid from using the multi-lingual admin feature for meta tags (you can't use any)

Here:
http://tikiwiki.org/TikiCopyrights

I just got:
{img src=images/code.png}%%% {CODE()} WARNING: No such module CVS! copyright.txt {CODE}

Similar to orphans pages and wanted pages, it would nice to have a way to have a list of used plugins (how many times used) from which we know how many are broken.


This happens if someone attempts to use a plugin which isn't activated. This can happen on upgrade for example or if a plugin was de-activated.

We need a way to know how many times each plugin is being used. So we can deactivate without causing issues.

Also, __approval of plugin security__ conflicts with wiki cache. When approving, cache should be cleared. Please test.


** Would need to watch this list
** Rick asks for a [http://irc.tikiwiki.org/irclogger_log/tikiwiki?date=2009-05-01,Fri&sel=120#l116|mass approve]

I'm creating a Tiki site with several small reusable bits of content (as Wiki pages). Cell phone users are my primary audience, so I'm relying on HAWHAW and HAWIKI. I'd like to use INCLUDE module or structures to reuse the content. Tiki handles it fine, but my mobile tiki doesn't support either INCLUDES or Structures. The INCLUDE lines pass right thru unparsed.

1. Is there an easy way for me to get INCLUDE to work?
2. Is it planned for support in a later release?
3. Are there plans for support for Structures?

Thanks for HAWHAW, it's great!

Rob

{img src=images/code.png}%%% {CODE()}
Notice: Undefined offset: 1 in lib/mods/modslib.php on line 359

Warning: mkdir() [function.mkdir]: No such file or directory in lib/mods/modslib.php on line 68

Notice: Undefined offset: 1 in lib/mods/modslib.php on line 360

Notice: Undefined offset: 1 in lib/mods/modslib.php on line 375

Notice: Undefined index: 1 in lib/mods/modslib.php on line 375
wiki-plugins/trackeritemfield/smarty_tiki/block.itemfield.php to impossible to copy
{CODE}

Using 1.10cvs from last week of october'07

module=>last_tracker_items filtered to show only status=>o shows opc

See this page:
http://www.moviments.net/intercanvisarxius/tiki-index.php?page=Benvinguda

which has this call to module under "Demandes" column:
{CODE(wrap=>y)}
{MODULE(module=>last_tracker_items,trackerId=>3,name=>Títol,status=>o,decorations=>n,flip=>n)}{MODULE}
{CODE}

Please note that the items "cadira" (status pending), and "compartir vehicle" (status closed) are still shown at the module output, and they shouldn't.

Link to see the tracker items through tracker feature:
[http://www.moviments.net/intercanvisarxius/tiki-view_tracker.php?trackerId=3&sort_mode=lastModif_desc&status=opc]

Since upgrading dev.tikiwiki.org the "submitted by" is not recorded in bug reports

Can not reproduce the problem. Can you give an url ?
This url http://dev.tikiwiki.org/tiki-view_tracker_item.php is working for me

1- Go here as anonymous:
http://dev.tikiwiki.org/Upcoming+Events

2- Click on a link

You are requested to logon even though Anonymous has tiki_p_view_calendar permission

This was working fine in 1.9.11

But now in version 2.0, there are two permissions:

|| Can browse the calendar | tiki_p_view_calendar
Can view events details|tiki_p_view_events||