Feature #51570

Unpersisted changes in Safe Requests should throw an Exception

Added by Marc Neuhaus about 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2013-08-30
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

With the recent change to not trigger persistAll in safe request methods (GET/HEAD) some users
stumble over not getting their entities saved because of this. Altough it's written to the log
and mentioned in the docs i think we should also throw an exception telling the developer about this
if the following conditions are met:

  • the current request method is a safe request method (GET/HEAD)
  • the current context is the development context
  • the user added/updated/removed an entity using a Repository or PeristenceManager
  • the user did not trigger persistAll using the PersistenceManager on it's own

Related issues

Related to TYPO3.Flow - Feature #47951: Warn if persistence stack is not empty at the end of a get-requestNew2013-05-05

Actions

Also available in: Atom PDF