[TYPO3-dev] Magento to TYPO3

[Niels Fröhling]

 Hy Georg;
>
> Magento supports and wants these brigdes! The services are not a hack 
> and will be even supported more and more. They are not only for 
> displaying products but for really more issues! It is possible to create 
> invoices and manage all products from anywhere, e.g. ERP,...
>   
 If it is like that, that you basically have a libMagneto and a 
Magneto-FrontEnd, I highly suggest to create a complete Typo3-extension, 
_with_ TS, _with_ FlexForms, _with_ feuser and the stuff. Try to offer 
support for DirectMail (to make product-boletins) for example. Create a 
back-end plugin that allows you to trigger these extended functionalities.
 I mean, I surely don't want to dictate you what and how to do it! Maybe 
I can just suggest you some things that make (to me) Magneto (or any 
other system) appear integrated and consistend inside the 
Typo3-Framework, :-) So then it (the extension) would be a wrapper 
instead of a bridge, and a good one.
>> I can imagine that a Typo3 + SMF or Typo3 + Plone or 
>> then Typo3 + Magneto will not make the burned kids feeling safe, so to 
>> say.
>>     
>
> Sorry I don't understand that. The difference with SMF is that IMO SMF 
> doesn't offer this open architecture.
>   
 When you got burned you're not even going near _possible_ fire, right?
 I suppose SMF could, if somebody wanted. Everything could be /nice/ if 
somebody did wanted to. I think (I only have experience with the Joomla 
stuff because I had to repair a completely desintegrated Joomla-Site + 
CP + SMF + Gallery2, I afterwards on my own account switched the site to 
elgg BTW) the quality of these bridges is proportional to the care of 
the programmers on each side.
>> The comment about SSO allready made our day, right? How are you 
>> going to explain and implement, and explain the implementation of a 
>> 'bridge' between Typo3 + Magneto? 
>>     
>
> The implementation is very easy!
>
> E.g. those 6 lines:
>
> -----
> $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
> $sessionId = $proxy->login('apiUser', 'apiKey');
> $filters = array(
>      'sku' => array('like'=>'1234%')
> );
> $products = $proxy->call($sessionId, 'product.list', array($filters));
> -----
>
> You will get all products (as array) where the sku begins with "1234". 
> It couldn't be really easier!
>   
 You don't have something more direct than a HTTP-connection? I suppose 
they offer other different data-exchange-implementations too? It's not 
so wise to start 2 httpd-processes, possibly more, on the same machine.
 For the SOAP-connection, does (that) SOAP(-implementation) offer 
caching? Do you plan to make the fe-plugin USER_INT?
 Are you going to offer a Javascript SOAP-client which can be integrated 
into a typo-site?
> Of course Magento doesn't have any TS!
 Of course. I meant your extension.
> My extension will be of course at forge, so everyone is invited to help 
> there.
>   
 I possibly at least would try it for a site that does have no payment, 
but the shop (display). It's in a Month or so. It's not exactly 
excessive, maybe 300 products, so possibly we could see how to optimize 
the integration on the low-end (means for simple purposes, possibly for 
simple people, or those in a hurry).
>> There are a lot of questions open, and even though I understand your 
>> enthusiasm, I understand Franz's protectionism also.
>>     
>
> Again: If someone wants to use tt_products, he is free to go! Magento is 
> getting stronger and stronger and the connection will also help TYPO3 a 
> lot! I see this connection more like an integration of Google Maps or 
> even like Mootools, JQuery (of course not identical!) but these are 
> stand-alone codes which enrich a website.
>   
 I think they are successfull, because your site and all of those tools, 
operate on _the same_ document-object-model. No concept-clash. I urge 
you :-), please offer more Typo3-functionality like TS (obviously not to 
work inside the Magneto, but inside the extension).

 Ciao
   Niels