Category: 3.x

I should be able to edit each quadrant:
http://tikiwiki.org/SWOT

http://alexandria.wiki.sourceforge.net/Hosted+Apps

http://profiles.tikiwiki.org/SourceForge_Software_Project


((SourceForge Hosted Apps))

{syntax type="tiki" editor="plain"}
When you move with the mouse over an item in the file gallery, and it is an image, it displays it beautifully, but when the image is too large (and in practice it is), then the display 'falls from your screen'

{syntax type="tiki" editor="plain"}
I was writing up a document that contains the following

-+/MSS/<CustomerID_from_Remedy>/<External_Device_IP>+-

When you hit the preview button, it shows up as "/MSS//" but if you save the page, it shows up exactly as it should

using long Chinese characters as browser title will cause the browser title borken, for example, if you use '机电工程师' as browser title, the browser will show '机电工程帛'.

it's maybe an adodb problem.

{syntax type="tiki" editor="plain"}
Url .../tiki-minical.php?view=weekly&day=24&mon=05&year=2009

In minical, in the light of daily and weekly scroll backward jumps in twos and forward does not change.


sorry for bad translation

JavaScript not executed when arrives via AJAX as when you click the edit page icon at the top (not button at the bottom).
Fails in Firefox 3 and Safari 4 beta on Mac OS

Add a feature to limit amount of space used by users (quota).

Add a status panek to allow the user to see the space used (on disk and database) by Tiki. Maybe also display the amount of space for each feature (filegals, wiki, ...).

An additionnal option could be to send a mail to the admin (or a specific user) when users data occupies nearly 90% of the specified quota.

It could be interesting to specify quotas separately for each features.

