Giter Club home page Giter Club logo

dce's Issues

Upgrade Wizard Bug (DCE 2.9.1 - Typo3 11.15.16)

Hi, I wanted to inform you that a problem with the Upgrade Wizard persists in version 2.9.1 (with Typo3 Version 11.15.16).
(I thought that maybe it is better to open a new issue for this)

When clicking on "Run Upgrade Wizard" in the Install Tool (or BE) while DCE is installed the same 503 Error message appears as mentioned in #28 (comment).

When activating ['SYS']['exceptionalErrors'] => 12290, additional information is displayed:

DceErrorScreenshot

Originally posted by @uzerterter in #28 (comment)

Undefined array key "_LOCALIZED_UID" in FalViewHelper

Versions

  • DCE version: 2.8.4
  • TYPO3 version: 11.5.10
  • PHP version: 8.1

Describe the bug

PHP Warning: Undefined array key "_LOCALIZED_UID" in /public/typo3conf/ext/dce/Classes/ViewHelpers/FalViewHelper.php line 64

Looked into the code, still not fixed there. I think there should be multiple array key access guards added there anyway.

image

Undeclared arguments passed to ViewHelper TYPO3\CMS\Fluid\ViewHelpers\Link\TypolinkViewHelper: useCacheHash

We updated from DCE 1.6 some time ago and everything worked on Typo3 10.

After updating to Typo3 11.5.16, DCE 2.9.1 throws this error:

Undeclared arguments passed to ViewHelper TYPO3\CMS\Fluid\ViewHelpers\Link\TypolinkViewHelper: useCacheHash. Valid arguments are: parameter, target, class, title, language, additionalParams, additionalAttributes, addQueryString, addQueryStringMethod, addQueryStringExclude, absolute, parts-as, textWrap

Last entry in DCE before going to Typo3 Core:

at TYPO3Fluid\Fluid\View\AbstractTemplateView->render()
in /var/www/zoechling-holz.rv-works.dev/httpdocs/typo3conf/ext/dce/Classes/Domain/Model/Dce.php line 868

Trim Phone Number

Hi,

is it possible to remove everything from a phone number except + and digits? Would be great to enter a phone number like this +49 30 012345-678 once, and link it as one correctly.

Kind regards

Core Exception with DCE-elements

Versions

  • DCE version: 2.9.3
  • TYPO3 version: 11.5.23
  • PHP version: 8.1.12

Describe the bug
We get the error message:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1316104317: The default controller for extension "Dce" and plugin "dceuid7" can not be determined. Please check for TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php. | TYPO3\CMS\Extbase\Mvc\Exception thrown in file /html/typo3/web/typo3/sysext/extbase/Classes/Mvc/Web/RequestBuilder.php in line 217. Requested URL: https://dummy-stage.domain.tld/a-slug

Did anyone get this error too?

We upgraded the typo3-instance two week before to typo3 v11. The first site on production runs well, buit the 2nd (multisite) has some problem as well. Beneath the error message some elements do not get rendered at all and stay blank.

The rendered html-code in debug of the fuild template looks very strange:

   content => ' <div id="c17568" class="frame frame-default frame-type-header frame-layout-0">
       <header class=page-header> <h3 class=""> <p>Something aaa</p> </h3> </header>     
       </div> <div id="c" class="frame frame- frame-type- frame-layout-">
       </div><div id="c" class="frame frame- frame-type- frame-layout-">
       </div>' 

Please look at the part of div id="c" - already the uid is missing.
No wonder, since the messages tells it cannot even setup the plugin: The whole content is missing as well.

