typo3bloke.net

Today early morning I sent three extensions to TER. Two of them are familiar to many people and one is new. Here is what was changed.

mnoGoSearch

As many people know mnoGoSearch is the alternative TYPO3 search engine. It is far superior to the indexed search. It is much faster, it has true pagerank feature and it can search for word forms (man/men, for example). This is not a complete set of features of course. Unlike indexed search and crawler, mnoGoSearch truly crawls the web site. It respects 'No index' flag on content elements (indexed search does not). mnoGoSearch is easier to setup (well, this is my opinion) and easier to manage.

Version 2.0 was the major update. It include new, Google–like look with a page rank indicator:

(Notice the search time! This is the first query. Indexed search would take nearly 30 seconds to find the same)

Next mnoGoSearch now can index some database data directly (not retrieving web pages),. This is especially useful for things like news, FAQ or other textual data in the database.

There is a new and better page browser provided by my "Universal page browser" extension (see below about its update):

And finally mnoGoSearch became friendly to Google Analytics! If you have Google Analytics on your web site, you can tell Google Analytics to track what people search on your web site. This way you can optimize your site and see what people want most. Here is how mnoGoSearch configuration in Google Analytics looks like:

Also this update simplifies flexform configuration a lot. Unfortunately I did not have time to update manual to include all changes. The update will follow soon.

Page browser

It is also known as "Universal page browser". This extension provides API to other extensions to have a highly customizable page browser. Now any extension can have XHTML compliant page browser within minutes with less than 10 lines of code (including nice formatting of the code).

The update was necessary because of the weird behavior of one tslib_cObj function that I used. I made a workaround.

Page path

Page path is a new extension. It provides a very simple API for other extensions who need to get a path to a page in Frontend from the Backend. For example, to get a proper URL to a single news item, use this code:

$pagePath = tx_pagepath_api::getPagePath($singlePageUid,
                                  '&tx_ttnews[tt_news]=' . $ttNewsItemUid);

$pagePath will contain something like "http://typo3bloke.net/post-details/update_to_realurl/".

Happy using!