AdoptOS

Assistance with Open Source adoption

Open Source News

Drupal 8.5.0-rc1 is available for testing

Drupal - Mon, 02/26/2018 - 18:28

The first release candidate for the upcoming Drupal 8.5.0 release is now available for testing. Drupal 8.5.0 is expected to be released March 7.

Download Drupal-8.5.0-rc1

8.5.x makes the Media module available for all, improves migrations significantly, stabilizes the Content Moderation and Settings Tray modules, serves dynamic pages faster with BigPipe enabled by default, and introduces the new experimental Layout Builder module. The release includes several very important fixes for workflows of content translations and supports PHP 7.2. Finally, 8.5.0-rc1 also includes the same security updates that are provided in 8.4.5.

What does this mean to me? For Drupal 8 site owners

Drupal 8.4.5, a security update and the final release of the 8.4.x series, has also been released this week. 8.4.x sites should update immediately to 8.4.5, but going forward, 8.4.x will receive no further releases following 8.5.0's release date, and sites should prepare to update from 8.4.x to 8.5.x in order to continue getting bug and security fixes. Use update.php to update your 8.4.x sites to the 8.5.x series, just as you would to update from (e.g.) 8.4.2 to 8.4.3. You can use this release candidate to test the update. (Always back up your data before updating sites, and do not test updates in production.)

If you're an early tester who is already running 8.5.0-alpha1 or 8.5.0-beta1, you should update to 8.5.0-rc1 immediately. 8.5.0-rc1 includes security fixes (the same fixes that were released in Drupal 8.4.5).

Site owners should also take note of the fact that Drupal 8's support for PHP 5 will end in one year, in March 2019. PHP 7.2 is now the best recommended PHP version to use with Drupal 8.

For module and theme authors

Drupal 8.5.x is backwards-compatible with 8.4.x. However, it does include internal API changes and API changes to experimental modules, so some minor updates may be required. Review the change records for 8.5.x, and test modules and themes with the release candidate now.

For translators

Some text changes were made since Drupal 8.4.0. Localize.drupal.org automatically offers these new and modified strings for translation. Strings are frozen with the release candidate, so translators can now update translations.

For core developers

All outstanding issues filed against 8.4.x were automatically migrated to 8.5.x. Future bug reports should be targeted against the 8.5.x branch. 8.6.x will remain open for new development during the 8.5.x release candidate phase. The 8.5.x branch will be subject to release candidate restrictions, with only critical fixes and certain other limited changes allowed.

Your bug reports help make Drupal better!

Release candidates are a chance to identify bugs for the upcoming release, so help us by searching the issue queue for any bugs you find, and filing a new issue if your bug has not been reported yet.

Categories: CMS

Fundamentals of Membership Management - Training session on Friday, March 2nd

CiviCRM - Mon, 02/26/2018 - 12:44

This two hour on-line training on Friday, March 2nd (9 am PT/ 10 am MT/ 11 am CT/ 12 pm ET) taught by Cividesk is perfect for new users of CiviCRM who would like to learn all the basics of CiviMember.  

Categories: CRM

Gartner Recognizes KNIME as a Leader in Data Science and Machine Learning Platforms

Knime - Mon, 02/26/2018 - 10:00
Gartner Recognizes KNIME as a Leader in Data Science and Machine Learning Platforms oyasnev Mon, 02/26/2018 - 16:00

Zurich, February 26, 2018 – For the fifth year in a row, KNIME® , the open source platform for data driven innovation, has been placed in the leader category in Gartner’s 2018 Magic Quadrant for Data Science and Machine Learning Platforms. The placement recognizes ability to execute and completeness of vision.

Gartner, Inc. describes leaders as having “a strong presence and significant mind share in the market. Resources skilled in their tools are readily available. Leaders demonstrate strength in depth and breadth across a full model development and implementation process. Leaders are in the strongest position to influence the market's growth and direction. This gives them the advantage of a clear understanding and strategy for the data science market, with which they can become disrupters themselves and develop thought leading and differentiating ideas.”

“To be recognized again as a leader, while also being significantly moved forward in vision and ability to execute, is humbling,” says Michael Berthold, CEO, KNIME AG. “We have a great community of users and enthusiasts who continually contribute to KNIME, and we are grateful for that. They are helping us build this open source platform that strives to be at the forefront of innovation.”

KNIME owes these accolades to its users from thousands of organizations (including many big players) across various industries, all enjoying the open source, free platform. “While other platforms are commercializing functionality, KNIME is continuing to cause a stir in the market by adding more functionality to the open source platform. The concept of adding the commercial KNIME Server for collaboration, automation, and deployment, without ever limiting open source usage is just brilliant,” comments Stefan Weingaertner, AI Associates. “It’s no wonder KNIME is in the leader category again this year.”

“We’re continuing to invest heavily in the development of our software to ensure our users have everything they need to get their job done, fast. We’re also ensuring there are simple and relevant ways to enable these users to share what they do with other members of their organization,” continues Berthold. “Our commitment to open source is solid and we’ve put everything on GitHub to back that up. This honest, transparent business model works for everyone and we plan on keeping it that way.”

For further information, contact KNIME at info@knime.com, or download KNIME and discover it for yourself. KNIME – Open for Innovation®.

News date Mon, 02/26/2018 - 16:00
Categories: BI

How to partner with influencers to create engaging marketing campaigns.

PrestaShop - Mon, 02/26/2018 - 09:32
Step by step process to find the right influencer for your brand.
Categories: E-commerce

Creando Experiencias de Usuario Consistentes con Liferay Adaptive Media

Liferay - Mon, 02/26/2018 - 05:18

La página web común de hoy en día es más compleja que nunca en lo que respecta a su programación. En la actualidad, compañías de todos los sectores utilizan imágenes, vídeos y cada vez más elementos interactivos para ayudar a mejorar las experiencias del usuario. A ello, hay que sumarle una innumerable cantidad de nuevos dispositivos con acceso a Internet, que presentan interfaces complejas que cambian la experiencia del usuario en función de cada persona, originando con ello nuevos retos en este campo.

Pero más allá de la complejidad de los sitios web, hemos sido testigos de un aumento del tamaño de las páginas web, debido a la gran cantidad de elementos comúnmente utilizados en cada una de ellas. Según HTTP Archive, estos elementos han supuesto un incremento en el tamaño medio de una web: desde los 702 KB en noviembre de 2010, hasta los 3.3 MB en septiembre de 2017. Lo que significa que el tamaño medio se ha multiplicado, aproximadamente, por siete en siete años.

Pero el incremento del tamaño de las webs y el uso de un mayor número de dispositivos diferentes para acceder a los sites, no son los únicos factores que pueden causar una gran disparidad en las experiencias de los usuarios. En la actualidad, los países tienen al mayor número de población con acceso a Internet registrado hasta ahora. Sin embargo, el ancho de banda promedio en cada país puede variar mucho, lo que, a su vez, puede generar diferencias entre las experiencias de los usuarios.

El uso de distintos dispositivos para acceder a los sitios web significa que los menús de navegación de los mismos, el tamaño de los textos, la ubicación de las imágenes, los espacios en blanco, etc., deben cambiar para poder adaptarse a las necesidades específicas de cada pantalla. Por su parte, el incremento en el tamaño de las páginas web y las diferencias en el ancho de banda, pueden resultar en una carga más lenta de los sites o en una imposibilidad de mostrar algunos de los elementos que la componen, frustrando así a los usuarios en su experiencia con la web. Sin buenas estrategias de experiencias de usuario que tengan en cuenta estos factores, y que contemplen una planificación a través de una programación detallada para abordarlos, puede que resulte difícil para las empresas llegar adecuadamente a su público objetivo.

Por ello, Liferay Adaptive Media se ha desarrollado para dar respuesta a estos desafíos que hoy en día se plantean en las organizaciones, abordando estas necesidades para mejorar la estrategia omnicanal de las empresas, así como el rendimiento de las webs.

Optimización para una Gran Experiencia de Usuario

