Category: 2.x

{syntax type="tiki" editor="plain"}
mod-last_modif_pages should not list the sandbox page.
Users could confuse it for real content.

Here, look. I'm going to link to this external page: http://www.casarizoma.org/wiki/tiki-index.php

[http://www.casarizoma.org/wiki/tiki-index.php]

See the extra "external" that got appended in the link (instead of after it)?

Theme control by category not working for me, on 1.10svn site updated to today May 8th. It used to work before, but I don't know when it stopped working (months ago??). I hadn't used the feature for a while

---
Addenda:
Maybe this is related to this other [bug1749] ?
The categorized object was a tracker...

Right now you can set theme control by many type of objects, but not trackers.
For forms to get information from new users, it might be useful to allow using some different and customized theme for them.
A possible solution is using wiki pages (which allow theme control by object), and tracker plugins inside; however this does not work for all tracker fields, so the option to set trackers at theme control by object is still desireable (imo)

You want a Tiki-powered site but none of the bundled themes fit with the look & feel you want for a project? You would like an easy way to generate a style? Me too!

I have a (crazy?) idea for a Tiki CSS generator. Before I explain it, please visit the StrangeBanana:
http://www.strangebanana.com/

Ideal end result would be: 1- submit logo or picture, 2- a corresponding CSS is generated, 3- result can be visualized from demo site and 4- then just use the custom css on your site!


http://themes.tiki.org/TikiThemeGenerator

Themes using the old preference format do not work/show in 1.10. While we want people to upgrade themes to 1.10, legacy mode should be enabled.

Please check this out on other Windows servers, but on my Windows XP WAMP setup, theme information isn't working right. The switch-theme module shows no style being used. Trying to select a theme in the module has no effect. Theme selection works normally with userslib.php CVS version 1.247.2.23, but as of version 1.247.2.24, it's broken. (Comparing the files shows the lines involved. To work with themes I have to be careful about updating userslib.php.)

{syntax type="tiki" editor="plain"}
Although there are permissions such as tiki_p_create_galleries there is no tiki_p_edit_image_galleries.

So a group with tiki_p_create_galleries permissions can add a new image gallery but cant edit the description after they have added it. Which is a problem if they made a mistake.

Trying to start using Images Gallery on a fresh 1.10 install on a Ubuntu 7.10 Server/Apach2/PHP5 platform. All image files are JPG.

__GD__
GD ("2.0 or higher" per phpinfo) was installed with the platform and Tikiwiki seemed to recognie it, but functionality is not right.

If I upload an image from a URL, I get a thumb sized as predicted. However, if I upload a local file I get a 100% sized thumb.

If I choose to "rebulid thumbnails" all thumbs are made 100% sized.

__Imagemagick__
I installed it (2.0.0-alpha per phpinfo) and it's PHP module using apt-get and restarted the whole system for good measure.

Uploading an image from URL or local file is the same. I get what appears to be a white, 2x10 pixel thumbnail and image.

If I choose to "rebuild thumbnails" there is no apparent change. If I only switch back to GD and choose to "rebuild thumbnails" I get perfect looking, though 100% sized thumbs again.

Image Gallery does not have Tiff support, let alone raw formats! A revamp should include some tool to insert/use metadata from the imaga files.

{syntax type="tiki" editor="plain"}
The Tiki date library does not implement the %l (lower case "L") for time.

{syntax type="tiki" editor="plain"}
The __Redirect__ plugin takes two parameters:
* page = foo (to redirect to a wiki page)
* url = http://foo.com (to redirect to any other page)

However, Tiki sanitizes the __url__ parameter, creating url, which breaks the plugin's redirection.

I think what's needed is a Gallery of "Tiki Sites in a Box". In other words, Tiki sites that are preconfigured to meet a particular kind of needs. The needs should be defined not in terms of features, but in terms of GOALS of the end user or organisation.

This could be a list of descriptions like this:

- I want a site to enable collaboration inside my organisation.
- I want a site to broadcast my ideas to the world and allow people to add to them and comment on them.
- I want a site that will act as an open knowledge base on a particular topic.
- etc...

Each of these could point to an example which would be a "fake" site that could act as a sandbox. People could go to this fake site, play around with it (but not reconfigure it), to see if it's what they are looking for.

This would allow easy single click configuration of Tiki. The user would simply click on one of the items in the Gallery, and the Tiki site would be configured accordingly.

One issue is: what happens if the user choose wrong and later wants to switch to a different model? I guess if no content has been created in the site it's fine, but what if content has already been created and that content is somewhat incompatible with the new model that the user is choosing?


Related:
*[tiki-view_tracker_item.php?itemId=1513|OpenSourceCMS type demo to test/develop and show off profiles]
*[http://info.tikiwiki.org/Use+Cases|Use Cases]

__Moving discussion of this wish to ((Profile Manager))__

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

This tracker item could not be found

'Shared' contacts don't shared the field names. If userA creates an entry with a 'custom' field of 'Company' as 'The Smith Company', we see this in the db:


||contactId|fieldId|value|hidden
1 | 7 |The Smith Company|0||


The problem is that other users do not 'inherit' that custom field: so other users seeing that record will see no description of the field name. Indeed, if another user chooses 'Company' from the list of fields to add, it will get a new fieldId:

||contactId | fieldId | value | hidden
1 | 7 | The Smith Company | 0
2 | 23 | Smith Industries | 0 ||

It should, especially for the predefined (semi-custom fields, like 'Company' and 'Street Address', defined in lib/webmail/contactlib.php) 'share' these values with others instead of creating new fieldId's.

As of Tiki 1.9.7, only Tiki admins (full admins) can manage Tiki menus. Yet, this is often something we may want to delegate to editors.

tiki_p_admin_menu would be very useful

If user watches activated (for all), any user is able to "watch" a tracker, so that he/she will receive an e-mail message with all the information from the tracker item, even if some field were declared as "hidden"... (sensitive info).

I already reported this at sf.net for 1.8 trackers. And I seem to see the same problem nowadays with Tiki 1.9....
This should be fixed for privacy of sensitive information collected through Trackers/forms

tiki_p_read_comments & tiki_p_post_comments exist in general permissions, but post is missing from specific wiki page override:

{img src=show_image.php?id=8}

tiki-admin_layout.php is totally broken for me in a 2.4 (using eatlon, btw)

http://www.ub.edu/optics/tiki/tiki-admin_layout.php
returns:
{CODE()}
An error occured in a database query!

Context:
File tiki-admin_layout.php
Url tiki-admin_layout.php
Query:
select `name`, `value` from `tiki_preferences` where
Values:
Message:
Algo est� equivocado en su sintax cerca '' en la linea 1
Built query was probably:
select `name`, `value` from `tiki_preferences` where
{CODE}

As preference syntax in tiki-admin.php?page=general, I have 2.0 - ...

So after I delete a quicktag, I am sent back to page 1, even if I was working on page 6

Say I want to follow all the action on a Tiki site, I have to register to several RSS feeds.

5 RSS feeds just on:
http://tikiwiki.org/tiki-index.php

And if a site activates a new RSS feed, I may not find out right away.

I would like a tiki-all_rss.php which combines all RSS feeds which I am allowed to see.

{THUMB(id=39)}{THUMB}

Steps to recreate in firefox:

1. Initialize site with a new database.
2. Lock setup and login as admin.
3. Click on pretty widgets and change theme.
4. Close Firefox browser. Browser's history cache is automatically flushed.
5. Attempt to log into tikiwiki as admin/admin.

Expected behavior appears to be a page where you are prompted to change the admin password. (Nice!) Actual behavior is blank page with "No input file specified" error. Error is always present

Steps to recreate in IE7.

1. visit tikiwiki url.
2. log in as admin/admin
3. IE7 generate "page cannot be found error"

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.