Category: 3.x

{syntax type="tiki" editor="plain"}
When a user uploads a file on the file gallery, the URL is saved where somebody could download the file. This URL is used by the category browser.
If the client uses a proxy (we use a SSH tunnel to connect to the wiki), the wrong URL is saved in the database (table tiki_objects).
This results in a link to the original tunnel and not the website itself.

If we could file wiki pages in Fgals (this would presumably be a link to the wiki page), it would be a way of filing wiki pages and benefit from the fgal explorer to order wiki pages.

This is an idea to consider.

{syntax type="tiki" editor="plain"}
Creating a new file-gallery in the root directory works for admin, but users with permission get an error upon clicking 'create new file gallery'
Message was
{CODE()}Notice: invalid variable value: $_GET["parentId"] = -1{CODE}

From what I understand -1 stands for the root directory.

TikiWiki Version 3.2:
The error is produced in file tiki-setup_base.php on line 259

The code tries to validate the '-1' as an integer variable. Defined by the {CODE()}$vartype array -> $vartype['parentId'] = 'int';{CODE}
The according $patterns array describes it as
{CODE()}$patterns['int'] = "/^[0-9]*$/"; // *Id{CODE}
Obviously the sign "-" is missing.
Therefore the check for a valid variable fails and the user can't create a new file gallery.
Why the admin group is not affected I do not know.

This is why Toggg created ((tw:TogggDeletorPhp))

Spreadsheets can be created directly through wiki SHEET plugin directly within wiki pages. this allows managing big tables visually, as well as having the data ready for producing graphs, etc. (see documentation for tikisheets at doc.tw.o, if needed)

However, when you create a sheet through a call to the SHEET plugin from the wiki page itself, there are 3 issues which need to be fixed:
# you need to know the id you want to assign it to,
# after that, tiki-sheets.php doesn't list it (even if the sheet is really created, and you can import data to it, and show it at the wiki pages, etc.).
# the sheet is not shown with the right css

Even if we have wysiwyg option available, I still think that is worth improving tiki sheets usability to be used directly from wiki pages, once those 3 previous issues are fixed.
---
Updated on Feb. 2, 2011, using trunk (7svn)
# Steps to reproduce the first issue
## Edit a wiki page
## Use the plugin helper to create a new sheet in that page. And since it's a new sheet, it doesn't have a sheetId yet, so that you leave all fields empty in the plugin helper for the pluginsheet
++ this will add this type of code in your wiki page:
++ {CODE()}{sheet}{CODE}
## Save the wiki page
++ you will see an empty sheet shown in place at that wiki page, with the button at the bottom to allow the user to "edit it" (so far, so good)
## Once you click in the edit sheet button, you end up in some url like this one:
++ http://localhost/tiki7trunk/tiki-view_sheets.php?sheetId=&parse=edit
++ which produces a WSOD (blank page).
*** In my case, I guess that this url should have been:
+++ http://localhost/tiki7trunk/tiki-view_sheets.php?sheetId=2&parse=edit
+++ since I had only one sheet previously created, with sheetId 1, so that the next one should be 2. However, this new url is still producing WSOD for me. (tiki caches cleared, just in case, repeated this step, and same WSOD)

The expected behavior is that the user is the user would be editing a blank new sheet with the url:
http://localhost/tiki7trunk/tiki-view_sheets.php?sheetId=2&parse=edit

and when the user saves that sheet, the new sheetId 2 exists, and the user is either sent back to the wiki page where he clicked at the button "edit sheet" (preferable option) or either sent to the corresponding tiki view sheet 2.

We should have some ready-made zones, where template designers can just

It should be possible to populate these zones with Site Identity or in the templates.


Please examples of floating boxes here:
http://www.jtricks.com/javascript/navigation/floating.html
http://www.phpletter.com/Demo/Jquery-Floating-Box-Plugin/

It could also be pull out thingies or horizontal bars

In a project management mode, you can use ((watch)) and ((alert)) but not everybody may be watching and alert is extra time.

For small teams and short delays, it could be good to have since_last_visit_new module content to be emailed to each group member periodically.

People get personalized content based on their last login (cool!)


Also, they don't get watches if they login regularly