Como se muestra en la siguiente infografía, el vídeo es el elemento que ha experimentado un mayor incremento de su uso en las webs, impactando directamente en el tamaño de las mismas. Por su parte, las imágenes continúan siendo el elemento más utilizado.

Sin embargo, pese a que el vídeo es el elemento que ocupa gran parte de los datos, las imágenes hoy representan más datos que nunca. Como se ve a continuación, si bien el número promedio de imágenes se ha mantenido relativamente constante a lo largo de los años, el tamaño promedio de las mismas ha aumentado progresivamente.

De acuerdo con un estudio de Kissmetrics casi la mitad de los usuarios esperan que un sitio web se cargue en menos de tres segundos. Si la web no se carga en ese tiempo, es más que probable que lo abandonen. Además, un 79% de los encuestados aseguró que no regresaría nuevamente a un site que tuviera problemas de rendimiento. Todos estos factores de la experiencia online del usuario influyen en los resultados finales de cada compañía; lo que evidencia la importancia de crear una buena y consistente experiencia online, que funcione para una amplia variedad de usuarios, en diferentes circunstancias.

A medida que los datos de las páginas web continúan creciendo, las organizaciones deben adoptar medidas para evitar que las complicaciones relativas al uso de diferentes dispositivos y los distintos servicios de ancho de banda afecten negativamente a la experiencia de sus usuarios. Abordando estas cuestiones con anterioridad y anteponiendose a estos problemas, las organizaciones serán capaces de proveer una experiencia de usuario moderna y agradable.

Tomando el Control de la Experiencia del Usuario

Una experiencia de usuario consistente y bien construida, que se ajuste a las circunstancias únicas de cada tipología de usuario, puede beneficiar a muchas audiencias distintas. En este sentido, Liferay Adaptive Media puede ayudar a:

  • Administradores de Portales: para definir la resolución de los recursos multimedia que se usan para procesar y mostrar las imágenes conforme a las características de cada dispositivo de acceso (tamaño de pantalla, ancho de banda y capacidad de procesamiento).
  • Creadores de Contenido: para la carga de elementos multimedia y generación de nuevas páginas de contenido sin tener que preocuparse por adaptar cada uno de ellos a cada tipo de pantalla y dispositivo. Adaptive Media trabaja de forma transparente para el usuario, en un segundo plano, para que el aspecto de estos elementos no se vean afectados negativamente por la variación del uso de dispositivos de acceso a la web.
  • Usuarios finales: para que puedan disfrutar de una experiencia mejorada al visualizar las imágenes adaptadas a cada dispositivo y conexión a Internet.
  • Desarrolladores: integrar fácilmente Adaptive Media en sus aplicaciones para que soportar los diferentes atributos de cada elemento.
Mejora tu UX con Liferay Adaptive Media

La aplicación Liferay Adaptive Media ayuda a los programadores a hacer frente a las complicaciones derivadas por el gran tamaño de las webs y las variaciones en los diseños de los dispositivos, con características que incluyen:

  • Integración de base con documentos y elementos multimedia
  • Integración opcional con blogs y contenido web.
  • Capa de compatibilidad que elimina la necesidad de modificar el contenido antiguo.
  • Redimensionamiento de imágenes almacenadas en Liferay, adecuada a cada resolución específica requerida.
  • Reducción del tamaño de la página y mejora de la velocidad de carga según el dispositivo y ancho de banda.
  • Aplicación de estos cambios de forma automática para usuarios finales, sin necesidad de hacer programaciones individuales.

Adaptive Media ayuda a los usuarios de Liferay DXP a crear experiencias que se adaptan a tus clientes, estén donde estén, independientemente del dispositivo que utilicen.

Mejora la Experiencia del Usuario con Liferay Adaptive Media

Averigua si Liferay Adaptive Media es adecuado para tu caso y aprende a cómo personalizar y adecuar la calidad de cada imagen para proporcionar la mejor experiencia de usuario posible.

Aprende más sobre Liferay Adaptive Media   Rebeca Pimentel 2018-02-26T10:18:32Z
Categories: CMS, ECM

Remembering J-P Stacey

Drupal - Mon, 02/26/2018 - 00:35

In 2017 we saw the passing of J-P, community friend, mentor, leader, and contributor. Within the community J-P's was known for his passions: Drupal, programming culture, gardening, cycling and the environment. We invited people to share their memories of J-P and his impact; we share them with you now in memoriam. This is a moving tribute and a celebration of his life.

We invite you to also share your tributes in the comments section.


J-P Stacey on the Tour de Drupal 2016 Photo by Christian Ziegler
The person

J-P was a bright intelligent, quirky chap, ADORED animals, he would melt at the mention of our pets names, he would happily spend hours cooing over stories of his beloved cat Indie, he'd oblige you in hours and hours of stories about your beloved animals - kae76

Whenever I was with JP he was always smiling. He was always there to help and it was always a pleasure to see JP at Drupal events and chat to him on IRC - aburrows

Nice. My overriding memory of J-P is how nice he was. When he moved up to Sheffield and started attending the Yorkshire meetups he fitted right in straight away. He always found time to ask how people were doing and genuinely cared what they were saying. He was always patient, positive and happy to help others - kmbremner

I remember first meeting J-P at DrupalCamp Oxford in 2012, when I had just started out running a small business and I remember thinking how much of a mad professor he looked, and discussing different parts of Oxford with him. The last time I saw J-P was sharing a meal with at DrupalCamp London 2017 near Euston. Both times J-P was actively seeking to engage people from the edges of the community (all the other Drupalists at the meal were freelancers or small businesses) and I know that was something he was highly instrumental at working with. I actually went back to that restaurant recently, and it seems slightly strange that I won't see J-P at another event - willhallonline

J-P being present just simply makes you happy, such an open genuine chap. Always disappointment around if he can't attend a catch-up, and anticipation if you know he will be there. J-P, always the gentleman, honoured my poor jokes with a titter or a laugh, even if it first met with an understandable groan - waako

I knew J-P, in that we participated together every year as mentors at the Friday Core Sprints at Drupalcon. Last year at Drupalcon Dublin, I asked J-P to be my "mentor mentor" because I was so impressed by his gentle and unruffled style. He organized the team at his table with exemplary grace and good humour. I was particularly struck by how quickly he gathered a group of enthusiastic people around him. Bye J-P, it was a true honour to have known you, if only once a year, in this particular context - michaellenahan

He was *always* cheerful! - greg.harvey

JP always took the time to talk to people and explain things to people who needed help. It's safe to say that helping people was a passion for JP - Ikit-claw

I recall the Friday evening of Drupalcamp London 2017, J-P and I met at Old Street Station and travelled to Kings Cross to meet up with fellow Drupalists for a meal at the Diwana Bhel Poori house for a meal. The trip and the hour long wait there for the rest to join us was filled with fun and interesting conversation. We realised how much we had in common and made each other laugh. That plus stimulating conversation over great food I will remember for a long while - TechnoTim2010

The thing I will always remember best about J-P his determination to stick to his principles; be they in code, in process, in environmental matters or even his house and garden! It was so sweet on occasion to see him struggle when pragmatism meant they couldn’t always be followed but it constantly reminded me to try harder myself. I miss J-P but I know I’ll be a better person for knowing him and looking up to him - rachel_norfolk

I met him via tour de drupal Amsterdam and Barcelona. J-P was cycling a long way alone, Criz and I would cycle the Pyrenees for 2 days and then we met for the final leg to Barcelona and had a really good time. I didn't get to know Stacey too much but felt he was a very calm, positive, free person - dasjo

Working on a project with J-P with him as lead developer and me acting as project manager, what I loved was the fact he would always push back on every story, but as we chatted about options, he'd end up getting excited and committing to even more than I expected to get in the first place - stevecowie

J-P was a brilliant companion on various Tour de Drupal cycle rides from the UK to wherever Drupalcon was being held. His great sense of humour, adventure and unflappable flexibility made him an excellent person to cycle with, and he was great at drawing people in, involving them and making everyone feel at ease. These same characteristics made him great fun to be around at a conference; I remember the "I'll do it if you will" approach that got us into talking at a Drupal unconference, with just a few minutes' notice in his case. He cared about others, and his strong sense of fairness and inclusion as well as pragmatism were of great value when there were difficult decisions to be made - martin_q

