Cannot render anything

[nicola883]

Hi. I've installed the plugin on Typo3 4.7 and magento 1.7. No error in Typo3 reports, I can see the admin view of Magento from typo3 and put the plugin on the page. I've put on root typo3 template the scripts taken from "common settings" in your wiki and from "generic routes". I get no answer from the page where is located the plugin (Error 324(net::ERR_EMPTY_RESPONSE) if I select "product from the plugin and "page not found" if I select customer/catalog. Maybe there is some error in the typoscript configuration or something that I'm missing? The Magento installation works on the same machine (localhost).

Many thanks for your help.

Nicola.

[witrin]

Could you be more precisely, what did you meant with "[...] if I select customer/catalog": Did you mean a custom route? If yes, which one (route, controller and action)?

I assume when you have selected a "[...] product from the plugin", you have picked a particular product from the product list. But your error (Error 324 (net::ERR_EMPTY_RESPONSE)) is a tough one ;), never had such an response noticed. Maybe there is something in your php or server error log?

[witrin]

I migrate currently TypoGento to Extbase and TYPO3 6.0. Unfortunately I've not the time to support the previous versions, but I had fixed (unreleased) some minor bugs before the migration.

I also had changed the generic routes setup, which contains foolishly some bugs. The Page not found errors are always caused by a misconfiguration of the dispatch routing. You could try an previous version of the generic routes setup. I'll try within the next days to release a hopefully complete working generic route setup. Please be patient.

With the upcoming release for TYPO3 6.0 you will get an easy to use single-page setup (including Ajax support) and a debug log for the routing, so you can better see how the URLs are mapped between TYPO3 and Magento. I also had fixed the redirect problems (caused by the base64 encoded parameter 'uenc') in the upcoming release.

[nicola883]

Perfect! Many thanks for you answers. I've checked for the 324 error. This is a chromium browser code, I'm sorry for the confusion. Anyway in that case the server doesn't answer to the request. I'm checking the error logs as you suggest, but in first view I don't see nothing that can help to discover the issue. The customer configuration that gives the page not found error is customer/catalog/category/view. If I change in custom/catalog/category/has I get the error "The block 'head' was not rendered for the requested URL 'localhost/catalog/category/has/?'"

So all looks like some misconfiguration: perfect what you are doing to help!

Before to switch to 4.7 version, I've fixed something in the code to adapt the plugin to typo3 6.0 like the substition of the readLLXMLfile() method with getParsedData() of the t3lib_l10n_parser_Llxml class.

I'm waiting for your job and I'm at your disposition if you need.

Nicola.

[witrin]

I've got the same error (324) last week in the interplay of the Extension Manager (TYPO3 6.0) and Apache on a Windows machine. Without it to track more precisely, the reason was a server crash, caused by PHP; but to get more information about it, it was necessary to consult the Apache error logs and the Windows application logs. The same setup on a LAMP and everything works fine.

The problem with your category might be, that you have selected the root category, wich is not allowed by Magento, therefore you have to create a subcategory before; not sure if this category needs to have at least one product. By choosing the action has, which is a common action to check if the controller 'has' another action, you get no layout rendered, so the block header, which is required by the TypoGento header integration config.tx_typogento.header.enable = 1 is missing.

Yes the readLLXMLfile() is a blocking canditate on the migration path to TYPO3 6.0.

Hope that helps.