Currently, (2.2) when using the mailin feature to post to a forum, Tiki does not actually check the email until a user views the forum. Only then, is the email checked and new messages posted to the forum.

This means that the RSS feed for the forums, and modules such as last_post will not be correct until a user goes to the forum.

Instead, Tiki should check the email at regular intervals (in the same way that Tiki checks for article mail-ins.

{syntax type="tiki" editor="plain"}
although they have tiki_p_admin_forum permission=__n__ (on v3.2).
My forum mods gets on tiki-view_forum.php?forumId=<int> the "Edit forum" button, which should be visible to forum admin only.
If they click on the button they get the error messages about missing permissions, so there is no serious problem with it, but it's confusing to see this button.

I've looked over templates/tiki-view_forum.tpl but didn't see anything as explanation for this.
(Btw: the if/else clause from line 15 to 19 doesn't make a sense (for me); it makes the same, never mind the case of the if-clause)

Hello,
I installed the same website on two different server (same source and same sql).
The first is a Unbuntu 9.04 with last Apache, Php, Mysql. Config with a VirtualHost.
The second is Windows Vista SP2 with EasyPhp 3.0. Config with a Directory and Alias.

On the first server (Ubuntu), some links in forum like "reply" are wrong (something like http://www.mysite.com/forumId=...). Also when I send a message the request finish on a blank page.

On the second server I don't have this pb.

A specific component is need for 3.x (maybe present in EasyPhp) ?

Thanks

When deleting forum posts / topics it just asks to confirm without telling the user again what he/she is trying to delete.

This is a bit odd. Using trunk from today, Feb 10th, 2009, even if this bug was showing up with previous trunks, also.

I post a message as plain registered user, that I get this message just after posting:

{CODE(wrap=>1)}
Error Error

Ha hagut un error en una petició de la base de dades!

Context:
File tiki-view_forum_thread.php
Url tiki-view_forum_thread.php?comments_parentId=3&forumId=1
Query:
select tc1.`threadId`, tc1.`object`, tc1.`objectType`, tc1.`parentId`, tc1.`userName`, tc1.`commentDate`, tc1.`hits`, tc1.`type`, tc1.`points`, tc1.`votes`, tc1.`average`, tc1.`title`, tc1.`data`, tc1.`hash`, tc1.`user_ip`, tc1.`summary`, tc1.`smiley`, tc1.`message_id`, tc1.`in_reply_to`, tc1.`comment_rating` from `tiki_comments` as tc1 left outer join `tiki_comments` as tc2 on tc1.`in_reply_to` = tc2.`message_id` and tc1.`parentId` = ? and tc2.`parentId` = ? where tc1.`objectType` = ? and tc1.`object`=? and tc1.`parentId`=? and tc1.`average`>=? and `approved`=? and (tc1.`in_reply_to` = ? or (tc2.`in_reply_to` = "" or tc2.`in_reply_to` is null or tc2.message_id is null or tc2.parentid = 0)) order by tc1.`commentDate` asc,tc1.`threadId`
Values:
0 3
1 3
2 forum
3 1
4 3
5 0
6 y
7 prova-0-21fe72956f@moviments.net
Message:
Column 'approved' in where clause is ambiguous
Built query was probably:
select tc1.`threadId`, tc1.`object`, tc1.`objectType`, tc1.`parentId`, tc1.`userName`, tc1.`commentDate`, tc1.`hits`, tc1.`type`, tc1.`points`, tc1.`votes`, tc1.`average`, tc1.`title`, tc1.`data`, tc1.`hash`, tc1.`user_ip`, tc1.`summary`, tc1.`smiley`, tc1.`message_id`, tc1.`in_reply_to`, tc1.`comment_rating` from `tiki_comments` as tc1 left outer join `tiki_comments` as tc2 on tc1.`in_reply_to` = tc2.`message_id` and tc1.`parentId` = '3' and tc2.`parentId` = '3' where tc1.`objectType` = 'forum' and tc1.`object`='1' and tc1.`parentId`='3' and tc1.`average`>='0' and `approved`='y' and (tc1.`in_reply_to` = 'prova-0-21fe72956f@moviments.net' or (tc2.`in_reply_to` = "" or tc2.`in_reply_to` is null or tc2.message_id is null or tc2.parentid = 0)) order by tc1.`commentDate` asc,tc1.`threadId`
{CODE}

As admin user, I can see that post, and any other.

{syntax type="tiki" editor="plain"}
When user replies to a forum the pagination changes so that only shows 2 posts:
The topic post and the first reply

It still shows only 2 replies per page don't respecting the configuration for the forum ( 10 replies per page, 20, etc ).

This permits mailing-list-like functionality.

After, adding or removing a user from a group dictates which forums they can read and get notifications for.

Maybe we should use the newsletter functionality as it already handles group inclusions and individual opt-outs...

Like newsletters, it should be possible for people to remove themselves from a mailing. Better than 1.9.7 newsletters, it should also be possible for the admin to see who removed themselves.

{syntax type="tiki" editor="plain"}
on tw.o you can set __any__ forumId regardless where the forum topic/thread post actually is saved, e.g.

http://tikiwiki.org/tiki-view_forum_thread.php?forumId=1&comments_parentId=34093
http://tikiwiki.org/tiki-view_forum_thread.php?forumId=2&comments_parentId=34093
http://tikiwiki.org/tiki-view_forum_thread.php?forumId=3&comments_parentId=34093
http://tikiwiki.org/tiki-view_forum_thread.php?forumId=4&comments_parentId=34093

it's always the same forum topic/thread but the __forumId=3__ is the correct one

on the other hand when you omit the forumId it yells error "No forum indicated"

it would be better when forumId wasn't required in cases when a thread moves to another forum, the old links wouldn't be misleading...

Made a new install of Tiki v3.2 on a Ubuntu 8.04.3 system as server (includes MySQL in version 5.0.51a-3ubuntu5.4).
Surfing at tiki-plugins.php produces the following error message:
{CODE(wrap="1",ln="0",ishtml="1")}<div class="cbox-data"><br>
<div class="simplebox error">
<div class="simplebox"><b>An error occured in a database query!</b></div><br>
<table class="form">
<tbody><tr class="heading"><td colspan="2">Context:</td></tr>
<tr class="formcolor"><td>File</td><td>tiki-plugins.php</td></tr>
<tr class="formcolor"><td>Url</td><td>tiki-plugins.php</td></tr>
<tr class="heading"><td colspan="2">Query:</td></tr>
<tr class="formcolor"><td colspan="2">
<tt>SELECT fingerprint, added_by, last_update, last_objectType, last_objectId FROM tiki_plugin_security WHERE status = 'pending' ORDER BY last_update DESC</tt>
</td></tr>
<tr class="heading"><td colspan="2">Values:</td></tr>
<tr class="heading"><td colspan="2">Message:</td></tr>
<tr class="formcolor"><td colspan="2"></td></tr>

<tr class="heading"><td colspan="2">Built query was probably:</td></tr>
<tr class="formcolor"><td colspan="2">SELECT fingerprint, added_by, last_update, last_objectType, last_objectId FROM tiki_plugin_security WHERE status = 'pending' ORDER BY last_update DESC</td></tr>
</tbody></table>
</div>
<br><br>
</div>
{CODE}
edit: Sorry, forgot to mention that this bug also affects the using of plugins. Using a plugin in a wiki page that needs approval produces the same error message. (Saw someone in [http://irc.tikiwiki.org/irclogger_log/tikiwiki?date=2009-10-02,Fri|the irc log] with this problem, which is also ===this=== bug, so I edit to clarify it.)

To reproduce:
#Go to a tracker item. Ex.:
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=2441

#Click full screen mode
You are sent to
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId%3D2441&fullscreen=y


After, that initial error, full screen mode works well

It has been suggested this has a link with ShortURLs
{QUOTE(replyto="Gary")}When using the short url, then clicking the fullscreen icon, and then clicking it again to leave fullscreen view, the url gets mangled and I end up at the home page. (Example: http://zukakakina.com/tw3/absE (external link) -> http://zukakakina.com/tw3/tiki-index.php?page%3DabsE&fullscreen=y (external link) -> http://zukakakina.com/tw3/tiki-index.php?page%253DabsE&fullscreen=n. (external link) The first = becomes encoded so the url breaks. chibaguy - r17975) {QUOTE}

"Fullscreen Edit" is a new cool feature of 2.x

Quicktags are kept, but Wiki & Plugins Help are missing so it makes editing less enjoyable.

"Edit Summary" is missing as well. Maybe it's intentional?

((doc:PluginCode)) doesn't show colors for php code, as it should according to doc page:
[http://doc.tikiwiki.org/PluginCode]
Tried with param colors=>php or colors=>phpcode:
{CODE()}
{CODE(colors=>php)}
/** Return system defined temporary directory.
* In Unix, this is usually /tmp
* In Windows, this is usually c:\windows\temp or c:\winnt\temp
* \static
*/
function tempdir() {
static $tempdir;
<b>$tempdir = '../tmp';</b>
<b>/*</b> if (!$tempdir) {
$tempfile = tempnam(false,'');
$tempdir = dirname($tempfile);
@unlink($tempfile);
} <b>*/</b>
return $tempdir;
}
}
{CODE}
{CODE}

And it returned:
{CODE(colors=>php)}
/** Return system defined temporary directory.
* In Unix, this is usually /tmp
* In Windows, this is usually c:\windows\temp or c:\winnt\temp
* \static
*/
function tempdir() {
static $tempdir;
$tempdir = '../tmp';
/* if (!$tempdir) {
$tempfile = tempnam(false,'');
$tempdir = dirname($tempfile);
@unlink($tempfile);
} */
return $tempdir;
}

}
{CODE}

---
Update: RFE for plugincode:
Why not using "wrap=>1" as default param instead as "wrap=>0"?

~np~When using three hyphens (---) you get a horizontal rule in v3.0 Beta 3, but if you use more than three hyphens (i.e. ---- ----- or ---------), you will not get a horizontal rule on the page. Greater than three hyphens was valid in version 2.x of TikiWiki to create a horizontal rule.~/np~

FYI: Notification messages with hashes in the url appear to miss that has param...
Reproduced also on dev.tw.o with current svn code.

Xavi

En/na tikiwiki-devel (a) lists.sourceforge.net ha escrit:
> Wiki page renamed by marclaporte.
>
> Date: 19 Apr. 09 23:53 UTC
>
> Old name: Mind Mapping
> New name: MindMap
>
> If you don't want to receive these notifications follow this link:
> http://dev.tikiwiki.org/tiki-user_watches.php?hash=
>

I currently keep track of bugs submitted by me by searching for my username. This results in a list of bugs, currently the first link looks like this:
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=2561&highlight=tobi_h

Klicking that link gives an almost blank page, removing "&highlight=tobi_h" shows the page as it should.

Update: This only happens if I am logged in. More detail, thx to chibaguy: "...left and center columns are empty, and the right column is a column width off the page to the right."

This does not apply to wikipages, where highlighting works.

When creating a horizontal rule previous version of Tiki wiki 2.x allow you to use multiple hyphens (>3).

~np~i.e. "---------------" in 2.x version would produce the same horizonttal rule as: "---"~/np~

~np~In 3.0 Beta 3 the only valid horizontal rule creator is three hyphens (---), not more than three hyphens.~/np~

{syntax type="tiki" editor="plain"}
Hi:
I can't add recurrent events in this web site:
http://moviments.net/uelm/tiki-calendar.php

Neither me, nor other editors in this web site.
Single items can be added with no problem.

However, I've tried to reproduce the problem in local , and I haven't been able to do so. I can add single events, and recurrence rules without problems.

I can provide the db of the problematic site, to allow further investigation of the settings in that site...

Obviously:
DD_belatedPNG fix is enabled by default on the site logo and is intended for IE 6 only.
The IE 6 check is in lib/setup/js_detect.php
strpos($_SERVER['HTTP_USER_AGENT'], 'MSIE 6') !== false

The problem with this is that IE 8 will also get detected, check this:
---
Mozilla/4.0 (compatible; __MSIE 8.0__; Windows NT 6.1; Trident/4.0; Mozilla/4.0 (compatible; __MSIE 6.0__; Windows NT 5.1; SV1) ; SLCC2; .NET CLR 2.0.50727; Media Center PC 6.0; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET CLR 1.1.4322)
---

The bug with all this lies in the fact that IE 8 shows a few js errors on DD_belatedPNG.js on each page load and that could prevent IE from submitting.