JP was involved with the modern web development apprentices (a.k.a. Drupal apprentices) programme in the UK. The last time I met JP was shortly before his holiday trip to Spain. We were scoping out some training days for the apprentices programme, as budget had become available to run 1-day topic-focussed trainings with external specialists. He was looking forward to training apprentices on test-driven development after his holiday - andrewmacpherson


#drupal #sprintweekend Sheffield 2016 Shared on twitter by @rivimey
The Drupaller & mentor

I was aware how deeply knowledgeable he was, and his ability to make that knowledge accessible to others, and his nature to always hear others out, always assuming he hadn't got the answer. He wasn't shy to press someone about a topic which he believed was being overlooked, or underrepresented - kae76

He was excellent at explaining and helping others - aburrows

I remember J-P presenting about Drush Make at DrupalCamp North West 2013. It really opened my eyes to how there was a more efficient way of doing things than I had known before. Years later he was a strong advocate for Composer evangelising the benefits to the local community and beyond - kmbremner

The thing I will remember most about J-P was his passion around open-source software. He was committed to Drupal and passionate about the community. It always seemed that he really cared about the *little* guy. The person starting up, or the newcomer to the community - willhallonline

He was always interested in problem solving, beyond that he was interested in understanding the problem, not solving it for you. He could explain code, like super-intelligent physics jokes, in the most clear manner and help you find direction. He would ask all the right questions about what you needed to achieve - waako

He totally "got" contrib, always looking for the pragmatic solution, always looking to use and/or improve existing code - greg.harvey

JP would take the time to help people learn code and point them in the right direction you could take to him on slack or irc and he would take the time to help you - Ikit-claw

J-P was always willing, if he had time, to help with any coding issues on IRC. He was busy much of the time. I would loved to have collaborated on a project with him, sadly never to be - TechnoTim2010

I’ve learned so much from J-P’s blog posts and always enjoyed our encounters at various events over the years. Highly technically competent and willing to spend time to share skills and knowledge, I saw J-P as part of the very fabric of what makes Drupal Drupal, the reason why I’ve hung around for so long - Steve Purkiss

Time. It didn’t matter how long it took for J-P to work with someone until they understood something - he’d see it through - rachel_norfolk

J-P was the alternative to Drupal stack exchange - stevecowie

JP shared his own learning very freely. After D8 came out JP set about learning the new API - he published what he learned on his blog, and those are some of the best D8 tutorials I've seen. "Did JP figure this out yet?" was often my first question, before approaching the official docs - andrewmacpherson

The future: what would J-P would want us to remember?

J-P would want us to remember the people behind the code; to spend the time helping new members of the community and making them feel welcome. To have a beer and get to know each other on a personal level - kmbremner

Documentation! Joking aside ... I honestly not sure how to answer this, fundamentally the J-P we all knew - cared about a lot of things, the environment, equal rights, good clean code, great clear documentation, meaningful social interactions and impact. But my everlasting memory is how much he held his family and friends in focussed concern - listening and hearing - sharing daft jokes and I personally honor him for his vulnerability he was an open book. This is the lesson I will learn and keep learning from J-P; listening and HEARING the ones you love, open honest vulnerability and there is never a bad time for a cat pun - kae76

Be kind to each other and get involved in the Drupal eco-system - aburrows

I think that the enduring message is that it is not about code. Code is far more ephemeral than community. People's enduring care for the Drupal community is what makes it powerful. And I feel that J-P knew that - willhallonline

He would want us to grow things, to experiment, cycle and to listen & engage with each other - waako

The planet - greg.harvey

I think he would want us to pay forward all the kind gestures he had done for others. If JP ever took the time to help you and see someone stuck who you could help I think he would want people to take 30 minutes to help someone else and encourage them - Ikit-claw

J-P was passionate about Drupal and would want us to share that passion, and help our fellow Drupalists. He was also passionate about Green issues and protecting and improving the environment, I am sure he would be happy I created a Drupal 8 site to support a campaign not to concrete over beautiful countryside, but instead push cycling and other non-destructive solutions -

We should consider our own green credentials and do anything we can for our local environment - TechnoTim2010

Learn, then teach - Steve Purkiss

His garden - rachel_norfolk

Go by your own pace - dasjo


From left to right: Christian, Youri, J-P, Stephen, Martin (Photo by Conor Cahill)
Reflections on Tour de Drupal 2016 Shared by MegaChriz - An evening in Belfast

On a cold Friday evening in Belfast - late September 2016 - J-P, Martin and Stephen arranged to meet me and Christian at a small restaurant in town. The streets were empty - as if everybody was either out of town or at home. But the restaurant was full till the brim - there was no more room inside. J-P, Martin and Stephen were sitting outside on the terrace of the restaurant when I and Christian arrived, having a drink and presumably trying to ignore the cold. Despite the cold, we had to wait for a table to become free inside before we could order some food (outside the ordered food would become cold in minutes, maybe even in seconds). So we sat there for about an hour and still no one came out to make room for us.

J-P had a hard time fighting his hunger and finally said "Maybe I should just go inside and stare at people to make them want to go away". J-P spread his eyes wide-open, pretend to be staring at us. That was one of the funniest moments I had with J-P.

J-P didn't go inside to stare people away, after some more time waiting there finally came room for us and together with Martin and Stephen, J-P ordered a 22 inch pizza. 

Tour de Drupal 2016

The next two days we cycled together from Belfast to Dublin. It was a great ride with mostly flat land and sometimes lots of rain! There were also some hills and J-P had a hard time cycling these on his Brompton. 

We hadn't arranged a overnight stay between the first and second cycle day, so on the first day J-P and Stephen had to make calls to several guest houses, bed and breakfasts, airbnb's, etc. to find a place for us to sleep. "Next time, I'll book an overnight beforehand," J-P said, "This was way too stressful."

The second day was more windy and because we seemed to be running out of time to get to Dublin the same day we took a shortcut. This was alongside a road where traffic was allowed to reach speeds of 100 km/hour. This was the part of the tour I didn't like much. One time I got blown to the berm, nearly falling off my bike! With time still running out I only got to Skerries as couldn't reach a higher speed (I took the rest by train). Despite that, I'm glad I have been able to cycle with this group.

It was our Tour de Drupal!


The Five Bikers Staring to the Sea. From left to right: Youri, Christian, Stephen, J-P, Martin. (Photo by Martin Quested)
AttachmentSize JP_bike_web_use.jpg84.89 KB
Categories: CMS

SalesAgility, the driving force behind SuiteCRM, joins Open Source Initiative as Corporate Sponsor.

Open Source Initiative - Sun, 02/25/2018 - 20:33

Commitment to openness, freedom and collaboration in open source demands a different corporate mindset, a different set of values and a different set of behaviors.

PALO ALTO, Calif. - Feb. 26, 2018 – The Open Source Initiative® (OSI), the global non-profit dedicated to promoting and protecting open source software, announced today the Premium Sponsorship of SalesAgility, the authors and maintainers of SuiteCRM. Began in 2013 as a fork of SugarCRM’s Community Edition, SuiteCRM is a completely open source CRM solution delivering all the functionality expected of an enterprise-class CRM application. SuiteCRM is now generally acknowledged to be the world's leading open source CRM solution.

SalesAgility, as an employee-owned and community driven consultancy, is deeply committed to open source, believing the culture of co-creation inherent to open source best serves the long term interests of clients and is the future of business applications. With its community focus, the company has embraced and celebrates the principles of open exchange, collaborative participation, open standards, rapid prototyping, transparency, meritocracy, and community: the same values the OSI promotes among communities of practice to drive genuine open source development.

“We’re so very pleased to have SalesAgility’s support, especially now, as the OSI enters it’s 20th year,” said Patrick Masson, General Manager of the OSI. “We’re thrilled to see the success of open source and the success of companies like SalesAgility who are authentically engaged in the open source community. This is where our work over the next decade must now focus, learning from that success to help companies understand best practices so more may realize the benefits of community-driven development. SalesAgility is one of these that we can reference and which can serve as a mentor to others.”

