Category: Feature request

Please see: ((Federated Timesheets))

Webcalendar offers a setting Timezone Offset to Subtract or add hours to server time.

{draw name=timezoneoffset}

This would make things simpler for site which all events are in a common timezone.

Ex.: Showing UTC time in RSS feeds is not very useful...

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))

I give anonymous users read acess to forums, etc. Their timestamps are all UTC based .. seems funny to them since all users including anonymous would be in local TZ

I can set it in Mytiki, preferences but that doesn't apply until someone logs in

I found a display_timezone setting of "EST" in the twiki_preferences table that seems to be totally ignored

Further, I found code in the php files that was commented out with a note "-- Obsolete from 1.7 timezone changes". I don't know what that means


Could a feature please be added to allow the admin to set a default TZ for the site (that the user could then override in Mytwiki, preferencs)

Tracker plugins are great.

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

Enable multilingual, create a tracker create a text field and set it as mandatory.
You can’t save without filling the field. (good and normal)

Turn the field to multilingual and dont set title for other language.
You can’t save an item anymore.

While they can be a discussion about the logic, having a title in every language used in that case shouldn’t be mandatory and one should be use as default when other don’t exist.

I remember it was once useable, if you had at least one field with a value it was good enough to allow saving.


http://bsfez-11581-7539.show2.tikiwiki.org/tiki-view_tracker.php?trackerId=1
You can’t save an item with only one language title

It is a small thing, but it would be nice if the calendar page would show which calendar is being viewed at the top of the page. I think it would make it more clear to users who are new to the system and just want to use the calendar.

__Objective:__

The objective of my feature request is a more efficient way to create, to edit and to display Calendar event data, when used together with a Tracker.

This would be useful especially in the context of project management tools like Kanban (under heavy development) and Trackercalendar.

All features and functionality like Trackercalendar, Kanban, Calendar events, should provide different simple and versatile views, based on the very same Calendar item and thus be freely combined and happily created by simply filling one simple Tracker form.

__Use case example / context and problem:__

I got the idea whilst working on a Tiki 25.0vcs (InnoDB, git, ...) for a small personal private office project, where I test a bunch of features.

I made a 'Task' list with Tracker ... this is planned to be used together with Kanban.

The 'Task' list contains a field type 'date and time (calendar event)' which creates a calendar event when the Tracker item is created. As far as I understand, the Tracker item displays the Start date (and time) of the Calendar event, which is connected / related to the respective Tracker item.

This is working fine and it is even possible to switch the relation of the Tracker item to another existing calendar event.
The name of the Tracker item will be the title of the Calendar event (which is good!)

Sadly the actual date and time is the only data that seems to be displayed in the Tracker item so far.
Imho it would be important to have the option to share the same item description for the Tracker item and the Calendar event.

Currently I can create a Tracker field 'Textarea' in the Tracker and use it as description.
But there is no option, that this description textarea would be displayed as decription of the calendar item. Aswell it is not possible to display the Calendar event's description in the Tracker item.

When the Tracker item is created it is only possible to distinguish the Calendar item's start date.
Only after creation the Tracker item can be displayed and from there an edit-button pressed and then the details of the Calendar item edited, like Start date and End date, duration, description, participants, and all the other data of a calendar event.
This process needs to be simplyfied.
All these data details needs to be optionally displayed in the Tracker and in the Calendar, in a way that Tracker and Calendar just provide a different view on the same event.

__Following additional functionality would be required:__

# Add a Tracker field type ' Calendar event details' to display data from the Calendar event that is (currently) connected to the Tracker item.
+
# This Tracker field type shall have options (maybe comma separated list) to display the content of one or more Calendar event fields like End date, duration, description, participants, etcetera.
+
# It shall be possible that several Tracker fields of type ' Calendar event details' exist in one Tracker item. This way this field type could be used
** either similar to a field type "item list' (display several calendar details in one Tracker field)
** or similar to a field type 'dynamic item list', respectively 'item link' (display one Calendar event detail per Tracker field for more detailed display option)
+
# The Tracker field type 'Calendar event' should provide the option (to the user) to distiguish and completely fill out all Calendar event data details at the time of Tracker item creation.
+The user should not be required additional steps to reopen the event for then providing the Calendar details that he would have wanted to provide in the first place.
+
# For long time the Trackercalendar did use no calendar items but individual 'date and time' fields to create a calendar like planning tool for ressources. As far as I know the Trackercalendar was not any connected with the calendar feature. Imho it would be a good idea to create the start and end dates of the Trackercalender by using the field type 'Calendar event'

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

{syntax type="tiki" editor="plain"}
((doc:Together)) works for tracker items. No reason for it not to work for wiki pages

Let's coordinate ((Together|here))

At tiki-admin_actionlog.php the admin need to check each box one by one and there are quite a few if you want to select all.
We should have a select all (while toggle will be ok but less adapted IMO).

It may have to do with the user interface.
It is not user-friendly and even reading the help online (good interface should be understandable without help) it is unclear how to use it until you tried a few times.

