Category: 3.x

Still a problem in 3.0rc1

If you have a Calendar where the Custom Priority, Category, Location and Participant options have been set, when editing an event if you Preview the edits then the refreshed screen no longer shows these options in the edit area and saving the event loses the data previously typed in.

{syntax type="tiki" editor="plain"}
After upgrade from 2.4 to 3.0 the MyTiki Mini Calendar no longer displays the very useful Caldendar-filter (small simple calendar interface). Otherwise the minicalendar feature works well.

I have done two fresh builds of Tiki 3.0 using "The News" theme.
In each build I have confirmed that the miniature, monthly-calendar
that appears under the heading "Calendar Filter" within the
personal calendar feature under MyTiki is missing. It's a handy
little calendar to have. I have been unable to determine what
php or javascript file creates this little gem. It would be nice
to have it back.

{syntax type="tiki" editor="plain"}
In version 3.0, recurring events are now handled. This is great.

However, in view mode, the extra line "Recurrence This event is not recurrent" and the blank line below (which contains hidden recurring event details" causes confusion

For example:
http://dev.tikiwiki.org/tiki-calendar_edit_item.php?viewcalitemId=106

It conveys the message that this event is not recurrent but this is an annual festival.

Congratulations on the work put in on the calendar. I love the recurring event feature!

Of course there is always more: I would like to be able to post an event that recurs, for example, the second Saturday of each month.

Currently, I can only post an event that recurs by date. Many of the events that I post occur on the first Wednesday of the month, or the second Thursday. They recur, but not by date; rather, they recur by designated weekday.

Thanks for any help you can provide on this.

P.S. Also, some events occur the same time each weekday (but not Saturday or Sunday). Providing for weekday recurrance would be a nice addition as well, but less important than the above.

I can't add an SVG image.
Even with HTML enabled, it will add an tag into my <object> tag preventing me from using SVG images.

With SVG already being an important element on the web, this is unexcuseable and needs to be fixed asap.

Hi,

I try to install Tikiwiki 3.1 on a PostgreSQL 8.3.5 database.
I create a local.php file and installer will find and connect the database.

After clicking on "continue" during the "Install profile" screen, the installer fails, printing the following message

Fatal error: Call to a member function fetchRow() on a non-object in /wiki/dev/3.1/appli/tikidev/installer/installlib.php on line 247


Looking at the shema database, there is only 5 tables
tiki_dynamic_variables
tiki_minichat
tiki_pages_changes
tiki_plugin_security
tiki_send_newletters_files


and 2 sequences

tiki_minichat_id_seq
tiki_sent_newletters_id_seq



Is there a fix ?


Regards,
Franck.

{syntax type="tiki" editor="plain"}
Receiving "Account disabled" error every time user logs in. User can temporarily log in using the activation link ("Account validated successfully"), but once the login cookie expires or the user logs out, user receives account disabled error when logging back in normally.

(reported by FF|Skyrider and coaboa)

As the admin I can't add permissions to Registered users or a new user group. In 3.1, I was getting errors when logged in as Registered user that I couldn't upload even though that was available to me (there's an open bug report about this). I don't get that error now and I can upload as a Registered user, but I cannot then go back and see it - no Galleries are visible to me. I can see them as an admin, though, but that is not useful since users need to view galleries also and aren't able to.

Also, I got these errors when I upgraded to 3.2:

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1091

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

Warning: in_array() [function.in-array]: Wrong datatype for second argument in /tmp/cpanel_phpengine.1254931905.289840z3jsIGfOH on line 1177

{syntax type="tiki" editor="plain"}
Can't create a forum as a registered user. There is simply no button, unless you have administrative rights over the forum

When trying to add a new page to an existing structure or create a new structure, I got the following error:

Field 'structure_id' doesn't have a default value

I check mySQL DB tiki_structure table, find the field 'structure_id' is not NULL,I check structlib.php,I find structlib.php not set the value of 'structure_id',only set 'parent_id',I guess that struclib.php have wrong.
structure is important feature ,wish to solve this problem


---
__''kerrnel22:''__ Unable to reproduce this in 1.9.10.1 CVS ...are you running CVS or release package 1.9.x? Also unable to reproduce in 1.10.0b1 CVS ...same question, are you running CVS or release package 1.10.0b1? If you are running the package in either, then it may be that the bug has been fixed in a patch to the CVS tree and you may need to wait for the next beta release.

---
re ''kerrnel22:'',i edit structlib.php line 202 :"$query = 'insert into `tiki_structures`(`parent_id`,`page_id`,`page_alias`,`pos`) values(?,?,?,?)';",to "$query = 'insert into `tiki_structures`(`structure_id`,`page_id`,`page_alias`,`pos`) values(?,?,?,?)'; ,then out tiki can run,and can create a new structure.

Have had this issue since 1.9.10.1 and it's still there in all subsequent versions even though the previous bug report detailing the same issue (#1649) says it's fixed.

The posted solution may work - although the Comments section of that bug report details a differing fix.
Would be good to get this fixed in the codebase rather than manually adding a fix to each new release.

If you need further info from me - please email nickallentbwa-at-gmail.com

When I try to add a page to a structure, I get this error:
=================================================================================================
An error occured in a database query!

Context:
File tiki-edit_structure.php
Url tiki-edit_structure.php
Query:
insert into `tiki_structures`(`parent_id`,`page_id`,`page_alias`,`pos`) values(?,?,?,?)
Values:
0 407
1 116
2
3 1
Message:
Field 'structure_id' doesn't have a default value
Built query was probably:
insert into `tiki_structures`(`parent_id`,`page_id`,`page_alias`,`pos`) values('407','116','','1')
=================================================================================================

{syntax type="tiki" editor="plain"}
"Delete unused images" in the Admin panels does not affect images uploaded via the WYSIWYG editor, and the user interface does not provide any other means of deleting ANY images from the FCKeditor upload directory.

{syntax type="tiki" editor="plain"}
My tiki site was updated from 2.x to 3.0 .

Wiki don't work when i turn to next page in blog/Forum.

I found it work when i change & to ? .for example
forum13&comments_offset=40 don't work
forum13?comments_offset=40 ok change by manual

also i find some bug in imageGallery

when i want to delete a pic
gallery44&remove=730 don't work
gallery44?remove=730 ok change by manual

hope some guys help me..thanks!!

I have a comment on a wiki page. When I click Reply to post a follow-up comment, I get an error. It looks like the Reply button is generating a bad URL:

__Not Found

The requested URL /mywiki/page=IVR_Revitalization&post_reply=1&comments_threshold=0&comments_reply_threadId=5&comments_offset=0&thread_sort_mode=commentDate_asc&comments_per_page=20&comments_grandParentId=0&comments_parentId=5&thread_style=commentStyle_plain was not found on this server.__

This would be a show stopper using Tiki threaded comments is very important feature requirement for us.

Thanks,

Paul

This is still a problem in 3.0rc1


Sorry - just spotted that this bug ===has already been reported as #2141=== but hopefully the additional information provided here will help resolve this more quickly.

You can no longer set/change the meta robots setting in Meta Tags Admin ie the NOROBOTS, NOFOLLOW settings

When you fill in the form field and click the Change Settings button the field blanks and viewing the HTML page source code shows that nothing has happened. The "revisit after" field works fine however.

Old 1.9 sites work fine and sites that have migrated through to 2.2 from 1.9 have their old values preserved but they cannot be changed. New 2.2 sites cannot have the setting established.

Examining the database for a new site shows that the metatag_robots row in the tiki_preferences table is missing. Hacking the table to add the row with appropriate values allows the appropriate HTML code to be generated in the head section of each page BUT the admin form still does not work.

Have also now spotted that ticking any of the Meta keywords options e.g the "Insert freetags in keyword list" and changing the settings does seem to set that option BUT the tick box is then blanked and then there is no way to 'untick' the option or you are not sure if it has been set or not.

very old bug - now fixed/not relevant

3.0 Beta 2:

After enabling the Categories feature through Admin -> Features, the following error occurs when adding or editing pages, articles, file galleries, and everything that needs to alter the database.

(Names are arbitrary)

An error occured in a database query!

Context:
File tiki-editpage.php
Url tiki-editpage.php
Query:
insert into `tiki_objects`(`type`,`itemId`,`description`,`name`,`href`,`created`,`hits`,`comments_locked`) values(?,?,?,?,?,?,?,?)
Values:
0 wiki page
1 sdf
2 sadfsa
3 sdf
4 tiki-index.php?page=sdf
5 1239375431
6 0
7 n
Message:
Unknown column 'comments_locked' in 'field list'
Built query was probably:
insert into `tiki_objects`(`type`,`itemId`,`description`,`name`,`href`,`created`,`hits`,`comments_locked`) values('wiki page','sdf','sadfsa','sdf','tiki-index.php'1239375431'page=sdf','0','n',?)

{syntax type="tiki" editor="plain"}
See the attached word document for a step-by-step example of how
to recreate this issue.

It is also unclear how to created nested categories by using
the "Batch Upload (CSV File)" feature.

-----------------------------------------
When a category is more than one-level deep, the "Category" field type on Trackers will only display one level.

Example:

Furniture Level 1
_________|__________
| | |
Tables Chairs Sofas Level 2
__________| __|___ ___|_____
| | | | | |
legs top legs back cloth leather Level 3

In the above example, if one selects the parent id corresponding
to "Level 2" in the above example, then the category field only
contains choices "Tables, Chairs, Sofas", rather than those choices,
plus the levels below them (i.e. "legs, top, legs, back, cloth, leather").

It could be very useful to have all levels starting with a given "parent" level as part of the Category field.

Feature suggestion: add a permission to "change group viewpoint"

This would allow a member of many groups to see a drop-down of his groups.
Choosing another group would allow only to see what members of this group can see.

So admins would be able to check that their users's groups permissions have been set up properly.

By clicking on the column header in the list of users in order to change the order of listing, the page is blank (just a little square appears in the upper right)

Right now, there's no way to resend either the email to the admin to validate a user or resend the email to the user to validate their email address. If either of those emails fail to happen or they get sent to "spam", the user cannot log in.

If the default install, feature_multilingual is disabled since r11761. Nevertheless, change_language (Users can change site language) is still enabled by default.
Since r17625, controlling change_language is dependent on having feature_multilingual enabled.

This creates confusion, like luciash wondering where change_language was today. It's abnormal you have to enable a feature to disable another feature.

{syntax type="tiki" editor="plain"}
On doc.tikiwiki.org, I renamed pluginBacklinks to PluginBacklinks and the backlinks are gone.

Since wiki page names should avoid special characters, we'll need to think about maybe using character substitutions in page names (a instead of à, _ instead of ') and use the description field for the exact format.

Please coordinate here: ((Character substitutions))

{syntax type="tiki" editor="plain"}
In tiki-admin.php?page=login, the "Use tracker to collect more group information" check box is always checked, so everytime you change something, the feature is enabled. Kind of annoying to have to pay attention to that all the time.

Trackers can have many fields.

Multilingual is a way to have multiple values.

Native multi-valued trackers would be useful in certain circumstances.

Another way is to use ((doc:Category Tracker Field)) or ((doc:Items List and Item Link Tracker Fields)) or ((doc:Drop Down - Radio Tracker Field)) with multiple choice option. Probably the best is to build upon the ((doc:Relations Tracker Field)).



We would also want multiple sets.

First Name 1 (field 46)
Last Name 1 (field 47)
Address 1 (field 49)

First Name 2
Last Name 2
Address 2

First Name 3
Last Name 3
Address 3

First Name 4
Last Name 4
Address 4

Could we imagine a new tracker field type "Set of fields":
Fields: List of fields in the set. ex.: 46,47,49
Number of repetitions: ex.: 3

This would create artificial fields (in this case 46-2, 47-2, 49-2, 46-3, 47-3, 49-3, 46-4, 47-4, 49-4)

So these fields could be used independently (ex.: 47-2), but since they are linked, we could have some smarter handling for forms, reports and exports.

We could want the input form to by default indicate only the first set of fields, and via jQuery, show additional set of fields.
We could want a report/export of this "Set of fields" which would aggregate everything in one listing.

{draw id="28"}