History: TikiFest Fosdem 2018 Whiteboard

View published page Collapse Into Edit Sessions

Preview of version: 14

TikiFest Planning (topics/activities)

TikiFest Planning (topics/activities)

Planning things

Fixing sessions

Crash course: how to solve "small" bugs and track regressions (phpStorm) - (started)

Editing a Plugin via plugin helper icon on a translated page looses the translation assigned!

https://dev.tiki.org/item5700

Tracker plugin, we can’t set the fields order anymore

https://dev.tiki.org/item6389

Plugin inline editing is saved but modal stays open

https://dev.tiki.org/item6285

Plugins should refresh content at start of inline editing to avoid overwriting previous changes

https://dev.tiki.org/item6324

Numeric field 0 value is returned as "No value" in the plugin list

https://dev.tiki.org/item6417

Tracker plugin, transaction step don't work

https://dev.tiki.org/item6496

Rebuild index exit page not where it started (BS)

plain page, no more admin icons, etc

Tracker plugins are not displayed in the plugin help anymore

Fixing and improving GUI for the plugin list

Intertiki "Never logged" wrongly over user on the userlist (JB)

Fixing multiple errors on page all over Doc and Dev (JB)

Structure create a child page is not there anymore (BS)

Fixing Demo/Tiki pending stuff

Next dogfood server (Amette)

KGB irc communication repairs

Better update/upgrade (switch branch) for the show instances

Reviewing trunk for regressions (untested commits)

Features request

Renaming a page should be logged in wiki history

Fixes and opinions

Login restriction (JML)

Opinions on suggested features of restricting the number of login devices per user.

Every month I can allow only 3-4 computers (browsers, actually), to access the site as paying subscribers with the same user/password (paying subscribers are all in the same tiki group).

I am thinking I could limit the browsers a user can use each month (via cookies?) to 3.
When a registered user connects to xxxxxx.com, we set a cookie in his computer, and we register his computer/browser as "authorised computer for 30 days"
Every time he comes back to xxxxxxx we read his cookie to we check if he is an "authorised computer". If he is already authorised we let him log in, if he is not we check how many "authorised computers" do we have listed from him. If we have less than 3 authorised computers we register his new computer and let him log in. If he already has 3 authorised machines no deny the login.
In case a computer is not used in 30 days we drop it from the list of authorised computers.

I will also need a "control panel" so I can manually remove authorised machines from the list (I guess I will have to make some exceptions as users buy new computers, delete cookies, travel...), or change the number of authorised devices to 4, 5, 2...

Looks good for Tiki19? Needs rethinking? Looks good to me.

Tracker variables in templates (JML)

According to https://doc.tiki.org/Pretty-Tracker#Syntax_tips we should be able to access and display all fields of a tracker item in the template of TRACKER plugins plus the following:

Copy to clipboard

($f_create): created date
 ($f_status_input): status input field
 ($f_status): status (output)
 ($f_itemId): the item id
 ($f_lastmodif): last modified date (this will display unix date, for human readable date look below)
 ($itemoff): the iteration number of each item
 ($tr_offset): the offset of the item, i.e. this is the nth item of the total number of x items

Tracker variables in mail output (JML)

We should be able to access and display all fields of a tracker in the outgoing mail template.

According to https://doc.tiki.org/PluginTracker we are also missing the following: