Category: Feature request

In Tiki4, and in Tiki5 where accesslib hasn't been deployed

{img src=images/code.png}%%% {CODE()} This feature is disabled: feature_games
Go back
Return to home page
{CODE}

Suggested:
if the current user has admins permissions (tiki_p_admin)
1- enable feature_games
2- add to tiki-syslog.php


We'll need to change all feature checks to use accesslib (job for 5.0)


Needs to handle more than one feature check.

Currently:
tiki-orphan_pages.php

has:
{img src=images/code.png}%%% {CODE()}
require_once('tiki-setup.php');
$access->check_feature( array( 'feature_wiki', 'feature_listorphanPages' ) );
{CODE}

but upon error. Ex.:
http://profiles.tikiwiki.org/tiki-orphan_pages.php

just shows one, even if two are needed.

Say Joe is English, but he can read French and Spanish. He gets to a page which is out of date, compared to English and French. Right now, he does not get any information tellling him to go to French or Spanish instead, except if one of the updates has been the subject of an urgent translation request.

It would be nice if there was a notice at the top of the page saying something like this:

---
The English version of this page is only 87% up to date.

Some of the missing information is considerered __critical__ (urgent translation request issued).

Up to date information is available in the following languages: French, Spanish.

To get a machine generated translation of an up to date version from another language, click here (Warning: the quality of the translation may not be good).
---

Note: Clicking on the Machine translation link would show the out of date English page and the MT into English side by side, so that the user could refer back to the proper (but incomplete) English version if nececssary.

At tiki-admin.php?page=i18n if you enable "Restrict supported languages" you see a text area with 5 languages.
This is too small and make painful selecting several languages.

The text area size cannot be extended.
It should be possible.

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

In history, a user can view pages, version after version, to find a change.
He can do it using the left and right arrows when viewing a page.

In the top nav bar (t_navbar) the buttons doesn't refers to the actual page he is previewing (displayed) but to the actual version of the page published.

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

# It is a bit confusing for most users are expecting unspecified-target actions to be applied to what they see.
## First button label should be changed to "Go back to the actual page (last version)"
## Second button label should be changed to "Edit actual page (last version)" (or eventually removed)
# To view the source of this version of the page (if I'm looking for a plugin code or some syntax), I have to remember the page version number, go back to the page, go back to history and view the source (if available).
## A "View this version page source" is missing

Gary may be consulted for better wording. ;-)

Include a "Secret Question" functionality during the registration process to be used prior to Password Resets & Forgotten Passwords.

The survey feature could be improved by two other survey ratings that the user taking part in a survey can answer. In my experience, the two most intuitive ratings you can ask from survey participants are missing from the list of options, and they are VERY easy to add:

School marks and percentages.

The latter is self-explanatory and gives participants a fine grained range of possible answers. The former is subject to localization, so do not forget tra() !

In the US, to my knowledge school marks run from A (best) to F (worst). In Germany they run from 1 (best) to 6 (worst). Also, school marks can be spelled out. In German that would be "sehr gut", "gut", "befriedigend", "ausreichend", "mangelhaft", "ungenügend". I do not know whether that is also possible for US (or UK) school marks.

School marks must be radio buttons, while percentages would be a three (!) digit numerical entry field, and the acceptance of values over 100 could either be always rejected, or depending on a additional option "allow to exceed 100".

Nowadays the voting on forums is confusing in educational or e-democracy scenarios, since it's not easy to understand why a voting of ! makes just 0.40, or a voting of 5 make 1.60, etc. as it may happen nowadays, since voting on forums seems to be linked to karma or score system.

There should be an option to unlink them, so taht a vote of 1, makes 1, and an option of 5 makes 5 to be included in the mean which is shown at the end on the rate value.

Say I include a bunch of pages in one larger page.

I click edit, and find that it's an included page. I should be able to edit directly that included page (assuming I have permissions), a bit like ((doc:section edit))



Benefits:
*Each page has independent history.
*They can be edited in parallel.



__Can page renames also survive inclusions?__


Related:
*{wish id=2668}

In trunk now (to be Tiki 19), with the update from Bootstrap 3 to 4, navbars have more styling flexibility. Regarding foreground (text) colors, instead of having CSS classes -+navbar-default+- and -+navbar-inverse+-, there are now -+navbar-light+- and -+navbar-dark+-, and also -+navbar-primary+-. And for background colors, there are -+bg-dark+- and +-bg-light+-.

So it would be good to implement admin L&F preferences/selectors to specify the background and foreground colors that the site uses for its main navigation navbar, and add switches in the code to put the CSS classes in the navbar HTML.

Themes should support all three color variations by specifying appropriate colors, etc.

subtitles and topline have 255 characters so why is title limited?

