Category: 2.x

The goal of having a newsletter system with group & permissions is that many different people may send newsletters.

Until 1.9.2, the "from" email was always the system email. In 1.9.3, the "from" email was corrected to be the user actually sending the newsletter.

We could have general options, overrideable on a newsletter-per-newsletter basis.

A- System default email
B- Email of person sending the email (so this person gets the replies)
C- Use a specific email (part of newsletter settings)

Selecting "Admin/Admin Home/General/Theme/ChaSelecting "Admin/Admin Home/General/Theme/Change Style Only" does not refresh the screen with the new theme.
Selecting "Change Style Only" twice shows the new theme.
Navigating to another page shows the new theme.
I wonder if it is a PHP cache thing.nge Style Only" does not refresh the screen with the new theme.
Selecting "Change Style Only" twice shows the new theme.
Navigating to another page shows the new theme.
I wonder if it is a PHP cache thing.

I can not find the ability to receive an email notification when a table gets changed.

It would be very useful if this capability were part of tikiSheets. Several other tikiwiki features have this feature through the watch capability.

{syntax type="tiki" editor="plain"}
When I configure webmail all is right but no mails sent appears on mail box. Is this a bug or misconfiguration ? Thanks.

Please see:
http://www.wikimatrix.org/wiki/feature:nofollow
http://googleblog.blogspot.com/2005/01/preventing-comment-spam.html

The Export feature is nice, but it would be nice to export/save wiki pages with html formatting intact. A way to edit offline then sync changes would be even better, but for now, I'd settle for a way to just view pages offline.

ML: You can ((doc:mail-in)) and ((doc:watch)) (mail-out), but no true sync

XML-RPC? IMAP?

http://www.socialtext.net/help-en/index.cgi?working_offline_with_unplugged

See: ((Offline))

Would be really nice to combine with an encrypted password manager for offline storage -> ((User Encryption))

On a new 1.10 installation...

When logging in as the ADMIN for the first time, the Change Password Enforced page appears (requiring new admins to select a new password). The OLD PASSWORD field should be maintained (pre-filled) with the existing admins password (by default: ADMIN). This __used__ to be the case in 1.9.

Pre-populate the OLD PASSWORD field with the user's existing password. This field should be disabled, so the user cannot change it.

When using the files wikiplugin nothing appears in the wikipage when previewed or saved in v2.x. When posted on the forum Sylvie sent me alternative plugin files which enabled the plugin to be used once on the page. But if the plugin is used more than once on the page, the page is completely blank (whitespace). PLease see the forum post for details: http://tikiwiki.org/tiki-view_forum_thread.php?comments_parentId=22894&topics_offset=22&topics_sort_mode=lastPost_desc&forumId=4

PLease note I am using TW on Windows (IIS) with MySQL but have recreated the bug on the opensource CMS demo.

Once a language has been selected for a page there is no way to set it back to its original state with no language associated with it. This is not that big an issue, but once you select a language you are stuck with the multilingual menu item at the top of the page, even if there are no other translations available.

I think it is preferable to have a link on the top of the page only if there is an available translation for the page. Regardless, it is bad practice to allow a user to change something with no way of returning that something to its original state

{syntax type="tiki" editor="plain"}
Hi,

I have set the following permissions for Anonymous

tiki_p_view
tiki_p_view_categories
tiki_p_view_categorized
etc

and the following category permissions

Anonymous tiki_p_view_categories
Registered tiki_p_admin_categories

Assign permissions automatically: Yes

Despite this neither Anonymous or Registered can view pages that have been categorized, the categories appear empty. Only way I can change this is by changing permissions on each individual page.
I've tried and tested this on 3 different installs, same problem each time. I am quite new to this but have spent many hours on this issue and would appreciate any advice.
I'm sure that there's a way but how?
Cheers

Wiki in question can be viewed at www.paddypaedia.com

There is a very common use case where a specific Group should be given User admin permission, ie tiki_p_admin_users, so that the setting up of new users can be delegated.

However this permission allows the user with these added permissions to edit the admin details and therefore be in a position to assign new users and themselves to the Admins Group - which has 'security' (in the broadest sense) implications.

Changes that avoid this are needed so that the admin details can only be changed by the admin.

FIXED

Not sure if this is a small bug or a feature request - but now that I have used the very useful Dynamic Variable feature in a number of sites I realise that a quirk of the feature is that only the first instance of the use of an individual variable in an individual wiki page is editable.

If you use the same variable a number of times in an individual page then the 2nd and any subsequent uses are not linkable to the edit facility.

This seems a bit inconsistent and it would be much more useful if any/all instances could be used to update/change the variable.

If this is unavoidable then it would be useful to declare this in the documentation.

Closing this as its not that important any more (Geoff Aug 2013)

When using OpenID + Registration CAPTCHA...
With Tiki 2.2...

I attempted to register using my OpenID:

#On the Login page, I entered my OpenID.
#My OpenID was validated and Tiki shows the page where I can either associate my OpenID with an existing Tiki account, or register as a new user.
#I completed the registration form (including the correct CAPTCHA), but Tiki keeps saying that the Anti-bot code was incorrect.

