What I realized shortly after we put out Magnolia 4.3 is that while we tried to explain new multisite support for example in this screencast there are still plenty of grey areas and lot of confusion when people actually get to use the multisite support.
Have you got magnolia-4.3? Setup multiple sites? All right, you are all done. The only thing left is to observe the load on the server and how many requests you can serve. You might have noticed that after activating the content, load on the public is bit higher even though there is no increase in traffic.
Last bunch of the entries have been all about the code. Today let's try something different. Partly because at the time of writing I'm just 34 thousand feet above Atlantic and really don't feel like coding anything, but partly also because i have been thinking about the problem I'm going to describe for while already.
I wrote about Magnolia cache few times already since it have been re-implemented for Magnolia 3.6. And it seems like with Sprint 4 of Magnolia 4.3 it came back to bite me.
Last time we looked at writing command and shortening the URLs using simple TinyURL API. This time, lets try to take this one step furter and generate URLs that are mobile-users friendly, i.e. URLs that can be easily recognized and processed by various mobile devices. Such are urls in QCode or DataMatrix scan codes.
Originally, I wanted to write about Magnolia-Twitter integration, but at some point I've realized such integration is so simple that there's no point writing about it. So instead, let's look how you can write custom commands for Magnolia.
Is it possible to do an A/B testing with Magnolia? The question popups often in the discussions with potential Magnolia users from various e-business companies. This really depends on what you want to test. The design of whole site or just best position for an ad on a single page or layout of one page or ...
Yet another week of development is nearly over (at least for me). What was this week all about? Apart from the really low temperatures outside (on Tuesday it was -24C at 4am), I focused mainly on extending the multi-site support in Magnolia.
I was asked recently if/how can someone create or configure the link control in Magnolia dialog so it would allow editor to choose not only the target of the link, but also the repository from which to choose such target.