Category: 7.x

In Tiki search results, there should be a "also do the same search with the following search engines:"

http://www.google.com/sitesearch/
http://wordpress.org/extend/plugins/bing-404/


{CODE(caption="This code worked in 6.x in templates")}{if $mid eq 'tiki-searchresults.tpl'}<div class="simplebox" align="center" style="padding:5px;border:2px solid #000000">
<img src="pics/icons/information.png" alt="Information" style="vertical-align:middle;" />
For additional results, try searching for <strong>{$words}</strong> in:
<span class="button"><a href="http://doc.tiki.org/tiki-searchresults.php?words={$words}&where=wiki">Tiki Documentation</a></span> or
<span class="button"><a href="http://www.google.com/search?q=tikiwiki+{$words}">Search all over the Web with Google</a></span> or
<span class="button"><a href="http://www.google.com/search?q=site:tiki.org {$words}">Search *.tiki.org with Google</a></span>
</div>{/if}
{CODE}


Since this will be configurable, we could also encourage people to send the site manager feedback, and thus tell us: what they were looking for and what they were expecting to find

Trackers are great in Tiki, it provides a way to build quick and easy register solutions.
When used in any context related to monitoring, it would be nice to have a way to associate a record with one or more events in time. For instance you would like to receive an email at the time the issue related to the task should be controlled and/or be resolved.

Thinking on it as a feature, the following could be considered in the solution:
*It could exist more than one "timer" in the tracker record,
*It should be added like any other tracker field to the record definition,
*It could have different ways to alert: email, rss, ... (maybe only one choice when instance),
*It could have rules, like auto disable when the record is closed (or other condition),
*It could be (as an option) reprogrammed,

and also
*Maybe a user wants to know about all his/her pending "timers".
*Maybe timer implementation could be independent objects that are linked to (special fields in) tracker records (or other objects), so global management is possible.

I guess that a good part of above functionality is already in Tiki in some form.

Currently, Tiki creates a single RSS feed per feature (e.g., wiki, articles, etc.).

For features that support i18n, this means that end-users will subscribe to a feed that contains items that they cannot read.

It would be nice if Tiki could create language-specific feeds each feature.

You can see this on info.t.o; we issue articles in English and French and Tiki includes both languages in a single feed: http://info.tiki.org/tiki-articles_rss.php?ver=2

To allow for greater styling, it would be great to allow HTML coding and/or wiki syntax in the __Site Title__ and __Subtitle__ fields on Admin: L&F.

Trying to create a spreadsheet results in DB error.

Incorrect integer value: '' for column 'parentSheetId' at row 1

La requête était :
INSERT INTO `tiki_sheets` ( `title`, `description`, `author`, `parentSheetId` ) VALUES( ?, ?, ?, ? )

Valeurs :

Probo
admin

La requête construite était probablement :
INSERT INTO `tiki_sheets` ( `title`, `description`, `author`, `parentSheetId` ) VALUES( 'Probo', '', 'admin', '' )

Stacktrace :
* C:\inetpub\wwwroot\tiki\7.2\tiki-sheets.php : 0 -> {main}(array ( ))
* C:\inetpub\wwwroot\tiki\7.2\tiki-sheets.php : 98 -> replace_sheet(array ( ))
* C:\inetpub\wwwroot\tiki\7.2\lib\sheet\grid.php : 2358 -> query(array ( ))
* C:\inetpub\wwwroot\tiki\7.2\lib\core\TikiDb\Bridge.php : 29 -> query(array ( ))
* C:\inetpub\wwwroot\tiki\7.2\lib\core\TikiDb\Pdo.php : 120 -> handleQueryError(array ( ))
* C:\inetpub\wwwroot\tiki\7.2\lib\core\TikiDb.php : 150 -> handle(array ( ))

Hello,

I'm using the BigBlueButton as stadalone and it works fine.
But there is an audio problem when I use it as a feature in Tiki.
Everything works fine except the audio. When I click on the headset it doesn't join the audio server (freeswitch).

I have the same problem on this site:
http://tiki.org/live

Tested on Tiki 6.3, 7.0beta2, 7.0RC1 with the same effect.
BBB version 0.71a as a VM
Firefox 4.01, Chromium 11.04

