Add a Text Area Field to add custom properties. (eg.: "gcm_sender_id" for FCM support)

TYPO3 Version: 12.4.8
Extension Version: 2.0.0
Composer Installation: Yes

First and foremost, thank you very much for your TYPO3 v12 modifications. I attempted to use the extension and encountered two problems, all of which were related to the fact that extensions in TYPO3 v12 are no longer stored in /public/typo3conf/ext.

1. When I check my console in the frontend, I receive the following error:

Failed to register a ServiceWorker for scope ('[...]/typo3conf/ext/pwa_manifest/Public/Javascript/') with script ('[...]/typo3conf/ext/pwa_manifest/Public/Javascript/sw.js'): A bad HTTP response code (404) was received when fetching the script.

2. Up until now, we had uploaded the manifest icons to our sitepackage extension. I tried using EXT: in the site configuration to set a dynamic path to the icons, but that does not get resolved. It would be awesome if this worked because I don't want to put them into fileadmin. 😅

Hey guys,

thanks for your plugin. Its my first contact with PWAs and it seemed simple to install. My test installation url is https://teamdoku.de/
I gave the plugin the base url as start url and / as scope. But its not going to work. May you help me to find the issue?
Sorry for the greenhorn question ;-)
Greetings,

Chris

Add the option to make shortcuts in the manifest.

reference: https://web.dev/app-shortcuts/

Currently, it is not possible as far as I know to do this in a clean and user-friendly way.

It seems weird to specify the Start URL when the entry Point / base is already set. The entry Point / base can also be overriden with basevariants which is very helpful for local development.
Maybe make an option to either specify a Custom URL or use the base(with basevariants) ?

Implement custom header to cache or disable cache for page.

You can set setting in page to disable cache. By default we send e.g. 'X-Service-Worker-Cache:' and we cache page.

Also, static cache pages could be set in Site Configuration.

We should add TYPO3 v12 support for this handy extension :-)

Some TCA changes regarding deprecated field definitions like

'type' => 'input',
'renderType' => 'colorpicker',

to

'type' => 'color',

and defined('TYPO3_MODE') || die(); to defined('TYPO3') || die(); should already do the trick.

Since these changes would contain BC Breaks a new version of this EXT would be nessary :-)

I'll open a PR in a few minutes.

Include tags in head to provide support for safari browser

If you have another extension that also adds fields to the site configuration,
it may happen that the fields to be displayed are overwritten by the configuration below:

$GLOBALS['SiteConfiguration']['site']['types']['0']['showitem'] = '--palette--;;default,--palette--;;base,
                --div--;Manifest;manifest,--palette--;Manifest;manifest,--palette--;Colors;manifestColors,--palette--;Manifest small icon;manifestSmallIcon,--palette--;Manifest big icon;manifestBigIcon,
                --div--;Manifest Shortcuts;manifest,--palette--;Manifest Shortcut 1;manifestShortcuts1,--palette--;Manifest Shortcut 2;manifestShortcuts2,--palette--;Manifest Shortcut 3;manifestShortcuts3,
                --div--;LLL:EXT:backend/Resources/Private/Language/locallang_siteconfiguration_tca.xlf:site.tab.languages, languages,
                --div--;LLL:EXT:backend/Resources/Private/Language/locallang_siteconfiguration_tca.xlf:site.tab.errorHandling, errorHandling,
                --div--;LLL:EXT:backend/Resources/Private/Language/locallang_siteconfiguration_tca.xlf:site.tab.routes, routes';

File: pwa_manifest/Configuration/SiteConfiguration/Overrides/sites.php

Better would be to replace it with string replace:
https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/SiteHandling/ExtendingSiteConfig.html#extending-the-form-gui