Latest Comments
- GREAT HELP!!!!
- 27.04.2012 17:42
- I haven't tried 12.04 alpha yet - and for sure, I won't do...
- 29.01.2012 08:21
- Full screen video?
- 29.01.2012 05:44
- Be careful, Comments are not admitted in the typoscript...
- 07.09.2011 23:23
[blog...]
TYPO3 Extension Builder - former called Kickstarter
Sometimes it's hard to find up-to-date information about TYPO3 issues in the web. That's of course TYPO3 is so long time in the web and there are forums, mailinglists, 1000s of blogs (like this), wikis and whatever. Another reason is that typo3.org is a really bad indexed website by Google.
Today I was looking for the new TYPO3 Extbase Kickstarter. And I was looking and looking and tried the terrible bad search on forge.typo3.org and... got almost mad.
Finally I found it here:
And surprice, surprice: It's called Extension Builder now! A good idea to make some difference to the old extension kickstarter. But I missed that point unfortunately.
Now, I'm happy, because the Extension Builder is part of TYPO3 TER. I don't have to download it by git as early, development version.
Here is some wiki documentation about the new style TYPO3 extension development:
Backend Language Caching in TYPO3 4.6
If you get lots of messages of this kind
[lang]: User xyz has cleared the language cache
in your new TYPO3 4.6.x then there is a simple solution. Add the following setting to your typo3conf/localconf.php:
$TYPO3_CONF_VARS['SYS']['lang']['cache']['clear_menu'] = 'TRUE';
This will add a menu "Clear Language Cache" to your "Clear Cache" menu. Now the user may manually clear the cache.
This also fix now the problem with cache-files and NFS. In our setup, the typo3temp is on a NFS-partition. And there seems to be some race conditions why you get errors like this:
Core: Error handler (FE): PHP Warning:
file_get_contents(/var/www/typo3temp/Cache/Data/t3lib_l10n/a232e71bc72d2771b802cab5b3f429b4):
failed to open stream: No such file or directory in /var/www/typo3_src-4.6.8/t3lib/cache/backend/class.t3lib_cache_backend_filebackend.php line 452
Usually the file exists - but maybe too late...
extbase extensions need comments to work - PHP optimizer must not remove it!
If you develop extbase/fluid extension for TYPO3 you will get in contact with PHPdoc blocks before classes, functions, variables. This is no nice to have feature but required for extbase to e.g. recognize the right data type.
I really have to learn this because I am not used to write PHPdoc blocks. Usually, I only copy an existing block and adjust the description which I find very important.
PHP optimizer or accelerators cache the compiled PHP bytecode and/or do other optimizations. Unfortunately some remove the PHPdoc blocks from the source code first. This is the default behaviour of eAccelerator.
With eAccelerator and extbase you get this exception thrown:
#1242292003: could not determine type of argument "section"
of the render-method in ViewHelper "Tx_Fluid_ViewHelpers_RenderViewHelper".
Either the methods docComment is invalid or some PHP optimizer strips off comments.
What to do?
- compile eAccelerator with option "--with-eaccelerator-doc-comment-inclusion": "If you want eAccelerator to retain doc-comments in internal php structures" (eAccelerator help)
- use another PHP optimizer. I use xCache on Debian Squeeze which seems to work fine.
Links:
Poulsbo GMA500 driver is going mainline kernel
Some days ago, I was brave to do a "do-release-upgrade" call on my fit-pc2. Before it was 11.04 and now I am running Ubuntu 11.10.
But of course this only works with my own linux kernel. I had som 3.2.0-rc2 running from november. This kernel won't be replaced by Ubuntu. That's of course, what I wanted.
My first problem after upgrade was the music playback. It run too fast (!) and alsa threw error messages about buffer underrun.
So, I assumed some problems with my "old" kernel and the updated alsa userland libs/tools. And decided to upgrade the kernel by a fresh "git pull".
After this, the music is working again - but where is my gma500 driver gone? It moved from staging to mainline drivers/gpu/drm/gma500/ !
Alan Cox started last november the move. And now it will be finished with coming kernel release 3.3. The driver is called gma500_gfx now.
I'm really happy about this!
The only thing I had to change, is my kernel config.
There is still one issue open: On bootup, the X-server output is only shown in the top half of the monitor.
I found a simple workaround. I just stop and start the lightdm. This "fixes" the issue for me now. I hope this will be fixed in coming versions of the driver.
I place my fix in /etc/rc.local:
stop lightdm
start lightdm
ab_booking 0.5.0 out with new features
- Check-in Overview
I promised for weeks to some users to release a new version of ab_booking. Only a few seconds ago, I did it!
New revision 0.5.0 is online in TER (TYPO3 Extension Repository) and on forge.typo3.org.
There are some tiny bugfixes and several new features, I am using on my site. Now it's p ossible to make prices depending on the duration of the booking.
For example you could enter rates for a double as follows:
- 1 night: 90 € + 10 € for room cleaning
- 2 nights: 2x90€ but no extra charge room cleaning
- 3 nights: 3x80€
- 7 nights: 7x(90€-20%)
You can achieve this by entering the following code into the price database field:
90,D:3:80,D:7:20%
Read (comma separated): It costs 90 per night. A discount ("D") is offered after 3 nights and the new price is 80. Another discount ("D") is vallid after 7 days and you pay 90 minus 20%. And so on...
The same with the room cleaning. If you want only an extra charge for people comming one night, you enter in single component:
10,D:2:-1
Read: It costs 10 per stay. A discount ("D") is valid after 2 days and the price is removed (-1). You could of course write as well:
10,D:2:5,D:7:-1
In this case the customers pay 10 for one night, 5 for 2-6 nights and no extra charge for more than 7 nights.
Or you can offer optionally breakfast and the customer may deselect it or not.
7,D:3:10%,O
Read: It costs 7 per person. A discount of 10% is applied after 3 nights. The customer may deselect this option ("O").
With 0.5.0 you may also influence the minimum stay for the customer. E.g. if you like to set a minimum stay of 3 nights for bookings more than 8 weeks in the future you can set:
3,W:8:2,W:1:1
Read: The minium stay is three nights. 8 weeks before booking start it is reduced to 2 nights. And in the last week before arrival it is set to 1 night.
There is an other view which is quite useful in my case: a check-in overview. Now you can put on an internal page a view with the coming arrivals and depatures for the next 4 days (sorry, not configurable at the moment). And you have a simple calendar field to jump to any date in the past and future!
Now ab_booking is much more flexible but for sure still not flexible enough for everybody. Please feel free to test ab_booking at ab_booking.bigga.de and to install it to your TYPO3 website.