Task #7338

Refactor TYPO3 Content Service so that it uses the Content Repository API

Added by Karsten Dambekalns over 9 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%


Description

The content service should use the CR API directly, now that we no longer hide it in the lower layers of FLOW3.


Related issues

Related to Base Distribution - Story #7144: As a PHP Developer I want to have an easy API to create a page and add content to it. Resolved

History

#1 Updated by Karsten Dambekalns over 9 years ago

  • Target version changed from 518 to 550

#2 Updated by Robert Lemke over 9 years ago

  • Status changed from New to Closed

#3 Updated by Robert Lemke over 8 years ago

  • Project changed from Core Team to Base Distribution
  • Target version deleted (550)

#4 Updated by Robert Lemke about 7 years ago

  • Project changed from Base Distribution to TYPO3.Neos

Also available in: Atom PDF