Category: 2.x

Tracker can be (and are starting to be) used for creating forms of offers and demands in communities... (knowledge banks, time banks, openmoney....)
In our case, from tracker demands there is a field linking (through "item link" field) to tracker offers (a demand in the demands tracker can be for a specific offer already inserted in the the offers tracker).

In this case, it's needed that (optionally) a inter-user message is sent to tracker item creator when that item is automatically linked from another tracker item (from another tracker, in our case).

Other way, it's hard for a user to know if another user has requested some of this offers...

http://moviments.net/intercanvis/trackers (1.10cvs)

http://moviments.net/valldelcorb/trackers (1.9.7)

It should be like this feature (tiki-send_blog_post.php?postId=95), but generic for all pages/features on a Tiki site.

Related: we need anti-bot code so spammers don't abuse it:
tiki-view_tracker_item.php?trackerId=5&itemId=546

At this site: http://www.moviments.net/ilp/
We had a file gallery called "Actes d'Assemblees i reunions" (without the surrounding double quotation marks)
http://moviments.net/ilp/tiki-list_file_gallery.php?galleryId=3

There was a child file gallery called: "Assemblea 080907" (without quotation marks)
http://moviments.net/ilp/tiki-list_file_gallery.php?galleryId=9

When I tried to upload a file (xls, "estat comptes.xls"), the server restarted in the middle of the upload and Firefox showed a "connection reset while loading page", etc.
I couldn't load other pages of this site or others on the same server for some seconds, but later on, server came up again.
So I could load other pages of the same tiki site. Then I tried again doing the same, and same behavior after attempting to upload that file: server restarted, etc.
After reloding file gallery, no file was uploaded, etc.

Then I went to the parent file gallery, and deleted at least the single quotation mark from the name, leaving that name as: "Assemblees i reunions"
Then the file could be uploaded with no problems at all on the child file gallery "Assemblea 080907"

This is the file, in case you want to reproduce with the same file, just in case:
http://moviments.net/ilp/tiki-download_file.php?fileId=20

{THUMB(id=23, url="tiki-browse_image.php?imageId=23")}Share page bug on BRANCH-1-10{THUMB}

{THUMB(id=24, url="tiki-browse_image.php?imageId=24")}{THUMB}

I can no longer reproduce this behavior in 1.10. Please retest. Dave Thacker

In TikiSheet: I'm trying to have 'T' or 'true' shown when two other columns have the same value. But =(H3==K3) when saved shows "true=(H2=". Note the truncation; the truncated stuff shows up in the expression field on the edit screen. Before being saved the cell shows 'true'. Adding a conditional ("?:") expression wrapper did not help.

Also, a spreadsheet could not have rows added to it until a similar expression was removed from the spreadsheet.

Show Category Path + Show Category Objects was implemented a long time ago, and somewhat in a rush. One of those temporary things which became permanent. It only works in wiki pages, yet it would be logical to have this throughout the various features.

Seeing the list of items in the same category is very useful as contextual navigation.

Mouse over summaries here is OK:
http://dev.tikiwiki.org/tiki-view_tracker.php?trackerId=5

But not here:
http://dev.tikiwiki.org/Rating

The mouse over functionality has not yet been coded in the trackerlist wiki plugin.

Seen on IRC:
{img src=images/code.png}%%% {CODE(wrap=>1)}
(10:33:47 AM) ***dthacker also wonders if there is a login-timestamp wiki syntax such as mediawiki's ~~~~ that would auto sign with user id and date/time.
{CODE}


Wiki pages are great to produce Neutral Point of View (NPOV) content. If we need to know who added what, we check the edit history.

For debates, discussions, opinions, etc, people will often use Tiki blogs, Tiki forums or comments at the bottom of wiki pages. These are more natural formats and it's clear who thinks what and who said what. Comments & forum threading make it clear who is responding to who/what.

