Skip to content

Releases: sailthru/sailthru-wordpress-plugin

Add Spider Option for Content API + Content Settings Page Rename Fields

15 Jul 21:15
2b70b32
Compare
Choose a tag to compare

Added option for users to change Spider value in Content API calls (defaults to enabled)
Renamed Global Vars to Custom Fields and updated helper text on Content Settings page

Fix: Do Not Include Scout Generated Pages for Non-Horizon Users

01 Jul 22:04
4b644a3
Compare
Choose a tag to compare

Fixed bug where “Scout from Sailthru” page was created for all sites, rather than just Scout-enabled sites.

Fix: Initialize Sailthru once page is entirely done loading

07 Apr 21:17
91e79e4
Compare
Choose a tag to compare

Fixed bug where Sailthru onsite JS would sometimes fail to initialize due to asynchronous loading of scripts

Fix: Load onsite JS async

26 Mar 16:25
71a1ba7
Compare
Choose a tag to compare

Fixed bug where onsite JS taking too long to load would prevent some pages from loading

Fix: Send HTTPS to Content API

18 Feb 17:59
c8e6d80
Compare
Choose a tag to compare

Fixed bug where HTTPS urls were sent to the Sailthru Content API as HTTP

Support optout status reset in Sailthru Subscribe widget

09 Jan 22:55
Compare
Choose a tag to compare

Enable the option to reset a Sailthru profile's optout status to "valid" when using the Sailthru Subscribe widget. This is supported both via the Widget menu, and via shortcode as described in changelog.md. To protect against spam, the option to secure the widget with reCaptcha is also supported. Instructions to set this up are found in the Sailthru plugin menu.

VIP: Clear cache because of 5.3 changes handling for user_activation_key being read

18 Dec 21:51
0719e94
Compare
Choose a tag to compare

WordPress 5.3 has updated the way how user_activation_key is being read. It used to be read directly from the database, but in https://core.trac.wordpress.org/changeset/45714 and https://core.trac.wordpress.org/changeset/45716 this has been updated, so it gets read from the WP_User object.

This means that any code updating the user_activation_key for a user has to properly clean the caches, otherwise the key won’t be properly read.

v3.3-beta Version

07 Sep 23:44
Compare
Choose a tag to compare
v3.3-beta Version Pre-release
Pre-release

This is beta software and should not be used in a production environment. This adds a number of new options to the UI to help customers manage their content without requiring development work.

  • Add abilility to combine WordPress tags with Sailthru interest tags via a UI setting
  • Added abilility to combine categories with Sailthru interest tags via a UI setting
  • Added ability to add any available taxonomy to Sailthru tags via the UI
  • Added a global whitelist of vars to be included in content api posts
  • Added a global tag option so a tag can be added to every post.
  • Added ability to turn on/off Content API syncing via the UI.

The final production release may introduce breaking changes to this codebase. If you find any bugs please open an issue.

v3.2.2

07 Sep 23:41
Compare
Choose a tag to compare
  • Updated sailthru_horizon_meta_tags filter to apply to Content API calls.

v3.2.1

11 May 20:11
be5ae2e
Compare
Choose a tag to compare
  • Added a filter to allow customers to override API verification in the setup process.
  • Changed ajaxurl used in widget to be namespaced to prevent collision.
  • Fixed issue whereby any error on a signup widget would render on all signup widgets on the page.
  • Added a filter to allow the localized js to be loaded in wp_footer()
  • Removed php 7.2 unsupported code. (Thanks srtfisher)
  • Added support for Page in Sailthru meta box.
  • Extended timeout for VIP API calls to 3 seconds.
  • Squished a few more bugs.