If the session container setExpirationHops() is called after a value is set, that value can be inadvertently expired. Reordered the commands so that setExpirationHops() is called first.
This seems like faulty behavior in the session container, but I might not be understanding Zend\Session completely. Regardless, this fix uses the same order of commands as the PRG plugin in master branch.
PRG Plugins fix - Lost data if expiration hops set after data is set
Merge branch 'hotfix/3019' into develop