Showing results 1376 to 1400 of 1561

Bug
Accepted Orphaned Localization TYPO3 CMS 10

#92809 Anchor Links in Link Wizard not translated correctly

I have a page A in the default language and a translated page B in ‘Free Mode’.
Page A has a Textmedia content element with an anker link to a content element on the same page.
The content element is selected via Link Wizard – it shows all records from page A.

But when I translate the Textmedia element to page B, the UID of the selected content element on page A doesn’t get updated.
Furthermore I don’t have the possibility to change the selection of the element, because the elements in the Link Wizard on page B are the ones from page A.

Shouldn’t see the editor for page B the content elements on page B in the Link Wizard?

Author Philipp Parzer
Created 11/10/20, 06:52
Updated 01/12/23, 12:41
Feature
New Orphaned Backend User Interface

#99422 Show/hide unused content in the page module only if the user check/uncheck the "show unused content" checkbox

Hello,

We want the editors stop hidding useless contents instead of deleting them, and cluttering their own working area.

This improvement is splitted in smaller, and if possible, independant patches.

link to the full video (publically accessible): https://drive.google.com/file/d/1cxHaU7JHPiDE1_4hFsfDiM1m2YxfHoLz/view?usp=share_link

This tasks relates to the time 1.20min of the video

Rachel

Author Rachel Foucard
Created 12/23/22, 16:27
Updated 01/10/23, 16:17
Feature
New Orphaned Backend User Interface

#99425 Move the delete button from the contents toolbars in the page module to the more action button

Hello,

We want the editors stop hidding useless contents instead of deleting them, and cluttering their own working area.

This improvement is splitted in smaller, and if possible, independant patches.

link to the full video (publically accessible): https://drive.google.com/file/d/1cxHaU7JHPiDE1_4hFsfDiM1m2YxfHoLz/view?usp=share_link

This tasks relates to the time 0.30min of the video

Rachel

Author Rachel Foucard
Created 12/23/22, 16:34
Updated 01/10/23, 16:15
Feature
New Orphaned Backend User Interface

#99421 Replace delete confirmation modale to a notification with undo action for related cases

Hello,

We want the editors stop hidding useless contents instead of deleting them, and cluttering their own working area.

This improvement is splitted in smaller, and if possible, independant patches.

link to the full video (publically accessible): https://drive.google.com/file/d/1cxHaU7JHPiDE1_4hFsfDiM1m2YxfHoLz/view?usp=share_link

This tasks relates to the time 0.42min of the video

The “related cases” have to be defined because some records are really deleted and others are just in the recycler.

Rachel

Author Rachel Foucard
Created 12/23/22, 16:24
Updated 01/10/23, 16:14
Feature
New Orphaned Backend User Interface

#99419 Add a recycler module access icon in the header toolbar list

Hello,

We want the editors stop hidding useless contents instead of deleting them, and cluttering their own working area.

This improvement is splitted in smaller, and if possible, independant patches.

link to the full video (publically accessible): https://drive.google.com/file/d/1cxHaU7JHPiDE1_4hFsfDiM1m2YxfHoLz/view?usp=share_link

This tasks relates to the time 0.34min of the video

Rachel

Author Rachel Foucard
Created 12/23/22, 16:09
Updated 01/10/23, 16:12
Feature
New Orphaned Backend User Interface

#85789 Category Management Module

Hi

I have a TYPO3 instance, in which I manage many categories (sys_category). They are organized in a deeper tree structure. Now I’ve realized, that it’s very cumbersome to manage them. The list module shows them in a flat list and when I have to change some categories in the hierarchy, the only way is via editing every single record and change the parent category.

I imagine a backend module, which shows all categories in a tree-structure like the page tree, where I can organize the categories with drag and drop.

Author Oliver Beck
Created 08/09/18, 10:31
Updated 12/09/22, 16:21
Bug
New Orphaned Frontend TYPO3 CMS 8

#83581 Logical error while checking validity of a shortcut

The function getSubpagesForPages in Class TYPO3\CMS\Frontend\Page\PageRepository uses the constraints given to filter the resulting subpages to also check if the target of a shortcut is valid. The validity of a shortcut target (as the comment line above the function call in question says: “If shortcut, look up if the target exists and is currently visible”) should only depend on its existence and visibility and not any other constraints used to filter the result of getSubpagesOfPages (e.g. a shortcut itself).

