Minor updates and code changes occur every day. Only significant or noteworthy updates are shown here. Updates shown with a gold background are (or were at the time) only available to Advanced HOPS members.

You are NOT currently subscribed to HOPS compliance system updates. More info

You are NOT currently subscribed to HOPS retail system updates. More info

Search: Clear

Time Date	System Updates
Update 1323 31 October 2025	Important - Chrome Updates Affecting POS Hello A recent Chrome update is having an effect on POS devies. Starting in Chrome version 142, Chrome now prompts users for permission to access devices on the local network. Chrome 142 started rollout on October 28, and will roll out to all Chrome users over the next two weeks. Stripe Terminal's JS SDK, which is used by HOPS POS for communication with Stripe card machines through the local network, requires this permission to be granted. This means that, when prompted, the user needs to ALLOW this access; if a user blocks this access, the POS will be unable to connect to the card reader. In general, the permission is only required to be granted once. An example of the permission prompt is shown on Chrome's blog post here: https://developer.chrome.com/blog/local-network-access Simulating this issue before Chrome 142: If you have not yet upgraded to Chrome 142, IT managers can use Chrome 141 and change the chrome://flags/#local-network-access-check flag to "Enabled" to test this new requirement. This new requirement was not expected by us, and it was not expected by Stripe either. HOPS first discovered this at the first railway site affected on Thursday morning. Stripe has sent notification to all its customers today (you may have received the same information as above from Stripe). Thank you Danny Scroggins
Update 507 14 December 2018	User photos are now displayed again, and are editable (under the new permissions 323, 324) from the user profile pages as before.
Update 323 16 July 2016	A new features has been added at the bottom of the timetables editing page to advise users of the update (or addition). There is also the opportunity to write a message describing the change that you have made. The message will be sent to users with permission 232, so assign that permission to the groups who 'need to know' (ie, roster clerks, operations managers, etc). (I suggest you don't put your entire staff on the distribution list...!)