My current project are some access restricted pages for my staff at Weltcafe Dresden. Some days I spent to setup the TYPO3 cal extension 1.4.1. Not everything works with the new standard templates as expected. But it's ok for the first step.
Next point on the list is of course a frontend login with two different user groups: one for me as admin and one for the staff.
The login worked very fast with the builtin felogin system extension. But one little detail didn't work: the redirect after login! This is configurable via the user or group settings, via TypoScript and via Flexform in the plugin settings.
After hours of searching and analyzing the source code, I found the solution: The option
plugin.tx_felogin_pi1.showLogoutFormAfterLogin = 1
disables the redirect! I always activated this option in Flexform because it sounds reasonable: "If set, you see direct the logout form after successful login". Yes, but you see only the the logout form without getting redirected anywhere.
This feature was introduced with TYPO3 4.5.0 and was diskussed in the old bugtracker [13798] [15421].
And you find other confused users in the current bugtracker at forge [29785].
For others, it's a feature. For me, it's a bug. But in any case, it's a bad documentation about this switch. So be careful!
ics_awstats is one TYPO3 extension using the perl awstats-script to analyze apache logfiles. It's only for backend-users to see, what's going on. It's possible to start the script manually or to schedule the execution with the TYPO3 scheduler.
With last update from 0.3.0 to 0.5.0 the extension stopped working on my installation. The lock-file was created but not deleted anymore and the link for removing it did'nt work.
I check the extension for this failure and changed to lines to reactivate it again. Because there is no bugtracker yet on forge for this project, I sent the patch to the maintainer. Hope, he will apply it soon.
If you like, you may checkout the patch and apply by yourself.
Find more:
UPDATE: The maintainer, ?Reto Zahner from Newmedia AG in Switzerland, fixed this issue and released 0.5.1 some days after my patch and bugreport. Thank you!
On Facebook some feeds of my blog are feeded automatically by the RSS Graffiti application. And I wonder for a while why the tt_news RSS feed contains the preview image but the t3blog RSS feed comes without it.
If find images with a short teaser much more interesting than only text. That's why I add an image.
I checked out the current class.rss.php from the forge.typo3.org repository. The developers changed a lot since the last release 1.0.0 and there is still no release 1.1.0. But this class didn't worked as expected because there is still a bug inside. So first I made a bugreport with a patch.
After this the content:encoded field was filled but the images where gone nevertheless. That's because they strip all tags out of the description with the PHP function strip_tags(). So I added the
-tag to the allowed tags in line 598:
$text = strip_tags($text, '<a><img><b><br><em><hr><i><li><ol><p><strong><ul>');
I really like perfectlightbox by ?Benjamin Niediek and I'm using the current tt_news extension version 3.0.1 in several installations.
In one of those sites with tt_news a customer pointed out a problem with the image titles in lightbox view. This only happens if you have several images. The title in lightbox view of every image keeps always the title of the first image.
This is really a tiny and anoying bug. That's why I tried to fix it and hopefully found a solution.
How it works:
Perfectlightbox used to overwrite the tt_news function ?imageMarkerFunc by its own one in the static/setup.txt:
### If dam_ttnews is also loaded do not include the imageMarkerFunc
[globalString = TYPO3_LOADED_EXT|tt_news|type=L] AND [globalString = TYPO3_LOADED_EXT|dam_ttnews|type=L]
## Do nothing
[else]
plugin.tt_news.imageMarkerFunc = tx_perfectlightbox->ttnewsImageMarkerFunc
[global]
But after several modifications in tt_news to enable OptionSplits (starting with 3.0.0?), the old function didn't work anymore. So, Ben decided to comment this overloading in perfectlightbox. Unfortunately this led to the problem described above.
I took now the tt_news imageMarkerFunc() and copied most of the OptionSplit-work into the ttnewsImageMarkerFunc of perfectlightbox. This seems to fix the problem not only in tt_news SINGLE-view but also in SINGLE2-view (using OptionsSplit).
With the following Typoscript I tested my patch with tt_news and OptionSplit in SINGLE2-view:
plugin.tt_news {
archiveTitleCObject {
10.strftime = %B - %Y
}
getRelatedCObject {
20.strftime = %d.%m.%Y %H:%M
}
displaySingle {
# configures tt_news to use 3 image markers. The first
# image is rendered to marker 1, the last 2 images
# are renderd to marker 3, the rest will go to marker 2.
imageMarkerOptionSplit = 1|*|2|*|3||3
image.file.maxW = 200|*|90|*|100||100
image.file.maxH = 200
# this configures tt_news to wrap only each "middle" (marker2) image
# with <div class="sv-img-small"> (div is closed later)
image.wrap = | |*|<div class="sv-img-small">|*| | || |
# This wraps all images in the first image marker to
# <div class="sv-img-big">|</div>.
# marker 2 and 3 will be wrapped to
# <div class="sv-img-small-wrapper">|</div>
imageWrapIfAny (
<div class="sv-img-big">|</div>|*|
<div class="sv-img-small-wrapper">|</div>
)
caption_stdWrap.required = 0
# This wraps the image caption in a <p> tag. have a look at
# the "middle" wrap which closes the div from above to surround
# the image and its caption
caption_stdWrap.dataWrap (
<p class="news-single-imgcaption">|</p>|*|
<p class="news-single-imgcaption">| </p></div>|*|
<p class="news-single-imgcaption">| </p>||
<p class="news-single-imgcaption">| </p>
)
}
}
Yesterday, I sent my patch to Ben and I hope he won't find any new bugs. Then it might be in the next perfectlightbox bugfix release soon.
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:
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!