Category: 3.x

Could also be a link or a license/confidentiality agreement

When using InterTiki, registration should be sent to master site

There should be a note, only visible to tiki_p_admin that the anti-bot code is not currently here because the GD lib is not there.

I've just installed a 3.0svn, and while using tiki-sheets.php, the modules in the left column go down , below the height of the central column.

{syntax type="tiki" editor="plain"}
With ajax on, the page-top links to sections don't work, on tiki-stats.php, in my Tiki 3.1 installations.

{syntax type="tiki" editor="plain"}
Freshly installed TikIWiki 3.0 beta 4 with the Company Intranet Profile.

Created a tiki sheet (either as admin or as a registered user, this happens in both cases).

Tried to insert a column.... it begins and then suddenly takes me to a new sheet labeled:

ERROR:

A SheetId is required.

-----
* __THIS HAPPENS ON SAFARI 3.2 (macOS)__
* __This behavior does not occur under Firefox 3__

{syntax type="tiki" editor="plain"}
In my tw 2.x I had a couple of wiki pages which contain in their name an apostrophe , after an upgrade to 3.0 those pages cannot be accessed anymore (I can only edit them using the page list) giving a 403 error :

Forbidden

You don't have permission to access /tiki-index.php on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.2.11 (Unix) mod_ssl/2.2.11 OpenSSL/0.9.8e-fips-rhel5 mod_bwlimited/1.4 Server at www.magowiz.net Port 80

I can only use edit to retrieve the page contents and copy in another page that must not have an apostrophe in its name (or simply rename the page removing the apostrophe) until the upgrade to 3.0 the pages where fully functional so for me it is a regression.


I still have this problem in 3.1

This tracker item could not be found

When I am in Firefox, I should be able to add an RSS feed directly (one click instead of login, and copy & paste)

I have just migrated a Tiki from one server to another and ran into
UTF-8 Problems. The browser showed Umlauts as the dreaded diamonds with
question marks in them.

Both servers are fully utf-8 compliant as described in
http://tikiwiki.org/UTF-8

The big problem is that on the new server PDO is available while it
isn't on the old one. According to the mailing list PDO is not default,
but as far as I can see in the code PDO will be default, if available
and not set otherwise. Setting

$api_tiki='adodb';

in db/local.php fixes the special character problem.

The issue seems to be that PDO gives a silent fuc# about encodings and
just pumps everything to the database and back as you hand it to it.
Additionally PHP/PDO doesn't read your my.cnf and therefore doesn't know
which encoding to use.
A quick fix is telling PDO which encoding to use - line 39 in
db/tiki-db-pdo.php :