Author David Otto
Assigned to Mathias Schreiber
Created 01/16/18, 15:54
Updated 12/06/22, 14:17
Bug
New Orphaned SEO TYPO3 CMS 10

#98362 AbstractMetaTagManager: $replace is useless on metatags with "allowMultipleOccurrences" set

Tried to override metatags from page settings in a plugin on this page.
Failed on og:image, always both, the page og_image and the image from my plugin are rendered, even if $replace = true is set.

TYPO3 Versions 10 & 11

lines 117 and 150 in TYPO3\CMS\Core\MetaTag\AbstractMetaTagManager
The code does not allow to replace metatags with “allowMultipleOccurrences” set

if ($replace === true) {
    $this->removeProperty($property, $type);
    $this->properties[$property][] = ['content' => $content, 'subProperties' => $subPropertiesArray];
    return;
}

if (isset($this->handledProperties[$property]['allowMultipleOccurrences']) &&
    (bool)$this->handledProperties[$property]['allowMultipleOccurrences']
) {
    $this->properties[$property][] = ['content' => $content, 'subProperties' => $subPropertiesArray];
}
Author Alexander Köberl
Created 09/16/22, 09:51
Updated 11/28/22, 12:23
Feature
New Orphaned Database API (Doctrine DBAL)

#84971 Support for Master slave database using wrapperClass and Doctrine's MasterSlaveConnection class

It would be awesome to provide a wrapperClass for $GLOBALS[‘TYPO3_CONF_VARS’][‘DB’][‘Connections’] that support Doctrine\DBAL\Connections\MasterSlaveConnection.php.

I think i have a working prototype bundled into a typo3 extension.

Basically, it is just a class that extends \TYPO3\CMS\Core\Database\Connection containing some of the code from Doctrine\DBAL\Connections\MasterSlaveConnection.php

Author Simon Ouellet
Created 05/11/18, 15:51
Updated 11/23/22, 10:13
Bug
New Orphaned Backend User Interface TYPO3 CMS 11

#99056 SingleSelect takes full width if select icons are used

Author Oliver Bartsch
Assigned to Oliver Bartsch
Created 11/10/22, 17:14
Updated 11/10/22, 17:14
Feature
New Orphaned Linkvalidator

#89426 Remove stale broken links in tx_linkvalidator_link

If a page (or content element, or …) is removed, the related broken links are not removed from tx_linkvalidator_link.

They are not displayed because only broken links of subpages of current page are displayed, so it is not a huge problem. But, eventually, this clutters up the tx_linkvalidator_link table.

Currently, there is no possibility to remove stale (no longer relevant) broken links except removing them manually from the db table.

Author Sybille Peters
Created 10/15/19, 19:35
Updated 11/03/22, 09:04
Feature
New Orphaned Install Tool

#88521 Incoherent settings interface: Presets don't show "non-final" warning while Site-Wide Configuration does

While the settings in “Configure Installation-Wide Options” show a warning if a change in LocalConfiguration will not be the final value

Note that $GLOBALS['TYPO3_CONF_VARS'] currently contains a different value. This could mean that the value is overwritten in AdditionalConfiguration.php. 

This is not the case under “Configuration Presets”.

Use case: you change e.g. the mail config from “Configuration Presets” -> Mail -> Custom while settings are set in AdditionalConfiguration.php. While used to getting the warning in “Configure Installation-Wide Options”, you won’t get a warning here.

Author Jonas Eberle
Created 06/07/19, 15:22
Updated 11/03/22, 09:04
Bug
New Orphaned Localization TYPO3 CMS 9

#88024 allowLanguageSynchronization doesn't synchronise cropping from images

I have an image in a TCA and want to reuse this image (and the cropping) in localised records. I configured the field (relevant snippet):

'image' => [
    'config' => \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig(
        'image',
        [
            ...
            'behaviour' => [
                'allowLanguageSynchronization' => true,
            ],
        ]
    ),
]

In backend now I have the possibility to switch between “Custom value”/“Value of default language” in the image field. I created a new record, added an image, cropped it. Now I localised the record, the image with cropping is copied over from the default language.

When I change the cropping of the default language record, the new cropping is not used for the localised record (“Value of default language” is set) in backend preview and frontend output.

When I now change the image in the default language record and apply a cropping, both are set in the localised record.

I encountered the same problem with l10n_mode=exclude: If the cropping is changed later it is not reflected in the localised record.

TYPO3 version 9.5.5

Author Chris Müller
Created 03/27/19, 16:26
Updated 11/03/22, 09:04
Bug
New Orphaned Localization TYPO3 CMS 8