“We are excited to be members of the Open Source Initiative”, said Greg Soper, founder of SalesAgility. “The work the OSI has done over the last 20 years is extraordinary, and we are looking forward to collaborate together to ensure the success of open source in all fields.”

The OSI has been crystallizing consensus around open source licensing, benefits of participation, and community norms for the last 20 years, and will remain committed to that work. Yet as successes have increased, in both the adoption of open source software and the communities that enable it, the OSI’s work will evolve. Many agree, “Open Source has won,” and an organization dedicated to simply promoting adoption and advocating for collaboration is no longer enough. Although the OSI will continue to take on this work when needed, the organization has identified additional goals for itself, specifically in helping organizations align with established norms, best practices, and the open ethos that has led to Open Source Software’s tremendous growth. Through the support of companies like SalesAgility, who are actively engaged in open source development, the OSI not only receives critical resources for continued operations, but importantly, real-life references that can help inform open source communities of practice, and even mentor organizations just entering the open source ecosystem.

About SalesAgility
SalesAgility is the driving force behind SuiteCRM, the world’s most popular open source CRM. SuiteCRM is a fully featured CRM, that can be deployed on-premise or in the cloud, allowing organisations and enterprises to be in full control over their own customer data. With a community over 88,000 people, a download count of over 800,000 and an estimated user count of over 4 million users, SuiteCRM is world’s most popular open source CRM.

Powered by a highly skilled team, SalesAgility provides SuiteCRM services that include support, consultancy, custom development, migrations, and training, as well as SuiteASSURED: a fully supported, discrete build of SuiteCRM, created to provide total care for enterprise-class customers and other large organisations. For more information, visit https://suitecrm.com or follow @SuiteCRM on Twitter.

About The Open Source Initiative
Founded in 1998, the Open Source Initiative (OSI) protects and promotes open source software, development and communities, championing software freedom in society through education, collaboration, and infrastructure, stewarding the Open Source Definition, and preventing abuse of the ideals and ethos inherent to the open source movement. The OSI is a California public benefit corporation, with 501(c)(3) tax-exempt status. For more information about the OSI, see https://opensource.org.

Media Contact
Italo Vignoli
italo@opensource.org

Categories: Open Source

Customize Elastic Search and Search by Synonyms in Liferay

Liferay - Sat, 02/24/2018 - 08:52

Q-Have you ever wondered if you can customize your Elastic Search, so that on your searches in Liferay, not only the words you're searching for come up in the results but also synonyms of these words?

A-Yes, you can!

Below, I'll show you an example of how I did it (by customizing my indexes and mappings settings).

Let's say that I have a web content article containing the word "small" and I search for the word "tiny".

 
  1. Navigate to Control Panel → Configuration → System Settings → Foundation
     
  2. Search for the com.liferay.portal.search.elasticsearch.configuration.ElasticsearchConfiguration system setting.
     
  3. Go to "Aditional index configurations" and add your own.

    You can start by copying the contents of your index-settings.json file there. Your index-settings.json file is packed in the Elastic Search module of your Liferay bundle.

    Now, modify it as this document describes: https://www.elastic.co/guide/en/elasticsearch/guide/current/using-synonyms.html .

    It should look like the image below (note the "synonyms" part of the json, where we wrote our list of synonyms):
      
     
  4. Now go to "Override type mappings" and copy into the text area input the contents of the file "liferay-type-mappings.json", also packed in the Elastic Search module (a jar that you will find in your Liferay bundle) into it.

    Modify it, also following the steps this document describes: https://www.elastic.co/guide/en/elasticsearch/guide/current/using-synonyms.html (as in the previous step).

    For example, you could add something like this:
      "content": {      "index": "analyzed",      "store": "yes",                "search_analyzer" : "my_synonym_analyzer",                "analyzer" : "my_synonym_analyzer",                "term_vector": "with_positions_offsets",                "type": "string"   },
    and something like this:
     "title": { "index": "analyzed", "store": "yes",                "search_analyzer" : "my_synonym_analyzer",                "analyzer" : "my_synonym_analyzer", "term_vector": "with_positions_offsets", "type": "string" },
    to it:

      
     
  5. Save your changes
     
  6. Navigate to Control Panel → Configuration → Server Administration and execute "Reindex all search indexes" under the section "Index Actions"


     
  7. Perform a search and... Voila!, the magic happens:


    Easy, right?

    If Elastic Search can do it, Liferay will do it too (since it leverages on Elastic Search for indexing its documents). You just need to know it can be done, and where in the control panel you can configure it.
     
Carlos Hernandez 2018-02-24T13:52:38Z
Categories: CMS, ECM

How to Upgrade to Liferay 7.0+

Liferay - Fri, 02/23/2018 - 15:35

So the question comes up how to do Liferay upgrades.

I'm not talking here about the technical details of how you upgrade one particular plugin to another type of plugin, what kinds of API changes have to be made, etc.

Instead, I'm thinking more about the general process of how to upgrade, what choices you're presented with and what the ramifications are for making certain choices.

Upgrades Are Projects

The first thing to remember is that upgrades are projects. You should totally build them out as projects, you should have a project plan, you should have a project team, ... Having a full project plan forces you to define scope for the upgrade and time box all activities so you will know how the project is proceeding.

As a project, you also should have a risk assessment/mitigation plan. Know in advance what you will do if the project runs long or runs into issues. Will you just stretch the timeline? Will you seek help from Liferay GS or a Liferay Partner? Are you sending your development team to Liferay training in advance or only if they seem to struggle? Will you rely on LESA tickets, Liferay documentation, community support via the forums or slack?

Liferay GS offers an Upgrade Assessment package where an experienced Liferay GS consultant will come onsite to review your environment and build a customized report outlining what your upgrade effort will be. This assessment can become the foundation of your project planning and can help set your upgrade in the right direction.

Upgrades Have Scopes

Upgrading from Liferay 6.2 to Liferay DXP 7.1, there will be scope to this project and the project is susceptible to scope creep.

For example, you might decide going in that your project is simply to get what you currently have migrated and running under DXP. During the upgrade project, though, you might decide to add some backlogged features or refactor your codebase or rework legacy portlet wars into OSGi portlet modules. Each of these things would be considered scope creep. Each change like these that the team takes on will negatively impact your project plan and schedule.

Upgrades Expose Bad Practices

The one thing I've found is that upgrades tend to expose bad practices. This could be bad practices such as using an ORM package instead of Service Builder for data access. It could be a non-standard way of decoupling code such as making all service calls via remote web services where a local service implementation would have been an easier path. It can expose when standard design practices such as design by interface were not fully leveraged. It could be as simple as having used an EXT plugin to do something that should have been handled by a JSP hook or a separate custom implementation.

Exposing bad practices may not seem very important, but upgrading bad practices will always add to a project plan. Something done initially as a shortcut or a hack, these things get difficult to carry forward in an upgrade.

The one thing I've found in 10+ years of experience with Liferay, it is often better to do things "The Liferay Way". It is not always easy and may not seem like the right way, but it usually ends up being the better way generally to develop for the platform.

Upgrade Project Recommendations

