Category: 23.x

Currently, German legislature is pondering the implementation of the dreaded article 17 (formerly Article 13) of the EU Copyright Directive into German law. Similar implementations must be under way in all member states.

This Article demands that "platform providers" (as general as this term sounds, this means everyone from Youtube down to a privately run Tiki installation) MUST provide online upload filtering of media that could possibly be copyrighted, which translates into "ALL media" AND a "red button" with which copyright holders are enabled to immediately (!) block content they find and deem infringes their held copyrights.

As the IT magazine "c't" informes, the proposed "German copyright service providers law" describes several stages that user uploaded media MUST go through before they may go online.

Platforms shall sign contracts with copyright organizations such as GEMA (for music) etc. Licensed content may go online directly. Other content will have to undergo online filtering. Depending on filtering results, content may be blocked or the copyright owner may be directly informed of the suspected infringement.

It has been speculated previously, that only VERY large companies like Youtube (Google) will at all be (technically) able to run such filter services, looking at the sheer amount of computing power and I/O bandwidth necessary. Youtube and Co could offer filter services for smaller platforms that lack the ressources, but possibly not free of charge. This has been critized as giving Youtube and Co. huge power and wide control over the internet, given the fact that technically there is no difference between filtering for copyright infringement and filtering for unwanted political content, in other words: Once installed, such filters could easily be used for censorship of the internet. This led to mass protest by young people all over Europe. The ruling conservative party promised angry voters that the implementation of the EU directive would not implement upload filtering, but apparently they broke their promise.

According to the government, filters SHALL be set to "mildly" filter, enabling the majority of content to go online, but mechanisms must be implemented for copyright owners to protest, as well as a "red button" with an immediate (!) takedown effect.

{syntax type=tiki}
{syntax type="tiki" editor="plain"}
This is the ((Tracking system for Tiki issues)).
If this is your first time, please read: ((How to Submit a new item on the Wishlist))

When URL is entered in a parenthesis it takes the closing one and includes it in the external link:

