Anybody reading this page and perhaps also using the RSS feed certainly noticed that I haven't written new stuff for quite a long time. My motivation for new articles is very low, so I decided to discontinue this blog and use the domain www.krausmueller.de to only present my TYPO3 extension jk_poll and inform about updates of it. Old articles are still to be seen under the menu item "Blog", but there won't be any new ones.

I suppose nobody will be extremely sad, as I think there were not many readers anyway ;).

When using VMware Workstation to test VMware Virtual Infrastructure you need Shared Storage for your virtual ESX servers in order to test features like VMotion. Until now I used an additional VM like this or this to connect its storage via iSCSI. But doing so you have another VM consuming the limited resources of your physical host. But there is another solution. Just use shared storage as described in this blog post. So you can test features like VMotion, HA and DRS without running an additional VM just for shared storage.

During my search on the VMware website in the section VMmark I found an interesting thing. In a test made with VMware ESX v4.0 (e.g. this one) the "Virtualization Software Availability Date" is mentioned as June the 30th.

We'll see if this date is correct ;-).

UPDATE: Ok ok, vSphere was already released on May the 20th. You can dowload an evaluation version here.

UPDATE 2: VMware put much effort into this evaluation. In the section "Guided Evaluation" you can find many videos showing for example how to install vSphere. At the moment there are still some missing, but I'm sure they'll update this section soon. Hopefully I can soon give you some of my own impressions after testing the new version ;-).

Translations for frontend extensions normally are placed in the file pi1/locallang.php. If the language needed is not defined you should send your translation to the maintainer of the extension. I think most of the time they will include it to the next version. If you edit the file for yourself there might be the risk of overwriting your changes with the next update of the extension (if your translation was not included by the maintainer). So before editing locallang.php and also in some other cases it makes sense to define or even overwrite (in case the current translation doesn't suit you) the language via TypoScript. For jk_poll this might look something like that:

plugin.tx_jkpoll_pi1 {
 _LOCAL_LANG.de {
  submit_button = beliebiger Text
  votes_total = anderer Text
 }
 _LOCAL_LANG.en {
  submit_button = some text
  votes_total = another text
 }
}

I think the changes you have to make for other extensions are quite obvious. You have to change the extension key ('tx_jkpoll_pi1' in this case) and find the right labels in locallang.php. The language is defined with '_LOCAL_LANG.de' and '_LOCAL_LANG.en'.

It's amazing how things can be taken out of context. Tonight german TV show Planetopia tries to show that the security issue of TYPO3 from 10th February was used to hack the homepage of Schalke 04. After the security issue was announced back in February the homepage was actually hacked and showed an article reporting the fact that striker Kevin Kuranyi was fired (which wasn't true). Planetopia tries to place this event into last week after the manager and coach of Schalke 04 were fired. Apparently this sells much better in context with the events of last week. Between the lines you can also read that Open source software (and namely TYPO3) is the cause for this (and therefore bad). Unfortunately other aspects of the topic are not considered.

Interesting side note: News and Pictures Fernsehen GmbH & Co. KG, the producer of Planetopia uses TYPO3 as Content-Management-System. If this side was also hacked in the past is unknown ;-).