Task #12841

FLOW3 Exceptions Collection: Collect requirements

Added by Daniel Brüßler about 8 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Start date:
2011-02-07
Due date:
% Done:

100%


Description

Tasks for this issue:

  • done: Info in mailinglists and forge-news to admins and the forge-developers
  • current: installation of FLOW3 and creation of the GettingStarted-app

Related issues

Related to wiki.typo3.org - Task #13128: Flow exception texts: Clean up meta info Resolved 2011-02-18
Related to wiki.typo3.org - Task #13127: MediaWiki hook: Select the header to show for TYPO3 CMS/Flow exceptions Resolved 2011-02-18

History

#1 Updated by Daniel Brüßler about 8 years ago

  • Target version set to sprint 2010/12

#2 Updated by Daniel Brüßler about 8 years ago

  • Target version changed from sprint 2010/12 to 843

#3 Updated by Daniel Brüßler about 8 years ago

  • % Done changed from 0 to 70

#4 Updated by Daniel Brüßler about 8 years ago

  • Status changed from Accepted to Closed
  • % Done changed from 70 to 100

Steffen Gebert (core 4):
- version 4 will have the same exception-technique, the url will have the information if v4 or v5

Karsten (core 5):
- parsing the source is not needed, details are there when an exception is thrown

=> in the wiki just the user-contribution text, no meta information, the mediawiki-hook must select the header to show

#5 Updated by Chris topher about 7 years ago

  • Project changed from Documentation to wiki.typo3.org
  • Category deleted (887)
  • Target version deleted (843)

#6 Updated by Chris topher about 7 years ago

  • Subject changed from Collect requirements - As provider I need the current requirements to FLOW3 Exceptions Collection: Collect requirements

Also available in: Atom PDF