However, in some cases, it is useful to have this type of interaction in wiki pages. The [http://doc.tikiwiki.org/Editorial+Board|TikiWiki documentation Editorial board] has monthly meetings to discuss and make decisions. Members can edit, comment and vote on motions.

The way people add their comments is not standard and if we are not careful, it can get messy. This often happens in wikis.

Some wikis use a special syntax for "signature". This would be a way to associate the name of the user and maybe the date to a specific comment. It would be nice to clearly and visually associate the user to the comment. Maybe the comment & signature are in a same box?

It would be nice also for people to be able to express support to an idea in the wiki page, with a thumbs up (+1) or a thumbs down (-1). Right now, the wiki ratings feature let's us vote only once per wiki page.

These syntaxes should be quicktags to it's easy to add. Maybe some of the less important meta data (ex.: date of comment) would be only visible on mouse-over. (and thus not in printed mode). The mouse over could also contain a link to the user's personal wiki page and some data about the user (his avatar, score, etc).


Ex.:
*click my PluginComment tool (in toolbar)
*Pre-fill text that will be mouse-overed with previously selected text
**add date & signature (with link to userpage)


Everyone: please share your ideas on this and how you have seen it implemented elsewhere.

Thanks!


Related:
{wish id=2102}

a) I spent weeks testing these features one by one.

It will save time if all these features are enabled and complete with samples.

This is the approach used by Joomla and Mambo.

It also helps us learn faster.


b) The assist module is useful but asking users to read a tedious configuration as the first step will eat up too much time.

Site configuration or Look at Feel should be the first one.

It is also the most dangerous but essential.

c) Provide a clue, in the assist if possilbe, to replace a damaged header.tpl with a skeleton header.tpl

The Site menu bar in Site Identity can be turned on (checkbox), but there's no textarea to input the code to be used for the menu bar. (Nothing is displayed at two of my 1.9.7 sites, anyway.)

When set, the template should use {eval var=$sitenav_code} and I guess this should be stored in the tiki_preferences table. But there's no way to input it. Seems like tiki-admin.php?page=siteid needs a textarea similar to the one for custom code content for Site nav code (PHP Layers menu tag, etc.)

Related:
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=1320
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=1178

Should the site map be generated from the wiki structure? from the menu?


https://www.google.com/webmasters/tools/docs/en/protocol.html#sitemapOverview
http://www.sitemaps.org/

The first problem (maybe local) is that the ad checkboxes on tiki-admin.php?page=ads tend to not stay checked. Please confirm if this is true for other users.

The bigger problem (on two servers): when I switch the logo from left to right on the Look & Feel admin page, the ad checkboxes on tiki-admin.php?page=ads get emptied. Maybe any update on Look & Feel resets the ad activate and publish checkboxes to empty; I didn't check.

Also, on the ads and banners admin page, only the bottom "Apply" button works, for me.

Site header banner ad configuration worked before it was split off as a separate page, afaik. Maybe a bug was introduced by the move to its own page.

This was not in 1.9 and I don't want this feature for most of my sites.

A lot of people who install this aren't doing it via Fantastico and trying to change email settings to suit your hosting provider is a pain. Editing the php.ini isn't always wise either because what works for one app will break another. I know that you can copy the php.ini to the directory, but that's something of a security risk. There's a reason that the default php.ini is stored outside the web root directory.

I know that I see a lot of users posting on the TikiWiki forums with questions about configuring SMTP.

