A new improvement to the author profiles in the Handbook! Beside posts, author profile pages now also include the ideas submitted and voted by the community!

A few design improvements and bug fixes are also included.

Release v1.59 (02/07/2019)

Design and UX Improvements 🎩

  • PLANET-3613 – IdeaPush: include ideas (Post_Type=idea) in Handbook Author profile pages
    • When clicking in author names in “Handbook > Improving P4“, users are redirected to author profile pages. Apart from posts, Ideas are now also pulled out (?post_type=idea), to give proper credits to the most active community members. See Lise’s or Berit’s profiles as example.
  • PLANET-3635 – Make the Progress Bar match the Call To Action colour when the counter is inside the form block
    • The colour of the progress bar should match the one in the call to action, currently, it’s always blue (as shown in the screenshot). Check it matches the colour on campaigns too.

Bug Fixes 🐛

Analytics

  • PLANET-3617 – DataLayer event is fired even when form submission is not completed
    • DataLayer event was being fired even when form submission was not completed, situation in which it should not have been fired. The dataLayer event ‘petitionSignup’ should only be fired when the data is correctly sent to the Engaging Networks database. There should be no event fired if there’s a form submission error. This has been fixed now and DataLayer is being fired only when the submission form is completed.
  • PLANET-3618 – Encoding issues with dataLayer values (gCampaign and gBasket)
    • There was a problem with the encoding of symbols (e.g “&“) of the dataLayer values for Campaign (gCampaign) and Basket (gBasket) names. These values are defined in the pages and campaign pages backend.For example:  “Meet & Dairy” is being sent via dataLayer as Meet & amp; DairyWhy is this important?
      Data is entering with different values from the standards that were priorly defined (and that are already been used by the NROs in other websites)Desired behaviour: Special characters and symbols (e.g “&“) should be sent via dataLayer as they are seen on the backend.

Design improvements 🎨

  • PLANET-3626 – Covers block: vertical alignment of button
    •  The vertical placement of the button for the Content style of the Covers block was misaligned, causing too small space between the columns and the read more button.
  • PLANET-3631 – Columns block: vertical space sans button
    •  The vertical spacing for the No Image style of the Columns block when no button is used does not account for the absence
      of buttons.
  • PLANET-3656 – Blocks update command: rename fields
    • Renamed the fields in the commands to make it clear to web admins the results of the automatic upgrade (see Snapshot below)

Content

  • PLANET-3654 – Articles Block behaving differently in Custom Tag pages
    • Article block “post Type” filters do not behave correct in custom #tag pages. Clicking on the Page itself filters behave correctly, but when accessing the same page via #Tag they do not.
    • In the images below, the Articles block should pull our “Stories” only, this happens when the Page is accessed directly (via url), but not when accessed via Taxonomy (Clicking on #Tag).

Article block back end

Custom developed page

Tag page

  • PLANET-3666 – Articles block: load more button not loading results
    • EN block form was breaking the articles block on one of the P4 instances. When clicking on the load more button in the articles block, more results were not displayed in the front end on desktop. On mobile, more results are loaded. This bug has been fixed and load more button works in all situations.

Geek alert

(this section is dedicated to developers or web editors with advanced tech knowledge)

  • PLANET-3718 – Fix notice level error of login_headertitle deprecated function
    • Fix notice error on P4 admin login page -`Notice: login_headertitle is deprecated since version 5.2.0! Use login_headertext instead. Usage of the title attribute on the login logo is not recommended for accessibility reasons. Use the link text instead. in /app/source/public/wp-includes/functions.php on line 4711`
Block: Form (Engaging Networks)

Insert Call to Action in your P4 pages and send data to your Engaging Networks account

Learn more