Category: Feature request

We have actually the logo module with several preferences and parameters:
http://doc.tiki.org/Module-logo

We have also the look and feel related section (logo):
http://doc.tiki.org/General-Layout-Options#contentlook_generallayout-1

We need to merge those:
* On the look and feel section it says for years (before Tiki 12) that it will be merged.
* Some parameters seems already used by both
* Some parameters are here and not there (site icon which is needed for bootstrap layout - brand image)
* ...

I t is important as it is one of the first settings visited by new users.

At some point a button was added to the logo allowing the admin to upload directly a logo without having to navigate in the admin control panel or modules. However it is not optional and is always displayed. See : https://tiki.org/forumthread78682-Is-it-possible-to-hide-the-admin-upload-logo-icon

Instead of using CSS, it should be possible for an admin to hide it for good.

While some issues have been fixed around logo image, brand icon and classic bootstrap layout, it's still necessary to go to L&F admin to turn on "site logo and title" (IIRC) before the logo module is available to be assigned on the admin modules page. That should be a separate wish.

See related ticket

As discussed during the TRM January 2022: https://tiki.org/Roundtable-Meeting-2022-01
We would like to add an option for documentation link that comes with a theme (more and more theme need documentation).

We discussed the idea to add a manifest;

^
Something human readable like

author: blabla
documentation: https://bla

This can be edited by hand by a non coding themes author

I'd say plain text but yaml is also OK.
^

Related:
((MemoryConsumption))


Here is a very famous error: "Fatal error: Allowed memory size of 8388608 bytes exhausted"
http://tikiwiki.org/art82

And they often cause blank pages. How can we can catch them and render a simple & descriptive error page (not enough memory) instead of a blank page?


__Maybe useful?__
Smarty validation class
http://www.phpriot.com/d/code/smarty/smarty-validator/index.html



Related:
Better protection against accidental site breakage with improper use of code in modules + template
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=1065

We can already send in content to Tiki via email:

add/edit wiki
add articles
via tiki-admin_mailin.php

and add forum posts via
tiki-admin_forums.php


joe@joe.com sends an email. The system recognizes that joe@joe.com belongs to the user "joe" and adds the tracker/wiki edit/forum post/article as if the user joe had logged in and added it via the web form.


Make this optional for security reasons. If someone spoofs the email address, he could send in content for someone else.

Hi:

I want to allow users to send photo moblog posts to our Articles section. After setting up an "Article-Put" account, I'm finding that only the text makes it into the article post, not the attached image file. Just to test, I set up a "Wiki-Put" account, and it DOES recognize and include the attachment (not inline, though, but as an icon and a link).

Does the Article-Put feature have handling for including images inline?

Rob

In my installation, I've tested sending tes

I'd like to have a way to comment on an item from GET by replying to it.

For example, right now an email with the subject:

GET:BigIdea

will send the user the BigIdea page.

A reply with the subject:

RE:GET:BigIdea

would generates a comment on the BigIdea page.

This use is different from appending or prepending. It's meant for a note in the margin not a modification of the original text.

We have this for wiki pages. Maybe add to tiki-admin_notifications.php?

{syntax type="tiki" editor="plain"}
Currently, Tiki does not offer a way to lock tracker items. As a result, it cannot be used for use cases where regulatory requirements mandate that records must be immutable—or at the very least, unchangeable by the end user.

For example, Tiki cannot be used to manage invoices, as regulations in many jurisdictions require that once an invoice is issued, it must never be altered.

That said, regulatory governance is evolving to adapt to the digital age. While practices that were acceptable with paper records need to be reinterpreted for digital systems, the underlying principles—such as immutability—must still be upheld.

In practice, this means that it is often acceptable (or expected to become acceptable) for a company to generate an invoice through software, provided that once finalized (or "closed"), the record becomes uneditable by the user. In such a setup, only a separate, trusted party—such as the software developer or a system administrator—would have access to the underlying database or the tracker interface for closed items.

To comply with regulations, this trusted entity should issue a formal declaration stating that the user (i.e. the company generating invoices) has no ability to alter closed items or access the database. With such a declaration, the software can then be considered compliant, and the user may legally generate official documents like invoices using the system.

__Back to Tiki__ the request is to have a way for a developer to lock closed tracker items.
(system preferences, additional master password, etc)

---

It should be a "per tracker" setting. (properties -> status)
While a new Lock action is a good idea, it won't allow automatisation (plugin List) or allow to apply on a lot of items in one shot. (to be think of...)

This feature isn't internationalized.

The usage of quicktags is hardcoded in the PHP, like

$quicktags = $quicktagslib->list_quicktags(0,-1,'taglabel_desc','','trackers');

for the trackers. The french translation e.g. reads

Catégorie : wiki, formulaires, etc.

So a french user would enter "formulaires", but never see his Quicktags in the Trackers feature.

I would like to offer the upload windows for images and files to open by default in advanced mode.

Some users don't realize that there is an advanced mode where they could/should set things like categories and such.

The admin should be able to force the advanced mode for all or a group of users.

It's a little annoying that when I want to post to my blog, and click on the post link, I am given a pull-down menu of blogs, all but one of which is not mine. Any reason not to filter this list to the set of blogs that I can post to? And, even better, jump to mine if there is only one such blog?

The e-mail notifications of watches (wiki, tracker, article, etc.) are sent out when changes are made. This means that the user submitting the change has to wait for the PHP-Code to send out all the mails before he can continue browsing. This is annoying and even...

... more evil is that with thousands of users to notify of the change the PHP-script will tend to time out and not all the notifications are sent!

