Author: Cameron Terry

Posted on

WordPress Cluster 6.14.1

  • Updated Must-Use Plugins;
    • Removed the previous Google Tag Manager tracking code for the WordPress Admin area.
    • This will conflict with the new Analytics must-use plugin.
  • New Must-Use Plugins;
    • Analytics (WordPress Cluster 1.0.0)
      • Provides a unified action so future enhancements do not specify hooks for admin_head, login_head, and wp_head.
      • Added the Google Analytics tracking code for WordPress Cluster as a whole.
        • This is namespaced to avoid collisions with other Google Analytics code on our sites (PA content, site-specific and, rarely, advertising.)

Post Deployment Notes

The release needs coordinate with Chris Kelly to remove the previous implementation on Google Tag Manager.

PR : https://github.com/dc-thomson/wordpress/pull/976

Posted on

Wave FM 1.0.0 Beta 3

  • Added a database upgrade mechanism to Wave FM theme.
  • Added integration for accepting information provided by Zetta feeds.
  • Adds an endpoint to the /stations/ posts which can be used to POST data to for the latest song information.
    • Checks to make sure the radio station exists.
    • This expects the following fields to be provided;
      • Artist
      • Song Name
      • Run Time (Song Length)
  • Modified the admin screen for Stations to display the Zetta feed link for ease of management.
  • Provides a template tag –
    wavefm_zetta_playing_now( $station, $echo )

    – which returns / echoes the currently playing or most recently played song for a given radio station.

Post Deployment Steps

Once this is deployed, the RCS Glue software needs to be updated. This is done by using TeamViewer, which Marc O’Neill currently has the credentials and access to.

Once on this server, the Glue service configuration needs to be updated in two settings specifically; HttpPostLocation and HttpPostFormat. Therefore the following needs to be updated.

For note; the pipe symbol (|) is used to denote different services to be contacted by the configuration.

HttpPostLocation

// Before
HttpPostLocation=http://wave.nwm.xrad.io/wp-content/wave102/in/now_playing_in.php|http://platform.g-media.com/api/postplayingdata.php?id=59|http://air.radiotime.com/Playing.ashx

// After
HttpPostLocation=http://wave.nwm.xrad.io/wp-content/wave102/in/now_playing_in.php|http://platform.g-media.com/api/postplayingdata.php?id=59|http://air.radiotime.com/Playing.ashx|https://wpcluster.dctdigital.com/wavefm/stations/wavefm/zetta/

HttpPostFormat

// Before
HttpPostFormat=artist=%SNGART%&title=%SNGTIT%&runtime=%RUNTIME%&password=wavepass|xml=%XML%&password=QD5sEg47XuV55FQ|partnerId=8UvDSnRz&partnerKey=2UH1Dm!uyM7J&id=s45554&title=%SNGTIT%&artist=%SNGART%

// After
HttpPostFormat=artist=%SNGART%&title=%SNGTIT%&runtime=%RUNTIME%&password=wavepass|xml=%XML%&password=QD5sEg47XuV55FQ|partnerId=8UvDSnRz&partnerKey=2UH1Dm!uyM7J&id=s45554&title=%SNGTIT%&artist=%SNGART%|artist=%SNGART%&title=%SNGTIT%&runtime=%RUNTIME%&password=wavepass

PR :

Posted on

Scots Magazine 3.1.0

  • Removed custom_style.php override as Selkie+ 1.2.0 no longer uses it.
  • Adjusted Scots Magazine’s custom CSS for primary colour to make use of the filters provided by WPC Customizer CSS Render implementation.
  • Deleted header.php template as the Scots Magazine specific functionality has been moved in to the new mast-head.php template part.
  • Fixed a bug with SM_ROOT using the wrong function to get the theme directory.

PR : https://github.com/dc-thomson/wordpress/pull/944

Posted on