Additionally, the registration form presented with the OpenID __does not__:
*Display the password minimum requirements (such as number of characters).
*Allow for the selection of groups.


__Duplicate of {wish id=1505}__

For sites with open content it's very important that a visitor who came through a link from search engine or somewhere else would have minimum problems with adding new information to the wiki.
My personal example: I have a blog on livejournal.com and now plan to create a homepage based on tiki, but I don't want to make all of my friends from LJ to pass registration on my site. Even if they all would, it's unreal to make them all use the same logins as there.

We are documenting some ((info:Use Cases)) which will become profiles. To be able to developer/test/improve these profiles, we would need a site like [http://www.opensourcecms.com/index.php?option=com_content&task=view&id=180|Open Source CMS] but for all profiles. This site only shows one profile.

These 20+ demo sites would provide admin access to easily test any profile. It would encourage people to generate and improve various profiles as well.

Related:
((Profile Manager))
((TRIM))

In order to avoid duplication of effort, It would be very nice to be able insert a calendar item when editing an article in Tiki.

I imagine that as a new option in article edit form, for any article type or just some type, like "event", or so. You should be able to select the date or dates to insert that info in the calendar feature, select which calendar, etc.

So that calendar and upcoming_events module is updated when a new article is posted with that option selected.

When sending newsletters, Tiki sends as HTML. However, if the recipient does not accept HTML, the newsletter may become malformed for the recipient. For example, the EXTERNAL LINK text becomes merge with URL links.

I would like an option to send the newsletter as "plain text", thereby stripping out all HTML from the newsletter.

For WiKi pages I use the WYSIWYG (FCKEditor) but this is not an option for Articles. There you can only use the simpel Text Area and Quicktags. It's must better if you can use the WYSIWYG (FCKEditor) for every text input.

http://sourceforge.net/projects/orgapp/

See details here:
http://tikiwiki.org/OrgChartDev

Many times, I don't want the Orphan page feature. But I do want the list pages. Since they now use the same option (feature_listPages), it's annoying.

Let's create feature_OrphanPages (off on a clean install). Menu items will need an update.

{syntax type="tiki" editor="plain"}
Attempting to use Opera or FireFox to call a tikiwiki page generates some % characters in the path and gives an error.

Using Internet Explorer this does not happen.

We need to be able to allow other BROWSERs to work with Tikiwiki pages.

This problem is not present in Version 1.9.11

As a result I cannot upgrade to version 2 or higher yet

the output of {maketoc} in Wiki is not contained in a special
DIV so one can not define a style for displaying it for example in a box or ...

{syntax type="tiki" editor="plain"}
I'm using staging and approving wiki pages and recognized, that the page description disappears under some conditions. I tried to find out this "some conditions" and hope to give sufficient informations:

* First a user or admin creates a new (wiki) page with description.

* The page is saved as staging page with the description.

* If the page is edited before approval (by user or admin), the description remains in the field.

* If the page is approved by an approver (= user with permission), the description remains in the field, too.

* If the page is approved by admin, the description is away.

* If the approved page with a description (equal, if approved by an approver or by admin with rewriting of the description) is reopened for edit, the page description field is blank.

With "page description disappears" I mean, that

a) the description is not saved when approving the page by admin and

b) the description field prior filled with a description is then blank, when the page is opened for editing (after approval).


__TikiWiki version:__

* 2.1 new installation

__Staging and approval settings:__

__Group permissions:__

Anonymous

tiki_p_view
tiki_p_view_categorized

Registered

tiki_p_wiki_view_history
tiki_p_wiki_view_source

Editors

tiki_p_view_categories
tiki_p_lock
tiki_p_minor

Approvers

tiki_p_rename
tiki_p_rollback

__Category permissions:__

Staging

Registered : tiki_p_view_categorized
Registered : tiki_p_edit_categorized
Editors : tiki_p_view_categories

Approved

Anonymous : tiki_p_view_categorized
Editors : tiki_p_view_categories
Approvers : tiki_p_edit_categorized

__Wiki staging settings:__

Use wiki page staging and approval : yes
Category for staging pages : Staging
Category for approved pages : Approved
Category for pages out of sync : none (see group settings above)
Force bounce of editing of approved pages to staging : yes
Delete staging pages at approval : yes
If not in the group, edit is always redirected to the staging page edit : Approvers

__Group settings:__

Default category assigned to uncategorized objects edited by a user with this default group :

Registered : Staging
Editors : Staging
Approvers : Approved

__Other Wiki settings:__

Page description: activated/checked
History only for data, description, comment change: not checked
Individual cache: I tried with and without activating/checking - no difference

If you send a Tell a Friend link from a wiki page that has spaces in the page name, the link in the email is broken. For example, you'll get:

http://www.tikiwiki.org/tiki-index.php?page=tell a friend

Confirmed on latest SVN as of 04/22/2008

Page name like
{CODE()}
((Unix Install - Information))
gets parsed with the <code> in it
{CODE}
Changing order of parsing may not be best solution at this stage. changing urlencode to rawurlencode may also not be ideal. Need elegant solution.