#86231 Distinguish between free-mode localization and chained translation

Based on my note https://forge.typo3.org/issues/86141#note-5 when analyzing the behavior

TL;DR

When skimming over the examples below, focus and compare the values in l10n_parent and realize that l10n_source is optional.

Usage

Localizations can be created using the graphical backend interface (e.g. page module) or by invoking direct commands to DataHandler [1]. Thus even if the page module is only valid for tt_content records, it does not prevent records from being translated or localized explicitly. That’s why this analysis used element instead of tt_conent a pointer to a database table holding relevant records.

Terminology

Connected Mode

When translating elements, each element is bound to it’s relative ancestor. This results into a chain (that can be used for language fallbacks etc.).
The following example illustrates that, l10n_parent always points to the initial record in default language, l10n_source points to it’s relative translation ancestor – that’s the record a new translation is based on. All records are connected in a chain.

+ element:1 - English (Default)           - language:0, l10n_parent=0, l10n_source=0
+ element:2 - French Translation          - language:1, l10n_parent=1, l10n_source=1
+ element:3 - Franco-Canadian Translation - language:2, l10n_parent=1, l10n_source=2

Free Mode

When localizing elements in free-mode, the previously mentioned translation chain is broken up, thus “free-mode localizaion elements” are in a specific language, but are not related to any relative ancestor and thus are idependent. The following example uses element:3 as “free-mode localization”, l10n_parent is set to 0, but l10n_source still points to it’s relative localization ancestor (just as information, not as a strict relation in like a “composition” [2] would have been).

+ element:1 - English (Default)           - language:0, l10n_parent=0, l10n_source=0
+ element:2 - French Translation          - language:1, l10n_parent=1, l10n_source=1
+ element:3 - Franco-Canadian Translation - language:2, l10n_parent=0, l10n_source=2

The Challenge

Translation from existing localization

It is possible, to create a new localization directly, that does not have a record in default language – or as alternative start a translation based on a “free-mode localization element”.
The example shows, that the “English (Default)” record is now missing – the translation chain should(!) start with “French Translation” as first chain link. Since no record in default language s involved l10n_parent stay empty with 0, only l10n_source point to their according relative ancestor records.

+ element:2 - French Translation          - language:1, l10n_parent=0, l10n_source=1  # <- translation chain or free-mode localization?!
+ element:3 - Franco-Canadian Translation - language:2, l10n_parent=0, l10n_source=2  # <- translation chain or free-mode localization?!

When comparing the “Franco-Canadian Translation” here to the one shown in the “Free Mode” section, it cannot be distinguished anymore, whether the record is part of a “translation chain” or has been created as “free-mode localization”.

The information in l10n_source is not mandatory

Besides that, the information stored in the l10n_source field is optional and has to be configured in the control section of $TCA using the translationSource property. Thus, that information might not be available at all. The following examples show persisted results without having the l10n_source information.

Connected Mode without l10n_source

+ element:1 - English (Default)           - language:0, l10n_parent=0
+ element:2 - French Translation          - language:1, l10n_parent=1  # <- part of a translation chain, which one?!
+ element:3 - Franco-Canadian Translation - language:2, l10n_parent=1  # <- part of a translation chain, which one?!

It is not possible anymore to determine at all, whether a record is part of a translation chain – since the relative ancestor is missing.

Free Mode without l10n_source

+ element:1 - English (Default)           - language:0, l10n_parent=0
+ element:2 - French Translation          - language:1, l10n_parent=1  # <- part of a translation chain, which one?!
+ element:3 - Franco-Canadian Translation - language:2, l10n_parent=0  # <- translation chain or free-mode localization?!

It is (like in section “Translation from existing localization”) not possible to distinguish between “connected translations” and “free-mode localizations”.

References

[1]: DataHandler commands “localize” and “copyToLanguage”: https://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/Typo3CoreEngine/Database/Index.html#command-keywords-and-values
2: Association, Aggregation, Composition in UML: https://www.visual-paradigm.com/guide/uml-unified-modeling-language/uml-aggregation-vs-composition/

Author Oliver Hader
Created 09/12/18, 08:51
Updated 11/03/22, 09:04
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 11

#90736 Wrong slug fields for siteroots (level > 1) in multidomain environment and no possibility to modify them

In a multidomain environment (where the sites are not located in the first level) the “is_siteroot” pages slugs are generated wrong. In addition, there is currently no possibility to manage them without directly modifying the slug in the database.

