0000045: Typogento cannot fetch blocks from Magento 1.4

Widok prosty [ Przejdź do komentarzy ]

[ Widok zaawansowany ] [ Historia zagadnienia ] [ Drukuj ]

Identyfikator

Kategoria

Ważność

Powtarzalność

Data zgłoszenia

Data modyfikacji

0000045

[Typogento] Bug

ważny

zawsze

2010-02-26 13:23

2011-03-23 08:56

Zgłaszający

viamedia

Widoczność

publiczny

Przypisany do

Priorytet

normalny

Rozwiązanie

otwarty

Stan

nowy

Temat

0000045: Typogento cannot fetch blocks from Magento 1.4

Opis

The shop frontend is useally a fbmagento_pi1 content element, that calls the dispatcher from Magento based on the route in the URL. On pages outside the shop itself, there is the possibility to add specific blocks via Typoscript, like cart_sidebar and top.links. With Magento 1.4 those blocks (outside the shop) are not displayed anymore. Typogento cannot get them via the connector model. It seems that rendering an controller triggers some additional loaders that fetch the needed configuration.

Dodatkowe informacje

I haven't time yet to have a detailed look, but a quick snap at Mage.php and Mage_Core_Model_App.php suggests that the initialization works a little different in Magento 1.4

Tagi

Brak powiązanych tagów.

Dołączone pliki

Powiązania

Komentarze
(0000107) viamedia (zgłaszający) 2010-02-27 16:42	I got it to work with a few hacks: 1) Copy the content from Mage_Core_Controller_Varien_Router_Standard::match to Flagbit_Typo3connect_Controller_Router::match, right after if (Mage::app()->getStore()->isAdmin()) { return false; } Now the blocks can be fetched, but the entire Shop frontend ist outputted too, right before the TYPO3 page. so 2) In class Flagbit_Typo3connect_Controller_Response the method outputBody is overloaded to return the content, instead of echoing it. It seems that the content is outputted before this function is called. So I replaced the sendResponse method with public function sendResponse() { ob_end_clean(); parent::sendResponse (); if ($this->isRedirect ()) { exit (); } } As I said: that's a really ugly hack, but it works, so it might give you a hint on how to fix this.

(0000109) viamedia (zgłaszający) 2010-03-02 09:55	Well, point 2 broke the Ajax functions, do I changed it to: public function sendResponse() { if(!Mage::app ()->getFrontController ()->getRequest ()->isXmlHttpRequest ()) { ob_end_clean(); } parent::sendResponse (); if ($this->isRedirect ()) { exit (); } }

(0000114) andi (zgłaszający) 2011-03-23 08:56	ob_end_clean(); is actually blocking the complete TYPO3 website. We inserted the code like suggested and both options with and without if block the complete website.

Historia zagadnienia
Data modyfikacji	Nazwa użytkownika	Pole	Zmiana
2010-02-26 13:23	viamedia	Nowe Zagadnienie
2010-02-26 13:23	viamedia	Zagadnienie monitorowane przez: viamedia
2010-02-27 16:42	viamedia	Dodano komentarz: 0000107
2010-03-02 09:55	viamedia	Dodano komentarz: 0000109
2011-03-23 08:56	andi	Dodano komentarz: 0000114