Selkie+ 1.2.0

  • Created a new template part called “mast-head”.
    • This makes it easier for child themes to change the mast head portion of the website without having to inherit the entirety of header.php in the process.
    • This means that functionality attached to the wp_head action are now left alone.
  • Refactored the Customizer controls to make use of the new WPC Customizer Manager functionality.
  • Now uses the new /customizer.css dynamic stylesheet.
    • The old mechanism – custom_style.php – which outputted a <style> tag in the <head> is now deleted.
  • Reorganised the Customizer setup in to its own folder and split up the different sections in to different files.
  • Introduced a collection of actions and filters for child themes to override and change the setup of Settings, Sections and Controls of Selkie+’s Customizer setup.
    • New Actions
      • selkie_plus_customizer_breadcrumb_colours_register
      • selkie_plus_customizer_button_colours_register
      • selkie_plus_customizer_colours_register
      • selkie_plus_customizer_cta_register
      • selkie_plus_customizer_fonts_register
      • selkie_plus_customizer_footer_colours_register
      • selkie_plus_customizer_header_colours_register
    • New Filters 
      • selkie_plus_customizer_breadcrumb_colours_settings
      • selkie_plus_customizer_button_colours_settings
      • selkie_plus_customizer_colours_settings
      • selkie_plus_customizer_cta_settings
      • selkie_plus_customizer_fonts_settings
      • selkie_plus_customizer_footer_colours_settings
      • selkie_plus_customizer_header_colours_settings
  • Maintained backward compatibility with the previous Customizer implementation.
  • Remove the in-line style for <header> tag background colour and moved it in to the new Customizer CSS functionality.
  • Fixed a number of instants where the localisation was missing or not specifying the text domain correctly or at all.

PR : https://github.com/dc-thomson/wordpress/pull/944

Posted on

WordPress Cluster 6.12.5

  • Must-Use Plugins updated;
    • Customizer (WordPress Cluster) to 1.1.1;
      • Addressing deficiencies and issues which came out of
      • When SCRIPT_DEBUG is set to true, the stylesheet will now put a CSS comment above the CSS selectors stating which setting it belongs to.
        • You will now see – /** CSS for “background_color”. */ – in the customizer.css stylesheet.
      • Reworked the check on CSS rules for a new filter that enables developers to use more esoteric CSS for a setting.
        • Useful for Fonts and / or Media Queries.
      • Added a new filter wpc_customizer_{setting id}_css_output which allows for the inclusion of custom CSS for a setting, which may or may not include CSS rules through the WPC Customizer Settings class.

PR : https://github.com/dc-thomson/wordpress/pull/939

Posted on

WordPress Cluster 6.12.2

  • Updated Must-Use Plugins;
    • Customizer (WordPress Cluster) 1.0.1
      • Fixed a deficiency in the CSS property handling, where it could not handle multi-valued properties like “border” which needs the default value as part of the string.
        • This means you can now specify a CSS property value like “1px solid %1$s”.
      • Fixed an issue where the CSS variable passed through the filter was not actually getting used in WPC_Customizer_Setting.
      • Customizer stylesheet changes.
        • Now includes a more sensible and cache ready version number which will update when one of the following changes occurs, covering both deploys and user behaviour.
          • WPC Customizer version number changes.
          • Theme version number.
          • Parent (if applicable) version number.
          • If the user makes changes and publishes them through the Customizer Admin UI.
        • Now includes an additional comment block which outputs the version number of the theme (and parent, if applicable), which can be used for debugging a caching issue on production.
        • Made a few tweaks to the CSS rendering process to ensure that it no longer spits out blank CSS lines for settings which have no CSS rules.
      • Added a new hook – wpc_customizer_css_after_render – which allows developers to handle more esoteric CSS needs with Customizer controls outside the WPC_Customizer_Setting implementation.

PR : https://github.com/dc-thomson/wordpress/pull/931

Posted on

WordPress Cluster 6.12.0

  • New Must-Use Plugins;
    • Customizer (WordPress Cluster) 1.0.0
      • A new mechanism to make handling Customizer settings with corresponding CSS easier to manage.
      • Produces a dynamic CSS file rather than forcing theme developers to include a <style> tag in the header. As currently implemented on a number of themes.
        • This is registered as style – wpc-customizer – and can be set as a dependency against the main stylesheet.
      • Providers a helper function which access the setting and handles the retrieval of the value or default value.
      • Please Note; this is the first iteration and mileage may vary.

PR : https://github.com/dc-thomson/wordpress/pull/924