Bug #12734

Linkviewhelper in Widgets in Backend produce Links with FE-Namespace

Added by Daniel Lienert over 2 years ago. Updated 25 days ago.

Status:Accepted Start date:2011-02-02
Priority:Should have Due date:
Assignee:- % Done:

0%

Category:Extbase: MVC
Target version:Extbase 6.2
Has patch:No Tags:
Votes: 0

Description

I built a widget that renders a breadcumb menu. In the widget template i use the ActionLinkViewhelper to render the links. This works fine in the Frontend, but in the backend it produces frontend specific namespace (tx_ext_plugin) instead of the backend namespace (tx_ext_web...).

I nailed the problem down to the method Tx_Extbase_Utility_Extension::Tx_Extbase_Utility_Extension():

When it is called from the method Tx_Fluid_Core_Widget_AbstractWidgetViewHelper::initializeWidgetContext it gets the namespace from $frameworkConfiguration['view']['pluginNamespace'] and works correctly.

When it is later called from the UriBuilder inside an ActionViewhelper (inside the widget template) $frameworkConfiguration['view']['pluginNamespace'] is missing and the default namespace is returned.

Sadly i cant find where $frameworkonfiguration or $configurationManager is reseted between this two calls.


Related issues

related to Extbase MVC Framework - Feature #9581: Possibility to create FE URIs from BE vice versa Rejected 2010-09-03

History

Updated by Bastian Waidelich about 2 years ago

  • Project changed from TYPO3.Fluid to Extbase MVC Framework
  • Category deleted (Widgets)

Updated by Bastian Waidelich about 2 years ago

  • Category set to 964

Updated by Anja Leichsenring 5 months ago

  • Category changed from 964 to Extbase: MVC
  • Status changed from New to Accepted
  • Target version set to Extbase 6.1
  • Has patch set to No

Updated by Alexander Schnitzler 25 days ago

  • Target version changed from Extbase 6.1 to Extbase 6.2

Also available in: Atom PDF