To facilitate your upgrade project, I offer the following recommendations:

  • Limit scope. As far as the upgrade is concerned, limit the project scope to getting what you currently have running under the later version. Do not consider refactoring code, do not consider reworking portlet wars as OSGi modules, etc. Limit the scope to just get on the new version. If you want to refactor or rework wars as OSGi modules, save that for a later project or phase.

 

  • Leave portlet wars as portlet wars. I can't say this strongly enough. It is absolutely not necessary for your legacy portlet wars to be refactored as OSGi modules. Your legacy portlet wars can be deployed to DXP (after necessary API changes) and they will automagically be converted into an OSGi WAB for you. Do not spend your upgrade cycles reworking these into OSGi bundles yourself, it is a complete waste of your time and effort.

 

  • Only rework what you have to rework. You'll have to touch legacy hooks and EXT plugins, there is no way around that. But that is where your upgrade cycles need to be spent. So spend them there.

 

  • Rethink upgrading bad practices. I know, I said limit scope and migrate what you have. The one exception I make to this rule is if you have exposed some really bad practices. In the long run, it can often be a smaller level of effort to rework the code to eliminate the bad practice first or as part of the upgrade. Cleaner code is easier than spaghetti to upgrade.

 

  • Use Liferay IDE tooling. The Liferay IDE comes with a built-in upgrade assistant tool. While the tool is not perfect, it can help you upgrade your Maven and Plugin SDK projects to be compatible with the later version, including suggesting and making necessary API changes for you. If you do not use the upgrade assistant, you are willfullly missing out on an automated way to start your upgrade.

 

  • Have a Backup Plan. Know in advance if you are going to leverage Liferay GS or a Liferay Partner to help complete your upgrade in case you are seeing delays. If you wait until you are behind the eight-ball before mitigating your risk, you will be less prepared to get the project back on track if it is going off the rails.

 

  • Get a Liferay Upgrade Assessment Package. Even if you are going to do all of the work in house, an upgrade assessment can highlight all of the aspects you and your team will need to consider.

That's pretty much it.  Have any horror stories or suggestions you'd like to share? Please add them below...

David H Nebinger 2018-02-23T20:35:41Z
Categories: CMS, ECM

Deploying Liferay 7.0 on to Tomcat 8.5

Liferay - Fri, 02/23/2018 - 13:21

Tomcat 8.5 is an in-between version of Apache Tomcat 8.0 and 9.0. According to the Apache site, it contains some features in 9.0 that have been backported to 8.0. This version of Tomcat is currently in the "Supported" matrix of the Liferay DXP Compatibility Matrix, and of course, the question is: How do I set up Liferay CE/DE 7.0 with Tomcat 8.5?

The short answer is: Exactly like you would on Tomcat 8.0, which can be found here. Much of this entry will be a reproduction of those steps. The order of the steps will be a little different.

This blog post will cover the bare minimum to get Liferay CE/DE 7.0 working on Tomcat 8.5, skipping some of the extraneous steps or providing alternate steps. These steps were run on a Windows 10 machine, but should be generally applicable to Linux environments as well. Differences will be noted. Despite having been done in Windows, "forward" slashes aka "/" will be used, as that is how Tomcat wants directories to be marked.

Terminology

$TOMCAT_HOME - location of the Tomcat 8.5 directory, usually inside $LIFERAY_HOME

$LIFERAY_HOME - location of the Liferay directory that will contain Tomcat, and all the usual Liferay directories, like data, deploy, logs, osgi, etc... This directory can be located anywhere.

Step 0 - Prerequisites
- Install Java JDK 8, and configure the JAVA_HOME variable if not done already.
- Test the validity of the path by using the command "java -version" in the command prompt/terminal
- If there is a JRE_HOME variable set, remove it.

Step 1 - Acquire all the necessary files
- There are 3 required files provided by Liferay: the Liferay WAR, the Liferay dependencies, and Liferay OSGI dependencies.
- These steps were performed using Liferay DE 7.0 SP6, the portal portion of Liferay DXP. If you have a Liferay subscription and wish to also do the same, the files are available from Customer Portal, here. The files for Liferay CE 7.0 GA 5 can be found here. The individual files can be found down at the bottom of the page.
- There are a number of JAR files that are not included in default Tomcat that need to be acquired. They can either be copied over from a Liferay Tomcat bundle, or downloaded individually.

  • activation.jar
  • ccpp.jar
  • com.liferay.osgi.service.tracker.collections.jar
  • jms.jar
  • jta.jar
  • jutf7.jar
  • mail.jar
  • persistence.jar

Locations on where to get these files can be found in the regular Tomcat 8.0 steps.

REMINDER: Don't forget the database driver JAR file.

Step 2 - Extract dependency files
- Extract the Liferay dependency JARs to $TOMCAT_HOME/lib/ext. It will be necessary to create the "ext" directory.
- Extract the "osgi" directory from the OSGI dependency ZIP into $LIFERAY_HOME

Step 3 - Configure catalina.properties
- In $TOMCAT_HOME/conf/catalina.properties, find the "common.loader" property.
- Add the following to the end:

"${catalina.home}/lib/ext/global/*.jar","${catalina.home}/lib/ext","${catalina.home}/lib/ext/*.jar"

OR

Replace the whole property

common.loader="${catalina.base}/lib","${catalina.base}/lib/*.jar","${catalina.home}/lib","${catalina.home}/lib/*.jar","${catalina.home}/lib/ext/global","${catalina.home}/lib/ext/global/*.jar","${catalina.home}/lib/ext","${catalina.home}/lib/ext/*.jar"

- This tells Tomcat that there are extra JAR files that it needs to recognize.

Step 4 - Configure catalina.policy
- Delete the contents of catalina.policy and replace it with:

grant { permission java.security.AllPermission; };   - Yes, delete the contents of the file and replace it with the above 3 lines.

Step 5 - Configure server.xml
- In $TOMCAT_HOME/conf/server.xml, the URIEncoding needs to be set te UTF-8 for Tomcat. Add the property URIEncoding="UTF-8" into the 2 <Connector> sections. In the default server.xml, it will be on line 69 and 116. 

<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" URIEncoding="UTF-8"/> AND <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" URIEncoding="UTF-8"/>

Step 6 - Configure ROOT.xml
- In $TOMCAT_HOME/conf, create Catalina/localhost/ROOT.xml
- Add the following to ROOT.xml

<Context path="" crossContext="true"> </Context>

- Note that in the original Tomcat 8.0 steps, there is a significant chunk of commented out settings. They are not used in this basic, minimal setup. If you are using JAAS, then yes, the commented out section is necessary.

Step 7 - Extract Liferay WAR
- Delete all the directories in $TOMCAT_HOME/webapps except for ROOT. These are just sample applications.
- Delete the contents of the ROOT directory. Alternatively, ROOT can be deleted along with the other sample directories and remade as empty.
- Unzip the contents of the Liferay WAR file into the now-empty ROOT directory.

Step 8 - Configure JVM
- This is where Windows and Linux diverge.
- In $TOMCAT_HOME/bin, create setenv.bat or setenv.sh, depending on OS.
- In setenv.bat, paste the following:

set "CATALINA_OPTS=%CATALINA_OPTS% -Dfile.encoding=UTF8 -Djava.net.preferIPv4Stack=true -Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false -Duser.timezone=GMT -Xmx2048m -XX:MaxMetaspaceSize=1024m"

- In setenv.sh, paste the following:

CATALINA_OPTS="$CATALINA_OPTS -Dfile.encoding=UTF8 -Djava.net.preferIPv4Stack=true -Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false -Duser.timezone=GMT -Xmx2048m -XX:MaxMetaspaceSize=1024m"

Note the following properties:
"-Xmx2048m" - Liferay 7.0 CAN be run with the default 1024m of JVM space, but it's not fun. I would suggest at least 2048m (2 GB) or higher for development work.

"-XX:MaxMetaspaceSize=1024m" - In Java 8, the property -XX:MaxPermSize was deprecated and is ignored. PermGen was replaced with Metaspace, which by default is unlimited. Setting it to 1024m is fine for development work.

Step 9 - portal-ext.properties (optional)
- In $LIFERAY_HOME, create or copy over a portal-ext.properties file. In the file, you can set various configurations like the database connection, and disabling of the setup-wizard.

Step 10 - Start it up
- There are 2 ways to start Tomcat from a command line/terminal.
- Executing startup.sh or startup.bat will have the process run in the background and will not output log into the current window.
- Executing catalina.sh run or catalina.bat run will have the process run in the current command line and will output log into the window. If the window is closed, or the terminal session disconnected, then the process will stop.

Skipped Steps
- In comparison to the original Tomcat 8.0 setup steps, the following sections were skipped:
JNDI database configuration
Mail configuration
PACL
Mojarra