Thanks,
Chris

on the test environment i can access tiki-calendar.php without a problem but as soon as i want to create a calendar and then access it on the live server i only get a blank page.

wether it is an already populated tiki or a clean install (wether using a completely new db or telling the tiki installer to clear the previous db and create a new one, wether using our theme or using the standard theme) i always get a blank page.

are there any special options in php/mysql/apache the calendar needs which i need to change?

the live server is a suse linux with php 5.3.3 and mysql 5.1.46
the local server is some xampp on a windows machine

Edit:
tested it with Tiki 6.3, 6.4 and 7.1

While it is a blank page in Firefox, Google Chrome says it is a 500 server error

Edit2:
Apache Error Log says:
PHP Fatal error: Call to undefined function cal_days_in_month() in .../lib/tikidate-php5.php on line 298, referrer http//...

The "Tentative" status for a calendar event always reverts to "Confirmed" after it is saved.

{syntax type="tiki" editor="plain"}
Calendar(month view) displays and highlights incorrectly in all browsers except IE6
I've tried Chrome and 2 versions of firefox.
they show the entire previous month, the current month and a week past the current month. not all the correct days are highlighted either.
In IE 6 only a few days pre & post month are shown and the current month is correctly highlighted.

update - I tried with IE 8 and it looks fine.
So apparently this display issue is only in Chrome and Firefox.
Also another noticed bug, the date is shifted by 1 day.
so if i set a calendar entry for 6/8/2011, it will show as 6/7/2011
once you go into the item, it displays the correct date.
it just shows incorrectly in FF & chrome. but shows correctly in all versions of IE

There are a lot of different PIM applications using the iCal format, that Tiki can export.

As example I showed a usecase, where s.b. needed a synchronisation between Tiki and Google calendars, to make Tiki generated events visible in his Google Calendar, to ease the effort of sheduling between Tiki generated events and his personal google events.

I suggest a project for Calendar Syncronisation.

Please see: ((Calendar Synchronisation))

{syntax type="tiki" editor="plain"}
When you have a group name like "Finance and Marketing Departments" and you create another group called "Finance and Marketing Departments Moderators". You will not be able to add users into the latter group if that user is already in the first group. This is caused by "duplicate key" error in the attempt to add the user, because the key length limitation is 32 chars.

This bug might probably be Mysql settings dependent.

Ugraded this site to 7.1:

http://alaindesilets.org/MyPublicSite/tiki-view_blog.php?blogId=1

and now, I can't upload files to the Files gallery.

Here is what I do:

* tiki-upload_file.php
* click on Browse button
* Navigate my disk and select an image file
* Click UPload Files button
* Nothing happens.

{syntax type="tiki" editor="plain"}
The symptoms are:
- backlinks work sometimes only
- when deleting a page it does not always become a wanted page
- others ???

The result is:
- unpredictable behavior
- negative impact on the user acceptance

The problem is, that the syntax of the links change:
Example:
1) Type "Page 1" in the WYSIWYG mode and save
-> "Page 1"
2) save again in WYSIWYG mode
-> ~np~<a class="wiki" href="tiki-index.php?page=Page+1" title="Page 1">Page 1</a>~/np~
3) save again in WIKI mode
-> ~np~[tiki-index.php?page=Page+1|Page 1]~/np~
4) save again in WYSIWYG mode
-> ~np~<a class="wiki" href="tiki-index.php?page=Page+1">Page 1</a>~/np~

This makes 3 1/2 different representations of a link to 'Page 1'

{syntax type="tiki" editor="plain"}
When using the Wysiwyg editor, there are 3 closing /np tags appearing after where the mouseover plugin is inserted in Tiki 7. This problem does not exist in Tiki 6.

As of Friday 4/15/2011, code plugins stopped displaying their contents on my 7.x head site.

For example, I have a code plugin with no options set that contains:

{CODE()}function validate_a as p (e as p)
'Sample validation function.
'Data for the current row is available in 'e.data'.
'For example, e.data.firstname, e.data.lastname
if e.data.a = "" then
validate_a.hasError = .t.
validate_a.errorText = "a cannot be blank."
end if
end function{CODE}

On my site, nothing displays except the edit marker for the plugin.

