Category: Documentation (or Advocacy)

Some file galleries were not visible although categorized so they should have been visible. Had to set the "This Gallery is Public:" but this flag is not documented so its behavior is unknown.

publish 1.9.0 notice on

tikiwiki.org
Freshmeat
Sourceforge

Finish up nice page: ((tw:WhatsNewIn1.9))

Right now I am on 1.9.11, going to upgrade to RC4, is that possible for upgrading from RC4 to release 2.0?? Or may be I can wait the 2.0 for a while.

BTW, it said that the 2.0 will be released in the second week of August, but right now it became in the August... Don't worry, Thanks for your hard working, we are all look forward the 2.0 :)

Consequently gets an error on this plugin using 2.1 on a Windows machine. Error message from a what I am sure is a proper trackerlist reference is:

ErrorError
No field indicated

Close Window

- - - -

Found out this was an issue related to not making the referenced fields public. I would suggest the documentation is clearer on this issue in the trackerlist documentation. Will have a look at the documentation.

When I tried using wkhtmltopdf for PDF export, all I got was 0 byte files. I turns out this is because the system running wkhtmltopdf must have an X server installed to work. This is not the case with my headless server, and I imagine that most web servers do not run X.

On the Manual database installation docs:
http://doc.tiki.org/Manual+Installation#Rename__htaccess_for_clean_URLs_optional_

Instruction 1.4 says
1.4. Rename _htaccess for clean URLs (optional)

You can rename _htaccess to .htaccess
-----

BUT in the files there is only htaccess.sh

SO, is this the same file as _htaccess?
Really want to change the name of htaccess.sh to .htaccess.sh?

Low priority since this is an Alternative. But it does prevent manual installations
from having clean URLs

The RC1 HomePage says

----
__Personal Blog and Profile__ (apply profile now)
Setup with many cool features to help you integrate the Social Web and establish a strong presence in the Blogosphere

Blog (Full set of blog related features)
Image Gallery
''__Calendar__''
RSS Integration
Video Log

-----

However the Calendar is not installed, so either the doc is wrong or the feature should be added to the profile.

add unstable Branch in Freshmeat and link to de.tikiwiki.org's daily snapshots...

ex.:

# Redirects
# This is useful if you are migrating from an old site, and you want the old URLs to still work.
# Just uncomment and edit the line below.
Redirect 301 /oldpage.html /tiki-index.php?page=newpage

Bugs & Wish list

Apparent bug of undocumented feature within the ARTICLESplugin, such that the "start" parameter does not seem to function.

In the example below, This was coded into the body of a wiki page. I was trying to have two ARTICLES columns, but show the first 5 (or so) articles on the left of the wiki page, then continue with articles 6 thru (say) 10 on the right column of the split wiki page.

Gary (chibaguy) suggested the code below (including the "start" parameter), but it appears that I get identical lists of articles, rather than one column listing articles 1 thru 5, and another parallel one listing articles 6 thru 10 (as expected). "Start" doesn't appear to be documented, but Gary chibaguy suggested it's use to me.

{CODE(caption="example code to reproduce problem")}

{SPLIT()}
{ARTICLES(start=1,max=5)}{ARTICLES}
---
{ARTICLES(start=6,max=10)}{ARTICLES}
{SPLIT}

{CODE}

Please see http://tikiwiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=35859&thread_sort_mode=commentDate_asc#comments

Gary suggested that I submit this as a bug, so this is it. It would be awesome to be able to do a two column split of articles via the inline plug, but not when the lists are identical.

Thanks to you for looking into this!!! -sd :)

Access to pages on doc.tikiwiki.org with names like "User / Group / IP / Page - Selector Tracker Field" is broken.

((tw:RestoreHelp))


If this is not ready in time we'll deactivate the feature and put a note to users than when they the should expect some 404 pages and that their help is welcome.

Copyright and license notices are missing from several *.tikiwiki.org sites. These are required, or participation and content become legally ambiguous.