One possibility would be to set the timeout higher, but that isn't really a solution at all. So the sending of mails needs to happen asynchronously. One simple solution would be to have a daemon running on the same system, which sends out the mails and the PHP-script just notifies the daemon of what to do. This would make installation a lot harder though and can't really be a desired solution.

Any possibilities to solve this in PHP directly?

Make File gallery tag image files in Tiki according to exif tags and such, and the other way round too.

For instance, we could tag files in shotwell, and upload them to tiki, to have all tags recognized and shown in tiki also.
"Shotwell 0.8 can write metadata to photo files on the fly - to enable this, select the option "Write tags, titles and other metadata to photo files" in the preferences dialog. Once this is selected, Shotwell will update metadata in photo files as soon as you tag them."

Ideally, tags added in Tiki to image files should be added to image exif metadata (and similar), so that when images are exported from tiki they should carry their own tags inside. At least, allow that optionally.

Add a new pref on the login control panel, similar to ''Password expires after'', to set a number of days after which users that have not logged in require admin validation before they can log in again.

This is to automatically weed out users that may have left a third party company, without the Tiki owner knowing about it, and needing to prevent those users accessing sensitive data (for instance after moving to a competitor company).

When shutting down a tiki-site it also affects all remote Tiki-Slaves doing authentication via InterTiki. There needs to be some way to shut down logins on the master Tiki, but still allow read-only access for InterTiki-Slaves.

{CODE(caption=>Basic idea)}
16:51 < ohertel> 2 switches... disable logins, disable logins including intertiki
16:51 < ohertel> first one is for a case like we have now.
16:52 < ohertel> and second one is for like "we update the database" ...
{CODE}

It's really useful to be able to set which fields show on the tracker items list, especially when using inline editing, but this is a -+tracker_admin+- only feature, so it would be good to add a new permission just to be able to set which fields show.

So I could take the time to test an issue in 9.6 and 10.4 and provide more information to the developer.

Thanks!

{syntax type="tiki" editor="plain"}
In barebones profile and in featured profiles, there is intro text about 1st login being necessary with u: admin p: admin (good)

However, this message stays and needs to be deleted by admin (bad)

Perhaps we should have a module with is only visible if admin password has not yet been set.

In edit mode (and maybe also in view mode) ((doc:Items List and Item Link Tracker Fields|ItemsList Fields)) should offer an "Add new item" button and an edit and/or delete icon where the user has those permissions.

This should be new field options and default to off (i.e. empty) for upgrades. This should work like the existing addItems param on ItemLink fields, perhaps with a companion addItemsWikiTpl option for a template.
Options:
* addItem (text to show on an add new things button)
* editItem (y/n to show an edit icon next to each item)
* deleteItem (y/n to show a delete icon next to each item)
* editInViewMode (y/n whether the edit buttons and icons also appear when viewing an item)

{syntax type="tiki" editor="plain"}
This feature arrived in {mr id=5960} but wan't made optional sadly, i might get round to it one day, so this is just a reminder really

I've made a page to display the ((Bug report evolution|Bug report evolution)) over time in dev.t.o, thanks to PluginPivotTable and dereived attributes of the dates, etc.

Charts are displayed, But the chart width seems to be hardcoded to 600px or similar, even if the PivotTable plugin params said width=100% initially, and I forced them to width=1000px, but no change. And in real world scenarios, with long dataset (like in the tiki community with the bug tracker :-) visualization is too concetrated.(and I did not find an easy way to make a quarter aggregation of items, but that's another topic)

Searching a bit, this seems to be an issue already identified in other implementations of pivottable.js in other softwares:
https://github.com/nicolaskruchten/pivottable/issues/848

An easy solution/workaround might involve maping param rendererOptions inside pivottable .tpl (to set plotly width and height) to to the width and height indicated in the pivottable tiki plugin params.
See:
https://pivottable.js.org/examples/scatter.html
{CODE()}
...
rendererOptions: { plotly: {width: 600, height: 600} }
...
{CODE}

Probably below this chunk of code in wikiplugin_pivottable.tpl (lines 411-51) in trunk:
{CODE()}
...
{{if $pivottable.heatmapParams}}
rendererOptions: {
heatmap: {
colorScaleGenerator: function(values) {
return Plotly.d3.scale.linear()
.domain({{$pivottable.heatmapParams.domain|json_encode}})
.range({{$pivottable.heatmapParams.colors|json_encode}});
}
}
},
{{/if}}
...
{CODE}

I would like the java irc client pjirc to use grab the usernames from the tikiwiki database to log the people in when they want to use the irc channel. it is very similar to the mod for Simple machine forums http://pjirc.dtmdotexe.com/index.php?option=com_smf&Itemid=26. It will only work for registered users and does not need to work with wiki markup or group permissions (works as long as you are logged in). You do need a php script to input the irc server/channel to connect to.

Illori

Make PluginChart optionally reuse some other lib already in Tiki to make js-based charts (raphaeljs, chartjs, d3.js, etc)

By default PluginChart was able to produce these charts:
https://doc.tiki.org/Spreadsheet+Graphics+and+Charts#Select_the_Graphic_Type_and_Output_Format

But it would make total sense to have the option to produce js-based or svg-based charts, like the ones currently produced by the Spreadsheet js feature ( , reuing raphael.js lib), or the ones in theory available in the ((doc:PluginChartJS)) plugin and lib.

Strategic feature to get Spreadsheets and charts out of them in the game again.

There is another request to have the png & jpg versions of the charts produced again (they are currently not shown), since this implies an easy solution for charts in PDF reports working automagically without requiring complex solutions to get js-based charts incluided in PDF reports.
This request, though, is to have an some optional parameter added to get the chart produced with some JS lib already in Tiki like the ones cited above. And we will see elsewhere how to ensure that they can be included in the printed PDF, etc.