For example, if a new page is created in level 2, depending on the way it is created (wizard and from type of the parent from which executed) the slug field is shown in tca form. Even if slug is set to “/” here, “/1” or similar is saved instead. After that the field is not shown ony more at all.

Suggestion: At least when the created page is set to “is_siteroot”, the slug should automatically bet set to “/”.

Regarding multi language sites (like in my case), the behaviour should be checked, too. But it looks like the translated pages slug ist correctly set to “/”.

I am using version 9.5.14.

- Root [0]
-- Start [1] (Just for assigning some global TS, often use case)
--- Domain A [is_siteroot + site configuration] -> Slug is set to "domaina" or (if set to "/" if form is shown) to "/1"
--- Domain B [is_siteroos + site configuration] -> Slug is set to "domainb" or (if set to "/" if form is shown) to "/2"
Author Jan Kornblum
Created 03/11/20, 17:45
Updated 11/01/22, 17:24
Bug
Needs Feedback Orphaned Backend User Interface TYPO3 CMS 11

#96765 Deleted subpages are not listed in the history

Deleted subpages are not listed in the history. As a consequence they can’t be rolled back.

HOW TO REPRODUCE THE ISSUE

Create the following page tree:

The database table pages shows the following records:

SELECT uid, pid, title, deleted FROM pages;
+-----+-----+-----------+---------+
| uid | pid | title     | deleted |
+-----+-----+-----------+---------+
|   1 |   0 | page 1    |       0 |
|   2 |   0 | page 2    |       0 |
|   3 |   0 | page 3    |       0 |
|   4 |   1 | subpage A |       0 |
|   5 |   1 | subpage B |       0 |
|   6 |   1 | subpage C |       0 |
+-----+-----+-----------+---------+

Delete “page 1” (ID: 1) from the context menu in the page tree:

The database table pages now shows the following records:

SELECT uid, pid, title, deleted FROM pages;
+-----+-----+-----------+---------+
| uid | pid | title     | deleted |
+-----+-----+-----------+---------+
|   1 |   0 | page 1    |       1 |
|   2 |   0 | page 2    |       0 |
|   3 |   0 | page 3    |       0 |
|   4 |   1 | subpage A |       1 |
|   5 |   1 | subpage B |       1 |
|   6 |   1 | subpage C |       1 |
+-----+-----+-----------+---------+

The “page 1” is marked as deleted and also its subpages (ID 4, 5, and 6). Now open the History/Undo function from the context menu in the page tree:

The history shows the deletion event of “page 1” but not the subpages. Even if the toggle switch “Show sub elements” is enabled. You can roll back the deletion of “page 1” but you can’t roll back the deletion of the subpages.

Author Michael Schams
Created 02/07/22, 01:44
Updated 10/12/22, 16:58
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 11

#98592 DataHandler: copy l10n-exclude fields even if excluded for current user

prose

cite: https://typo3.slack.com/archives/C025BQLFA/p1629827725005900

step by step

Pre-requisites: TYPO3 installation with at least one additional language. e.g. default + EN

Then u need:

  • backend user with no admin rights. I name it ‘editor’.
  • don’t give this user rights to see `is_siteroot`

Now:

  • with an admin account: create a new page, name it “Atemberaubende Weltkugel” (uid:1), make it a root-page (check `is_siteroot`)

Then:

  • log in as ‘editor’
  • visit page uid:1 in page module
  • click “translate page”
  • save page

what now happens

