Newsletter portlet available for testing

Hi all,

As from today you can test newsletter portlet on our sandbox here . Feel free to add, change, delete. If you find it usefull or you have some ideas how can we improve existing functionalities leave us a comment. Our sandbox is deployed on Liferay 6.0.3 but we can prepare that plugin for newer versions of Liferay. Pricing and licencing is coming soon ๐Ÿ™‚


Liferay 6.0 Newsletter portlet – update

Hi all,

As we getting more and more questions about Newsletter portlet (when and how much) here is a little update.

We’re aiming at end of March with release of both Community and Commercial version of our Newsletter portlet. For now we know that it will have double licencing – one for commercial use and one for non-profit, educational purposes. We still thinking about shareing source code – how to do it so we can re-use all the upgrades made to it by community so it can be more functional with every release.

For now our newsletter is scope aware (so you can define different newsletter channels for different scopes e.g communities). Newsletters emails are made by editors with a help of WYSIWYG editor. Editors can assign / delete emails from newsletter channel and export user list to CSV file. There is additional portlet for sign in and out of Newsletter where users can choose desired channels.

Those are basic functionalities planned for first release. We have couple of more waiting in our queue but for now I want to hear what other functionalities do you need boys and girls? ๐Ÿ™‚

Well brother it doesn’t look good

Taken from Liferay JIRA. Question is those new tickets are related to trunk (which is unstable so they should be closed or tagged “will check that in 6.1 RC) or to stable version (6.0.6) of Liferay.

Liferay hate, love, learn

Today I saw a intereting page. It’s all about why Liferay sucks. I know that LR is no shiny diamond (I hate Liferay blogs portlets) and I know it has many very interesting features (I love Liferay web content structures) but lets see what other people say:

Built on top of obsolete and over-engineered fundamentals (Java Portlet API) that are pain to work with. Community edition lacks proper Javadoc. No real support for easy portlet development, portlets are NOT simple portal extensions as proclaimed by Liferay. Liferay code looks like a bunch of util method calls, some methods have 100+ lines of code. In the end, people end up hacking their way through Liferay / Portlet API to satisfy various business requirements, instead of building something that would suit their needs. Liferay is an illusion of something that can do everything (“Hey, it has CMS, it has forums, it has galleries!”) and this is something sales people like to listen to – User-440ujs

I don’t agree on Javadocs – you can see that they are updated (see here). As for all other things I agree in 50%. Source code is messy and scriptles are overused but beatifull code wont help you sell portal to your customer.

Next one.

The CMS is a joke. Making a Liferay site look like anything other than Liferay is an act of self-torment. Whoever is in charge of Liferay UX needs to be replaced. Avoid this turd like the plague! – User-107fzu

Yep, styling is hard but thats beacuse pages consits of many portlets. It’s like saying that space shuttle is more complicated than a car – yes it is. But as for Liferay UX – I agree in 100%. Liferay UX (even in the newest LR 6.1) is horrible. Tons of Javascript, unconsistent configuration pages (I’m talking about web content structure). As I said beafore many thing in Liferay and in UX also are just proof-of-concept. Sometimes I’m wondering is there anyone responsible for LR UX as whole one product. In terms of UX Liferay is light years behind WordPress and miles behind Alfresco and Joomla.

Developing a new portlet is both, extremely painful (i mean, physically painful) and limited (Liferay is a lot of things, but open to new technologies is not one of them). Hot deploy is a very attractive feature, sadly it basically doesn’t work, you can have a well nice 70% of struggling with the tool, 20% testing, leftovers for coding. If you need something that hasn’t been developed for it before, well prepare to be another lost soul – User-987i9x-250c0e

I don’t agree on the first sentence. Developing portlets is harder if you don’t know how to do it. It’s not simple (and sometimes unsecure) PHP where you can write echo “Hello world”. Hot deploy – I’ve heard that someone is working on fixing that (I think it was Tomas Polesovsky).

Other comments were about lack of LDAP integration (we tested that last month and it worked fine ootb), no way to delete old instance (well in such complex system turning offย  is a safer option than delete).

On the opposite we have many Love comments (most came from Jorge Ferrer) but one of them is worth pasteing here:

Liferay rocks! Not simple tool for dummies (hey guys – it’s Java not PHP), but you can extend everything! Try to learn commercial portals – Tomas Polesovsky

The part you should remember is “you can extend everything! Try to learn commercial portals”. If you will work on large projects you will see that difference between PHP and JAVA is not so big – you will ran to same problems in both.