Three issues with recurrence rules in 3.0 (tested in 3.0beta1, at the http://tikiwiki.org/TikiLiveCD 0.5a)

# When you hit preview event (before adding the new event to the calendar), the recurrence rule data is lost.
# -- A recurrence rule conflicts with something else. I get "~~red:Events cannot end before they start~~", but the settings are not to produce this warning/error message. The event canot be posted to the calendar. See image attached to this bug report.--
# If admin has not set the default calendar to be viewed by default (I didn't even know about that new setting in 3.0), events are not shown in the calendar for each user until that single user clicks on "Visible Calendars", and select the calendar (even if only one!), in order to view the events he/she has just added. Another user has to do the same process.
---
updated May 4th 2009: the second bug report from the list of three can't be reproduced anymore, at least with tiki3rc1.
The third, seems fixed in a quick trial I?ve just made (I read days ago that nyloth fixed that).

The first one about the preview is still applicable.

should have Recurring events feature on calendar, that will be great...

{syntax type="tiki" editor="plain"}
Per [http://tools.ietf.org/html/rfc2616#section-14.30|RFC 2616 Section 14.30], the "Location" header given with a HTTP 3xx redirect response must be absolute. TikiWiki violates this requirement, and PHP doesn't fix it up again.

The instance I encountered was the index.php, but a simple "grep -ri 'header.*location' ." in the tikiwiki source tree will list hundreds of more instances of this problem. To see it in a live setup, monitor your network traffic (e.g. using [http://www.wireshark.org/|Wireshark]) and visit the root directory of any tikiwiki site, e.g. [http://dev.tikiwiki.org/]. You can then have a look at the HTTP response and notice the incorrect location header.

All user agents that I know of do accept a relative URL as the location of a redirect, and interpret it as relative to the URL of the original request. However, any user agent might decide not to follow such redirects, and it would still conform to HTTP specs. Tikiwiki shouldn't rely on browsers to accept broken behaviour.

These regex expressions could be shared in a wiki page.

Ex.: ZIP code, Postal Code, Phone number, etc

Idea by Fernando Galandrini

Hi

When Search engine friendly url feature is enabled. The registered users cannot delete their own post. Please note the registered user can delete the post when search engine friendly url is turned off.

The url on the browser appear as follow
[http://localhost/tikiwiki3/blog9&remove=25|http://localhost/tikiwiki3/blog9&remove=25]

When i print out the $_REQUEST array. The result was as follow

blogId is 9

There was no "remove" in $_REQUEST array.

Please suggest the workaround for this issue.

{syntax type="tiki" editor="plain"}
I want to allow registration without E-Mail.
Even though I have disabled all E-Mail checking it reports a validation failure.
The function validate_email called in tiki-register.php does as first task a format check on the E-Mail and returns false if the format is wrong. Emptpy emails result in false too.
Is this a valid decision at this point?

When I click the Actions → Replace on tiki-list_file_gallery.php?galleryId=1 (used to be replacing the image file with another one), it does nothing...

link on Replace just points to tiki-list_file_gallery.php?galleryId=1#

I would like TikiWiki's search engine to return results with links to matching sections within pages.

A Wikipedia example of this would be a search for "Life and career." It brings up an entry for John R. Brinkley that has links to the entire article on John R. Brinkley (http://en.wikipedia.org/wiki/John_R._Brinkley) and another for the "Political career" section of that page (http://en.wikipedia.org/wiki/John_R._Brinkley#Political_career).

If I tried to do this in TikiWiki, I would get a search result with a link like the following:

http://mywiki/tiki-index.php?Page=John_R._Brinkley&highlight=Political%20career

That might help if I were searching for this in Google, but it doesn't do what the wiki content creators at my company want. If there is a workaround, I'd love to hear it.

It would be nice:

*to be able to see what is changed from the default value
*to be able to reset preferences to the default

All this, on a panel by panel

Copied some suggestion I just throwed on irc..., after fighting each time on some of my production sites to manually send messages to many users which are kind of lost some times at the beggining of their participation in a tiki-site-powered community.

{QUOTE()}
(11:37:39) xavi: I was just wondering about a new and easy improvement of the registration process of new users to a community sit eusing tiki
(11:38:07) xavi: just through allowing an admin to add acustomized welcome message to new users successfully registered to the site...
(11:38:29) xavi: ... with the text and links he might need to tell to new users....
(11:38:52) xavi: ...in a similar way to what mailman does for the welcome message to new users...
(11:39:48) xavi: ...I imagine a simple text area, like site identity does, where the admin can write any simple text (with or without wiki markup? like the newsletter feature does/allows)...
(11:40:45) xavi: ...so that the admin can set that message easily (without manualy searching for the appropiate template to hack through ftp)...
(11:42:48) xavi: ..and the the new user, can review the infos and tips that he/she needs to know on that site: "now you can: # watch that forum where that important thing is discussed.... #join that newsletter/blog/articlefeature to be up to date about news from that community, #review and/or subscribe to that tracker..., ...
(11:45:22) xavi: oh well, I can't code php+mysql myself (yet, at least ;-) ), but I guess that this shouldn't be that difficult nor time consuming to an experienced coder, provided that that person agrees on that this feature is "low hanging fruit" to improve the experience of newcomers to a community, through improving the communication while the first steps of that person in the community site...
{QUOTE}

This could also be important for ((Workspaces)), and ((Organic Groups)). So that, not just to register (join the registered group), but as a customized message per group, so that, when joining a new group (at registration time, or later on through the subscribe groups plugin), you get the specific message with hints, links and remindings of things adapted for that group.

If Tikiwiki 1.9.4 or 1.9.5 is installed in the wwwroot of a "real" subdomain that resides on its own (win)server (not an alias to a subfolder under the main-domain), then rsslib.php inserts an additional backslash after the domain-name.

Links of rss-feed then look like: ~~#FF0000: sub.domain.com\/tiki... ~~ and RSS feed gets obviously broken.

As a quick-fix for my site I resolved this in the file rsslib.php by deleting the string:
~~#FF0000: ~np~ .dirname( $urlarray["path"] ) ~/np~ ~~
in the variables:
~~#FF0000: $home, $img, $read, $cssStyleSheet, and $xslStyleSheet ~~
in order to get RSS-2.0 to work again.

Unfortunately I'm not any more a coder and don't know php good enough to fix this for everybody and contribute in the CVS (I did no more coding since turbo-pascal under DOS in the mid 90's, but at least still can read a little bit :-)

all the best,
Felix

PS: Thanks everybody here for this great software!!!

{img src=images/code.png}%%% {CODE()}
{rss id=7, max=5}
{CODE}

Should show 5 most recent news items from RSS#7, like on info.tikiwiki.org and not like:
{rss id=7, max=5}

For example:
http://dev.tikiwiki.org/tiki-tracker_rss.php?trackerId=5

Go here:
http://tikiwiki.org/tiki-forums_rss.php?ver=2

And click any link

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"}

{syntax type="tiki" editor="plain"}
Editing articles fails for me in a tiki 3.3 site.
This is the article that I could finally add, when found a workaround:
http://entitatsdelamarina.org/art10

* At creation time, I added three email adresses to be notified, separated by commas, and made a mistake in one of them (email@domain@org,email2@domain.org,email3@domain.org). Note that first email address has an extra @.
* Tiki notified me that I had an error in email@domain@org (good catch, so far, so good!)
* changed email@domain@org for email@domain.org, and reattempted to submit the article
* I got: 400: Bad Request. Your browser sent a request that this server could not understand.

Ok, removed those email addresses, and finally could save the article successfully.

Then I wanted to edit the article again (moving two lines from the header to the body), but I keep getting the same error 400 at saving time (I didn't make any attempt to set email address for monitoring any more; in fact, the field is not shown any more!)

The new 3.0 release of categorize.tpl doesn't show all the available categories to a user when a hierarchy of categories is used if the user is not in the 'top' category.

There are also problems with the use of categorisation in the Structures admin screen where categorisation of all the wiki pages in the Structure does not show the changes after submitting the request - although the changes are made.

No longer relevant