Hey Guys - I'm new to tikiwiki and have been trying to access the movies on this page -> http://tikiwiki.org/TikiMovies BUT most of the ones referencing USA point to an expired account and the ones mentioning Europe generate an error saying i don't have permission (even when logged in) ..??..

e.g., in the section "Preliminary_Settings", the USA link resolves to this -> http://esc45.midphase.com/suspended.page/ even though the link is coded for this address -> http://www.teluguvaariki.com/sri-addons/tikiwiki_videos/Wiki ... and when i hack the url to just the root domain, i get the same error and suspect this user's account is DOA ... i should note that i tried this a week or so ago and got the same response hence delayed sending this thinking it might clear up by now ..??..

and then when i click on "Editig a wiki page (Europe)" i get error - ie., "You do not have permission to use this feature" ... that link shows as -> http://tikiwiki.org/tiki-listmovies.php?movie=Wiki.swf&action=Display

the same thing happens with the other videos in other sections like "Editing a wiki page", "Image Galleries", "Articles", "FAQs", etc ... the only video link that does work is the 24 minute intro with David Lankes - which is excellent by the way :>)

accordingly, please advise ... i would really like to watch these videos to get up to speed as i'm already having numerous problems ... a) i was able to install okay but the images in the gallery won't upload, or when they do appear to upload, i get a blank screen and see no images ... b) i can't get the secure login link to work with my dedicated server that shares a SSL cert across domains ... thus i installed tikiwiki on avantigroup.com/tiki but for the https i need to make a url callout that is https://secure.cooltea.org/avantigroup.com/tiki but tikiwiki won't let me do this from admin control panel and forces https://avantigroup.com ... ugh ... sure, i could go in and hack the template but this kind of defeats the smarty template approach but i digress ...

thanks in advance for your attention to this matter and on positive side, it does look like you have a lot going for your project and i look forward to diving in further ... to be continued ... cordially, chuck scott

A newly registered user cannot edit most of doc.tw.org

An anonymous user cannot edit doc.tw.org, even with CAPTCHAs.

There is no clear text on a page of doc.tw.org which tells a user why they cannot edit that page, or what they can do about it.

at the pages in dev.tiki.org I often get an error in chrome.
Like page: http://doc.tiki.org/Wiki+Plugin
Error on the screen: Fatal error: Allowed memory size of 201326592 bytes exhausted (tried to allocate 350 bytes) in /home/two/doc/lib/init/initlib.php on line 187

This may be 2 bugs:

When you select Admin - External feeds and create a new feed, a blank page is presented after clicking "Save." It appears as though the external feed is saved, though.

Created feeds are not being updated on a schedule, nor are they being updated when the "Refresh" option is clicked. Clicking "Refresh" results in a blank page being displayed.