While Tiki has a "friendship" feature, it is so basic, that I am putting as "missing". What is missing is proper Social Networking with "transactions" between community members (Ex.: [http://www.nomadics.it/|hospitality exchange network], carpooling, dating service, etc) with reputation system. Something like LinkedIn, Facebook or the www.phpbeer.com project.

Since this is a vast project, we'll coordinate at ((Social Networking))

After adding the following to wiki pages it stops them rendering.


{CODE(caption=>~np~ bash ~/np~)}

LOCATION=smb://server/directory/
IFS=$'\n'
for SONGS in $(find -type f |grep .mp3 | awk 'sub("./","") {print $0}';find -type f |grep .wmv | awk 'sub("./","") {print $0}'; find -type f |grep .ogg | awk 'sub("./","") {print $0}')
do
echo $LOCATION$SONGS
done
{CODE}

Some of the preinstalled themes seem to be incomplete:
I have the word "loading..." in the top left corner of each page.

Check: http://list.vic-fontaine.com/
(test user/pw if needed: smarty)

I found this forum topic:
http://tikiwiki.org/tiki-view_forum_thread.php?forumId=6&comments_parentId=32558&highlight=loading

However, in this case, preinstalled themes are affected.
For example:
bluegreen.css: error
boreal.css: works fine
brtiki.css: error
codex.css: works fine
etc...

In Tiki 1.10, there is a feature to protect all emails against spam harvesters. Great.

1- Check that this protection is indeed powerful (so spammers can't get around it)

2- Have an option to show an image of the email when javascript is not available.

3- Extend this protection to [tiki-view_tracker_item.php?itemId=1147|the e-mail address in tiki-contact.php]

Wiki Syntax for special characters seems to fail in 1.10 (I can get it in WYSIWYG). Thus, ~np~~169~~/np~ no longer shows the copyright symbol.

The problem appears to lie in TikiLib - parse_data
if (!$simple_wiki and $prefs['feature_wysiwyg'] == 'n') {
$this->parse_htmlchar($data);

Here's this issue - I have WYSIWYG set to Y, but NOT showing by default. It seems that the test should be whether WYSIWYG is actually showing - I have no idea what the variable is.

{syntax type="tiki" editor="plain"}
entering the words "visual studio" in the search_box module causes the following message to be returned in the UI:


An error occured in a database query!

Context:
File tiki-searchresults.php
Url tiki-searchresults.php?highlight=visual+studio&where=pages
Query:
select `data` from `tiki_dynamic_variables` where `name`=?
Values:
0 comspec
Message:
Table 'tikidb.tiki_dynamic_variables' doesn't exist
Built query was probably:
select `data` from `tiki_dynamic_variables` where `name`='comspec'

spellcheck should get lang from wiki page lang, not from users' interface language, or elsewhere.

For instance, I have firefox in catalan, tiki lang pref. in catalan. If I edit an English page in doc.tw.o site, and I clikc on spellcheck, Tiki should search for dictionary tables of English lang, and nowadays it searches for Catalan tables on db.

----
Update: I confirm this is still happening. On doc.tw.o, for instance...

---------------------------
Context:
File /tiki-editpage.php
Url /tiki-editpage.php
Query:
select `word` from `babl_words_ca` where `word`=?
Values:
0 Tiki
Message:
Error Message Table 'doctwo_doctwo.babl_words_ca' doesn't exist
---------------------------

The tiki_p_admin_trackers permission is needed to both edit the main attributes of a tracker and add/change fields etc., as well as to Export or Import csv files.

This means that when it makes sense to allow some users the privilege to Import and Export data in batch mode then they will also have edit access to the field structure etc which may not be appropriate.

Hello there,

I just upgraded our TikiWiki from 1.9.11 to 2.0. I am really happy with 2.0 by the way! Way to go!

Everything went well during the upgrade, except that I get this error message every time I try to administer our categories:

http://dev.tikiwiki.org/tiki-browse_image.php?imageId=52

Everything else seems to have upgraded just fine. Yes I did follow the instructions during the tiki-install.php and run the 1.8 -> 1.9 SQL script prior to the 1.9 -> 2.0 SQL script. I noticed that there were around 150 SQL "errors" during the upgrade script, but I thought nothing of this.

Thanks a million!
Russ
rfruhwirth2@unl.edu

Every time a new object gets created (wiki page, blog entry etc) the item recieves only global permissions.

It would help a lot if the admin could define 'standard permissions' for each group for specific features.
(needs to be integrated with improvements to "permissions by category" introduced in 1.9 - which provides a coherent approach for "object" based permissions to compliment user based perms.)

To keep wiki pages inside the group, the admin would assign the read right only to that group, and a member of that group posting a new item would not have to worry about security as much.

Am not sure what to do when user is member of multiple groups... maybe she can select in a drop-down which is the one that wins, or maybe the admin determins that when creating the user?

Reccomendation: Inherit permissions. (particularly for wiki)
The default behavior for a new object should be to inherit permissions from the page it was created from (global if none). Particularly in a wiki, this would facilitate the use of "private areas" - key feature for tikiwiki as groupware so committees. groups, etc. can operate in privacy, if so desired. Whoever create the page should be able to disable this inheriting, but it should be on by default. Admins can then create private wiki spaces by customizing perms on one page (the group home page).

This is best explained with an example:

~pp~
Paragraphs are parsed

just fine here

{TAG(tag=ul)}foo{TAG}

but now

paragraphs and

line breaks aren't working!
~/pp~

This only happens for tag=ul, not even for tag=ol.

This happens regardless whether wiki paragraph formatting is enabled and regardless of whatever is inside the ~np~{TAG(tag=ul)}~/np~, even ~np~{TAG(tag=li)}~/np~'s.