CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.6 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

Feature #12571

Feature #26684: Extension Mode, that respects backend Author restrictions

Storage PID is not respected

Added by Michael Knoll over 2 years ago. Updated 8 months ago.

Status:Resolved Start date:2011-01-27
Priority:Should have Due date:
Assignee:Michael Knoll % Done:

80%

Category:-
Target version:YAG 2.0
Votes: 0

Description

Now storage pid can be set at the moment.

History

Updated by Michael Knoll about 2 years ago

I think we don't need that for 1.0 so I will skip this for the first release.

Updated by Michael Knoll about 2 years ago

  • Target version set to YAG 1.x

Updated by Michael Knoll about 2 years ago

  • Tracker changed from Bug to Feature

Updated by Daniel Lienert about 2 years ago

  • Parent task set to #26684

Updated by Michael Knoll over 1 year ago

Here are some thoughts on the storage PID problem:

We only want to have one PID for all record types. We do not want to have a folder for each record type.

What PID is used at which place?
  • We take PID from a Starting Point if we create a content element
  • We take PID from selected page / sysfolder if we use backend module
How is PID set?
  • In Backend modul, we set PID of currently selected page / sysfolder
  • If we select a PID for content element, we do this in starting point selector. Selector should respect user access rights automatically.
How do we handle PID in classes
  • It should probably be enough to set storage pid in abstract repository by
  • Currently selected PID, if we are in backend
  • By Starting point of content element, if we are in frontend
  • We should remove 'respectStoragePage(false)' in pt_extlist data backend
Update Script
  • There must be an update script that handles following issues:
  • Set all PIDs of "old" records to a PID that must be defined for this update procedure
  • Set pids of content elements correctly (Process Flexform-XML which is rather ugly...)

Updated by Michael Knoll over 1 year ago

  • Status changed from New to On Hold
  • Target version changed from YAG 1.x to Waiting for Donation

Updated by Michael Knoll about 1 year ago

  • Status changed from On Hold to Accepted
  • % Done changed from 0 to 80

Feature is almost finished. Won't be released in public version until enough donations had been done.

Contact us if you are interested in this feature!

Updated by Daniel Lienert about 1 year ago

  • Target version changed from Waiting for Donation to YAG 2.0

Updated by Daniel Lienert 8 months ago

  • Status changed from Accepted to Resolved

Also available in: Atom PDF