Category: 3.x

{syntax type="tiki" editor="plain"}
Please see:
http://demo.tikiwiki.org/mysql/Video_2009-08-29_IE6_png_fix_slow.wmv

So with #sitelogo a img, it takes about 2 minutes to load certain
pages, because it goes through each image.

Tiki can read and display RSS feeds: good
Tiki can read, combine and display RSS feeds : great


The next step is to import the data into Tiki and treat it like a native article / event / whatever.

If the remote article / event / whatever is modified, the item should be re-imported (but not duplicated). Using the URL to identify the uniqueness. (Some systems many use titles in the URL and if the title changes, we'll end up with a duplicate)

Related:
*[tiki-view_tracker_item.php?itemId=496|RSS feeds on tiki calendar + calendar data sharing via RSS (remote calendars)]
* http://profiles.tikiwiki.org/Collaborative_Watch

E-mail notifications (watches) should provide those cumulative options:
*Digest mode (daily, weekly, monthly)
*HTML mode (using TikiWiki HTML diff)

^ Related to http://dev.tikiwiki.org/bug1184 . Opened a new one since those comments below are updated of a new trial I made today - Jan. 7th, 2009^
Issues detected while dogfooding "__minimum-clicks for pdf from doc.tw.o/Documentation structure__". An opportunity to improve the current features for production.
Related links:
http://doc.tikiwiki.org/Documentation
and
http://doc.tikiwiki.org/tiki-print_pages.php

Printed to html using SeaMonkey browser 1.1.12 and to pdf CUPS/pdf printer, both under Ubuntu 8.04 GNU/Linux
page numbers refer to a pdf produced today out of there:
[ftp://ftp.ourproject.org/pub/edutiki/090107_doc_tw_o___Tikiwiki_Documentation_SeaMonkey.pdf]
(25Mb)
-----------------------------------------------------------------------------

* Autonumbering of headings is shown on the table of contents, but not on the pages themselves (using the default theme in doc.tw.o, based on thenews.css I guess). I would say that this worked for me a month ago on a 2.1 site using feb12.css with another (shorter) structure of wiki pages ( http://www.iesbarcelona.org/ESSO350/tikiwiki-2.1/tiki-index.php?page=2008+Fall+-+Final+Paper ).

* page 39: .htaccess from dynamic content is not shown in the full page. Can this be modified at printing time so that the full content is shown on the page?

* page 41: a CODE block longer than a single sheet of paper is cut at the end of the page, not showing the rest of the content. Can this be modified at printing time so that the full content is shown on the page?

* Some pages didn't have the title manually displayed. Those ones doesn't show the title of the page (as section of the full pdf)... Maybe the best workaround is to add a setting for the user to select whether he/she wants adding all page names as titles to the pages, or not. For our case, maybe it's easier to remove extra title (easy to identify when you have too title too similar one after the other) than having to figure out where a new page starts... (see plugins pages...). Example: page 127: PluginJS is shown, fine, but not PluginLang, PluginListpages? Plugin Manager?, on the following pages...

* copyright license is needed at the end?

* It would be nice to allow at structure-printing time to select which version among the ones allowed by the PLUGIN VERSIONS (where applicable), had to be selected for printing. Right now, it might be useful for people looking for an updated documentation for their 1.9.x, so that all plugin versions were pre-set to display the content from 1.9.x. Moreover, after April (only some months to go for that) we will have the same issue with people looking for 3.x documentation, or just 2.x. Well, this is just to raise this point for the following months, so that, the better for us for producing our own documentation, the better for other communities producing their documentation using Tiki and coping with their versions also... (Firefox, for instance?)

* when the content is copied and pasted to OpenOffice (using OOo 2.x and 3.x), there are images or tables which are wider than the page size.

* Is it possible to have page breaks added before headings of level X (and let the user select a page break just before a heading level 1, and 2, for instance).
---
Update on Dec 7th, 2012 (Tiki9.x LTS):
* RFE still valid....

{syntax type="tiki" editor="plain"}
I assume that the system suppose to display the image, but it downloads it instead.

I mean when in file gallery, click on Actions icon, then Display. It downloads it instead.

So if I change the format of short date, I can see right away the formatted result with the current time.

This was done in later versions of 1.9.11 but not in 2.0

Should be in new magic admin panel

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

Found an bug where including multiple excerpts from the same page would only display the first excerpt. Any subsequent includes would display empty text.

On attempts after the initial one the get_page_info() function is not called.

{syntax type="tiki" editor="plain"}
I have a problem similar to [http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=291|this one]: "Edit" button in Wiki points to "/\/tiki-editpage.php?page=HomePage".
Other buttons also have invalid URLs, links have correct URLs.

Configuration: TikiWiki 3.2, Windows XP, Apache2.2, TikiWiki is in the server root directory.

This bug is tied to [http://example.com|http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=1964&trackerId=5&show=view]

I have had various issues navigating my wiki seemingly because $base_url is not getting built correctly, or at all. The first of these issues happens at login where the user puts in a bad username or password. The redirect to the error page fails on Firefox and has a URL with doubled forward slashes after the domain because the $base_url is not getting passed. URLs get built as follows (where 'example.com' is my domain):

Firefox:
{img src=images/code.png}%%% {CODE()} http://example.com\/tiki-error.php?error=Invalid+username {CODE}

IE:
{img src=images/code.png}%%% {CODE()} http://example.com//tiki-error.php?error=Invalid+username {CODE}

This happens with relative URLs all over tikiwiki in my installation, which is a WAMP with virtualHost entries in the httpd.conf to resolve 2 distict domains on the same server.

No indent
: One indent
:: Two indents

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

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]

{syntax type="tiki" editor="plain"}
When showing a page in print view (tiki-print.php), attachments do not show. Instead, a message called "No such attachment on this page" appears.

NOTE: I was able to fix this for tiki-print.php, but not for tiki-print_multiple_pages.php

On a new installation (clean DB), Tiki does not set the site's default language.

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.

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.

When I first met Tikiwiki, I was looking for only a wiki program. The translating for page (multilingual) feature of Tikiwiki made me to choose it.

But I always wonder: does Tikiwiki really need to have so many features ?

We all know that multi-features software is more complicated for developers as well as users than single-feature software. For example, Tikiwiki has a forum built-in, do you think this forum is better than phpBB3 ? Tikiwiki also has an article feature, do you think this feature is better than Joomla! CMS ?

At present, I have a website built with Joomla, I want to add a new wiki section, but Joomla has no wiki component. In fact, I think we should combine these best softwares together, not re-create the wheel. Joomla doesn't need to build a new wiki component if we can integrate Tikiwiki with it. In fact, this integration only needs at least one function: synchronize the users so they can login in to Tikiwiki without register twice.

I should inform you that Joomla! will be the most popular CMS soon, so I hope the Tikiwiki team take some time to consider this integration suggestion.

Thanks.

Google Maps integration is an excellent feature. It would be helpful to provide [http://openlayers.org/|OpenLayers] as as an alternative.

If we had this, we'd use it on http://dev.tikiwiki.org

The Trac Repository Browser:
http://trac.edgewall.org/wiki/TracBrowser

Let's coordinate here: ((Repository Browser)) and ((Code Review))

There are lots of possibly-related bugs here and they're all related to internal wikilinks within tables and a certain lack of whitespace, so I'll just list examples (copy and paste this into a page):

!!-Examples (warning: wide)
~pp~
!!!~np~||((foo))|text||~/np~
||((foo))|text||
works fine


!!!~np~||((foo))|((bar))||~/np~
||((foo))|((bar))||
~np~<td class="wikicell">foo</td><td class="wikicell">bar<a href="tiki-editpage.php?page=foo%FF298432%FFbar" title="Create page: foo%FF298432%FFbar" class="wiki wikinew">?</a></td>~/np~


!!!~np~||((foo t))|((bar t))||~/np~
||((foo t))|((bar t))||
~np~same problem as ||((foo))|((bar))||~/np~


!!!~np~||((foo))|((bar|baz))||~/np~
||((foo))|((bar|baz))||
~np~<td class="wikicell" colspan="2">baz<a href="tiki-editpage.php?page=foo%FF298432%FFbar" title="Create page: foo%FF298432%FFbar" class="wiki wikinew">?</a></td>~/np~


!!!~np~||((foo t))|((bar t|baz t))||~/np~
||((foo t))|((bar t|baz t))||
~np~same problem as ||((foo))|((bar|baz))||~/np~


!!!~np~||((foo|boo))|((bar|baz))||~/np~
||((foo|boo))|((bar|baz))||
~np~<td class="wikicell">boo</td><td class="wikicell" colspan="3">bar<a href="tiki-editpage.php?page=foo" title="Create page: foo" class="wiki wikinew">?</a></td>~/np~


!!!~np~||((foo t|boo t))|((bar t|baz t))||~/np~
||((foo t|boo t))|((bar t|baz t))||
~np~same problem as ||((foo|boo))|((bar|baz))||~/np~


!!!~np~||text|((bar|baz))||~/np~
||text|((bar|baz))||
works fine


!!!~np~||text|((foo))|((bar|baz))||~/np~
||text|((foo))|((bar|baz))||
~np~same problem as ||((foo))|((bar|baz)||~/np~


!!!~np~||text|((foo))|((bar|baz))||~/np~
||text|((foo t))|((bar t|baz t))||
~np~same problem as ||((foo))|((bar|baz)||~/np~


!!!~np~||text|((foo))|nospace|((bar|baz))||~/np~
||text|((foo))|nospace|((bar|baz))||
~np~nospace disappeared! <td class="wikicell">text</td><td class="wikicell" colspan="3">baz<a href="tiki-editpage.php?page=foo%FF290656%FFbar" title="Create page: foo%FF290656%FFbar" class="wiki wikinew">?</a></td>~/np~


!!!~np~||text|((foo t))|nospace|((bar t|baz t))||~/np~
||text|((foo t))|nospace|((bar t|baz t))||
~np~same problem as ||text|((foo))|nospace|((bar|baz))||~/np~


!!!~np~||text|((foo|boo))|nospace|((bar|baz))||~/np~
||text|((foo|boo))|nospace|((bar|baz))||
~np~same problem as ||((foo|boo))|((bar|baz))||~/np~


!!!~np~||text|((foo t|boo t))|nospace|((bar t|baz t))||~/np~
||text|((foo t|boo t))|nospace|((bar t|baz t))||
~np~same problem as ||((foo|boo))|((bar|baz))||~/np~


!!!~np~||text|((foo))|has space|((bar|baz))||~/np~
||text|((foo))|has space|((bar|baz))||
works fine


!!!~np~||text|((foo|boo))|has space|((bar|baz))||~/np~
||text|((foo|boo))|has space|((bar|baz))||
works fine
~/pp~

!!
I think the code responsible for this just needs a total rewrite.

{syntax type="tiki" editor="plain"}
I have several tikiwikis (v 3.0 beta 4) on the same domain. Both behind the same .htaccess protected directory. The goal was to setup a working instance of InterTiki between these two Tiki's.

By way of example
* Apache .htaccess limit: http://www.mydomain.com/p/
* Master e.g. http://www.mydomain.com/p/master
* Client e.g. http://www.mydomain.com/p/client

__BACKGROUND__
A few setup issues have been noted (these details have now been added to the InterTiki documentation). Most notably is correctly specifying the location of "/remote.php" for the above case. For our above example to following is req'd:
* host: http://www.mydomain.com
* path: /p/master/remote.php

On the master, I have successfully made contact using either the IP shown in the Apache logs, or by simply using "127.0.0.1" in this case.

Likewise (also added to InterTiki docs) there was some oddity related to order of events with how the server info was being plugged into MySQL tiki_preferences interlist table. I have not properly tracked this down so will not go into it further at this time.

Also of note (for another bug or support request) is that I am unable to get InterTiki on the master to log out anything.

__BUG/FEATURE REQUEST__
''Note: InterTiki operates as designed and is simply unable to get behind an Apache Basic Auth wall. However, hard-coding in setCredentials line for the XML_RPC_Client should work in this case but does not.''

After getting setup dialed in like above, the client received the following message:
''XMLRPC Error: 5 - Didn't receive 200 OK from remote server. (HTTP/1.1 401 Authorization Required)''

Some digging into /lib/userlib.php finds the calls for setting up the XML_RPC_Client at lines (around) 228, 2812, 2831, 2860 and 2905. Looking into the XML_RPC_Client class in /lib/pear/xml/rpc.php shows that there exists a setCredentials($username, $password) method. The setCredentials method exists to allow for RPC calls to get through Basic Apache Authentication.

__Possible Bug__
I went ahead and modified the clients (and eventually the master's) /lib/userlib.php in the above locations with a simple addition of:
$client->setCredentials("myApacheUsername", "myPassword");

This time, when logging in from the client, the response was:
''XMLRPC Error: 5 - Didn't receive 200 OK from remote server. (HTTP/1.1 302 Moved Temporarily)''

And with that I am stuck. It seems like (as a workaround hack for the time being) the ability is there in the XML_RPC_Client methods to get through an Apache Basic Auth, but the return code is weird at best.

__Possible Actions__
#Ignore -- Explicity note that InterTiki masters/clients must not exist behind Basic Auth walls.
#Investigate why a hacked userlib.php returns a 302 code and determine if this is as designed or a bug.
#Possibly add a basic username/password entry field in the client administration page for driving the setCredentials method.

This may or may not be considered an error, but is not-as-expected behavior.

!!Problem
When setting up InterTiki, one would assume that 127.0.0.1 would work as an IP filter for localhost. However, it was pretty clear that this was not working in 3.0 (beta 3, beta 4, rc1)

!!Regression
* Turned on the XMLRPC debugger in /lib/userlib.php around line 2817 ''$client->setDebug(1);'' to look at the response back from the server and do a bunch of printouts.

Traced InterTiki problems to the IP security check to the following (line 55) in /remote.php.
{CODE()}
if (!isset($prefs['known_hosts'][$key]) or $prefs['known_hosts'][$key]['ip'] != $tikilib->get_ip_address()) {
{CODE}

By changing the line to the following, the IP check problems went away:
{CODE()}
if (!isset($prefs['known_hosts'][$key])) {
{CODE}

{syntax type="tiki" editor="plain"}
This follows extensive regression into InterTiki setup problems. There are 2 bugs in here, but they are likely related as they exhibit the same performance. I am unsure where the problem lies (someone familiar with the code could fix this in a heartbeat).

!Background
Both these apply to a fresh install of Tiki and getting InterTiki up and operational. I have replicated this bug on 2 different setups (2 different hosts).
# Tiki 3.0 beta 4
# Tiki 3.0 RC1

!!Server Setup Error
During initial server setup, as Tiki Admin, setting up the KnownHosts information. Typically, I would only setup one known host for demo purposes. However, in spite of tweaks, I kept seeing the InterTiki response error __Invalid Server Key__.

!!!Regression
I tracked through to code to the /remote.php validate function, around lines 58 or so. It seems like it always ended up inside the if clause (failing the validation).

Inserting
{CODE()}''print_r($prefs['known_hosts']);'' {CODE}
at the top of the validate function I received the following from the master:
{CODE()}
Array
( [0] => Array (
[name] => tiki2
[key] => mysecretkey
[ip] => 127.0.0.1
[contact] => mizraith )
)
{CODE}

!!!Explanation
No wonder it failed the test, as the if statement was indexing into "known_hosts" using the key.
{CODE()}
''!isset($prefs['known_hosts'][$key]) or $prefs['known_hosts'][$key]['ip'] != $tikilib->get_ip_address())''.
{CODE}

As you can see, the initial setup from within Tiki failed to properly key the database entry. The database entry has a key of [0].

Adding another "known_host" in the InterTiki admin shows correct behavior:
{CODE()}
Array
(
[0] => Array
(
[name] => tiki2
[key] => mysecretkey
[ip] => 127.0.0.1
[contact] => mizraith
)

[anotherkey] => Array
(
[name] => another
[key] => anotherkey
[ip] => 123.123.123.123
[contact] => mizraith
)

)
{CODE}

!!!Additional Regression
Editing that first Known Host in the InterTiki admin screen does not fix the key value. AFAIK, one has to __delete__ the first known host that is entered (throwaway). From then on, it seems to work.

!!Client Setup Error
Although I didn't recognize it at the time, I have seen this same error during client setup of InterTiki. In that process, admin must enter a Known_Server. The first server you enter in seems to go into the database with a key of [0], even though InterTiki will search on the server's key name.

{syntax type="tiki" editor="plain"}
Tiki automatically includes the "id" attribute for headings. For example:

{CODE()}
!my heading
{CODE}

Becomes:
{CODE()}
<h1 id="my_heading">my heading</h1>

By default, the value of __id__ is the text of the heading. However, as per the XHTML specification, __id__ ''must'' begin with a letter -- not a digit.

Therefore, if I have:

{CODE()}
!2009 Highlights
{CODE}

Tiki generates:
{CODE()}
<h1 id="2009_Highlights>my heading</h1>
{CODE}

Which is invalid.

See http://validator.w3.org for details.

Trackers can have many fields.

Multilingual is a way to have multiple values.

Native multi-valued trackers would be useful in certain circumstances.

Another way is to use ((doc:Category Tracker Field)) or ((doc:Items List and Item Link Tracker Fields)) or ((doc:Drop Down - Radio Tracker Field)) with multiple choice option. Probably the best is to build upon the ((doc:Relations Tracker Field)).



We would also want multiple sets.

First Name 1 (field 46)
Last Name 1 (field 47)
Address 1 (field 49)

First Name 2
Last Name 2
Address 2

First Name 3
Last Name 3
Address 3

First Name 4
Last Name 4
Address 4

Could we imagine a new tracker field type "Set of fields":
Fields: List of fields in the set. ex.: 46,47,49
Number of repetitions: ex.: 3

This would create artificial fields (in this case 46-2, 47-2, 49-2, 46-3, 47-3, 49-3, 46-4, 47-4, 49-4)

So these fields could be used independently (ex.: 47-2), but since they are linked, we could have some smarter handling for forms, reports and exports.

We could want the input form to by default indicate only the first set of fields, and via jQuery, show additional set of fields.
We could want a report/export of this "Set of fields" which would aggregate everything in one listing.

{draw id="28"}