This is hot
- Upgrade VIA Epia-Board to current 2.6.28.7
- 769 times viewed
- 23.02.2009 18:41
- t3blog Update to version 0.8.1 (Security, Bugfixes)
- 173 times viewed
- 03.02.2010 14:33
- LaTeX Font Selection
- 100 times viewed
- 29.01.2010 17:17
- linux.bigga.de now with RSS Feed
- 99 times viewed
- 25.11.2009 09:36
[blog...]
t3blog Update to version 0.8.1 (Security, Bugfixes)
After a long time, snowflake updated yesterday the Typo3 t3blog extension. The version number jumped from 0.6.2 to 0.8.0 and immediately after to 0.8.1.
What a step!
Maybe the security vulnerabilities found in t3blog were the reason for submitting the fixed and updated version.
New is a view for the most read posts. Nice feature, but there seems to be missing some parts. E.g. in the widget selector the title is missing and it only works as pi2-widget if you add the following line to your template:
plugin.tx_t3blog_pi2.views < plugin.tx_t3blog_pi1.views
The page browser changed completely and uses now the extension pagebrowse. Ok, I had to adjust the CSS settings, but now it's working again.
Also "my bug" has been fixed - almost. There remains a problem with the category-tags. I fixed it locally. Let's hope that snowflake keeps maintaining the extension.
In the updated documentation is also a reference to a blog near by me:
Update 2010-02-04:
I've added two bug reports to bugs.typo3.org:
- Bug 13425: this reports about the views-widget issues I wrote in this post. And of course
I added a patch . - Bug 13426: another problem with the widget usage. In this case the blogList-widget and only if you use the storagePid.
A patch fixes this problem (at least for me).
Update 2010-02-10:
My two patches are accepted by snowflake and will be included in next release: Bug 13425, Bug 1342. Thank you Dominic!
LaTeX Font Selection
Recently I redesigned my default letter template in latex. I use the scrlttr2 package from the koma-script suite. In some .lco-file you may adjust a lot of settings.
But how to change the default font? And which fonts exist by the way?
First of all, I installed the texlive extra fonts:
apt-get install texlive-fonts-extra
In your document you select now the fontpackage if there is one. E.g.
\usepackage{charter}
And/Or you change the default font family:
\renewcommand{\familydefault}{bch}
Sometimes you have to do both. But who wants to read the manual for every font. Only to see, that this font is absolut awful...
The FontCatalogue on www.tug.dk helps you very much with the selection. You see for every font the syntax to include it and some text written with it. Perfect! Have a look at:
http://www.tug.dk/FontCatalogue/
MSIE Compatibility Meta Flag in Typo3
If Microsoft Internet Explorer find an error in your (Typo3-) website, it changes back to a compatibility mode. So it tries to show the page in IE 7 or 6 style.
Nobody really wants to see his page in these broken browsers!
The Internet Explorer understands for this case a meta-flag in the page head which informs about the browser version this page is developed for.
In short: Microsoft didn't understand HTML. But that's not new. You have to adjust all your settings for a specific Microsoft browser version _and_ you have to tell the browser which version you thought about.
I prefer to tell the visitor that my page is intended for the cutting edge browser, so I add for Internet Explorer visitors the following tag:
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
It's usually no problem to add new header elements to the typo3 page. But typo3 inserts these tags _after_ all other meta tags, the title tag and all link tags.
Surprise, surprise: Microsoft doesn't understand it's own meta tag if it's placed after the link tags! Don't now why, but Microsoft just tells you to place it "before all other elements".
And now, it's getting complicate in Typo3. My solution is to change the headTag (<head>) into the following:
page.headTag ( <head> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> )
Now the small image compatibility mode just right of the address bar in the IE disapears. Great!
By the way: The Typo3 backend of version 4.3.0 has problems with the switch to the compatibility mode. See Bug 11968.
Add Searchbox for Indexed Search to Typo3 Page
I started now to add the Typo3 indexed search to some of my websites. But how to add a searchbox on top of the website? There are several extensions for this, but some simple TypoScript is sufficiant. The following code in my template generates such a box (see on top of this page). The style is done of course by CSS.temp.searchbox >
temp.searchbox = COA
temp.searchbox {
20 = TEXT
# pid of page including index_search plugin
20.typolink.parameter = 46
20.typolink.returnLast = url
20.wrap = <form action="|" method="post"><span>
30 = TEXT
30.value = <input name="tx_indexedsearch[sword]" value="Search item..." \
type="text" title="Search the homepage." onfocus="javascript:this.value=''" />
40 = TEXT
40.value = <input name="submit" value="Search" type="submit" class="submit" />
50 = TEXT
50.value = </span></form>
wrap = <div class="absearchbox">|</div>
}
page.10.subparts.SEARCHBOX < temp.searchbox
[more]
Bugfix for t3blog RSS feed showing wrong category names
Recently I discovered RSS feeds as cool feature of t3blog. So I imported this blog as feed in my main website www.bigga.de. But I wondered about the category names above the titles. It seemed to be switched "linux" and "typo3".
Today I got deeper in the code and found the reason for this. The category names were not switched but totally wrong because it took the amount of categories (you may assign multiple to one blog entry) as selector for the category name in table tx_t3blog_cat.
This maybe right in former times but in current release 0.6.2 you have to join table tx_t3blog_post_cat_mm as well.
I fixed this issue for me and made a bug report for Typo3 on bugs.typo3.org
You find my