Category: 7.x

Please see: ((Federated Timesheets))

{syntax type="tiki" editor="plain"}
!Tracker :wishlist : When you edit an item you reaches a not sorted list as you have sorted it before

!!Fact
When you edit an item of a selected and sorted item list, you get the selection but not sorted.

!!solution and workaround
__
NONE __ So you need to :
*go back to list , kept in another tab of navigator
*edit separately each one


!!extension to
This can concerns all trackers for 6.x, 7.x

!!importance
This is very annoying to lost time when you are redacting and following your wishes list, quite a large one, if you can't navigate into item of your sorted list of your wishlist...


Good job
Best regards

Trebly
(ref:B10126-04)

- Imagine you have a record with ten fields, but you only have a 'n' in the last column. It is not easy to select this column.
- Since each field contains a separate field, it suggests that each brings you to some different page.
- If one link of a record is active, the record is not selected.

!Trackers - wishlist - lack of Return to list command (#....)

!!Fact
when you access from a list of items of a trackers, to go back to the list you need to restart from the beginning...

!!Details
As when you reach the item form you can navigate into the extracted and sorted list, you have no command (link, button) to go back to your list.

Then you need to do again your selection, sort again (see previous report #3765)

!!extension to
This concerns all trackers for 6.x, 7.x

!!importance
This is very annoying to lost time when you are redacting and following your wishes list, quite a large one

Good job
Best regards

Trebly
(ref:B10126-02)

{syntax type="tiki" editor="plain"}
!Trackers : wishlist : -> "edit:delete" access seems to be " a little random (#...)

!!Fact
When you access to your wishlist and then reaches the item panels (to edit) sometimes the "edit/delete" tab don't appears.

It seems partially to be in relation with the item color.

!!solution and workaround
__
NONE so Urgency__

!!extension to
This can concerns all trackers for 6.x, 7.x

!!importance
This is very annoying to lost time when you are redacting and following your wishes list, quite a large one, if you can't update your wishlist...


Good job
Best regards

Trebly
(ref:B10126-03)

{syntax type="tiki" editor="plain"}
__Wiki / Translate / Translate this page to a new language__

When creating a tranlsation of a wiki page by way of the "Translate this page to a new language" button, the following is automaticlaly inserted above the untranslated text trabsferred fromn the original page to the new page:

^Translation of this page is incomplete.^
I assume this is designed for the benfit of people reading the page (rather than those editing it) and as such I find it very useful for the following two reasons:

If you are using a site in one language, say English, and a page appears in another, say French, its very useful for the reader to understand that:
* nothing is wrong e.g. they haven't mistakenly navigated to the wrong page or changed their language settings, and
* the site editors are aware that the content requires translating.

The problem is that it displays in the wrong language (e.g.in our example above in English when the reader may only understand French). The reader needs to see "Translation of this page is incomplete." in their own language regardless of the language of the untranslated text beneath it, otherwise the benefits above are lost.

(Of course, the same should all apply to Articles but they don't seem to have the "Translate this page to a new language" feature yet - only the ability to link to another already created Article at present).

When watching the history of a wiki page, the two most recent versions are pre-checked. But, when watching the history of a spreadsheet no versions are pre-checked: http://demo.tiki.org/trunk/tiki-view_sheets.php?sheetId=3

After svn switching from trunk to 6.x, my wiki has internal server errors on certain pages, especially if I'm logged in.

I maintain my svn on a windows machine, and I zip up my image, ftp it to my linux server, unpack it, run admin upgrades, and clear the cache. After all that I can browse the site as anonymous, but not as an admin or editor.

I am considering switching back to trunk, as the bugs there are less serious.

{syntax type="tiki" editor="plain"}
Admin -> General -> Navigation - Use Tiki feature as homepage:

When i set this to a different feature then "Wiki" and go to http://mydomain.com
I keep getting send to wiki "HomePage".

The feature does get set in database and when you logout you get send to the set feature but not when you go to the domain name directly.

Also the drop down box never shows the feature that is last choosen when changing the set feature a few times it shows the 3th or 4th last feature that has been choosen after reloading the page it shows "Wiki" again although a different feature has been choosen and set in the database.

{syntax type="tiki" editor="plain"}
This isn't so much WYSIWYG as the wiki editor but see no such feature checkbox.

Anyway if you click a wiki editor button twice, like bold, I expect it to undo the action, like the WYSIWYG editor. Instead it tries to make the text doubly bold, which is apparently not possible.

Also if you use a button and drop focus from the editor, I expect the preview Ajax to update as usual, but it does not.

I have my wiki set to use MySQL full-text search, but since Friday it seems to be using PHP (Lucene?) search instead -- and failing.

It *was* giving an out-of-memory error. I switched Lucene from incremental indexing to bulk indexing -- which should not affect MySQL search at all. I then tried to build an index, which timed out after 60 seconds. (Not surprising: my wiki has 5000+ pages.)

Now my "full-text" search (using module="search_box") gives 0 results.

The watch object names for trackers in My Watches could be more descriptive -- i.e. use the subject name.

{syntax type="tiki" editor="plain"}
The plugin section of the wiki help is listing the plugins aplhabetically based on their english name. When it is translated to another language the sorting remains based on the english name, it is quite confusing and looks a bit chaotic in other languages in my opinion. Is there a specific reason why the code here is written this way? If not, can this be fixed for Tiki 4? I dont know how to do it but would appreciate it :)

Saving a wiki page gives a SQL error. It looks like a typo in the WHERE clause.

The query was:

SELECT `version` FROM `tiki_history` WHERE 1=1 AND `pageName` = ? AND `lastModif` < ? ORDER BY `version` Array
Values:

Using the Custom Component JavaScript Class V11
1295471823
The built query was likely:

SELECT `version` FROM `tiki_history` WHERE 1=1 AND `pageName` = 'Using the Custom Component JavaScript Class V11' AND `lastModif` < '1295471823' ORDER BY `version` Array

My administrators and anonymous users can see my wiki. My registered users and editors, who inherit base permissions from anonymous users, cannot see my wiki.

!Wishlist and trackers : sort default on display (# .... )

!!Fact
When you activate 'the wishlist' with 'list yours' but in fact in any case of selection, you get the order into the database...

!!Proposal
The list should have __a default sort order__ :
- __I propose here a reverse by item number, so the most recent is as the beginning
__
!!while it's not done
If not, you need :
#click on the column id, and wait
#click again to have the last submitted first or have to go to the end clicking again and wait...

!!extension to
This concerns all trackers for 6.x, 7.x

!!importance
This is very annoying to lost time when you are redacting and following your wishes list, quite a large one

Good job
Best regards

Trebly
(ref:B10126-01)

Problem: Corrupted URLs when linking pages using international characters in the page name.
It works when the link is first saved, but a reload and a subsequent saved will corrupt the URL.
The same problem occurs in 6.x 7.x and 8.0 SVN.

In these tests the WYSIWYG editor is used.
(I have formatted the output a little for better readability)

--- Test using latest 8.0 SVN version ---

1. Create the page "ÆØÅ page"
2. Create the page "MyLinkPage"
3. Add a link to "ÆØÅ page" on MyLinkPage, using the link tool in the menu
4. Save and exit editor

Content of MyLinkPage (wiki source view)
<p><a class="wiki" href="tiki-index.php?page=%C6%D8%C5+page">ÆØÅ page</a></p>

Content of MyLinkPage in the database (tiki_pages.data)
'<p><a class="wiki" href="tiki-index.php?page=%C6%D8%C5+page">ÆØÅ page</a></p>'

5. Edit MyLinkPage again <<<<<<<<<<<<< URL is no longer encoded, but the page name is

Content of MyLinkPage (WYSIWYG source view)
<p><a class="wiki" href="tiki-index.php?page=ÆØÅ+page">&AElig;&Oslash;&Aring; page</a></p>

6. Add some text in the WYSIWYG editor
added some text

8. Save and exit editor <<<<<<<<<<<<<<<< CONTENT HAS A CORRUPTED URL

Content of MyLinkPage (wiki source view)
<p><a class="wiki" href="tiki-index.php?page=%C3%86%C3%98%C3%85+page">ÆØÅ page</a></p>
<p>added some text</p>

Content of MyLinkPage in the database (tiki_pages.data)
'<p><a class="wiki" href="tiki-index.php?page=%C3%86%C3%98%C3%85+page">ÆØÅ page</a></p>
<p>added some text</p>
'

---- end of test ----

As far as I can see, the problem occurs when the WYSIWYG editor loads the page
(it works the first time, because the links are not loaded, only saved).

I tried a similar test using the wiki editor
The wiki editor stores the wiki content.
Thus database the content is: ((ÆØÅ page|ÆØÅ page))
The wiki editor has no problems.

A variation is loading the page using the wiki editor, then switching to the WYSIWYG editor
The source in WYSIWYG is afterwards

<p><a class="wiki" href="tiki-index.php?page=Ã?Ã?Ã?+page" title="ÆØÅ page">&AElig;&Oslash;&Aring; page</a><br />
added some text</p>

thus also corrupted the URL.

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

After a version upgrade (any data transfer etc...), if a dir containing gallery is forgotten in the new installation (nothing is perfect), it seems that there is no check when the gallery is loaded, this can (most of time) crash Apache.

nota : I have not tested for "files" only for "images" but I pur it into the the categories before I imagin that the problem exist on both.

Checked on 6.x and 7.1

The WYSIWYG editor should have a button to create HTML comments that will only be visible in edit mode, and not in read mode.

As with all HTML, the comment tags should not be visible in WYSIWYG mode. The commented text should be a different color; perhaps grayed out.

This feature would enable editing discussion to happen right within the page being edited. Editors could more easily reference the text under discussion, since it would be right next to the comments. Discussing pages separately in the forum would no longer be needed, or would be optional.

Feature request: Add an etherpad module to Tiki.

Etherpad allows __really__ real-time document collaboration for groups of users.
It's free and open source, with parts under Apache License 2.0, BSD, LGPL 2.1 and GPL 2.0 licenses.

On August 14 2011 the people at etherpad have released a jQuery plugin and a PHP class for easy injection of pads into web pages.

More at etherpad.org

{syntax type="tiki" editor="plain"}
I was logged in as admin and tried to post a comment to an article. I typed in a title and comment then pressed "Post as Anonymous." The page that comes up has no css, and at the bottom it says:

Fatal error: Call to a member function generate() on a non-object in /templates_c/en^%%C6^C6E^C6EF0FD6%%antibot.tpl.php on line 28.

The comment goes through fine.

Hi,

I have the idea for a new feature or better to say a major extension of the use of existing features.

Areas would be related with the usability of the Website, where you can assigne content to certain perspectives in a way, that a link to this content will guide you sametime aswell to the content as to the related perspective.

Anonymous users (and registered) would find the content in the context of menus and modules, the webdeveloper decides.

I see "Areas" Important for certain usecases, it could be built with up mainly with existing features - only few code should be necessary.

See more description on http:dev.tiki.org/Areas

Cheers
Torsten

Group watches works in 6.2, but in 7.1. The settings do not save. When the group watch is selected the response shows that the group is set. But when navigating back to the settings page, none of the groups are selected.

{syntax type="tiki" editor="plain"}
I have a group which does not have permissions to admin content templates in their category or the global permissions (the only permissions applying to the group) yet the group is still able to admin content templates.