Issue Bug Closed

#58857Not possible to set the storagePid via "Record Storage Page"

Pascal Maechler 05/16/14, 10:55 updated 06/16/23, 19:19

Description

After a short chat with Felix Oertel, i now open this bug report.
In the current version of extbase 6.2.0, there is no way to set the persistence.storagePid via the field “Record Storage Page” in the plugin content element under Behavior.

Steps to reproduce:
  1. Create a content element of type plugin and select an extbase plugin which at least outputs some list data
  2. Set the persistence storagePid in the static constants
  3. Open the FE and navigate to the page where the plugin has been placed
  4. Everything seems to work fine, records will be loaded from the defined storagePid
  5. Manipulate your repository find method and output $query->getQuerySettings()->getStoragePageIds()
  6. After reloading the FE, the records will be loaded and because of the added line above, the storagePid will be displayed on the page, too
  7. Remove the storagePid from the persistence settings
  8. If you reload the FE, you will see no records and no output of the storagePid (of course, you deleted it)
  9. Instead of re-setting the persistence storagePid via TypoScript, select the storagePid in the “Record Storage Page” in your plugin content element under behavior
  10. If you reload the FE, you will see the storagePid as output of the $query->getQuerySettings()->getStoragePageIds(), but you cannot see any records

Expected behavior:
If I set the storagePid in the Record Storage Page field of the content element, I expect that this will be considered in the query.

Current behavior:
The set storagePid is recognized as storagePid, but was not considered in the query.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.