The translated page has `is_siteroot` set to `0` (it is the ext-tables.sql default value – see https://github.com/TYPO3/typo3/blob/v12.0.0/typo3/sysext/core/ext_tables.sql#L75).

what I expect

The translated page `is_siteroot` aligned with default-language. Because this reason: “‘l10n_mode’ => ‘exclude’” (https://github.com/TYPO3/typo3/blob/v12.0.0/typo3/sysext/core/Configuration/TCA/pages.php#L718)

Author Anonymous
Created 10/12/22, 16:14
Updated 10/12/22, 16:17
Task
New Orphaned Backend User Interface TYPO3 CMS 12

#98560 Improve the usability on the user settings page for screen reader users.

I’ve opened issue #98556 yesterday. But remembered that I’ve also find a different set of problems for the password field on the user settings page. I’ve created a small screen recording in TYPO3 v12 with DDEV on MacOS 12.6 with VoiceOver announcing.

  • As you can seen in the sidebar the description underneath the first password field with a p element and an unordered list element gets not announced in the screenreader. the p and the ul might be wrapped and an aria-describedby attribute added to that wrapping element to create an association. currently that information might go unnoticed to at least for some screen reader users potentially.
  • i’ve used the same password pattern i’ve successfully used in the installer. there i have used tester111 and on the user settings page /typo3/module/user/setup i’ve changed the password to tester222. as you can see but not hear in the video the password fails not meeting the password requirements. it is only shown in the admin notice but not announced to the screenreader. me as a user dont know anything went wrong (nor if the process was successful – in that case i get three admin notices with user setting were updated, a notice to reload the backend that most changes take effect and another notice that the password was updated – i can see those but i dont get the announce aurally)
  • in the context of a password that was not meeting the criteria i have the problem that the hide and show functionality used in the installer is not available here therefore i am unable to crosscheck before hitting save and at the same time in case it fails i have no idea which criteria i failed to meet.
  • after i have entered the password and the confirmation password i am not sure where the save button is. as i sighted user i know it is at the top but if i rely on the the aural interface i ahve to remember that it was at the top ( in case the working memory is small then that might be a problem). in the video i have used the rotor to find the list of available form controls to navigate to it afterwards i have simply tried to hit enter after entering the passwords and it saved that way as well. but that is unexpected. having the save functionality at the end of the page in the dom and just move it up by css might be worth a thought.
  • and there is also no need to confirm the change of the password by entering the old password it looks like?

i’ve then noticed there is also another place you are able to change the password in the TYPO3 backend: /typo3/module/system/BeuserTxBeuser . if i choose my user there there is a single password field. that field also has no hide and show functionality and i am able to change(?) the password to something like test which isnt meeting any of the requirements at all without a problem if i hit save i get an announcement that my record was successfully saved. in case the password IS saved there i could have made a typo and just save it unnoticed and wonder at a later point i am unable to login when i type in the password i thought i’ve saved without the typo. and no password requirement checks are applied here it seems. it seems inconsistent between the different places you enter passwords. and again no already existing password is needed (or is it because i am an admin user? – *again the disclaimer not a typo3 user here)

Author Ralf Koller
Created 10/09/22, 12:52
Updated 10/09/22, 12:53
Task
New Orphaned Install Tool TYPO3 CMS 12

#98556 Improve the usability of the password field + the hide/show functionality for screenreader users

A few weeks back I’ve taken a look how a password field and in case available, the hide and show password option, is announced in screeenreaders across different CMS systems. one of the CMSes I have taken a look at back then was v11 of Typo3. I got reminded to that issue today when I tested the new TYPO3 v12 support in DDEV (*disclaimer: i am not a Typo3 user). The behavior is slightly different but the overall result more or less the same. For the context I have tested on MacOS 12.6 with VoiceOver in Safari. A few observations:
  • the announcement of the recommendations showing up when the first character is entered into the password field gets immediately stopped on the second keystroke. if you enter a password manually you usually add the first one or two characters fast, as soon as you know you are in the password field, that way the announcement gets cut off (see v11.mp4). problem if you leave the field and reenter that announcement isn’t made again. seems it is only announced when it shows up for the first time.
  • for sighted users the password strength is communicated by the change of color of the password field. screenreader users are completely missing out on that information.
  • the state change if the password is hidden or shown with the icon/button isn’t announced. one functionality which I considered convenient in Joomla was if you change the state of hide/show the focus shifted back to password field.
Author Ralf Koller
Created 10/08/22, 23:50
Updated 10/09/22, 10:25
Task
Under Review Orphaned composer / dependencies / third-party TYPO3 CMS 12

#98481 Hash package version into public resource paths

This applies to installations in TYPO3 composer mode using
typo3/cms-composer-installers v4 where TYPO3 extensions
are stored in vendor/ and their public resources as linked
to public/_assets/.

The symlink name in public/_assets/ should be extended to be not
just a hash of the relative path to the vendor folder, but also
acts as a cacheHash, by including the package version into the
symlink name.

That means an extension update of packages/extensions
will trigger a new symlink name.
This has the drawback that that names in public/_assets/ are
no longer predictable, but brings the benifit that this will allow
TYPO3 to skip modification-timstamp-lookups in
GeneralUtility::createVersionNumberedFilename() and to generate
performant JavaScript importmaps via trailing slashes1 syntax.

Author Benjamin Franzke
Assigned to Benjamin Franzke
Created 09/30/22, 12:43
Updated 09/30/22, 14:08
Bug
New Orphaned TYPO3 CMS 11

#98457 Processed file doesn't exist

Use case: configure TYPO3 so that f:uri.image generated files are created inside typo3temp instead of fileadmin folder.

Steps to reproduce:
1. have ‘fileadmin/ (auto-created)’ storage with uid=1
2. have ‘typo3temp’ storage with uid=2
3. setting processingfolder field of ‘fileadmin/ (auto-created)’ storage to ’2:assets/_processed_’

This setup results in f:uri.image renders the correct path (eg: /typo3temp/assets/_processed_/e/6/959161_10151652466566963_1259477499_o_5a95879fc3.jpg) but the file doesn’t exist.

Author Christian Toffolo
Created 09/28/22, 09:30
Updated 09/28/22, 09:30
Feature
New Orphaned Form Framework

#88056 mode insertIfNoUpdatePossible

Formhandler had the option insertIfNoUpdatePossible for records which did not exist. So if the where clause fails, an insert will be executed. It would be great for the form framework.

Author Bernhard Eckl
Created 04/02/19, 15:45
Updated 09/24/22, 15:12
Bug
New Orphaned Backend User Interface TYPO3 CMS 11

#92664 Some input elements are cut off when resized and cause horizontal scrolling

A user should be able to resize a website up to 200% without text getting clipped or truncated. It mostly works when the user hides the .scaffold-content-navigation.

There are some input elements that are cut off:

  • In General: URL Segment
  • In Behaviour: Link Target
  • In Resources: Include static Page TSconfig (from extensions)
  • In Resources (Lightbox File selector): “Upload files”, “Add new media asset” and “Create new folder”
  • In Access: Usergroup Access Rights
  • In Social Media: Type of card to show
  • The date picker

#tas2020

Author Jakob Widhalm
Created 10/22/20, 10:42
Updated 09/24/22, 14:42
Bug
New Orphaned Fluid TYPO3 CMS 11

#97707 Fluid forms return old values

TYPO3 unserializes old values and sends them to controller action.

Steps to reproduce;
1) Setup an action that simply returns a default response.
– Should be blank so to speak.
– Should have one parameter. For simplicity, make it be a DTO with one
parameter for the input field and a reference a simple validator.
2) Setup the validator. Make it simple, something like if string is longer than 3 characters (or whatever) and return an error if shorter.
3) Setup a simple form with one input field for the validator and a submit button.
4) After setup, run the following test.
– Submit a VALID string. The form will return with no errors.
– Then, submit an INVALID string. It will be accepted.

