Hoewel deze url natuurlijk bij uitstek geschikt zou zijn voor een Nederlandstalig blog over TYPO3 heb ik er voor gekozen om deze content te behouden vanwege de bezoekers die hier komen.

Op termijn zal ik deze URL waarschijnlijk ook gaan gebruiken voor de blog die nu staat op http://henjohoeksma.nl

Op dat weblog komen artikelen in het Nederlands over o.a. TYPO3, maar ook QuickTips, documentatie, extensies die ik heb geschreven etc.

See you there!

After a little search I found already a patch has been written to get this fixed and it is in the current core (I am working on 4.2.10 here, not sure when it was included though).

The solution is quite straightforward: you already had the possibility to specifically allow new tables using

mod.web_list.allowedNewTables

but now you can also use

mod.web_list.deniedNewTables

to meet your needs… Especially if you use it together with the hideTable setting…

Well – it worked like a charm so I am happy and decided to do what I just did now: save this information if it ever happens again and I am left picking my brain where and when I had dealt with that issue before!

Here the link: http://bugs.typo3.org/view.php?id=1347

Set the permalogin in the install to 1 instead of 2, and make sure you have the lifetime value set as well!

Do I need to say more?

I couldn’t find a decent way of having linkable tags in my single posts, so I came up with my own: newstags.

It takes the keywords, transforms them into tags that are (optional) linkable to a page with the search plugin for news.

For now: just install, include static templates, and change the constant to the pid where the search plugin is located. Next add the plugin under the tt_news element where you get your single view with and your tags are there.

Make sure you restrict the search plugin from tt_news to only search in keywords. You can achieve this by setting the following in TS Setup:

plugin.tt_news.searchFieldList = keywords

It should be in TER soon, if you want it now, leave a comment.

Update: The extension is now available in TER right here.

If you were frustrated as I was, and this extension is welcome to you, please consider donating a considerable (just kidding) amount of money via paypal.

Do you have any experience with Goldmine? Let me know! I’m eager to hear your stories!

Enough about my shipment euphoria’s

I started off with Dmitry’s book right away and though I haven’t found much time to read yet – I can tell it helps me in what I needed most in using the TYPO3 API: a clear breakup into sections and a nail-down on the classes and the class groups that exists. Thus providing some clarity on the whole – which I was in need for (no, not desperately ).

To be continued.

Most of the time I have written some extensions for custom requirements of my customers.

You can get Dmitry’s book on Amazon. Click to image to bring you there right away!

I will get back on this as soon as I start reading – but I have no doubt it is a worthy investment.

So – what do you put in?

I used to use macina searchbox when I just started working with TYPO3, but getting more feeling with typoscript, I personally like using as less as extensions as possible.

So, how do I do it?

First of all, make sure you implement Indexed Search (setting up the indexing etc.). You really should read the documentation on that - although if you’re like me you’d like me post it here for you!

Second make sure you a subpart Marker (or when using TemplaVoila make sure you map the location to a typoscript object). Usually mine is named lib.searchbox.

Third thing you do is prepare some constants in your TS template:

plugin.tx_indexedsearch.searchUID = 2
plugin.tx_indexedsearch.showAdvanced = 0

The searchUID constant is the page containing your search results (your page with the indexed_search plugin on it).

In the setup you now use the following code to give you the searchbox.