(E.g. Google -- https://google.com/)

The expected result would be that the ")" is not included as part of the link.

On a Tiki23 if the layout option is set with : Classic boostrap (Fixed top menu) the menu is lost when navigating on the admin pages.

The original website logo (brand icon) is changed for a Tiki icon making things more confusing.

{img fileId="1571" thumb="box"}

Bottom module is also lost...

All bootstrap themes or themes bootstrap adaptation will suffer from this problem.
This block upgrading websites.

Note of fixes todo for -+release.php+- hopefully to be tested out on v 22.2
* Fix db connection issue on smarty syntax check step
* Use php -+passtru+- on composer install when using debug-packaging so you can see what's going on
* Use -+php console.php translation:getstrings+- instead of the deprecated get_strings.php

{img fileId="1618" thumb="box"}
Those radio buttons should look like bootstrapped Tiki (colors, borders rounded, etc).

The following markings appear when using an item link (where you allow select multiple items).
It just looks a bit odd. See screen shot for info. {img fileId="2136" thumb="box"}

When the name of a new gallery is very long, an error occurs:
{img fileId="1357" thumb="box"}

Hello, especially the Admin UI revamp team.

I love the new Tiki Admin UI, whilst I am quite massively missing a few nice ideas or our old one. When I supported the idea of a more WP-like approach, I never thought we would lose the old feature tiles panel, which has a lot of advantages in respect of time saving.

I suggest, that we could put it into a module and then add it to the list of standard admin modules, that can be optionally loaded into the admin dashboard.

Aswell there are a number of administration places, where the new admin dashboard style is not yet applied. I assume that is just a matter of time and ressources.

Comments welcome.
Best regards,
Torsten
---

Testing something I checked https://next.tiki.org/tiki-syslog.php where I can see a failed to get user by cookie several time (every 5 minutes) for a user "1974" (seems to be me).

{img fileId="1620" thumb="box"}

Uploading an animaged gif image file that shows a bug reproduced is not an easy task tin dev.t.o.
I had to do that because the record rtc feature is not usable yet, and I wanted to reproduce the issue visually. I did that in an animated gif. I edited the corresponding [item7795|bug report], and uploaded the gif file throught the toolbar icon to "Choose or upload images".
I got the image uploaded (to the default location, I didn't change it, expecting "happy path"), but the wiki syntax automatically inserted seems to not be adapted to displaying gif images.
I recall that any plugin img param that attempts to resize the image converts it to png (or Tiki used to do so years ago), so that I removed the param to make a zoombox, I just left the param to indicate the fileId. But nothing was displayed in the parsed textarea of the tracker item once saved.

Similarly, going to the view file (icon shown from the since last visit module) showed nothing, which might trigger the falsse sensation that the file upload failed.
https://dev.tiki.org/file1?fileId=1562&view=page

But it didn't fail.
If you use the oldish syntax to display the image as an image, then it displays properly, as it can be reproduced here:
https://dev.tiki.org/item7795-Cannot-use-Record-RTC-page-self-refreshed-before-accepting-perm-to-record

Couldn't we get that plugin img when using fileId param to automati8cally display the gif image as image when the plugin notices that it's a gif image indeed?
Somehow...
HTH

Google complain (now?) that there is an issue with my sitemap /tiki-sitemap.php?file=sitemap-index.xml

============

Sitemap can be read, but has errors
Unsupported file format
1 instance

Your Sitemap does not appear to be in a supported format. Please ensure it meets our Sitemap guidelines and resubmit.

============

The file look like this : cat /home/domain/public_html/storage/public/sitemap-index.xml
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by https://git.io/phpseo -->
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9”>
<sitemap><loc>https://www.domain.com/storage/public/articles.xml</loc><lastmod>2021-09-12T07:31:23+00:00</lastmod></sitemap>
<sitemap><loc>https://www.domain.com/storage/public/blogs.xml</loc><lastmod>2021-09-12T07:31:23+00:00</lastmod></sitemap>
<sitemap><loc>https://www.domain.com/storage/public/blogposts.xml</loc><lastmod>2021-09-12T07:31:23+00:00</lastmod></sitemap>
<sitemap><loc>https://www.domain.com/storage/public/sitemap.xml</loc><lastmod>2021-09-12T07:31:23+00:00</lastmod></sitemap>
</sitemapindex>

This file shows error with tools like: https://www.xml-sitemaps.com

XML Validation Results

error Problem detected, please check details below
Sitemap URL http://www.domain.com/tiki-sitemap.php?file=sitemap-index.xml
Character Set
Sitemap is valid No
Warnings -
Errors
Incorrect http header content-type: "text/html; charset=iso-8859-1" (expected: "application/xml")

(If I check https://www.domain.com/sitemap.xml it says it is ok)

Something turned wrong at some point OR Google changed the way it works ?

PS : As temporary mesure on my site I set in Google the sitemap to look for https://www.domain.com/sitemap.xml

===

Update 2021-12-06 after last Tiki23 upgrade:

When I look at the xml produced there : https://example.com/tiki-sitemap.php?file=sitemap-index.xml

I see this and it is rejected of course.
{CODE()}
https://example.com/articles.xml2021-12-06T20:58:02+02:00https://example.com/sitemap.xml2021-12-06T20:58:02+02:00
{CODE}

If I try to split the url and submit those link with date or without is is still rejected.

At some point I see where are my sitemaps: https://example.com/storage/public/sitemap-index.xml

<!-- Generated by https://git.io/phpseo -->
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<sitemap>
<loc>https://example.com/storage/public/articles.xml</loc>
<lastmod>2021-12-06T20:58:02+02:00</lastmod>
</sitemap>
<sitemap>
<loc>https://example.com/storage/public/sitemap.xml</loc>
<lastmod>2021-12-06T20:58:02+02:00</lastmod>
</sitemap>
</sitemapindex>

This is accepted but Google find 0 url...
So I have to submit separately:
https://example.com/storage/public/articles.xml
https://example.com/storage/public/sitemap.xml

I was searching for "tiki Show Category Path" using Google.
The second result is : https://doc.tiki.org/tiki-editpage.php?page=Show+Category+Path

Obviously this is wrong...

{CODE()}
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwjT6tiLm_TzAhW6iP0HHc6vD8gQFnoECAoQAQ&url=https%3A%2F%2Fdoc.tiki.org%2Ftiki-editpage.php%3Fpage%3DShow%2BCategory%2BPath&usg=AOvVaw3jBGKxwUEoDWAyBGqffbcI
{CODE}

{img fileId="1622" thumb="box"}

Creating the first H5P file is successful, but when you try to create additional H5P files, it fails.

{img fileId="1697" thumb="box"}

I added this here because there have been no responses in the forum. The category is support request, and I assume this does not mean request for paid support.

See https://tiki.org/tiki-view_forum_thread.php?comments_parentId=77291#threadId=77544

Maybe this can be handled by a new developer to the project.

There are --2-- 1 issue--s-- of icons alignment for ISO (safari) you can see at https://tiki.org/Wishlist-Triage-Team

* social network alignment
* --translation action button--

{img fileId="1623" thumb="box"}

{img fileId="1624" thumb="box"}

You may need to be logged in to see the issue.

~~#F00:Update~~ : The translation icon I now properly aligned on Safari.

If you take a close look at a long bug report like my "umbrella bug report", you'll see that it bears so many comments, their display gets paginated. That's a good idea. But one would expect that the first comment on page "2" is one following the last on page "1".

But that isn't the case... The last on page 1 is dated August 31st, the first on page 2 is from August 22, 2020...

And yes, I did reload the page to be sure that I do not see old data...

Thanks
hman

Tiki has a way to create "user" plugins with: https://doc.tiki.org/Plugin+Alias

At https://doc.tiki.org/tiki-admin.php?page=textarea or on the instance I created:
Go to Admin, Control Panels => Editing and Plugins => Plugin Aliases.
Create Aliases (or edit) and click on "Plugin parameter documentation" you will see a new form with checkboxes.

This happen on Safari 14.1.2 on Mac OSX but not on Chrome

The "Safe" checkbox overlap with text.
{img fileId="1638" thumb="box"}

1. The {include page=“name”} command is tremendously useful for naive wiki users who add content. It lets them create macros and re-use them at will.

So I suggest that this might deserve an alias {macro } and deserve a description in the wiki syntax help.

Also a slight simplification. If there is no ‘page=”name”’ text but there is {macro “name”} then use “name” anyway.

Any user could do {macro “myheader”} at the top and {macro “myfooter”} at the bottom and {macro “myusualrant”} wherever they want. They just have to make an orphan wiki page for each macro they want.

2. This is so useful and flexible that you might deprecate the “apply content template” thing on the Properties tab. It is hardly any easier to use, and it allows the user to choose only one macro at the beginning. It should keep working for the users who have already used it, but there’s no particular reason for anyone to use it again.

3. To really put the icing on the cake, you might let admins have two macros for each user page, one at the top and one at the bottom. These should not be visible when the user edits the page. So for each page category, the admin could decorate it a special way. Some might automatically get polls or other info visible. Or dancing bunnies, or whatever. It lets admins customize user wiki pages without coding, in ways that are hard to do without coding now. Without annoying users with the displayed calls on their edit pages which they might edit wrongly.

At tiki-admin.php?page=i18n if you enable "Restrict supported languages" you see a text area with 5 languages.
This is too small and make painful selecting several languages.

The text area size cannot be extended.
It should be possible.

{img fileId="1625" thumb="box"}

On the -+tiki-user_information.php+- -> text "__My Info__" is constructed from two strings: "Info" - which is loaded from -+language.php+- (this is OK) and with string "My", which is untraslatable.
Word "My" doesn't load from -+language.php+- (looks as constant).

Interactive translation top bar is not displayed with Bootstrap classic layout.
It is displayed only if you use Tiki classic layout.

When "jQuery Select2 Select Boxes" _placeholder and _firstlabel are lost.
This is pretty bad when you create display in a modern way without wasting space for a label outside the field to be filled.
It displays instead "Select an Option".

-+{select _field="tracker_field_something" _trackerId="10" _firstlabel="pick somethingt" class="form-control"}+-

{img fileId="1783" thumb="box"}
{img fileId="1784" thumb="box"}

Hi all, I have been using tikiwiki since it was about v14 and have seen it use more and more compute resource. I recently pulled a production site from AWS as the compute bills where starting to get out of hand. I think I would have a hard time convincing small sme's to fork out hundreds of euro each month for in-house tikiwiki hosting. Any thoughts are welcome. I have tried disabling various features but it still takes up cpu time. This isn't a complaint, I love tikiwiki , but if tikiwiki increase in size it will become a software suite for large corporations ONLY. Cheers, Kevin.

I've followed the doc page to setup record rtc in tiki23 on a linux box (thanks for the documentation)
https://doc.tiki.org/Record-screen-audio-video

I can't succeed at my attempt to use Record RTC since the wiki page gets self-refreshed each time I click at the button to "Start Recording" before I can accept the firefox popup that asks me to grant perm to this page to record/use media or something (I can't read the message properly since the page is self-reloaded too quickly)

I have a valid https now (It was an invalid https in my first attemps)

Reproduced here in dev.t.o

{img src="display1562"}