Releases for Optimizely

2018 Apr 08 - 8.x-3.1

- Fixed: Issue #2958572 by Watergate: Out of memory exception on Windows

- Fixed: Issue #2913679: Error message for duplicate project code does not replace variables

2017 May 25 - 8.x-1.4

- Cleaned up code to Drupal coding standards

- Fixed: Issue 2847940 by nehakhadke: Remove @file tag docblock from all the .php files

2016 Nov 02 - 8.x-1.0

- Implemented cache invalidation of pages via cache tags.
- Fixed: Issue #2823398: Invalid use of * should be rejected.
- Added leading slash / to paths if slash is missing.
- Refactoring, formatting, and other minor changes.

2016 Aug 26 - 8.x-2.17-0.0

- Tested to work under Drupal 8.0.0.
- No code changes.

- Updated to work under Drupal 8, RC 1.
- Removed all calls to SafeMarkup::checkPlain().
- hook_install() - set default language for langcode key.
- hook_uninstall() - delete all variables stored by the module.

- Tested to work under Drupal 8, beta 14.
- No code changes.

Maintenance release:

- Issue #2584933: Optimizely suggests no protocol in HTML snippet by dremy
- Issue #2577193: Increase Optimizely Snippet's Load Priority by SeeWatson
- Issue #2564383: Unable to save Url with parameters by richardcanoe

- Started cleanup of code formatting as suggested by SeeWatson in issue #2581409

- Updated to work under Drupal 8, beta 12.

- AliasManager methods require paths with leading slash.
- Removed _format property in route definition for ajax call.
- In several Testing cases, added leading slash to paths.

- Tested to work under Drupal 8, beta 10.
- No code changes.

* Updated to work under Drupal 8, beta 6.

- Changed code to get a mutable config object (default is immutable).

Issue 2382447 fixed by alexweber
- adjust parameters used by drupal_add_js() to use values specific to Drupal 6.

- Updated to work under Drupal 8, beta 1.
- Replaced functions url() and l() with D8 equivalents.
- Replaced use of hook_permission() with permissions.yml file.

- Updated for Drupal 8, alpha 14.
- Added check to prevent deletion of default project.
- Confirmed correct display of error msg with path such as <back>.

- Issue: 2330675 - Broken links on Account Info tab
Link to Optimizely site to purchase upgrade to Optimizely was broken.
Applied patch supplied by tz_earl
- Issue: 2324367 - Remove unnecessary .DS_Store files
Applied patch supplied by tz_earl
- Issue: 2323041 - OptimizelyTestPageSnippetTestCase fails in multiple ways.
Didin't apply patch as related code was fixed / enhanced but still provided
commit credit as the solution was still helpful. Applied patch supplied by tz_earl

2014 -Aug-11

8.x-2.14-beta1

- First release of version 7.x-2.14 converted to work under Drupal 8, alpha 13.

- Tested in two environments:
Linux Mint 16, Apache 2.4, PHP 5.5, MySQL 5.5
Windows 7, Apache 2.2, PHP 5.4, MySQL 5.6.11

- Known issue: clearing of caches when projects are modified is often done sitewide rather than being done more selectively on particular subpaths. This could cause a sitewide performance hit.

- Issue: 2303917 - Default project can be deleted with manual url
Added check and related "Default project can not be deleted." error message
to prevent project ID 1 from being sent to delete functionality.
- Issue: 2304545 - Path not displayed in error messages
Added htmlentities formatting to path values when displaying errors.
- Issue 2306399 - Warning: Illegal string offset '#value'
Removed ['#value'] in 'project-row-' . $element[$key]['#project_code']['#value']
and $element[$key]['#oid']['#value'].

Fixed weird git merge issues that resulted in messed up files.

- Bug fix: Check for unique wildcard paths "*" in either existing oe the addition of projects was not validating correctly
- Bug fix: Check for valid paths that included wildcards "*" not validating correctly
- Bug fix: Logic in hook_init function not supporting wildcards "*"
- Bug fix: Added support for parameters in project paths
- Bug Fix: Added check for unique path within new project path submission
- Bug fix: Prevented Default project from being enabled from the project listing page when the project ID / Optimizely account ID is not set.
- Added support for complete alias lookups when adding / editing project paths to all for entries using both alias and source values
- Added support for https (secure pages) to Optimizely snippet calls
- Added path alias details to project listing when path setting is < front >, includes the display of the actual path to < front >
- Added support for < front > to also check related alias and source values
- Added support for parameters "?" in project path setting
- Added support for optional slave data base connections on SELECT queries to help performance
- Removed project setting validation to allow more than one project entry using the default project ID - regression from previous 2.1x version

• Removed unused page cache clearing function, now using drupal_match_path() for all path logic
• Fixed validation of project entries to force unique project code values.
• Allow second project entry when using the Optimizely account ID over ride the default project entry.

Minor bug fixes.

Official production release:

• A default project entry always exists that when the Optimizely account ID is added to the module configuration page will allow the basic Optimizely project javascript file to be applied site wide. The default entry can be disabled. This provides the basic functionality of the 7.x-1.x module.
• Support for multiple project / experiment entries. Prevention of duplicate project entries by Optimizely project ID with the exception of the default entry that uses the account ID for the initial javascript call. A duplicate entry in this case can be made to allow for settings to be applied to a project entry using the default account ID while disabling the default project entry.
• Each Project entry has settings to include or exclude paths pointing to a related Optimizely javascript file.
• Each Project entry can be enabled or disabled allowing project entries (settings) to persist and enabled /disabled as desired.
• Targeted Drupal page cache and Varnish cache will be refreshed with new, edited or deleted Project entries. This results in applying project javascript files to site paths immediately without the need to do a full cache clears to the whole site. An issue that high performance sites will like who are also often users of Optimizely testing.
• Basic Unit Tests