This has been ((http://tikiwiki.org/tiki-view_forum_thread.php?comments_parentId=37418&topics_offset=23&topics_sort_mode=lastPost_desc&forumId=4|reported on the forum.))

Tested in v3.1. When choosing to store File Gallery items in a directory instead of the database, the directory field requires the full server path. If the abbreviated relative path to the wiki is entered, file uploads fail.

This conflicts with both doc.tw.o (as of today's rev) and Admin > Wiki, which allows the attachment directory to be specified relative to the wiki directory.

http://doc.tikiwiki.org/tiki-index.php?page=Features

Help System is not listed as a feature for Tiki Tracks. Is it the same as WebHelp? If so, then one or the other should be renamed for consistency

The "Help System" link on Admin::General points to non-helpful swamp on doc.tw.o

If the user didn't change the value of the destination of the help system, it should be updated to what the default value is now.

Need to hunt down what all the previous values were (ex.: http://doc.tikiwiki.org/tiki-index.php?page=) and to update via sql

And for clean installs as well (of course)

However, if someone modified the default value, we don't touch.


Reminder to add a reset to default value in 3.0 (new admin panel should permit this)

The URL's for the help buttons are not being built correctly. Users are unable to get help during the initial setup.

Tested on 1.10.0b1. To reproduce:
After a fresh install go to the Administration:Administration page
Click on the General icon.
Click on the help icon at the top of Administration General
The help URL will use the local host name instead of doc.tikiwiki.org

Other notes:
Help shows enabled on the features page (apparently enabled by default)
All pages reached through tiki-admin.php seem to have this problem

In some PHP version, http_build_query would not work correctly and would not show correctly URL parameters for admin and edit options (in converting the templates from SMARTY).

Make sure that http_build_query function from php is working correctly as some version work only with 2 parameters (even it is said to be Php 5.1.1) and others 3 parameters.

See this issue reported in:

http://tikiwiki.org/tiki-view_forum_thread.php?topics_offset=1&forumId=6&comments_parentId=37095

http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/branches/4.x/changelog.txt (got link to that from -german- http://doc.tikiwiki.org/Tiki4) contains link to http://tikiwiki.org/ReleaseNotes42 which does not exist

A lack of documentation on the correct usage of code in the Custom Site Header section may result in a broken site (blank white page)

For example, if one wanted to display a menu based on a users group but did not use the proper code (because he can't find documentation showing the proper code) there is a good chance the site could break.

It has happened to me a couple times but fortunately was able to go back or to another tab and remove the site breaking code and save again.

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.

The installation documentation (I referred to all pages linked from the main page plus several postgresql-specific ones) do not give any indication that TikiWiki is only usable if installed in document root (aka TikiWiki is greedy/must run the whole domain). This should be specified as a installation requirement.

A better solution (IMHO) would be to fix the coding (e.g. replace absolute paths by relative ones) so that TikiWiki would place nice if installed in a subdirectory.

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.

!!!After upgrade the admin can't login anymore

!!!The failure sequence :
#Create a new directory or repository for the new version
#Update with your files (particularly images or icons)
#Site enable (example a sub-domain) on Apache
#Copy the database on new name
#Install manually .htaccess (compare and insert your valid options )
#Update "local.php"
#run <your new domain>/tiki-install.php. Goto the end (note an error occurs if your say at the end "run tiki" without locking or not because tiki-setup tries to re-open a session already automatically opened by installer). You just launch again (default tiki-index)
#~~#F00:__Try to login as admin : You will be rejected as wrong password __~~

!!Analysis - many possible reasons :
There are a lot of reasons to be in this situations. So to be successful a lot of conditions must be satisfied :

#If your new version uses the same current domain (after upgrade for my own I defines the same "servername" as current one and then keep the other when a particular name containng the version :
- The Cookies of session will try to reconnect an older version and a trace shows that the password is not the one you have given (generally empty). So the cookies of the site name must be cleared on your navigator

#The temp files or session table contain too wrong data : they must be cleared on server for your current copy (SVN update case)

#Your admin record in user_user record contains sessions data : they create a conflict which makes crash your login

#Be careful of the fact that you can have an open session in your navigator with the same site (sometimes we uses a lot of tab management which can create this : on firefox use showcase and search to clear your old sessions

#Generally avoid these problem is sufficient but at the end you will be prompt to update your password (as for the first login as admin with password admin). This can fail for the following reason : if the .htaccess is not set or modrewrite not well operational the <site name> will include the "port" used by your server. If your NAT translates the port address (i.e. 80-> 4397) you will get the following url <site>:4397/.... which fails

It is sure that if you use only one site close everything and upgrade you will get the minimum of problems but you will get someone anywhere.


!!~~#099:This situation is common and complex for whom have to manage product and data migration from one version (or several) of tiki to a new one.~~
It is not seen generally by developers, because it is not at all their common upgrade process nor test.

Hello,

Here is a wish in regards to my learning curve.

I heard that Tiki is good at allowing others to create forms.

Here is the print screen of __this form_, which is quite impressive.

---

::{img src="http://yogapartout.com/extlinks/ftp/useCase/imgs/printScreens/wishToLearnViaVideoHowToCreateAformLikeThis.jpg" link="http://yogapartout.com/extlinks/ftp/useCase/imgs/printScreens/wishToLearnViaVideoHowToCreateAformLikeThis.jpg" width="800"}::

---

I'm actually _the Tiki's most populare Newbie_ as I am still learning the basics about Tiki.

Here is my panel box of what my form, the only one I have looks alike on my admin panel

---

::{img src="http://yogapartout.com/extlinks/ftp/useCase/imgs/printScreens/LearnViaVideoHowToCreateAform.jpg" link="http://yogapartout.com/extlinks/ftp/useCase/imgs/printScreens/LearnViaVideoHowToCreateAform.jpg" width="800"}::

---

Is there a video somewhere that shows how to create (this actual form I'm using to communicate this need) a form?

Daniel.

The "Directory Batch Upload" page states "Please do not use this feature to upload data into the database." The page is stating that it should not be used, thus rendering it unusable. Clarification is needed.

Hi All,

I’m working on the Tikiwiki 2.2 with a LDAP authentication.

In the login option, I see it is possible to automatically give someone access in the Tiki if this person is in LDAP directory.

My question is: Is it possible to define access with a Distribution List group and not with the entire LDAP directory?

On another note, do you know why “LDAP Member is DN” can not be set to “yes?”

Thanks for your response

Hi there,

I want to nkow if it is possible to integrate the tikiwiki login process with another page, I want to create another secure page using the tikiwiki login process, Do you guys have any hint for doing that?

My page will be in php also, I know that I will probably have to do some inclusion but don't which file to include in my code and which function.

Any help will be much apreciated.

Thanks

Could someone please make the fields this tracker uses available to the community, please? (easily done, since there's an export/import feature!)

I'm trying to create a support web site, so obviously need much the same thing as this site. Trackers are quite a learning curve, so a couple of good examples would be really useful!

If someone does this, I'll add an export of the fields I end up using and make them available too (I've got a couple of other tracker apps up my sleeve too).

Cheers!

I think this feature refers to the small calendar that can appear in a left or right module. The help link currently points to the calendar page, which only describes the JS navigation calendar.

Read and tried the various methods in the various (sometimes conflicting) MultiTiki documentation. Could not figure out a path to success.

It appears that (although it was claimed otherwise on some other pages) that shell access is required for MultiTiki.

Questions that came about during attempt at integration:
(1) Is it possible to setup MultiTiki when one is on a hosted server (via FTP only)? If so, what is the process? I would be willing to write up the process if I could figure out how to do it.
(2) Which of the MultiTiki's is supported for TikiWiki3 ?
(3) Is there a web-based installer for setting up several tikiwikis on the same domain (but in different folders)?


How can I help vette the install process?

I would really like to setup an InterTiki + MultiTiki site as my coroporate intratnet. This would closely mimic the sub-web functionality in TWiki but allow for group wiki's to get their own distinct identity. At this point, TikiWiki is nearly more functional than TWiki, but the InterTiki/MultiTiki difficulties may be the deal breakers.

Can you please make the http://dev.tikiwiki.org/tracker5 "trackers fields" available for download so we can import it to our tracker.
We need a tracker with similar functionality but so far I have not managed to create on.

Thank you.

Noob here enjoying the site, enjoying the software and finding my way around. Thank you.

It means spending a *lot* of time at the Tiki sites.

I get the message already about the dogfood. Cool.

But every day, every page load, I must dismiss this notice to uncover what is underneath. Or scroll the viewport out from under it.

It is located on top of the navigation.

Can we not have it fixed in the page above the navigation, or permanently dismissable once logged in, or ...?

Can we just use the site now, and stop swatting at the javascript? :)

I'm just setting up svn etc now. And wouldn't have the balls to make such a visible change right off the hop anyway. It's not real important obviously. But if somebody is there and knows and can do, it would make surfing the sites more pleasant...

Cheers!!

TW5.0beta1
http://dev.tikiwiki.org/Hello+World#To_create_a_new_plugin seems to be outdated. the plugin cannot be installed i the prescribed way.
By the time a php plugin file with a "wikiplugin_" prefix is saved to the lib/wiki-plugins folder, the Administration/Editing, plugins gives an empty pages. So do all the pages containing the new wiki plugin. Nothing is listed as a plug-in to be installed.

Two smaller corrections
* The sample code containing an extra '}' (last but one in wikiplugin_helloworld_info())
* The name to save the plugin must be lib/wiki-plugins/wikiplugin_helloworld.php instead of lib/wiki-plugins/wikiplugin-helloworld.php.

Fresh install of Branch-1-9 daily build.
The help system (the system that turns the feature descriptions into live links that point to the docs) is not enabled by default.

Not Enabled on a fresh install of Sa Jun 16 15:42:39 CEST 2007

When upgrading to 2.0 rc4 from 1.9.11 install failed because I was not logged into the app. By the time I reached that stage, I was no longer able to login. Need to make note at the beginning of the upgrade procedure instructions to FIRST LOG INTO TIKIWIKI AS ADMIN

Some versions of the Tikiwiki documentation suggest that a watch does not report a change to a web page that has been designated as a "minor" change. That does not appear to be the case for Tikiwiki 1.9.2.

If you ask me, the ability for a wiki user to make a Minor edit without bothering the "Watcher" crowd is a great idea and makes for a better community wiki dynamic.

Please read:

[http://irc.tiki.org/irclogger_log/tikiwiki?date=2009-04-18,Sat&sel=117#l113]


Something like:

{img src=images/code.png}%%% {CODE()}
{if isset($objectCategoryIds) and in_array(1, $objectCategoryIds)}
This is the documentation for {$page}. For bug reports and feature requests, please visit [http://dev.tiki.org/{$page}]
{/if}
{CODE}

Documentation of Tiki (doc.tw.o) needs some help, as well as any other tiki site aiming to produce structured documentatation to be exported as "printer-ready" (.pdf, .odt, ...)

!!- (1). Original idea, as posted in devel list (but improved, and made it easier, below, in (2) )
I include here a copy of the [http://sourceforge.net/mailarchive/forum.php?thread_name=467565F1.9080905%40ub.edu&forum_name=tikiwiki-devel|original post at tiki-devel list]:

{QUOTE()}
[Tikiwiki-devel] New documentation file: Tiki198alpha.pdf
From: Xavier de Pedro Puente <xavier.depedro@ub...> - 2007-06-17 16:44

(...)

There are some issues that, it solved from coders, they would make
easier to produce next documents like the pdf ones:

(1) Page Title is not automatically shown on wiki pages on the server,
and thus, manual header1 was added everywhere (Almost). But when
printing to html, page title is duplicated. => if Show Page Title option
is disabled under "Admin > Wiki", Page title should not be added
automatically at print-to-html time.

(2) to produce the same structure (same level structure of headings) as
in table of contents http://doc.tikiwiki.org/Documentation , some hack
(optional) would be very welcome so that heading 1 in doc.tw.o pages is
not printed as heading 1 in through the multiprint, but as header 2, at
least. (optional).
This is, for instance, what is produced when printing a full structure
from a Workspace - AulaWiki Mod - : a coder could grab the code from
AulaWiki Mod as a reference....
In there, the description of the page is set as the Page title (header
2, I think), and the page title is included below for completeness (in
lower font, and with version number next to it)...

edutwo_ws_print_structure4.png

(3) Numbering of headings: somehow, in Workspaces this is handled
internally, and the user/documenter doesn't need to bother with manual
numbering: it's produced also at print time.
[http://edu.tikiwiki.org/tiki-workspaces_view_structure.php?print=4]

Example of print structure differences between Tiki's multi-print and
Workspaces print structure:

Print to html "Aula-Wiki Tutorial" from here:
[http://edu.tikiwiki.org/tiki-print_pages.php]

or from here:
[http://edu.tikiwiki.org/tiki-workspaces_view_structure.php?print=4]

Well, as you could imagine, some changes to the code to make the work of
documenters a bit easier would be very wellcome also... :-)

(...)

{QUOTE}

!! (2) Update July 20th: Easier solution
Easier solution: Get levels for first heading in each wiki page of the structure not from the content of the page.

^__Example__: a page may start with a "! Title of page" (first level heading), and after that, "!! Subtitle of page" (2nd level heading), ...

Imagine that this page corresponded to "2.3.1 Module whatever" as the level in the table of contents of such structure.

The solution would be then that "!Title of page" (in that page "2.3.1 Module whatever"), when sent to (or fetched by) tiki-print_pages.php as a whole structure, was converted to "!!! Title of page"; and "!! Subtitle of page", should be converted to "!!!! Subtitle of page"..., and this way sequentially for all the title headings on each page from the structure...
^

The procedure below should become a 1-click from wiki (structures) to[http://doc.tikiwiki.org/Tiki19beta.pdf|PDF]. Please see:[http://doc.tikiwiki.org/Printing+the+Documentation|How to produce the .pdf out of the .odt]

-----

Dec 13 2008. Update:
Previous problem is fixed. However, I notice that automatic numbering with heading within a page (!!#, !!!#, ...), should be also considered in the global autonumbering.

Plus width of wide images and tables would be better if not that wide when exported to html (maybe an option), for the case when you plan to import it to OpenOFfice, and they are too wide to the document. Should this be another RFE or bug report?

---
REOPENING BUG
update on Jan. 7th, 2009:
See the other bug report: autonumbering didn't work for me with doc.tw.o/Documentation, even if it did a month ago on another site/structure

Related (and newer) bug report/RFE:
[http://dev.tikiwiki.org/bug2255]

When the system is set up to use staging & approval and the Structures are turned on, pages/topics created using the Add Page feature included with Structures get created with a staging name. The structure fails/disappears when the page is approved (fails in that the structure loses the staging name and does NOT substitute in the page without the staging name).

Here:
http://doc.tikiwiki.org/tiki-index.php?page=Structure&structure=Documentation -> structurs is 8.48

Yet, here: http://doc.tikiwiki.org/tiki-index.php?page=Documentation&structure=Documentation , it is 4.31


I don't understand the 8.48

Should be 4.31, no?


See related chat log:
http://irc.tikiwiki.org/irclogger_log/tikiwiki?date=2008-12-16,Tue&sel=315#l311

Tiki trackers are great for a bug tracker, as we are dogfooding here.

But what about for a "help desk" setting? -> Private requests from many customers to one company.

Imagine a hosting company. They may have public forums & trackers. But they also have a place where customers can ask direct support requests. And only the customer and the company can follow this tracker.

There is a way for people to just modify their own tracker. But this is more for a user profile, than a series of support requests.
http://doc.tikiwiki.org/tiki-index.php?page_ref_id=3204

You can also give permission to add a tracker item but not view. But they can't modify existing tracker items. (like sending in a black hole)

If we want people to submit many tracker items, but only see/edit their own, what should we do?

Currently, there is and option "Item creator can modify his items?" at tiki-admin_trackers.php

Maybe we need one: Only item creator can view his items?" Of course, staff working for the company would be admins and could see the trackers for all companies.

Or there could be login drop-down, and only that user can see. Even nicer would be that it's possible for people of the same group to see.

Maybe this possible with the current feature set. In which case, just documentation is necessary.

Some things to experiment:
"My items" in tiki-my_tiki.php

Current workaround is to make a tracker for each customer.

Please see: ((Issue Tracker))

---
Related:
Trackers need "tiki_p_trackers_view_own" permission to view own items only
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=211

If install script fails (for some reason), we should at least let user proceed with manual installation.

when performing a search only the first page of results is available, the pagination links at the bottom of the page do not navigate to the subsiquent pages.

TikiWiki Powered Sites listed [http://info.tikiwiki.org/tiki-browse_gallery.php?galleryId=1|here] contains many websites which are moved away from Tiki, for example [http://wiki.kde.org|KDE Wiki]. A total clean up of invalid websites is required for the listing.

This is an ongoing task.

It will never be finished as we are always adding more features :-)

Info:
on tw.org the naming convention is to use a ,xx suffix where xx is the lang code. For example ((Home)) is linked to ((Home,fr))

The comments on the page ((doc:permission)) report a couple of typos that should probably be fixed since they claim to date from March 2006.

People want to help Tiki.
Tiki needs more energy.

Let's make it easier to connect!

1st thing is to review all documentation. Make it faster/simpler/easier to transform a casual user into an active contributor.


1- http://tikiwiki.org/Participate

2- Update documentation at ((tw:ReportBug)) and at ((tw:RequestEnhancement))

3- All links/info on dev.tw.o

!!Problems

__Pretty Much Resolved by the wiki ALIAS function__ - so closed.

Redirect plugin
*is not included by default in TikiWiki because it could be used for bad things
*creates redundancy (in search results, page listings, etc) - maybe redirected pages should not appear in list?

Renamed pages
*do not automatically redirect - creates broken links.


!!Proposed solution:

!!!renamed pages
*When a page is renamed the user must choose "hard or soft redirect" perhaps better known as "redirect or refer from old page?"
**hard redirect places redirect plugin on pagename-old to pagename-new.
**soft redirect puts something at top of page like
^This page has been renamed: pagename^


!!!Add synonyms/aliases to a page

suggestion (mlp): adding aliases to a page should automatically create pages with hard or soft redirects to pagename. Note that the adding of alias pages must not destroy data if page already exists.

Ex.:
dev.tikiwiki.org/Tracker
dev.tikiwiki.org/Trackers
dev.tikiwiki.org/Bug tracker

would be aliases. It would avoid the pollution we have here: http://dev.tikiwiki.org/tiki-orphan_pages.php


doc.tikiwiki.org/Install
doc.tikiwiki.org/Installation
doc.tikiwiki.org/Installer

Each wiki page should be able to put one or many aliases. These aliases would work in search. All the aliases should have an important weight in the internal search engine.

We could use this instead of renaming pages. Also, when we do rename a page, we could have an option to have the old page name to be an alias of the new one. Thus, better for external search engines.

Theses aliases could even be used as meta tag for this page.

Putting aliases to non wiki pages (ex.: tiki-forums.php) would make ((doc:structures)) more useful. Now, using structures for site navigation only makes sense if you only have wiki pages. And who ''only'' wants to have wiki pages with all the great features offered by TikiWiki? :-)

It also help to use cleaner page links in sentences. If my Wiki page is called Install, I have to do the following now:

{img src=images/code.png}%%% {CODE()}
For more information about ((Install|Installation))
{CODE}

With aliases, I could do:
{img src=images/code.png}%%% {CODE()}
For more information about ((Installation))
{CODE}

Page aliases - and hard redirects - should permit to set status "Moved Permanently" for robots to send traffic to main page.

What would we do with page renames? (which correct links in wiki pages). Needs some thought. We don't want some unwanted changing of text in existing wiki pages.


Do we need?
Redirect to internal or external http is ok because a special permission is needed to use. -> tiki_p_wiki_alias . In security admin, warm that giving tiki_p_wiki_alias to untrusted people is a security risk.


Related:
[wish1119|Better handling of page renaming]
[wish1610|Redirect plugin : should permit to set status "Moved Permanently"]
[wish1292|Plural WikiWords when using ((WikiWord))]

In 1.10, there is a "minor" button when you save a wiki page.

When using the wiki for translation, checking minor tells the system that the corresponding translation are __still valid__.

I believe __minor__ also prevents sending notification emails to those watching the page. (why bug them for a corrected typo?)

You can get to help easily enough, but it's kind of hard to find the "wishlist" page.