Dolfijn

Ok, I found it. The path for the BeesBlog module is a little different: it uses the format <my-theme>/css/modules/beesblog/views/css/beesblogstyle.css. So, my first attempt was close but not close enough. Thanks for showing the way.
public function hookDisplayHeader()
    {
        $this->context->controller->addCSS($this->_path.'views/css/beesblogstyle.css', 'all');
    }
 

Final solution : it turns out that this bug (not getting the Shop ID from the current context) is already fixed in the Mail::Send function. Only available in bleeding edge. So I migrated to the latest greatest and it all works well.
Thanks for the pointers.

I solved it!
Problem was indeed the individual bees tables that had the latin1 char set. I solved it by exporting these tables to a sql file. There I changed the encoding to utf8 and then dropped, create, insert the new tables. And now I can use the special symbols too.
Thanks for all suggestions, especially those from musicmaster!
By the way, if I had payed attention to the TB Server Requirements, I would have configured MySql with full UTF-8 support. And this problem would never have occured in the first place 🙂

Thanks!!!
Didn't know about Module-> Positions. Know I do and the problem was solved easily.

Sorry. Already found it by myself. There is a new (when comparing to the Smartblog module I used in PS) selection box that has to be ticked for each post: the available language box. If ticked, the posts show up!

In the mean time I found out that the problem only exist when using Firefox. With IE or Chrome it all works well. But it is a good idea to always show the VAT number as this is a B2B shop. Thanks!