No indent
: One indent
:: Two indents

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

I upgraded a website from 21x to 22x and I got this error/warning now

-+Trying to access array offset on value of type bool on line 670 of /home/bsfez/public_html/lib/prefslib.php+-

I check the logs -vvv --logs (and fixed other things) but there is nothing about this one. Would be nice to know where to look if this is not a regression.

When I run php console.php files:check it shows

Found 1 Issues, details below:
The following files are unknown, exists in the folder, but not in the database
+-----------+----------------------+
| Name | Path |
+-----------+----------------------+
| index.php | ../mypath |
+-----------+----------------------+

It shouldn’t see it as an issue (may prevent monitoring automatisation).

MediaWiki/Wikipedia has an interesting way of dealing with meta-data concerning a wiki page. [http://en.wikipedia.org/wiki/Help:Infobox|Infobox] is very flexible and is very suitable to an encyclopedia. It's easy to create new ones and they are very flexible to adapt to the topic. As soon as a bunch of pages have something in common, you can create one and it gives visitors and quick overview of what characteristics this entry has.

There are over a hundred of these templates:
http://en.wikipedia.org/wiki/Category:Infobox_templates

Here is a simple one:
http://en.wikipedia.org/wiki/Template:Infobox_Animal

Here is a more advanced one where special language codes, when parsed, are shown with a nice presentation:
http://en.wikipedia.org/wiki/Wikipedia:Babel

This is a great way to have ad-hoc, organically growing meta-data around wiki pages which share some sort of structured/comparative data.

In TikiWiki, we use ((doc:trackers)) for tabular data. We need to have an even tighter integration.

Goal: that the metadata be stored both in the wiki page and the trackers
That you can update in one or the other. This would permit us to make lists/tables with all the data from all the infoboxes, without duplicating the data. (not sure if/how to do this with MediaWiki)

We'd need a Wiki Page field-type in trackers. Say I have an "Animals" tracker with all the Meta-Data. One of the fields should be the name of the associated wiki page. And that wiki pages "knows" to get latest data from tracker (like we do now for ((doc:PluginTrackerList)) and ((doc:PluginTrackerItemField)).



{img src=images/code.png}%%% {CODE(caption="2008-06-22 on #mediawiki on freenode.net", wrap=1)}
[09:48] marclaporte: Say I have lots of data in various infoboxes, is it possible to make a report/list/table of all these infoboxes and have them link to the various wiki pages?
[09:48] Splarka: you can use Special:Whatlinkshere on each infobox
[09:48] Splarka: (sorta)
[09:49] marclaporte: tks, would you know of an example?
[09:51] Dantman|FS: SMW
[09:51] Dantman|FS: Doing that with data is basically the purpose of SMW
[09:52] Splarka: http://en.wikipedia.org/wiki/Special:Whatlinkshere/Template:Infobox_Aircraft
[09:52] marclaporte: There are some lists here: http://en.wikipedia.org/wiki/Comparison_of_wiki_software -> how to reuse that info in infoboxes on each page
[09:52] marclaporte: tks
[09:53] marclaporte: Splarka: : yes, that's what I am looking for
[10:05] marclaporte: Splarka: : So now I know where the template is used. What if I want to make a mega chart for all the planes from all the infoboxes?
[10:06] Splarka: well, that might be something more for the category system
[10:06] Splarka: (or ask Dan about SMW, unless he means Super Mario World)
[10:08] Dantman|FS: heh
[10:10] marclaporte: Dantman|FS: : What is SMW?
[10:10] Dantman|FS: Semantic MediaWiki
[10:10] Dantman|FS: http://semantic-mediawiki.com/
[10:11] Dantman|FS: It's an extension for MediaWiki
{CODE}

!!Other things to think about:
*When watching a wiki page, how to watch tracker(s) which are associated with that wiki page?
*In page editing of tracker data, have a quick & nice interface like the ((doc:dynamic variable)) feature

Related:
*[wish2102|Support some of the MediaWiki syntax that doesn't conflict with TikiWiki syntax]
*[wish1191|Wiki editing: Preview with diff, like Mediawiki]
*[wish1781|Support for the Wiki creole markup (syntax)]
*[wish1220|MediaWiki import script]

When a user creates a new page from an existing page (either through the Create Page module or by clicking on a "?"), categories could be inherited.

The problem is that this is not necessarily behaviour required for all TIki installs, and might have to be coded as admin configurable.

Categories have assosiated privileges. Tiki would be more secure if categories where inherited when a new child page is created in a structure.

Sub galleries should, at least optionally, inherit the permissions of their parent (can be overridden of course).

The problem we have here is that if you have a directory for a Project of some sort, and someone creates a subproject gallery, that subgallery is world-viewable, instead of inheriting the Project permissions.

It seems more logical to me to have new children automatically have the permissions of the parentId unless specifically changed.

Like we have for: tiki-view_tracker.php?trackerId=

Syntax highlighting for PHP (and presumably other languages) does not appear to work at first glance. Upon further inspection, its clear that syntax hiliting within the CODE plugin expects a HTML file, rather than an inline code example. I propose a reversal of behavior to expecting an inline example.

Using this code:
{CODE()}
{CODE(colors="php")}
// this is a comment
basename($alpha);
{CODE}
{CODE}

This is output:
{CODE(colors="php")}
// this is a comment
basename($alpha);
{CODE}

On the other hand using this code:
Using this code:
{CODE()}
{CODE(colors="php")}
<?php
// this is a comment
basename($alpha);
{CODE}
{CODE}

The highlighting is now enabled, but its not really the right code example any more:
Using this code:
{CODE(colors="php")}
<?php
// this is a comment
basename($alpha);
{CODE}

Further reading:
[https://groups.google.com/forum/#!topic/codemirror/j7CsgZgM01c]
[http://codemirror.net/mode/php/index.html]

{img fileId="264"}

Special characters is now via a popup. This is bad because the one click javascript insert doesn't work. "Basic" special characters should be integrated in the template.

Could (should?) be contextual to language. Current page? User language(s)? What if use speaks many?

It could also be a drop down-menu like with available languages. Go edit a page on wikipedia to get an idea.


wikipedia's Basic" special characters:

Additional French special characters:

Additional Spanish special characters:

We should let our translators edit this according to their local needs.


Related:
http://sourceforge.net/tracker/index.php?func=detail&aid=1185212&group_id=64258&atid=506848

Installed a Tiki from git 836e12ee and ran Composer.
Got some warnings:

{CODE()}
Could not scan for classes inside "vendor/adodb/adodb-php/" which does not appear to be a file nor a folder
Could not scan for classes inside "vendor/h5p/h5p-core" which does not appear to be a file nor a folder
Could not scan for classes inside "vendor/h5p/h5p-editor" which does not appear to be a file nor a folder
Could not scan for classes inside "vendor/pear/xml_rpc" which does not appear to be a file nor a folder
Could not scan for classes inside "vendor/smarty/smarty/libs/sysplugins/smarty_security.php" which does not appear to be a file nor a folder
{CODE}

{CODE()}
Package container-interop/container-interop is abandoned, you should avoid using it. Use psr/container instead.
Package montefuscolo/xmpp is abandoned, you should avoid using it. No replacement was suggested.
Package symfony/inflector is abandoned, you should avoid using it. Use EnglishInflector from the String component instead.
Package zendframework/zend-version is abandoned, you should avoid using it. Use ocramius/package-versions instead.
Package zendframework/zendservice-akismet is abandoned, you should avoid using it. No replacement was suggested.
Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested.
Package sensiolabs/security-checker is abandoned, you should avoid using it. Use https://github.com/fabpot/local-php-security-checker instead.
{CODE}

May be it could be cleaned ?

When people register to a Tiki site, they sometimes use their email instead of a username. While this works, there should be a warning that this email will be visible in wiki page history, etc.

There is an option to use email as username, but this should not be for community sites.


Other checks would be for accents, existing username, etc.

In groups of people you often have the problem to find day/time when all the people have time to meet.

Especially if they are not in the same room.
And even if they are present its difficult to talk about all the pro and cons when is the best time.


http://www.doodle.com/
Is offering an easy solution. Everybody marks the spots when he has time. Doodle comes up with a proposal, when is the best time to meet. No discussions, every vote has the same weight, non-party and you can always reproduce how the decission was formed.

Can we integrate something like this? Especially because the Tiki direction goes more in decision making.
That feature would fit perfectly in.

phpBB is a popular open source forum software.
Sometimes, a forum is not enough.
So, the data must be migrated from phpBB to Tiki forums...

If you want to help:
Please post links to similar scripts.
ex.: phpbb to invision board, etc
If/when we do a script, we should do for all major forums.
---
__From kerrnel22 on 11/20/07:__

I have almost completed an integrated TikiWiki forum migration tool for 1.9.8.x and 1.10. Initial release will be to migrate only Tiki forums from one Tiki install to another. However, hooks are in place, and the intention is there, to work on extending the migration tool to importing of phpBB2 (or any other forum software) into Tiki. If you would like more information, email tiki.kerrnel@kerris.com. I expect a general release of the forum migration tool (for Tiki forums only) into cvs of both branches for beta testing by December 1/07. If all goes well, I'll have something released for phpBB2 migration prior to Dec 31.