Did anyone experience that issue already? How to solve?
We've seen a part of the code in
Classes\Components\ContentElementGenerator\OutputPlugin.php:62
asking for Typo3-Version10.
Should this and other locations with similar code be expanded to Typo3 v11? (Maybe i'm totally wrong)

We are looking forward for any solution.

Thank you, Thomas

Typo3 12 Compatibility

it would be great to get a typo3 12 compatibility for this extension.
Will there be an update for Typo3 12 in the near future? Asking for my next web project.

Undefined array key warnings

Versions

  • DCE version: 2.8.3
  • TYPO3 version: 11.5.9
  • PHP version: 8.0.18

Describe the bug
After upgrading to PHP 8.0 DCE throws the following warnings.
Currently unable to test if it's related to development context or anything but the only thing changed was the php version afaik.

Core: Error handler (FE): PHP Warning: Undefined array key "dce_enable_autotranslation" in /var/www/html/public/typo3conf/ext/dce/Classes/Domain/Repository/DceRepository.php line 536
-- | --
Core: Error handler (FE): PHP Warning: Undefined array key "dce_enable_autotranslation" in /var/www/html/public/typo3conf/ext/dce/Classes/Domain/Repository/DceRepository.php line 527
-- | --
Core: Error handler (FE): PHP Warning: Undefined array key "dce_ignore_enablefields" in /var/www/html/public/typo3conf/ext/dce/Classes/Domain/Repository/DceRepository.php line 510

Order of a section may get shuffled when deleting an section entry

There is some weird behavior when deleting an element from a longer section, as in it sometimes reorders the section elements somewhat randomly, tho there does seem to be some kind of pattern to it.

My simple DCE element:
image
image

Now I create the content element based on the DCE element and add 20 section entries numbered 1 to 20 (left backend, right frontend):
imageimage

So far, so good. However, when I now delete the 5th entry (or basically any other) and save, the the order gets shuffled (left backend, right frontend):
imageimage

Also, this does not always occur and I couldn't reliable replicate the issue with fewer section entries like 10 or so, but it happened every time when starting with 20 section entries tho.

I am running DCE v2.8.4 and Typo3 v10.4.27

Undefined array key "NEW[...]" in typo3conf/ext/dce/Classes/Hooks/AfterSaveHook.php line 367

Saving a record which should throw "SQL error: 'Unknown column '[XY]' in 'field list'' " throws the PHP warning:
"Undefined array key "NEW[...]" in typo3conf/ext/dce/Classes/Hooks/AfterSaveHook.php line 367".

For me this happened when I tried to save an object of a custom extension where the field name in the database was incorrect (misspelled). It didn't find the field and accordingly couldn't save the record.

PHP-version: 8.0
Installation: TYPO3 11.5.13
DCE-version: 2.9.2

To reproduce:
Create a custom extension with a field in tca which doesn't exist in the database. Save record. The error above should appear instead of the correct "unknown column"-error.

Can be fixed as follows (Line 367 in AfterSaveHook.php):
instead of:
if (!$pObj->substNEWwithIDs[$id]) {
add a check for array key:
if (!array_key_exists($id, $pObj->substNEWwithIDs) || (array_key_exists($id, $pObj->substNEWwithIDs) && !$pObj->substNEWwithIDs[$id])) {

Not thoroughly tested though.

EXT:container causes unwanted behaviour

Versions

  • DCE version: 2.9.0
  • TYPO3 version: 11.5.13
  • PHP version: 8.1.3

Describe the bug
When EXT:container is installed, in page module the following warning is thrown:

PHP Warning
Core: Error handler (BE): PHP Warning: Undefined property: DOMText::$tagName in /var/www/dce/Classes/Components/ContentElementGenerator/OutputTcaAndFlexForm.php line 306

This only occurs, when the DCE/system caches has been cleared.

Additionally, this may cause missing items in CType dropdown (see #15 (comment))

Emptying the recycler leads to internal server error (500)

Versions

  • DCE version: 2.8.4
  • TYPO3 version: 11.5.13
  • PHP version: 8.1.1

Describe the bug
Selecting all items in the recycler and clicking on "delete" shows an endless button spinner animation. Even if there is no DCE to delete. Browser console shows that the AJAX call leads to an internal server error (500).

The TYPO3 log shows:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1476107295: PHP Warning: Trying to access array offset on value of type null in /Users/***/typo3conf/ext/dce/Classes/UserFunction/CustomLabels/TtContentLabel.php line 28 | TYPO3\CMS\Core\Error\Exception thrown in file /Users/***/typo3/typo3_src-11.5.13/typo3/sysext/core/Classes/Error/ErrorHandler.php in line 137. Requested URL: http://local.***.de/typo3/ajax/recycler?token=--AnonymizedToken--

Invalid flex form data structure on field name "pi_flexform" with element "bild" in section container "container_bilder": Nesting inline elements in flex form sections is not allowed.

Hello Armin, thanx for your great work on DCE.

The error above occurs on TYPO3 10.4 when i try do use a DCE with

  1. Normal Element named title
  2. Sektion named bilder
  3. in the section a FAL - Element bild

This seems to be somethin that leads to such nested elements that were working in earlier TYPO2 Versions like 7.x.

I don't have such deep knowledges in Flexforms. So, can you help ?!

Waldo

handling of individual icons for DCEs

Versions

  • DCE version: 2.x.x
  • TYPO3 version: 11x
  • PHP version: 7.x

Describe the bug

Using own icons for the DCEs works nice but to move them from one website installation to the next you must put them in the fileadmin. This is not ideal. The perfect place would be a sitepackage. Assuming that you use a standard bundle of DCEs to start a new website.

But you can not travel with them in a standard-starting-sitepackage that you use for every website, since the links are in the database and if the name of the sitepackage changes the links crash.

solution: ?

DCE is also quite harsh if the links to the icons crash, then the whole website crashes. Would be nice if it would be a bit more forgiving. Maybe with a missing icon in the DCE backend view and not with a crash of the whole site.

Argument 1 passed to T3\Dce\Domain\Repository\DceRepository::findByUidIncludingHidden() must be of the type int, null given

Versions

  • DCE version: 2.9.2
  • TYPO3 version: 10.4.32
  • PHP version: 7.4.11

Describe the bug
When I click at "System -> Reports" or the "Upgrate Wizard" I get this error:
TypeError

Argument 1 passed to T3\Dce\Domain\Repository\DceRepository::findByUidIncludingHidden() must be of the type int, null given, called in C:\xampp\htdocs\git\typo3-bildkunst\public\typo3conf\ext\dce\Classes\UpdateWizards\FileToFalUpdateWizard.php on line 103

Solution: add this if-statement:
if (isset($affectedDceRow['uid'])) { ... }

Container multi language (free mode) issue in 2.8.1

Scenario:
-Simple DCE with wrapping container ("Enable DCE container" = true and "Enable detail page" -> false)
-everything works fine on default language -> sys_language_id = 0
-on sys_language_id = 1, the dce container has the right number of elements inside, but they are all the same (equal to the first element)
-Version 2.8.0 does not have this issue -> I found lines 182 - 186 in Classes\Components\DceContainer\ContainerFactory.php to be guilty of this behaviour. Those lines are not present in 2.8.0, i guess those lines fix another issue but cause this new one.

Note:
I only tested this with "Free mode" -> not with the other modes.
Also tested only TYPO3 versions 10.4.23 and 10.4.25

Best regards
Sascha

Using standard image field for mapping causes error

Versions

  • DCE version: 2.9.3
  • TYPO3 version: 11.5.17
  • PHP version: 7.4

Describe the bug
I create a fresh TYPO3 11 installation with DCE, then I did:

  • create a new DCE
  • create an FAL field using the suggested configuration (https://github.com/a-r-m-i-n/dce/files/9921386/configuration.txt)
    and fill out other required fields
  • Map field value to TCA column -> existing field "image - Integer"
  • save the DCE
  • create a page and use the DCE you just created
  • insert an image and save
  • I get the error:

503
Oops, an error occurred!
An exception occurred while executing 'UPDATE tt_content SET image = ? WHERE uid = ?' with params ["NEW636280595631b052851626", 4]: Incorrect integer value: 'NEW636280595631b052851626' for column database.tt_content.image at row 1

Now I can fix it for already created elements by clicking on "Update TCA mappings", but doing so for every new element isn't a good workflow :)

copy and paste of DCEs with the TYPO3 system

Versions

  • DCE version: 2.x.x
  • TYPO3 version: 11
  • PHP version: 7.x

Describe the bug
Sometimes a DCE is a good starting point for a new one, if they are quite similar. But using the TYPO3 copy and paste system in list view doesn't work as expected. Usually you loose most of the input fields or you even get input fields from other DCEs.

Changing field of type section to element causes issues

Versions

  • DCE version: 2.8.4
  • TYPO3 version: 11.5
  • PHP version: 7.3

Describe the bug
I've had a DCE with a "section" field including 3 fields inside. I've then changed the section field to element.
However, the variable now was not available at all in frontend.
I then checked the database and it turns out that "section_fields" still had a value of 3.

After clearing this field, the variable was available again.

Container > Detail stops working after first translated item.

Hi @a-r-m-i-n , I'm asked to repost the bug report here, in Reference to the discussion in the Slack channel yesterday.
Please let me know if you need any more info to reproduce this error.

Current setup:

  • Enable DCE container = True
  • Hide other container items, when detail page is triggered = True
  • Detailseite = True
  • Slugs and Detail all setup according to DCE documentation

Result:

  • All works in Default language
  • Without Slugs the detail page works as expected
  • First element in English works with Slugs enabled
  • In English, after the first DCE, the detail stops working and shows all items in list view.

This is somehow related to the slugs, without the clean URLs the page renders normally.

Kind regards,

Erik

Template files & browser are broken on typo3 >9

Typo3 11.5.6 or 10.4.24 (migrated from 9.5.31)
PHP 7.4.27
DCE 2.8.1

Template file browser is missing and file URI inside a text field is displayed instead.

image

Even though a file is specified with correct syntax, it seems to not be resolved correctly which leads to no elements being rendered.

Workaround: switch to inline type & copy-paste file contents, inline templates work fine.

DCE: Frontend-fluid-paths not working?!

Versions

  • DCE version: 2.9.4
  • TYPO3 version: 11.5.27
  • PHP version: 8.1.13

Describe the bug
Hi Armin,

i discoverd a bug, as far as i can see:

You described the TS-setup here:
https://docs.typo3.org/p/t3/dce/main/en-us/AdministratorManual/TyposcriptConfiguration.html#

I use this one in the code:

# DCE - config - include fluid-styled-content-partials for DCE
plugin.tx_dce.view {
  templateRootPaths {
    10 = EXT:vb_frontend/Resources/Private/ext/dce/
    20 = EXT:fluid_styled_content/Resources/ext/fluid_styled_content/Private/Templates/
    30 = EXT:fluid_styled_content/Resources/Private/Templates/
  }

  partialRootPaths {
    10 = EXT:vb_frontend/Resources/Private/ext/dce/Partials/
    20 = EXT:vb_frontend/Resources/Private/ext/fluid_styled_content/Partials/
    30 = EXT:fluid_styled_content/Resources/Private/Partials/
  }

  layoutRootPaths {
    10 = EXT:vb_frontend/Resources/Private/ext/dce/Layouts/
    20 = EXT:fluid_styled_content/Resources/Private/Layouts/
  }
}

There is no way to get layouts works, except when providing it in den DCE-Module >> DCE-Element >> Misc-Tab >> Layout-Path.
But this is not what we need here.

We would need a working Fuild-Path-Setup.

The behavior instead is like:

  • Regardless, if plugin.tx_dce.view is here or not, it's never considered for renderung DCE-Frontends;
  • I can delete the snippets above by deleting all the lines: the paths in plugin.tx_dce.view are not defined by DCE itself; does not change anything;
  • I can delete it by plugin.tx_dce.view > - does not affekt anything;
  • I can change the order of the single lines with the paths: does not affect anything

So, it seems the path setup by plugin.tx_dce.view is not considered at all in the frontend.
So, the basic question is, IF it is intended to work with these pahts, as the documentation tells?

Thank you for your feedback!

Thomas

DCE container not having the possibility to get input from an editor

I you use DCEs containers, very often the headline changes every time you use the container-DCE on a different place/page on the website.
Since it is usually a organic design block it is not so perfect to work with two DCEs. One on top and then the container.
It would be nice if an editor could also pipe input to the container head.

BE module: usage not counting hidden items

Versions

  • DCE version: 2.9.3 but I think it is the same for all versions
  • TYPO3 version: 11

The module is showing a usage counter - thats quite handy. But it counts only active elements. In some projects the editors add many items and all are hidden for some time. To me this looks like this DCE is not used - and maybe can be deleted.

If it would show the total amount of all instances, the info would be better usable.

Best wishes,
Mario

[bug] When editinga DCE directly from the file manager. Links are not updating.

Versions

  • DCE version: 2.9.3
  • TYPO3 version: 11.5.24 / 11.5.25
  • PHP version: 7.4 / 8.2

Describe the bug

In short: When editing a DCE directly from the File Manager / Dateiliste. Links are not updating.

In our case, we have a simple Download list module (Repeating DCE List with a Name & Link Flexform). A client wants to update his old download files for new ones. So he went into the file manager, and looked at which DCE modules reference the old download files. He then opens one of the DCE Download Modules referencing the file. Which opens neatly in a frame. He starts changing the links, but after selecting a new file the link input never updates, and the old file never updates. This is an issue only with the Typolink configuration.

I found out that when opening the module directly on for example the downloads page. The links are being updated just fine. So this is a problem with the view from File Manager. I tested this scenario in another project, and could confirm the same behaviour.

01
1: Open file from file manager

02
2: See which modules reference the file

03
3: Edit the file directly in the module overlay (this is not working)

em_conf.php and composer.json have opposing settings

Versions

  • DCE version: 2.9.3
  • TYPO3 version: 11.5.19
  • PHP version: 8.1.12

Describe the bug
composer.json says:

   "require": {
        "php": ">=7.3",

em_conf.php says:

    'constraints' => [
        'depends' => [
            'php' => '7.3.0-7.4.99',

Both together do not make sense.
It leads to have composer running on PHP 8.1 correctly, what is basically ok. But should faild for the em_conf-contraint and for bug #43 .
Our experience is, that DCE runs well on PHP 8 except bug #43
So, please adapt em_conf:

    'constraints' => [
        'depends' => [
            'php' => '7.3.0-8.1.99',

or even to php 8.2.

Many thanks,
Thomas

Uncaught TYPO3 Exception in Classes/Components/ContentElementGenerator/OutputPlugin.php

When running typo3/sysext/core/bin/typo3 scheduler:run from a cronjob I got the following error:

Uncaught TYPO3 Exception syntax error, unexpected '' (T_ENCAPSED_AND_WHITESPACE), expecting '-' or identifier (T_STRING) or variable (T_VARIABLE) or number (T_NUM_STRING)
thrown in file [...]/typo3conf/ext/dce/Classes/Components/ContentElementGenerator/OutputPlugin.php
in line 54

I also got this error when testing the code with an online php parser.

Systeminformation:
TYPO3 10.4.24 classic installation (non-composer)
PHP 7.2.23
dce 2.8.1 and latest github version

DCE Container on pages with news detail page outside of the news record, does not work

The DCE Container feature checks for tx_news_pi1|news to be present. It does not respect if the news record being displayed contains the actual DCE container element.

This makes it currently impossible to use DCE container on news detail pages, outside of the news detail page itself (e.g. in a sidebar column).

Possible fix: At this point, when the news parameter is present (https://github.com/a-r-m-i-n/dce/blob/master/Classes/Components/DceContainer/ContainerFactory.php#L52), get an instance of the news record and check if the current element is part of news being displayed.

Bug trows exception on FileToFalUpdateWizard

Versions

  • DCE version: 2.9.3
  • TYPO3 version: 11.5.19
  • PHP version: 8.1.12

Describe the bug
https://github.com/a-r-m-i-n/dce/blob/master/Classes/UpdateWizards/FileToFalUpdateWizard.php
On line a missing array key is check an old way:

 [ TYPO3\CMS\Core\Error\Exception ]
  Warning: Undefined array key "uid" in /html/typo3/web/typo3conf/ext/dce/Classes/UpdateWizards/FileToFalUpdateWizard.php
  line 100

=> Appears by running the upgrade-wizard (cli or backend)
=> Appears only in some constellations of content we did not find out exactly. But something like: a old non FAL-file-field is there, but not even used once: The read records a NULL / empty and leads to that error

Please make the fix on line 100:
old
if ($affectedDceRow['uid'])
new
if (!isset($affectedDceRow['uid']))

We assume it's related to PHP 8.
Anyways, DCE runs on php 8 and has missleading settings in em_conf.php and composer.php
There i write another issue.

Please fix as soon as possible since we deploy that on many sites adapting the line manually on live systems.

Thank you very much,
Thomas

Rendering problems on other language versions as the main language

Versions

  • DCE version: 2.8.1
  • TYPO3 version: 10.4.26
  • PHP version: 7.4

Describe the bug
After the upgrade from 2.7.7 to 2.8.1 i noticed something:
If you have DCE-Elements on a page then every dce element on the page is rendered as the first dce element on the page but only on different languages as the main language.

After a downgrade from 2.8.1 back to 2.7.7 everything was alright again.

I could reproduce it on two different TYPO3 installations.

Cheers,
Chris

Disabling frontend caching not working

Versions

  • DCE version: 2.9.4
  • TYPO3 version: 11.5.26
  • PHP version: 7.4.3

Describe the bug
After upgrading to TYPO3 11, the "Cache DCE frontend plugin" does not work anymore.
Something does not work anymore at the registration of the plugins, a quick look in $GLOBALS['TYPO3_CONF_VARS'] all the DCE registered plugins have no "nonCacheableActions" set even though they have the "Cache DCE frontend plugin" disabled in backend.

Screenshot 2023-06-07 at 13 09 45 Screenshot 2023-06-07 at 13 09 59

2.8.2 breaks t3:// templates

Versions

  • DCE version: 2.8.2
  • TYPO3 version: 10.4.26
  • PHP version: 7.4

With 2.8.2 "t3://" paths for templates such as "t3://file?uid=1234" stopped working. I suspect file: paths have the same issue, but I have not tested it yet.

I don't think this is intended behavior, as the changelog states that this file reference feature is now only marked as deprecated. It is not yet a breaking change, where support for it is actually dropped.

Dependency repositories ext-json/ext-dom not available anymore

Hey

just wanted to update from DCE v2.6.2 to 2.9.3 via Composer (Composer-based project) but unfortunately the repositories for ext-json and ext-dom are gone (or now private).
I'm running ddev composer req t3/dce and the output is:

Info from https://repo.packagist.org: #StandWithUkraine
./composer.json has been updated
Running composer update t3/dce
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 4 updates, 0 removals
Downloading ext-json/ext-json (dev-main b4052aa)
0/1 [>---------------------------] 0% Failed to download ext-json/ext-json from dist: The "https://api.github.com/repos/alirezac0/SomeBBShit/zipball/b4052aa796309eb390f4c61cec10124d71b5ad90" file could not be downloaded (HTTP/2 404 ):
{"message":"Not Found","documentation_url":"https://docs.github.com/rest/reference/repos#download-a-repository-archive"}

Any ideas how to continue? As long as the repos don't come back, you can't update.....

Thanks
Matthias

Problem with config field type: file upload

Versions

  • DCE version: 2.8.4
  • TYPO3 version: 10.4.28
  • PHP version: 7.4

Describe the bug
when i add field type : upload file in my custom dce, and i add content type my custom dce, i have error like

TCA internal_type of field "settings.myfield" in table tt_content must be set to "db" or "folder".

Screenshot_29
Screenshot_30
Screenshot_31

I checked also with :

  • DCE version: 2.6.2
  • TYPO3 version: 10.4.21
  • PHP version: 7.2
    and ï've had the same error

backend search not working

  • DCE version: 2.8.4
  • TYPO3 version: 11.5.13
  • PHP version: 8.0.11

When dce is installed the spinning search wheel in typo3´s backend never stop spinning when trying to search in backend in the searchform top right
billede

<f:debug>{_all}</f:debug> does not work in template fluid area

Versions

  • DCE version: 2.9.4
  • TYPO3 version: 11.5.28
  • PHP version: 8.1

Describe the bug
Debugging all variables does not work, when you want to debug some variables it works.
Bildschirmfoto 2023-07-14 um 11 45 15

i have a new information, you have the debug problem only when the typo3 system is in the debug mode.

Wrong File Path in Composer mode

Versions

  • DCE version: 2.9.3
  • TYPO3 version: 11.5.26
  • PHP version: 8.1
  • Typo3 Composer Mode

Describe the bug
If i use the new Composer mode. To be fit for TYPO3 V12.

See https://github.com/TYPO3/CmsComposerInstallers/releases/tag/v4.0.0-RC1 and https://b13.com/core-insights/typo3-and-composer-weve-come-a-long-way then the Codemirror Code in the Backend is not loaded. Console says wrong MIME Type because the Url for CSS Point to HTML instead to CSS.

I have made a new Commit for that
master...i-kiu:dce:master

Incompatibility to `smichaelsen/no-insecure-typo3-extensions`

Versions

  • DCE version: 2.8.3
  • TYPO3 version: 11.5.9
  • PHP version: 7.4

Describe the bug
The installation of the package is not possible if a project uses smichaelsen/no-insecure-typo3-extensions as well:

Problem 1
    - Root composer.json requires t3/dce 2.8.3 -> satisfiable by t3/dce[2.8.3].
    - smichaelsen/no-insecure-typo3-extensions dev-master conflicts with typo3-ter/dce 2.2.0 || 2.2.1 || 2.3.0 || 2.3.1 || 2.4.0 || 2.4.1 || 2.5.0 || 2.5.1 || 2.5.2 || 2.6.0 || 2.6.1 || 2.7.0 (t3/dce 2.8.3 replaces typo3-ter/dce *).
    - smichaelsen/no-insecure-typo3-extensions is locked to version dev-master and an update of this package was not requested.

Do not provide file picker wizard for file templates (cause t3:// links are not supported)

I have a problem with DCE and TYPO3 v11. Maybe it's a misconfiguration of the new v11?

I'm developing a new site locally under the subdirectory /kohlern

Now when I select a file as template via popup in the fileadmin folder I first see it as "t3://file?uid=4"
After saving it get's translated into /kohlern/fileadmin/template/dce/headerSlider.html
instead of fileadmin/template/dce/headerSlider.html and it doesn't work in the frontend.

Is this a problem with v11? Do I have to change something in the configuration so it doesn't get mismatched because of the siteroot?

Upgrade Wizard fails

Versions

  • DCE version: 2.9.0
  • TYPO3 version: 11.5.13
  • PHP version: 7.4.27

Describe the bug
The upgrade wizard fails. No additional bug message, no PHP error.

It's a local installation used for testing and development.

Here is what was written to the /var/log/dce_update_wizard.log:

Mon, 01 Aug 2022 14:38:46 +0200 [DEBUG] request="703737bdc7216" component="T3.Dce.UpdateWizards.FileToFalUpdateWizard": Executing update of T3\Dce\UpdateWizards\FileToFalUpdateWizard 
Mon, 01 Aug 2022 14:38:46 +0200 [DEBUG] request="703737bdc7216" component="T3.Dce.UpdateWizards.FileToFalUpdateWizard": Checking for new folders to create in fileadmin 
Mon, 01 Aug 2022 14:38:46 +0200 [DEBUG] request="703737bdc7216" component="T3.Dce.UpdateWizards.FileToFalUpdateWizard": 0 new folders created. 
Mon, 01 Aug 2022 14:38:46 +0200 [DEBUG] request="703737bdc7216" component="T3.Dce.UpdateWizards.FileToFalUpdateWizard": Moving old media files 
Mon, 01 Aug 2022 14:38:46 +0200 [DEBUG] request="703737bdc7216" component="T3.Dce.UpdateWizards.FileToFalUpdateWizard": All found media files moved. Start indexing new files in FAL 

And some screenshots:
Bildschirmfoto 2022-08-01 um 14 38 39

Bildschirmfoto 2022-08-01 um 14 38 45

Bildschirmfoto 2022-08-01 um 14 39 15

dceOnPageUid

I have realized a background slideshow with the dce extension. But as there is the same background on each page I handle it over a folder in the page tree which gets implemented into the layout.

Normaly I would only load the js ans css files if a dce is used on the page using the [dceOnCurrentPage("42")] condition. But as the dce is not on the page but in the folder it does not recognize it. A condition like dceOnPageUid would be prefect to. Do you have a solution for my problem?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.