maikschneider / bw_static_template Goto Github PK

Version 12 of TYPO3 has been released - this extensions needs to support the new major version as soon as possible!

The small JavaScript snippet in the backend preview is blocked in TYPO3v12 when the Content-Securit-Policy of the backend is enabled. Should be refactored to a module include.

With the TYPO3 update to 12.3, the content element bw_static_template is no longer displayed in the special tab of the NewContentElementWizard.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update all dependencies

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update actions/checkout action to v4
• chore(deps): update dependency bk2k/bootstrap-package to v14
• chore(deps): update typo3 packages to v13 (major) (typo3/cms-base-distribution, typo3/cms-core, typo3/cms-lowlevel)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Hej there,

we're using the extension to work on a continuous prototype within a new TYPO3 project. Because we can't merge the database only one frontend developer can actually work simultaneously on the prototype.

Is there a way to use "mergable" json files for providing the temporary data or do you have another idea how to solve this kind of issue?

Thanks

Hej there,

is it possible to provide an optional title for the TYPO3 content element "Static Template" to have a better overview in the backend web module to distinguish between the different static elements.

Thanks so far

This repository was transferred from bitbucket. After the next release of this extension in official TYPO3 TER the old repository should be deleted.

Thinks to take into account:

• All links (README, TYPO3 documentation, composer.json,..) pointing to the old repo should be updated
• Existing issues need to be created over here and the authors should be notified
• Packagist URL update