I know. You are like, what?? Yeah. It will be accepted, even though the validator said it has errors.

Where things go wrong:
Here: \TYPO3\CMS\Extbase\Mvc\Controller\ActionController::forwardToReferringRequest() . In this method, arguments are sought from __referrer internal arguments instead of the submitted values. Normally, if errors are found, only two elements are found in the arguments form variable: controller for controller name and action for action name. This is because they were submitted originally with the form and they will recycle as long as the validator finds errors. Nothing else will be added to it. This is good… until it validates. When it validates, results are sent directly to the action controller and not through the error controller. When the process goes back to the form, the object or arguments submitted will be added to the form and returned to the user. Remember it validated. When you then send a wrong value, it goes to the error controller, old values (that validated) are unserialized and forwarded to your action. And that’s how you end up with old values in your action.

Assumption:
Form post values processing seem to be built under the presumption that once a form validates, you won’t need it again. This needs correcting.

Author John Miller
Created 05/29/22, 13:47
Updated 09/24/22, 14:28
Feature
New Orphaned Form Framework

#98259 Set GET/POST values to additionalParams of form-tag

Hello form Team,

I have a multi-step formular and I want to edit a record.
I have added the record UID to GET vars and I found a solution to set the default values to the values of the requested record.
If I switch to page 2 the record UID is gone.
I need a solution to add the record UID as parameter for the URL.

For static values I would do something like that:

type: Form
identifier: newEvent
label: Create a new event
prototypeName: standard
renderingOptions:
  additionalParams:
    tx_events2_events:
      event: 42561
  submitButtonLabel: Submit
  fluidAdditionalAttributes:
    class: withtip frame-indent

Can you please add a placeholder for GET and/or POST vars?

Stefan

Author Stefan Froemken
Created 09/05/22, 10:30
Updated 09/05/22, 10:32

Showing results 1376 to 1400 of 1561