Feature #38094: Option to redirect after form submitting - TYPO3 Core - TYPO3 Forge

Custom queries

12 LTS
Accessibility
Dashboard issues
Easy tasks
Extbase Issues
FAL Issues
FAL Sprint 2023
Hierarchical Issues
Issues reported for v11
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
Most wanted Bugfixes
Most wanted Features
My open issues
New & Unassigned
No feedback within 90 days
Open Bugs
Open issues of 10
Page Tree Regressions after 2020-07-28
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (5)

Christoph Dörfel
Felix Nagel
Patrick Broens
Stefan Neufeind
Webtech AG

Actions

Copy link

Feature #38094

closed

Option to redirect after form submitting

Added by Webtech AG almost 12 years ago. Updated over 5 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

Form Framework

Target version:

Start date:

2012-06-15

Due date:

% Done:

100%

Estimated time:

PHP Version:

5.3

Tags:

Complexity:

Sprint Focus:

Description

There are no options to set a subject for the new form wizard. Please add a third field for the subject.
There are also no options to set a forward to a TYPO3 page (e.g. jump to page). These features are really important.

Related issues 1 (0 open — 1 closed)

Has duplicate TYPO3 Core - Feature #44482: Postprocessor to do redirect (on success)

Closed

2013-01-13

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Lorenz Ulrich almost 12 years ago

Please keep in mind that one issue per change is needed. The subject stuff is a duplicate of #35787. So maybe we can rename that to "Option to redirect after form submitting".

Actions

Copy link

Updated by Ingo Renner almost 12 years ago

Subject changed from No subject or forward to a page in the new form wizard to Option to redirect after form submitting

Actions

Copy link

Updated by Ingo Renner almost 12 years ago

Priority changed from Must have to Should have
Target version deleted (~~4.7.2~~)

Please do not set the target version, this is up to the release manager - or the point in time when you provide a patch and when it is merged. For this issue particularly I'd say it is a feature and thus cannot go into 4.7.x anyway.

Actions

Copy link

Updated by Stefan Neufeind over 11 years ago

Or could we maybe do it as part of a post-processor? A "redirect processor" that then sets a destination which will be redirected to once all processors have finished their job?

Actions

Copy link