CAT | typo3
Een paar dagen geleden ben ik begonnen om mijn persoonlijke weblog om te toveren.
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!
28
hiding intermediate tables in IRRE including the new item link
0 Comments | Posted by henjo in typo3
In the current documentation of typo3’s api it seems impossible to hide the ‘new record’ link for the intermediate tables when using IRRE.
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…
After loosing a deal because the other candidate had WordPress with the needed stuff almost done while for TYPO3 some stuff needed to be developed, I was kinda in shock.
How could it be? TYPO3 loosing from WordPress which I stopped using fervently after discovering the power of TYPO3… I felt abandoned, a little betrayed actually…
And now it happens to me again. Why? Yesterday I saw a movie on youtube about a guy installing a WordPress site, with a unique theme and… a shop in less than 5 minutes. He even had a product in and added a payment solution in that time… And now… Now I just upgraded to the newest version of WordPress fully automatically…
I think I need to start looking if Users/Permissions/Roles and localization have been improved as dramatically as this…
Should I consider trading TYPO3 for WP?
I have come to love the TYPO3 way of things, the power, the community, the friends in freelance collegeaus that I met… So should I? Or should I not?
I had it today: an indexed search implementation that got messed up links in the result browse box. Since I couldn’t find a solution using google (sometimes I am a fool when it comes to picking the right keywords I guess) a fellow freelance colleague tipped me on TYPO3’s bugtracker and more specifically bug 1347.
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
So you are using the felogin extension and the permalink doesn’t show up?
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?
Sometimes I am frustrated with TYPO3. Small things like a blog which are set up so easily using for example WordPress, can take a hell of a time with TYPO3. TimTab in my case.
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.
Last Friday I received the book I mentioned earlier. I always use the cheapest shipping arrangements on Amazon where they tell you it can take about 30 days before you receive your order. Well – even while I am living in one of the outer areas called Middelburg of the Lower Lands (also known as The Netherlands, Le Pays Bas or Holland) – I always receive them in about 5 or 6 days!
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.
I expect to recieve Dmitry’s book the end of this week on how to build extensions for TYPO3. The API sometimes is a mess for me and I am convinced his writing will help me understand the core of TYPO3 better, and become more advanced in programming extensions.
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.
Well – this is what I have put in standard:
User-Agent: *
Allow: /
Disallow: /fileadmin/templates/
Disallow: /typo3/
Disallow: /t3lib/
Disallow: /typo3conf/
Disallow: /typo3_src/
Disallow: /typo3temp/
Disallow: /uploads/
So – what do you put in?
24
How I add a separate searchbox on my TYPO3 website using indexed_search
0 Comments | Posted by henjo in design, typo3, usabillity
Basically what I do implementing a searchbox that needs to be an all pages, is using some plain typoscript to get this running well.
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.
Basecamp
Get me at Technoratie
Typo3











