Release v1.29

The product team is back to releasing after a workshop-packed September, working on the ideas you submitted or voted, fixing bugs you reported, improving cosmetics and preparing for future integrations (Form).

Also, we are looking for PHP Development power!

Release v1.29 (09/10/2018)

• PLANET 2513 – Search: Remove grey slug from results
  • Following an suggestion from our New Zealand colleagues, we changed the Search results slug, making it more visually appealing by removing the grey slug that displays “POST”, “PAGE”, or “DOCUMENT”.

• PLANET 2654 – Unify breadcrumbs styling (bug fix!) 
  • A rogue coma ( , ) was appearing between tags in Search and Author Profile pages which led us to review all of our breadcrumbs and see about getting them to be more consistent across the site. Breadcrumbs look aligned across the instances with >> PAGE-TYPE * Categories/Issues * #Tags

• PLANET 2612 – Articles block: manual override functionality (bug fix!)
  • The Block: Articles was not allowing for Post types and Tags to remain disabled (in cases of “Manual Override”) when an Editor returned to the block to customise it further. Everything works fine now.

• PLANET 2615 – Tidy up buttons
  • Our Design team addressed a few misalignments and inconsistencies in our buttons. Everything is beautifully aligned now.
• PLANET 2625 –Articles block: URL from search results breaks the block (bug fix!)
  • Some funny front end things were happening in the Block: Articles if editor were to manually paste a URL to a Search results page (e.g. https://www.greenpeace.org/international/?s=&orderby=post_date&f[ctype][Post]=3&f[ptype][story]=59) in the button URL field.
• PLANET 2632 –Posts: dateline style (bug fix!) 
  • In Chrome, the dot ( . ) separating the Author name and Date tried to get away. We brought it back inline!

• PLANET 2647 – Search page: Zero results typo (bug fix!) 
  • Typo in the “Zero Results” page. Facepalm. Fix. Release.

• PLANET 2517 – Investigate how the creation of the style.css (and javascript files) can be done in the plugin instead of composer
  • Dev magic –> How to create the style.css via a plugin rather than using the composer or the CircleCI process? We scouted for a solution and found that gulp works fine to generate our css and js code.
• PLANET 2156 – Send user form data (frontend) to EN API
  • Our journey towards the integration Planet 4 < > Engaging Networks continues! In the (soon to be released) Block: Form P4 editors will be able to create advocacy pages in P4, add a Engaging Networks (or other CRM) form to their content and choose which fields to show. The integration will work in the backend as well, making sure that fields are picked up from EN (or other advocacy tool) to P4, and that submitted data from a EN form in P4 are sent and stored to Engaging Networks platform using its API.