$dbTiki = new PDO("$db_tiki:$db_hoststring;dbname=$dbs_tiki",
$user_tiki, $pass_tiki,array(PDO::MYSQL_ATTR_INIT_COMMAND => "SET NAMES
utf8"));

But I think that this is not safe to commit...
e.g. someone started with Tiki on MySQL 4.0 which used latin1 as
default, so all her tables are latin1. She upgrades MySQL to 5.1, but
doesn't change the Tiki database to default to utf-8 and hasn't
converted the database. Then the PDO-fix above will most probably
produce the same problem, just the other way around...

No idea, what to do actually, but wanting to raise awareness here!

This is a dangerous issue as people with utf-8 databases upgrading their
system or Tiki and switching automagically over to PDO will end up with
mixed stuff in their database: clean UTF-8 and double-byte
ansi-control-characters which MySQL converted to their right unicode
codepoints (freaky, hm? ;) ).

I hope, I was capable of describing the problem in a way that's
understandable....

I am trying to customize the look and feel of the Site Search Bar that gets added to the top of each page when the "Activate" button is clicked next to the "Site Search Bar" subsection of the "General Layout" tab of the Administrator "Look & Feel" page.

Basically, I just want to add "Enter keywords" here in the textbox.

I am having a hard time finding where this code is defined.

I have looked in the following files:
templates\tiki-searchindex.tpl
templates\tiki-searchresults.tpl
templates\modules\mod-search_box.tpl
templates\modules\mod-search_new.tpl
templates\styles\simple\modules\mod-search_box.tpl
templates\styles\simple\modules\mod-search_new.tpl

Could someone point me in the right direction?

Any insight is appreciated.

Thanks!

Goal: to add a way to represent relevant data in a timeline.

This will most probably be done by re-using an existing library and/or service.

Let's coordinate here: ((TimeLine))

Tracker plugins are great.

There should be something about them in the tips, when creating trackers.

The Problem
i.e. the structure tee ist partial accessible for anonymous -
but in the Page view /tiki-index.php?page=xyz all the substrucktures are clickable but they are not accessible (permission of the subtree gives a 302 for the visitor - so he must go back ...

a robot like google creates so much traffic becose he want follow this dead links

so i thought this is solvable by a sitemap
but Tiki has no intern tool for a sitemap like some other cms.
so i started with a online sitemapgenerator - but disasterarea 302 permission
next sitemap-gen.py from sourceforge but the same disasterarea 302 permission
but much bigger becourse it generates from the apache accesslog.

So next i thought about this mess!OK Why create a link if it is not clickable for anonym
yes thats the first solution to give the thing a straight line

looks like a big bugfamily

<lq_013> before a few day's i started with working on a sitemap for tiki
<lq_013> first Idea with using a external tool end up in a disaster
<lq_013> this courced by permission on some struktures
<lq_013> next disasterpart is the rewrite seo engine wich produces some pages 4 times
<lq_013> each accessible in an other way
<lq_013> the sitemaptool from sourcefrge which makes analyse of the access.log produces much more shit
<lq_013> some things can be restricted in a config file but thats no god Idea
<lq_013> so my suggestion to solve some of this sitemap disasters is to cancel all a href=... where annonymous can't click to
<lq_013> this is more then recommented becourse all visitors and searchengines follow this links and get a 302
<lq_013> with redirekt to login or whatever

I am a new Tikiwiki admin/user, and although DELIGHTED with the product, must confess to being disappointed with structures, TOCs and MAKETOCs functionality. See my posting in >Forum >Documentation for details of these issues.

Using Structures to assemble Wiki pages into a book is a very powerful way to manage sets of pages in a holistic manner.

A common usage requirement however is to be able to restrict access to some selected pages within a Structure, which works fine from an access control point of view, BUT when the toc function is used ALL the pages will be listed within the Structure no matter what Category permissions the individual user has. This means that users have visibility of some pages that they cannot access - which may be very undesirable!! and conflicts with the WYSIWYCA principle.

It would be extremely useful to be able to filter the resultant list from the toc function, to just the pages/links that the individual user's categorisation permission allow them to see. In this way the categorised pages would not be visible at all in the same way as they are treated in many other functions e.g. List pages etc.

Still does this in 3.0b4

FIXED

3.1 on Linux, Apache, PHP5
*created tracker
*duplicated that tracker
Since then if I'm in tracker admin (tiki-admin_trackers.php) the third tab
says “Duplicate Tracker”. Clicking on it, it will load the
“Import/Export” page though.
Going into a trackers details there are 4 tabs again, and those have
correct names / load the correct pages.

Hi, i'm using TikiWiki sinca a while and it's a great tool with hundreds of capabilities.
I'm using a lot the tracker module but in my humble opinion, it lacks an essential feature which would provide some great enhancement:

Graphical statistics generation.

In order to be clear, i'll try to give a real life example for better understanding.

I'm working in the field of information security and was searching for a tool that would bring together wiki, cms and security-related bug tracking capability, in order to migrate our internal knowledge base from a mediawiki install, which is indeed a great user-friendly tool but far less complete and security conscious than tikiwiki....

I'm using the tracker module to gather information about security incidents and in order to provide detailed executive reports, it would be very handy to have a graphical statistics generation tool, which would permit requesting over selected tracker fields, and permitting a graphical representation of gathered data in a defined time window or other things like that.

I hope that this will seem clear and that you will find this idea a good one.
Congratulations and thank you very much to all those who contribute.
Good bye.

{syntax type="tiki" editor="plain"}
Create a Tracker with any number of fields.

Use the "insert new item" tab to insert an item.

Just click "Save", without selecting either the "View inserted item" or "Insert new item" radio buttons. You will be returned to the tracker list, but the browser (I.E. 7.0) will hang indefiniately and lock up.

Work-Around.
Selecting either of these radio buttons - "View inserted item" or "Insert new item" - will avert any browser locking problems.

I have seen this behavior on two different trackers, one in 3.1 and one in 3.2 instance. 3.1 tracker had 16 items. 3.2 tracker had over 70 items. Both behaved well if "Save" was paired with radio-button selection.

When you use the tracker field "items list" to link (for instance) offers and demands (or gods from an inventory, etc.), the option to specify to list only the open items, for instance, is needed. If a product is out of stock, would be set as out of stock, and maybe marked as "pending", or if discontinued, marked as "closed". And it shouldn't be listed through the "items list" field.

Nowadays (2.0rc2), it's not clear to me how this could be achieved (if so).

Sometimes we need a checkbox field in a tracker to be mandatory. Like:
^[[ ] I accept the terms and conditions.^
or
^[[ ] I agree with the three rules of tw.o dev community.^

This cannot be accomplished yet because the checkbox can be left empty, even if the field was marked as mandatory, and the tracker item is inserted (without that box checked).

{syntax type="tiki" editor="plain"}
When any tracker item such as a radiobutton or dropdown is set to editable by admin-only in the "Field is hidden?" tracker, the item is not visible through tracker plugin (only the name shows up)

Error appears in tiki 3.1 and after upgrade to 3.5 as well.

The same error happens when selecting "editable by admin only" in the dropdown menu or selecting a group in the "Editable by" box.

I have created an tracker with the google maps field.

When I try to add an location with the help from the "Google Map Locator" it doesn't have a "back" button and doesn't save any data back to the form/tracker.

URL generated by the tracker to Google Map Locator:
tiki-gmap_locator.php?for=item&itemId=&trackerId=&fieldId=3


{img src=show_image.php?name=map_locator_from_tracker.png&galleryId=1 }

{syntax type="tiki" editor="plain"}
For tracker items, displaying the item shows the current date and time for the fields "created" and "lastModif".

I have checked the DB values, and the proper values are stored in the database.

db values :
created : 1265627980
lastmodif : 1265627980

value : 2010-02-08, 11:19:40
Date displayed when viewing tracker item : vrijdag 12 Feb, 2010 10:16:22
(= current date / time)

when listing tracker items, the proper date is shown for all the tracker items.
The problem occurs only when viewing a tracker item.

#Create a Tracker with a drop down field that has several choices. #Enter one choice twice in Succession to get a "default" value.
#Enter an item using the tracker, but select a non-default value in the drop down field.
#Create two wiki pages each with one of the plugins as defined below...
~np~{TRACKERLIST(trackerId=3,showlinks=y,sort_mode=created_desc,url="tiki-index.php?page=Tracker+Plugin+Test&itemId")}{TRACKERLIST}~/np~

~np~{TRACKER(trackerId=3,url="tiki-view_tracker.php?trackerId=3")}{TRACKER}~/np~

Notice that the TRACKERLIST plugin, has a "url" argument that will display the page with the TRACKER plugin. The "url" has "&itemId" at the end of the url, so that clicking any item, will open the page with the TRACKER plugin, and you should see all the fields filled in with their correpsonding values (from that item).

For the dropdown menu, the value displayed is NOT the one that was originally selected by the user, but rather the default value.

The TRACKER Plugin is great for "Insert New" functionality, but cannot be used for "Edit Item" functionality, as fields with default value settings cause an overwrite of the user's input for those fields.

This situation prevents the user of the TRACKER plugin as a round-trip tool (insert with TRACKER --> TRACKERLIST --> edit with TRACKER), as the user's values are blown away and replaced with the default field values.

Note: values selected using "Category" field types are never selected using the TRACKER plugin to edit a TRACKER item. For some reason the TRACKER plugin does not pick up category values from category fields, although does allow inputing them.

Instead of this:
{img src=images/code.png}%%% {CODE()}
*[tiki-view_tracker_item.php?itemId=909|Integrating fotonotes or wikigraphe or DOM Image annotation to the Image gallery]
{CODE}

I should be able to indicate something like:
{img src=images/code.png}%%% {CODE()}
*{bug909}
{CODE}

and have the nice link generated. And if the title of the bug changes, I am OK. Having some more info about the bug in a mouse over would be a nice bonus!

Having a drop down menu or bug picker would be sweet too!

Maybe even some backlinks detection!

You can see an nice example here that even has a bug icon
http://winscp.net/eng/docs/history