Although Tiki tracks reads for specific blog, it would be nice if Tiki tracked reads for a specific blog post.

I noticed today a bunch of trackback spam in my Tiki-powered blog.

According to Wikipedia, "Many blogs have stopped using trackbacks because dealing with spam became too burdensome."
http://en.wikipedia.org/wiki/Trackback

If you get trackback spam in Tiki, here is how to clean:

Using phpmyadmin, go to the table: tiki_blog_posts

And find the colums "trackbacks_to" and "trackbacks_from". They should contain:

a:0:{}

instead of the spam.


Now, a more permanent solution to avoiding Trackback spam would be nice. Checking how other blogging software does it should provide some tips.

Some ideas:
0- A way to turn it off (this exists in more recent version of Tiki 1.9.x, see "Trackbacks Pings" in the admin panel)
1- Easier mass deletion
2- Email notification to blog owner
3- Using an online service to check for spam.

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

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.

In Tiki it is not possible to create tracker items automatically from a remote system. There is no way to include/connect Tiki to a external system.
It would be good if Tiki could be used as frontend and/or database to some automation via M2M (machine to machine) communication.

As example, in Sharepoint you can add list-items via a https-call (API-call). In my environment i used Sharepoint as database and frontend to manage and document backups, which is legally mandatory for us. For that i use some Powershell scripts that do the backups and create a list entry in a Sharepoint list via a API call (https with authentication).
This is also relevant if you like to have a frontend for e.g. (hardware) production and distribution where you can use a barcode scanner that fires a API-call to Wiki to list a parcel in a Tiki tracker.
And so on, and so on, the usage cases are really unlimited and it's a very important function, heavily used in e.g. big Sharepoint Intranet applications.

here: tiki-admin_trackers.php?trackerId= "What field is used for default sort?"

creation & lastModif date should be added

Because:

#1 This is a legitimate & useful way to sort tracker items

#2 If tracker has no sort order, items will not appear in trackerlist plugin. Tracker must be edited (tiki-admin_trackers.php?trackerId=3) after adding some fields so it gains a sort order.

#3 Plus, there appears to be some weirdness in the tracker item count related to this issue.

Tracker export feature works well.

But it provides list of category IDs instead of names. Names would be easier to work with.

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"}
Tracker Field Category just displays one level beneath parentID which I would call a bug as it blows up tracker forms when having a lot of categories with multiple sub-levels to chose from. Addionaly it is (pretty tracker example) intended not to allow editing of (wiki tpl) pages so categories have to be applied through the tracker form itself. In my case I have approx. 250 Categories.

{syntax type="tiki" editor="plain"}
On a Tiki29 I'm using the trackers feature with the tracker field relations to link between 2 trackers.
If I read the tooltip, the online help and the documentation (https://doc.tiki.org/Relations-Tracker-Field) what is working to filter on a tracker should work with the tracker field relation "filter" parameter.

From the __tracker list items view__, I can use: type=trackeritem&tracker_id=2&_sort=tracker_field_actionsDate
This is working fine.

If I use this (and other variations) within __the filter field of the tracker field relations__, the html front and to insert/edit an item is broken for the tracker field relation.

I had a look at the code.
At lib/core/Tracker/Field/Relation.php I discovered (and updated the documentation)
By default the objects that can be selected are sorted using "title_asc" unless the "Format" field is not used.

If, in the options of the Relations tracker field, the "Format" field contain something, the option of the multiple select list of objects will use the first field in the "Format" field.

For exemple, using "({tracker_field_actionsDate}) {title}" will tell the sort to use the field "tracker_field_actionsDate".

BUT, the direction will stays "_asc" as this is hardcoded.
It should be possible:
# To select more precisely what field(s ?) should be used for sorting the objects
# It should be possible to use any direction, _asc or _desc.

In a tracker I can use a rules for an item link. (to hide a different field if the item link field contain one of several value for exemple).

If I set the parameter "Select multiple values" to yes, the rule is not working anymore.

To be used with Google Maps & Tiki Maps to show locations of tracker items.

For example, the venues of phpbeer.com:
http://phpbeer.com/tiki-view_tracker.php?trackerId=1

Text areas are nice. But wiki pages with history are even nicer.

Not sure how it could done though...

phpBB is a popular open source forum software.
Sometimes, a forum is not enough.
So, the data must be migrated from phpBB to Tiki forums...

If you want to help:
Please post links to similar scripts.
ex.: phpbb to invision board, etc
If/when we do a script, we should do for all major forums.
---
__From kerrnel22 on 11/20/07:__

I have almost completed an integrated TikiWiki forum migration tool for 1.9.8.x and 1.10. Initial release will be to migrate only Tiki forums from one Tiki install to another. However, hooks are in place, and the intention is there, to work on extending the migration tool to importing of phpBB2 (or any other forum software) into Tiki. If you would like more information, email tiki.kerrnel@kerris.com. I expect a general release of the forum migration tool (for Tiki forums only) into cvs of both branches for beta testing by December 1/07. If all goes well, I'll have something released for phpBB2 migration prior to Dec 31.