- The database and mail configuration can also be done via portal-ext.properties, in Step 9 above.

Conclusion
There are no specific steps that differ between Tomcat 8.0 and Tomcat 8.5. Essentially, steps are the same for a basic configuration of Tomcat 8.5 with Liferay 7.0 CE/DE. PACL and Mojarra may have some differences, but I've never used them. I believe Tomcat 8.5 is just a hair faster than Tomcat 8.0, but that's a subjective topic.

Jonas Choi 2018-02-23T18:21:43Z
Categories: CMS, ECM

Seis tendências de Experiência do Cliente para 2018

Liferay - Thu, 02/22/2018 - 14:46

O que define uma boa experiência do cliente está em constante transformação devido às constantes mudanças de comportamento do público e o uso de novas tecnologias. Entretanto, embora CX mude com o passar do tempo, sua importância para potenciais clientes e o sucesso dos negócios cresce a cada dia.

De acordo com um estudo feito pela Spigit, 75% das empresas pesquisadas em 2016 tinham como seu principal objetivo a melhoria da experiência do cliente. No entanto, a resposta para tornar isso possível encontra-se na continuidade. As seis tendências seguintes ajudarão você e seu negócio a criarem estratégias eficientes para atender às expectativas do seu público e atingir o sucesso com o passar do tempo.

1. Os Maiores Desafios Internos de uma Organização São Enfrentados na Experiência do Cliente

De acordo com uma pesquisa feita pela Forrester, os três maiores desafios na implementação de uma estratégia para a experiência do cliente são: a cultura da empresa (54%), sua estrutura organizacional (45%) e seus processos internos (41%). Todos esses obstáculos são, na maioria das vezes, associados ao CEO do negócio. Deste modo, 2018 pode ser um grande ano para empresas e CEOs principalmente, tomando decisões que poderiam permitir seus times a obter grandes ganhos em relação aos seus esforços de CX. CEOs e os departamentos deveriam focar na colaboração e comunicação efetivas para progredir substancialmente.

2. O Poder das Experiências sem Interrupções

Serviços como o Amazon Go lideram na criação de experiências de consumidores sem interrupções ao possibilitar compras online, até então realizadas apenas em supermercados, removendo o processo de checkout através de cobranças instantâneas. Como demonstrado pelo Customer Think, o público espera que as experiências avancem de maneira consistente e uma organização importante, como a Amazon, geralmente define os padrões para outros negócios. Neste caso, fazer compras sem obstáculos torna, o simples ato de comprar, fluido e mais rápido do que nunca.

3. Melhorando Experiências Baseadas na Localização

A tecnologia beacon tem sido usada por muitos anos, mas a sua adoção agora pode ser feita para deixar a experiência do cliente mais integrada e rápida. De acordo com a Dimension Data, os negócios estão trabalhando para fazer com que os pontos de contato físicos com o usuário sejam tão simples e eficientes como experiências onlines. Por exemplo, hotéis estão utilizando beacons para substituir chaves de quarto e empresas estão permitindo o acesso de colaboradores à locais seguros e informações sigilosas baseada na localização através dos beacons. A lacuna entre interações interpessoais e experiências online está cada vez menor. Clientes podem integrar todos os aspectos das suas atividades cotidianas às empresas.

4. Crescimento e Aperfeiçoamento da I.A. nas Operações de Negócios

A Inteligência Artificial terá papel importante em vários aspectos da experiência do cliente, mas garantir que isso aconteça depende da capacidade de reconhecer o discurso da sua audiência. A Customer Think detalhou como os sistemas de reconhecimento de voz podem ajudar os assistentes de voz a aprender rapidamente o modo como cada usuário fala, incluindo seus padrões, dialetos e sotaques únicos a fim de evitar a frustração e tornar seus papéis, nas empresas e em casa, essenciais no futuro. O Gartner prevê que 85% das interações dos clientes serão gerenciadas sem uma figura humana até o ano 2020, o que significa que sistemas automatizados e inteligência artificial gerenciarão a grande maioria dos processos. Com um uso cada vez maior de I.A. nas operações das empresas através de chatbots, agrupamento de dados, ferramentas de análise e muitos outros programas, espera-se que, em 2018, encontremos muitas outras empresas usando esta tecnologia de diversas maneiras.

5. Impulsionando o Gerenciamento de Identidade do Consumidor (CIAM)

Dados continuarão a ter importante função no modo como as organizações interagem com seus clientes. Por sua vez, empresas estão adotando o gerenciamento de identidade do consumidor (customer identity and access management - CIAM), que usa caraterísticas como o registro de clientes, autenticação “multi-fatores”, auto-gerenciamento de conta e administração do acesso a dados para escalar e personalizar canais para cada usuário e seus objetivos pessoais. Como discutido por Janrain, CIAM cria interações personalizadas elaborando estratégias de engajamento baseadas em insights de dados e na eliminação de obstáculos que podem afetar as experiências dos clientes. As empresas irão buscar este tipo de solução que seja robusta no gerenciamento e segurança de dados.

6. O Tempo se Torna um Produto

Enquanto ótimas experiências continuarem a ser uma prioridade, o The Economic Times destaca que o tempo de um cliente é um fator que se torna cada vez mais importante em cada interação. Desde realizar o processo de checkout o mais rápido possível a solucionar problemas de um item online obtendo respostas rapidamente através de chatbots, as empresas devem se esforçar para diminuir o tempo necessário dos clientes para receber os produtos ou serviços que eles desejam. Isso pode evitar que sua audiência se frustre e que potenciais clientes não abandonem sua jornada antes de concluí-la.

Mudanças para os Negócios Digitais em 2018

O modo como organizações realizam negócios e como elas são impactados pelas mudanças no marketing digital, irão, novamente, mudar em 2018. Leia mais sobre isso em negócios digitais.

  Transforme Sua Experiência do Cliente em 2018

Acompanhar as expectativas sobre experiência do cliente requer um software que está pronto para atender uma série de demandas. Leia mais sobre as estratégias possíveis com Liferay.

Leia Quatro Estratégias para Transformação Digital do Negócio   Isabella Rocha 2018-02-22T19:46:52Z
Categories: CMS, ECM

Drupal core - Critical - Multiple Vulnerabilities - SA-CORE-2018-001

Drupal - Wed, 02/21/2018 - 12:10
Project: Drupal coreVersion: 8.4.x-dev7.x-devDate: 2018-February-21Security risk: Critical 16∕25 AC:Basic/A:User/CI:Some/II:Some/E:Exploit/TD:DefaultVulnerability: Multiple Vulnerabilities Description: 

This security advisory fixes multiple vulnerabilities in both Drupal 7 and Drupal 8. See below for a list.

Comment reply form allows access to restricted content - Critical - Drupal 8 - CVE-2017-6926

Users with permission to post comments are able to view content and comments they do not have access to, and are also able to add comments to this content.

This vulnerability is mitigated by the fact that the comment system must be enabled and the attacker must have permission to post comments.

JavaScript cross-site scripting prevention is incomplete - Critical - Drupal 7 and Drupal 8 - CVE-2017-6927

Drupal has a Drupal.checkPlain() JavaScript function which is used to escape potentially dangerous text before outputting it to HTML (as JavaScript output is not auto-escaped by either Drupal 7 or Drupal 8). This function does not correctly handle all methods of injecting malicious HTML, leading to a cross-site scripting vulnerability under certain circumstances.

The PHP functions which Drupal provides for HTML escaping are not affected.

Private file access bypass - Moderately Critical - Drupal 7 - CVE-2017-6928

When using Drupal's private file system, Drupal will check to make sure a user has access to a file before allowing the user to view or download it. This check fails under certain conditions in which one module is trying to grant access to the file and another is trying to deny it, leading to an access bypass vulnerability.

This vulnerability is mitigated by the fact that it only occurs for unusual site configurations.

jQuery vulnerability with untrusted domains - Moderately Critical - Drupal 7 - CVE-2017-6929

A jQuery cross site scripting vulnerability is present when making Ajax requests to untrusted domains. This vulnerability is mitigated by the fact that it requires contributed or custom modules in order to exploit.

