<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Sign of life</title>
	<atom:link href="http://www.typogento.com/blog/typogento/sign-of-life/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.typogento.com/blog/typogento/sign-of-life/</link>
	<description>the official TypoGento Blog!</description>
	<pubDate>Sat, 31 Jul 2010 04:57:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Badgergirl</title>
		<link>http://www.typogento.com/blog/typogento/sign-of-life/comment-page-1/#comment-8262</link>
		<dc:creator>Badgergirl</dc:creator>
		<pubDate>Tue, 13 Apr 2010 13:33:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.typogento.com/blog/?p=67#comment-8262</guid>
		<description>Not much signs of life nowadays... What has happened to this project, which I thought sounded very promising...?</description>
		<content:encoded><![CDATA[<p>Not much signs of life nowadays&#8230; What has happened to this project, which I thought sounded very promising&#8230;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jochem</title>
		<link>http://www.typogento.com/blog/typogento/sign-of-life/comment-page-1/#comment-6152</link>
		<dc:creator>Jochem</dc:creator>
		<pubDate>Tue, 26 Jan 2010 11:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.typogento.com/blog/?p=67#comment-6152</guid>
		<description>If speed is of any relevance, indexed search should not be used. See dimitri's blogpost on indexed search (http://dmitry-dulepov.com/article/eight-performance-tips-for-your-typo3-web-site.html). I haven't tested indexedsearch on a large site with full indexed search capability, but on a small site it gave an enormous performance boost (search took 1 second instead of 25) so maybe that WOULD be an option.

Mnogosearch is a good option, but apache solr is too. I dont really know if and how Solr integrates with the current Typo3 version but it will be in V5.0 though. See this presentation of the possibilities Solr offers: 

http://www.slideshare.net/ingorenner/apache-solr-for-typo3-at-typo3-usergroup-day-netherlands</description>
		<content:encoded><![CDATA[<p>If speed is of any relevance, indexed search should not be used. See dimitri&#8217;s blogpost on indexed search (http://dmitry-dulepov.com/article/eight-performance-tips-for-your-typo3-web-site.html). I haven&#8217;t tested indexedsearch on a large site with full indexed search capability, but on a small site it gave an enormous performance boost (search took 1 second instead of 25) so maybe that WOULD be an option.</p>
<p>Mnogosearch is a good option, but apache solr is too. I dont really know if and how Solr integrates with the current Typo3 version but it will be in V5.0 though. See this presentation of the possibilities Solr offers: </p>
<p><a href="http://www.slideshare.net/ingorenner/apache-solr-for-typo3-at-typo3-usergroup-day-netherlands" rel="nofollow">http://www.slideshare.net/ingorenner/apache-solr-for-typo3-at-typo3-usergroup-day-netherlands</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ThaKilla</title>
		<link>http://www.typogento.com/blog/typogento/sign-of-life/comment-page-1/#comment-3744</link>
		<dc:creator>ThaKilla</dc:creator>
		<pubDate>Thu, 22 Oct 2009 09:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.typogento.com/blog/?p=67#comment-3744</guid>
		<description>There's a new TypoGento Version and everything works fine.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a new TypoGento Version and everything works fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: georgk</title>
		<link>http://www.typogento.com/blog/typogento/sign-of-life/comment-page-1/#comment-3415</link>
		<dc:creator>georgk</dc:creator>
		<pubDate>Wed, 23 Sep 2009 16:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.typogento.com/blog/?p=67#comment-3415</guid>
		<description>I'm not aware of the features &#38; inner workings of the magento-searchengine,
however I'd definitely vote against indexed_search as for its well known performance issues on large sites.
Currently we prefer to use mnogosearch (with dmitry's typo3-extension) for large instances, and are planning to test lucene for comparison.
hth georg</description>
		<content:encoded><![CDATA[<p>I&#8217;m not aware of the features &amp; inner workings of the magento-searchengine,<br />
however I&#8217;d definitely vote against indexed_search as for its well known performance issues on large sites.<br />
Currently we prefer to use mnogosearch (with dmitry&#8217;s typo3-extension) for large instances, and are planning to test lucene for comparison.<br />
hth georg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barbara Wijbenga</title>
		<link>http://www.typogento.com/blog/typogento/sign-of-life/comment-page-1/#comment-3314</link>
		<dc:creator>Barbara Wijbenga</dc:creator>
		<pubDate>Fri, 18 Sep 2009 08:26:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.typogento.com/blog/?p=67#comment-3314</guid>
		<description>Hello,

What is the planned release date for Typogento 6.0? I've just started with this and have Magento 1.3.2.3 installed.
I'm asking this so I'll know if it's worth downgrading Magento for now.
If 6.0 is released next week or so I won't have to.

Thanks,
Barbara</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>What is the planned release date for Typogento 6.0? I&#8217;ve just started with this and have Magento 1.3.2.3 installed.<br />
I&#8217;m asking this so I&#8217;ll know if it&#8217;s worth downgrading Magento for now.<br />
If 6.0 is released next week or so I won&#8217;t have to.</p>
<p>Thanks,<br />
Barbara</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nightowl</title>
		<link>http://www.typogento.com/blog/typogento/sign-of-life/comment-page-1/#comment-3191</link>
		<dc:creator>Nightowl</dc:creator>
		<pubDate>Fri, 11 Sep 2009 06:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.typogento.com/blog/?p=67#comment-3191</guid>
		<description>Hi

Sounds good, I'm working with both TYPO3 and Magento and have a few project where Typogento might be the perfect solution. Do you have any idea when version 0.6 will be published?

As I read this post the newest Magento is not compatible with typogento 0.5.1 - How incompatible are they? Can you install it and make a few changes to the core or is it best to just wait for typogento 0.6?</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>Sounds good, I&#8217;m working with both TYPO3 and Magento and have a few project where Typogento might be the perfect solution. Do you have any idea when version 0.6 will be published?</p>
<p>As I read this post the newest Magento is not compatible with typogento 0.5.1 - How incompatible are they? Can you install it and make a few changes to the core or is it best to just wait for typogento 0.6?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Falko</title>
		<link>http://www.typogento.com/blog/typogento/sign-of-life/comment-page-1/#comment-3154</link>
		<dc:creator>Falko</dc:creator>
		<pubDate>Tue, 08 Sep 2009 07:52:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.typogento.com/blog/?p=67#comment-3154</guid>
		<description>Hello, nice work with typogento! I think mnogosearch would be an option for both (I know there is an extension mnogosearch for TYPO3), but it requires additional software (but if TYPO3 and MAGENTO integrate, why not MnoGoSearch, too?) to be installed. Keep up with your good work, Falko</description>
		<content:encoded><![CDATA[<p>Hello, nice work with typogento! I think mnogosearch would be an option for both (I know there is an extension mnogosearch for TYPO3), but it requires additional software (but if TYPO3 and MAGENTO integrate, why not MnoGoSearch, too?) to be installed. Keep up with your good work, Falko</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Coleman</title>
		<link>http://www.typogento.com/blog/typogento/sign-of-life/comment-page-1/#comment-3063</link>
		<dc:creator>Charles Coleman</dc:creator>
		<pubDate>Wed, 02 Sep 2009 21:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.typogento.com/blog/?p=67#comment-3063</guid>
		<description>Which search to use... that's a tough call.  It seems that I would lean toward the TYPO3 search since (I'm totally guessing) most people using Typogento are focusing on the TYPO3 side of things more than that Mangento side of things.

The nice thing about search in Magento is the popular search terms that are automatically generated.  This is an excellent SEO feature built right into Magento that has helped us generate more traffic on our sites.

There are bonuses on both sides of the fence.  I probably prefer that indexed search be used.</description>
		<content:encoded><![CDATA[<p>Which search to use&#8230; that&#8217;s a tough call.  It seems that I would lean toward the TYPO3 search since (I&#8217;m totally guessing) most people using Typogento are focusing on the TYPO3 side of things more than that Mangento side of things.</p>
<p>The nice thing about search in Magento is the popular search terms that are automatically generated.  This is an excellent SEO feature built right into Magento that has helped us generate more traffic on our sites.</p>
<p>There are bonuses on both sides of the fence.  I probably prefer that indexed search be used.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zoltan Petrovan</title>
		<link>http://www.typogento.com/blog/typogento/sign-of-life/comment-page-1/#comment-3008</link>
		<dc:creator>Zoltan Petrovan</dc:creator>
		<pubDate>Mon, 31 Aug 2009 05:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.typogento.com/blog/?p=67#comment-3008</guid>
		<description>We started to use mnogosearch several month ago. I think it's faster and more flexible than  "indexed search". You can find the details here: http://mnogosearch.org  and there is a T3 plugin by Dmity Dulepov in the T3 extension repository.</description>
		<content:encoded><![CDATA[<p>We started to use mnogosearch several month ago. I think it&#8217;s faster and more flexible than  &#8220;indexed search&#8221;. You can find the details here: <a href="http://mnogosearch.org" rel="nofollow">http://mnogosearch.org</a>  and there is a T3 plugin by Dmity Dulepov in the T3 extension repository.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: torstendlp</title>
		<link>http://www.typogento.com/blog/typogento/sign-of-life/comment-page-1/#comment-2891</link>
		<dc:creator>torstendlp</dc:creator>
		<pubDate>Sat, 22 Aug 2009 10:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.typogento.com/blog/?p=67#comment-2891</guid>
		<description>Hello,

great to hear from you again. 
We all know that you work very hard and that it is not a obligation for you to go fast forward with T3 and that you have to look at your business in the frist place. I think everyboda understands this and is thankful that someone at all tries to bring a great thing like Typogento forward.

I try to get a typogento-version working right now... with some problems ;-)
Maybe you could take a look at the BugTracker at the issues 0000030 and 0000034. Any help would be appreciated!

As you ask about feature requests in your article. Two things I would love to see:
1. Inclusion of Magento KWs and Description in Typo3 pages for products etc.

2. The possibility to display the overview version of products (like in the product list) on any T3-page. It should be possible to choose freely, which products whould be displayed on which page.
Example: I am migrating a shop with a huge amount of static content pages to T3 right now. The Content-Part has about 6000 pages with informations around our products, manufacturers etc. It would be great if I could include a product list (as gallery or in list view) on each page, that fits the pages subject. Therefore it would be great not only to have the option to show a single category or a single product detail but to exactly specify which products whould be displayed in a content element of each page (chosen from a list or by product number).

Thank you very much for your ongoing work with Typogento!

Torsten</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>great to hear from you again.<br />
We all know that you work very hard and that it is not a obligation for you to go fast forward with T3 and that you have to look at your business in the frist place. I think everyboda understands this and is thankful that someone at all tries to bring a great thing like Typogento forward.</p>
<p>I try to get a typogento-version working right now&#8230; with some problems <img src='http://www.typogento.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /><br />
Maybe you could take a look at the BugTracker at the issues 0000030 and 0000034. Any help would be appreciated!</p>
<p>As you ask about feature requests in your article. Two things I would love to see:<br />
1. Inclusion of Magento KWs and Description in Typo3 pages for products etc.</p>
<p>2. The possibility to display the overview version of products (like in the product list) on any T3-page. It should be possible to choose freely, which products whould be displayed on which page.<br />
Example: I am migrating a shop with a huge amount of static content pages to T3 right now. The Content-Part has about 6000 pages with informations around our products, manufacturers etc. It would be great if I could include a product list (as gallery or in list view) on each page, that fits the pages subject. Therefore it would be great not only to have the option to show a single category or a single product detail but to exactly specify which products whould be displayed in a content element of each page (chosen from a list or by product number).</p>
<p>Thank you very much for your ongoing work with Typogento!</p>
<p>Torsten</p>
]]></content:encoded>
	</item>
</channel>
</rss>