The first time any user comments on a wiki page, the edit new comment box opens too small to be usable. It can be expanded in Chrome or Firefox if the user isn't too confused.

Once there is a comment, the edit new comment box opens at the proper size.

There should be a setting to allow comments to be editable, by user and/or admin.

{syntax type="tiki" editor="plain"}
At the end of install in

URL:
http://<domain>/tiki-install.php?nolockenter&install_type=update

The crash ends with :
(xdebug track begins)

Zend_Session_Exception: session has already been started by session.auto-start or session_start() - on a try catch no problem
Notice: Undefined index: min_pass_length in D:\Trebly\teawik-ld8-7xSa\lib\tikilib.php on line 1612
Notice: Undefined index: pass_chr_special in D:\Trebly\teawik-ld8-7xSa\lib\tikilib.php on line 1614

(xdebug track ends).

Track file joined

Trebly

~~#390:''Remark out of subject :''~~
Into my notes and refs dates are often in not common format yymmdd with B1=2011 date=B10117 is 01/17/2011, B2 is 2012. I used this for the last twenty years, has been used to make able soft to hold 2000 years and sort date (kept stored on six chars with historical data compatibility)in yymmdd yy=98,99,A0,A1..... B0, B1,B2. Used to make able at the end of eighties an important soft to hold long term plans. I use it since this moment and this goes on naturally and can't changed on my computers and data and can be used till year 2370.

When I upgraded this site:

http://alaindesilets.org/MyPublicSite/tiki-view_blog.php?blogId=1

from 6.1 to 7.1, the layout got screwed up (I'm using the DarkRoom theme).

Before the upgrade, the layout looked like this:

* [http://dev.tiki.org/tiki-browse_image.php?imageId=125]

After the upgrade, it now looks like this:

* [http://dev.tiki.org/tiki-browse_image.php?imageId=126]

Notice how the position of the login and the search forms changed, and how it looks weird in the TW 7.1 version (plus, it causes a lot of waste in screen realestate).

Detect browser language is not working to me (to luciash, in fact, in a site which I admin), in a recently upgraded site from 2.4 to 3.0.

This affects Tiki 3 to 7 and is a regression from Tiki 2.

!ENH trunk 7x : ability to introduce [breakline] in some texts and their translations

!!Nature of the problem
I many text it is unhallowed to use any markup language and filters are applied to these text.
Nevertheless, regardless HTML the this creates one main problem :

For <label> <input> and others strings with implicit new type "tikitypes" as warnings, comments etc... it is often necessary to have for a good GUI <breakline> at optimized positions.
HTML allows <br /> in all these cases (and all tags for strings into many tags.

Sometimes after translation because the words are longer a simple remark or a label which precede an input which followed himself by buttons-icons see the buttons at the next line.

All these cases needs to allow a [breakline] command which is then the lonely tag allowed.

I made this first for prefs in tiki_admin for labels (particularly when they are dependent and have a disposal on two columns)

!!What have been done
!!!Define the [breakline] command
!!!Create a smarty modifier "breakline"
It just replaces into strings [breakline] by "<br />" after the firewalls have been passed...
!!!Apply to list.tpl (class adminoptionbox)
Sample in list.tpl
<label for="{$p.id|escape}">{$p.name|escape}:</label>
Become
<label for="{$p.id|escape}">{$p.name|escape|breakline}:</label>

!!What to do ?
Nothing I just have to commit.
But it changes general common rules. It is a [MOD] of second level the level of developers.

Ready to commit.

What's your opinion ?

trebly

{syntax type="tiki" editor="plain"}
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

If an address is specified to send the test mail to in step 3 of the installer, an error is displayed when attempting to send the test email:

Fatal error: Call to undefined function iconv_get_encoding() in /srv/http/projectwiki/lib/core/Zend/Validate/Hostname.php on line 535

If an address is provided, and the CC box is unchecked, the following error also appears:

Notice: Undefined index: email_test_cc in /srv/http/projectwiki/installer/tiki-installer.php on line 837

If the user does not provide an email address and attempts to send the test email, the mail is reported as sent (or displays a user friendly error message.)

I'm using PHP 5.3 and Archlinux, and starting a clean install of 7-beta-1. I haven't gotten far enough into the process to see if other emails can be sent.

{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.