Neue Rituale

Version 1.0.2 Add composer support Add missing audio mime types Add clear buttons in process view Optimize xml handling Fix Error messages and SSML empty input detection

The module can help you to make your website content more accessible. It synthesis text fields via the Google Text2Speech Api. Synthesis jobs are placed in a queue and processed one after the other. The text fields can be configured by selection or via SSML. Voice, language and speed are configured via JSON. The module's queue supports LazyCron, but can also be triggered manually. Features Simple integration via the native file field. Support SSML. Direct synthesis via save action Queue for many synthesis jobs Process page for an overview of the queue Download & Install Github: https://github.com/neuerituale/ProcessTextSynthesis Modules directory: https://processwire.com/modules/process-text-synthesis/ Composer: nr/processtextsynthesis

This module allows you to add media metadata information to FieldtypeFile fields. Under the hood it uses the PHP library by James Heinrich and stores the raw data in the fields' filedata property. Download & Install Github: https://github.com/neuerituale/PagefileMetadata Modules directory: https://processwire.com/modules/pagefile-metadata/ Composer: coming soon

Hi Teppo, Would it be possible to make the 'isRepeatableField' in Indexer.php method hookable. I would like to attach our FieldType 'FieldtypePageTableNext'. That would be great. ?

Hello @TomPich, if I have understood correctly, you are looking for $value. $page is the page on which the sections are created, $value is the section page (@see ___renderValueWrapper() ). The :root properties in css must also be defined in :host for the shadow dom. :root, :host { --color-white: #fff; --color-light: #F5F5F5; --color-gray-light: #EEEEEE; --color-silver: silver; }

Hey @kongondo, will Padloper be developed further and when will it be available again?

Version 1.0.4 - Optimize updateAllFeeds method.

The module provides a paths under which cronjobs can be registered. It lists all registered cronjobs and can execute individual ones manually. The last execution, the last status and, in the event of an error, the last error message are displayed. Download & Install Github: https://github.com/neuerituale/ProcessCronJobs Modules directory: https://processwire.com/modules/process-cron-jobs/ Composer: coming soon

@Gideon So Yes, the module requires PHP version 7.4 or higher. I will show that more transparently in the next version. You could replace the line with this one private $essence = null;. But I think there will be more incompatibilities to php@7.1.

Thanks for the great modules. Maybe this was answered, unfortunately I didn't find anything about it. How can I remove or overwrite the routes from "DefaultRoutes.php"? I have already tried it with this: $module = $this->wire('modules')->get('AppAPI'); $module->registerRoute( 'auth', [ ['OPTIONS', '', AppApiHelper::class, 'noEndPoint'], ['GET', '', AppApiHelper::class, 'noEndPoint'], ['POST', '', AppApiHelper::class, 'noEndPoint'], ['DELETE', '', AppApiHelper::class, 'noEndPoint'], ] ); Unfortunately, they are still accessible and functional.

Good to know. ?

Are you sure? I thought only when personal data is transferred. (e.g. in cookies). By the way, here is a basic example of how to store the oembed image in a separate image field. In this example, the field name is "mediaImage". But i think it is a good idea to integrate this as a feature of FieldtypeOembed.

Yes, the developer needs to take care of it. We use it in different ways. One variant works with the template tag. For this, the content from `html` is wrapped in a `<template>` tag. Instead of the content, a message is displayed that refers to the external content of its respective provider. After clicking, the content of the template tag is appended into the DOM with JavaScript. Here is an example: https://koerber-stiftung.de/en/projects/the-berlin-pulse/highlight-the-berlin-pulse-digital-tools-give-repressive-governments-the-upper-hand/#s18430 Another way is to insert the `html` (iframe) of videos (Youtube or Vimeo) via the nocookie domain or with dnt=1 parameter into Plyr. The embed data can also be used to configure the video player and placeholder (poster image, duration, aspect ratio). The click on the play button is then also the consent. Data is then also sent via the "normal" youtube domain. The advantage of this method is that it only requires one click (trusted click) because the html is already initialised. https://koerber-stiftung.de/mediathek/debattle-das-wortgefecht-4/ Another feature is you can find pages by OEmbed properties like:`$pages->find('my-embed-field.providerName=YouTube')`

Version 1.1.6 Fix issue #6 TypeError Wire Oembed class Update Readme

Version 1.0.3 - Update composer file - Optimize library loading - Update library versions - Optimize backend preview