For Drupal 8, this vulnerability was already fixed in Drupal 8.4.0 in the Drupal core upgrade to jQuery 3. For Drupal 7, it is fixed in the current release (Drupal 7.57) for jQuery 1.4.4 (the version that ships with Drupal 7 core) as well as for other newer versions of jQuery that might be used on the site, for example using the jQuery Update module.

Language fallback can be incorrect on multilingual sites with node access restrictions - Moderately Critical - Drupal 8 - CVE-2017-6930

When using node access controls with a multilingual site, Drupal marks the untranslated version of a node as the default fallback for access queries. This fallback is used for languages that do not yet have a translated version of the created node. This can result in an access bypass vulnerability.

This issue is mitigated by the fact that it only applies to sites that a) use the Content Translation module; and b) use a node access module such as Domain Access which implement hook_node_access_records().

Note that the update will mark the node access tables as needing a rebuild, which will take a long time on sites with a large number of nodes.

Settings Tray access bypass - Moderately Critical - Drupal 8 - CVE-2017-6931

The Settings Tray module has a vulnerability that allows users to update certain data that they do not have the permissions for.

If you have implemented a Settings Tray form in contrib or a custom module, the correct access checks should be added. This release fixes the only two implementations in core, but does not harden against other such bypasses.

This vulnerability can be mitigated by disabling the Settings Tray module.

External link injection on 404 pages when linking to the current page - Less Critical - Drupal 7 - CVE-2017-6932

Drupal core has an external link injection vulnerability when the language switcher block is used. A similar vulnerability exists in various custom and contributed modules. This vulnerability could allow an attacker to trick users into unwillingly navigating to an external site.

Solution: 

Install the latest version:

Reported By: 
  • Comment reply form allows access to restricted content - Critical - Drupal 8
  • JavaScript cross-site scripting prevention is incomplete - Critical - Drupal 7 and Drupal 8)
  • Private file access bypass - Moderately Critical - Drupal 7
  • jQuery vulnerability with untrusted domains - Moderately Critical - Drupal 7
  • Language fallback can be incorrect on multilingual sites with node access restrictions - Moderately Critical - Drupal 8
  • Settings Tray access bypass - Moderately Critical - Drupal 8
  • External link injection on 404 pages when linking to the current page - Less Critical - Drupal 7
Fixed By: 
Categories: CMS

4 Ways to Build a Lasting Relationship with Your Customers

PrestaShop - Wed, 02/21/2018 - 04:19
Whether you’re a marketing rookie or a master, you already have one powerful tool at your disposal: your brain.
Categories: E-commerce

Why You Should Join the 7.1 Community Beta Program

Liferay - Tue, 02/20/2018 - 23:32

So Jamie just announced the new Liferay 7.1 Community Beta Program here: https://community.liferay.com/news/liferay-7-1-community-beta-program/

I recommend everyone who has working code in Liferay 7.0 or Liferay DXP should join the 7.1 beta sooner rather than later.

Why? Well, mostly because Liferay's engineering team is focused on the 7.1 release, so anything that you find in beta, well that will be something that they will want to fix before release. Without those bug reports, some incompatibility that you encounter later on falls under the regular release process and that will only work against your release schedule.

Let's say, for example, that you have spent time building out a comprehensive audit solution for your Liferay 7.0/DXP environment where you have a slew of model listeners and a custom output mechanism to route the audit details to an ElasticSearch instance that you report on using Kibana. You've got a decent investment in your auditing solution, one that you plan on leveraging in 7.1 on.

You're basically looking at two choices.  Choice #1 is to do nothing; wait for the official 7.1 GA to come out and for your organization to decide it is time to consider an update to 7.1. Now I can't predict what might be part of 7.1, but let's argue that it has one or more bugs related to the audit mechanisms.  Perhaps the model listeners registration has changed or the audit messages are broken or the output mechanism isn't invoked consistently, ... I don't know, some sort of bug that maybe could have been caught sooner but ended up getting by. But now that you're looking at the upgrade, you've found the bug and want to report it. That's fine, Liferay wants you to report bugs, but at the time you've found it 7.1 is out and fixing the bug ends up becoming part of the release process.

Choice #2 is to join the Beta program. Now you dedicate a little bit of time to test your code under 7.1 before it goes out and you find and report the issue. Now Liferay has this list of things that they want to knock out for the first GA, so your report becomes one of many that Liferay really wants to deal with for a solid initial release. Your bug gets dealt with before it can impact your own upgrade schedule, and this actually helps you from the early reporting.

So please, please, please sign up for the 7.1 beta program.

Get the 7.1 beta and beat on it as much as you can.

Run the DB upgrade against your current database. Update and deploy your custom modules, make sure features, functionality and APIs are still there that you depend on. Point your load test tool at your instance and see if you have a measurable difference in performance or capacity vs your current environment.

Just bring it. Find and report the problems.

Together we can make the next release one of the best ever, all that's missing is you.

David H Nebinger 2018-02-21T04:32:04Z
Categories: CMS, ECM

User Guide documentation sprint to happen remotely, March 22nd/23rd/24th

CiviCRM - Tue, 02/20/2018 - 17:35

The Documentation Working Group is planning a remote sprint to improve content in the User Guide. Everyone is invited to participate! Experience editing our docs will be helpful but not required.

Sign up to join this sprint

Categories: CRM

Creating Consistent User Experiences with Liferay Adaptive Media

Liferay - Tue, 02/20/2018 - 11:53

The average web page is far larger in size and more complex in its programming than it has ever been before. Today, businesses across all industries are using images, video and interactive capabilities more and more to help create better user experiences. In addition, there are countless types of devices being used to access the internet, creating a complex interface that changes the user experience from person to person.

Beyond the complexity of websites, individual web pages are steadily growing in size thanks to the many elements commonly used in each. These elements have increased the average total web page size from 702 KB in November 2010 to 3.3 MB in September 2017, according to HTTP Archive. This means that the average size has multiplied by approximately five times in seven years.

It isn’t just web pages increasing in size and devices multiplying in number that can cause such a wide disparity in user experience. More countries than ever have a large portion of their populations accessing the internet. However, the average bandwidth in each country can vary greatly, leading to even more variations in user experience. Differences in devices mean that navigation menus, text size, image placement, white space and more will change to suit the specific dimensions of various screens. In addition, the increasing size of web pages and large differences in bandwidth can cause sites to load slowly and frustrate visitors, or even fail to load various elements at all. Without great UX strategies that take these factors into account and plan for them through detailed programming, it can be difficult for companies to properly reach their target audiences.

As such, Liferay Adaptive Media has been created to address these needs and improve a company’s omnichannel strategy and behind-the-scenes performance.

Optimizing for Great User Experience

Video has made the largest gains in accounting for the size of web pages during the last seven years, with images still accounting for the majority of data, as seen in the charts below.

However, while video is taking up a great portion of data, images are accounting for more data than ever. As seen below, while the average number of images has stayed relatively the same across the years, the average image size is steadily increasing.

According to statistics from Kissmetrics, nearly half of web users expect a website to load in two seconds or less. Should the site not load in three seconds, then they are likely to abandon it. In addition, 79% of those polled said that they would not return again to a site with performance issues. These online factors influence the bottom line of every company and illustrate the importance of creating an online experience that performs well for a wide variety of users under many different circumstances.

As page data continues to grow, businesses must take steps to prevent complications from negatively affecting their user experience due to device specification, bandwidth and more, while still providing a pleasing modern user experience.

Taking Control of User Experience

A well-constructed user experience that conforms to the unique circumstances of users can benefit many different audiences. Liferay Adaptive Media can help:

  • Portal Administrators: Define media resolutions that will be used to process and serve uploaded images according to the characteristics of the accessing device (screen size, bandwidth and processing capacity).
  • Content Creators: Upload media and create new pages of content without needing to worry about their appearance being negatively impacted by varying screen sizes and devices, with Adaptive Media transparently working in the background.
  • End Users: Enjoy an improved experience by consuming images that best fit to their devices and Internet connection.
  • Developers: Easily integrate Adaptive Media in their apps to support different media qualities.
