Releases: gigya/wordpress
Releases · gigya/wordpress
6.5.0
Changes
- Changed package name to gigya/gigya-wordpress (!) for more practical automated installation
- Graceful failure when Composer dependencies have not been installed
6.4.0
Changes:
- It is now possible to control internal SAP CDC plugin logging, regardless of the debug level set in WordPress. Logs are written to a separate internal log file.
6.3.0
Changes
- Improved validation in the field mapping configuration, so that it is now possible to catch non-existent fields and other issues at the configuration stage
- Fixed an issue where actions added by the plugin could not be overridden
- Fixed a possible login issue when using private/public key pair authentication
6.2.0
Changes
- Added a report that can be generated to find out which users are not synchronized between WordPress and SAP CDC
- Added a configuration option for user verification by UID only (recommended)
- Fixed an issue when the Override WordPress Link option was unchecked
6.1.1
Changes:
- Updated CN data center host name
- Fixed possible PHP notices/warnings in the admin UI
6.1.0
Changes:
- Removed social features deprecated in SAP CDC, such as comments, game mechanics, share UI, etc.
If you are still using these features, they will stop working even in prior versions of the plugin! Please contact SAP CDC support for more information.
6.0.3
Changes:
- Fixed JavaScript loading from SAP CDN not under gigya.com domains
- SAP JavaScript is now only retrieved via HTTPS
- Added a new way to install SAP CDC plugin with Composer (contrib. Alexisferat)
6.0.2
Changes:
- Removed RSA private key format validation to allow additional PK formats supported by SAP CDC
6.0.1
Changes:
- Fixed a logout issue with dynamic session
- Changed all admin calls to SAP CDC to use HTTPS by default
- Added environment information to additional SAP CDC calls for better debugging
5.11.1
Changes:
- Changed all admin calls to SAP CDC to use HTTPS by default