Improve Your UX with Liferay Adaptive Media

The Liferay Adaptive Media app help programmers combat the complications caused by large page sizes and variations in device layouts, with features including:

  • Core integration with documents and media
  • Optional integration with blogs and web content
  • Compatibility layer removing the need to modify old content
  • Resizing images stored in Liferay to certain image resolutions
  • Reducing page size and improving loading speed based on device and bandwidth
  • Applying these changes automatically to end users without individual programming

Adaptive Media helps Liferay DXP users create experiences that are tailored to their customers, wherever they are, regardless of device.

Improve User Experience with Liferay Adaptive Media

Find out if Liferay Adaptive Media is right for you and see how you can tailor image quality in order to provide the best user experience possible.

Learn More About Liferay Adaptive Media   Matthew Draper 2018-02-20T16:53:28Z
Categories: CMS, ECM

Meet Jimmy, Ambassador of the month | February 2018

PrestaShop - Tue, 02/20/2018 - 11:33
Jimmy joined the Ambassador Program in August 2017 and he is our first Ambassador in Hong Kong. We are happy to have him among us, and we thank him for his dedication to PrestaShop.
Categories: E-commerce

Liferay 7.1 Community Beta Program

Liferay - Mon, 02/19/2018 - 19:12
Welcome to the Liferay 7.1 Community Beta Program!     During the Liferay 7.0 development cycle we launched the Community Expedition program.  With over 600 participants this was one of our largest and most successful community programs to date.  It is in large thanks to our awesome community who was instrumental in the success of Liferay Portal 7.0.     It is with great pleasure that I announce our next community initiative: Liferay 7.1 Community Beta Program.  The main goal for this program is to ensure that Liferay 7.1 meets your expectations by giving you the opportunity to provide vital feedback and bug reports during the duration of the 7.1 testing cycle.  The program will once again be hosted on the Liferay Developer Network and is scheduled to begin in early March.   Why participate? Besides the gratitude you’ll receive from the Liferay Community (and the Liferay QA, Engineering, and Release teams), other reasons to join include:
  • Get a heads up on new features in Liferay 7.1.
  • Help test your upgrade to make sure everything works as smooth as possible.
  • Engage other members of the community (including Liferay staffers).
  • Gain credit towards the Liferay Top Contributor award.
  • Receive a small token of our appreciation for your efforts.
Joining the Community Beta Program The Liferay 7.1 testing cycle will begin with the first Alpha release of Liferay 7.1 and will conclude when GA1 is released.  This will be a shorter testing cycle then we have had previously so timing is of the essence.  What you will need to do is to download a new pre-release when it becomes available, try out the new features highlighted on the beta program site (more details soon) and provide your feedback and report bugs to Liferay.  Here’s how to sign up:  
  1. Sign up for the program.  This let’s us know more about you and what your interests and environment are.  Once we are ready to launch the program we will send a follow-up email with more instructions.
     
  2. When a new pre-release (Alpha, Beta, RC) is released, we will provide an announcement on the beta program site with any important details for the release.  Be sure to download the pre-release and provide feedback and bug reports in the Forum on the beta program site.
     
  3. If you run into any problems or just have questions in general about the release, feel free to post in the Forum on the beta program site.
We look forward to your involvement with our community and hope that you will learn a lot about the release and meet some new faces along the way!   Now Live

Liferay 7.1  Community Beta Program is now live!! Join today:

https://dev.liferay.com/web/liferay-7.1-community-beta-program

Jamie Sammons 2018-02-20T00:12:34Z
Categories: CMS, ECM

DrupalCamp London 2-4 Mar'18

Drupal - Mon, 02/19/2018 - 14:45

The following blog was written by Drupal Association Premium Supporting Partner, DrupalCamp London.

The people surrounding Drupal have always been one of its strongest selling points; hence the motto “Come for the code, stay for the community”. We bring individuals from a multitude of backgrounds and skill sets together to push forward towards a common goal whilst supporting and helping each other. Within the community, there are a number of ways to connect to each other; both online and in person. A good way to meet in person is by attending DrupalCons and DrupalCamps.

DrupalCamps

A DrupalCamp can be similar to a DrupalCon but is on a much smaller scale. Where a ‘Con has 1,600+ attendees a ‘Camp ranges anywhere from 50-600 people. In Europe alone there were over 50 camps in 2017, including DrupalCamp London.

DrupalCamp London

DrupalCamp London brings together hundreds of people from across the globe who use, develop, design, and support the Drupal platform. It’s a chance for Drupalers from all backgrounds to meet, discuss, and engage in the Drupal community and project. DrupalCamp London is the biggest camp in Europe (followed very closely by Kiev), at ~600 people over three days. Due to its size and location, we’re able to run a wide range of sessions, keynotes, BoFs, Sprints, and activities to take part in.

What happens over the three days? Friday (CxO day)

Friday (CxO day) is primarily aimed at business leaders who provide or make use of Drupal services (i.e web development agencies, training companies, clients etc), but naturally, everyone is welcome. Throughout the day we'll have speakers talking about their experiences working with Drupal and Open Source technologies in their sector(s) or personal life. With a hot food buffet for lunch and a free drinks reception at the end of the day, you'll also have ample time to network with the other attendees.

Benefits of attending 

Benefits for CTOs, CMOs, COOs, CEOs, Technical Directors, Marketing Directors and Senior Decision Makers: 

  • Understand how leading organisations leverage the many benefits of Drupal
  • Network with similar organisations in your sector
  • Learn directly from thought leaders via specific case studies
Saturday/Sunday (Weekend event)

Over the weekend, we have 3 Keynote speakers, a choice of over 40 sessions to attend, BoF (Birds of a Feather) talks, Sprints, great lunch provided (both days) and a Saturday social. With all the activity there is something for everyone to get involved in.

Benefits of attending 

Networking 

Over 500 people attended the weekend event last year and we are expecting it to grow even more this year. Not all attendees are devs either, with a fair share of managers, designers, C-Level, and UX leads there's a great opportunity for all skill sets to interact with each other. Big brands use Drupal (MTV, Visit England, Royal.gov, Guardian, Twitter, Disney) and this is a chance to meet with people from those companies to compare notes, and learn from each other. 

Recruitment

As above, the chance to meet so many people from various skill sets is a great way to line up potential interviews and hires for any aspect of your business. At the very least you'll be able to meet interesting people for any future potential hires. 

Marketing & Raising company profile 

Attending an event with a huge turnout is a great way to meet people and talk to them about what you and your company do. Embedding your name within the tight-knit Drupal community can attract the attention of other companies. Sponsoring the camp means that your logo and additional information can be seen around the camp, in tote bags given to attendees, and online. The social and sponsors stands are the perfect chance to talk to other companies and people attending DrupalCamp, to find out how they use Drupal for their benefit. 

Learning 

DrupalCamp isn't just for Devs, over the weekend there are sessions on a broad range of topics including community & business, UX, and general site building/using Drupal. The technical topics aren’t just Drupal specific either, this gives developers (and others) the ability to learn more about general core coding concepts and methodologies. The methods and techniques learnt help with day to day development and long-term work. In addition to the planned sessions, BoF (birds of a feather) sessions, there are ad-hoc get-togethers where people can talk on any topic, allowing a free discussion to share ideas. 

Warm fuzzy feeling/giving back 

Drupal (like any open source software) wouldn't survive without the community. Camps and other events allow the members to come together and see ‘first hand’ that they’re giving back to a community that helps power their tech, maintains their interests, and enables them to make a living.

How to get involved?

It’s easy to get involved with DrupalCamp London, check us out on Twitter for updates and you can find out more about the event and buy tickets on our website.

Categories: CMS

CiviCamps in the UK, 2018!

CiviCRM - Mon, 02/19/2018 - 06:47

 

This year we will have two CiviCamps in the UK to choose from!

  • May 15th in London

  • October 5th in Manchester

Categories: CRM
Syndicate content