|
Issue |
Solution |
ID |
|
The performance listing shown in AVTiki gives no indication that a performance is sold out or has no availability. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
A performance availability indicator has added to AVTiki's performance listing. |
AVT-5268 |
|
AVTiki currently only adds a table column cell to each row of the performance listing if an image has been configured in the 'Logo 1' field of the Venue Configuration application Performances|Basic page. This causes a table rendering issue when some performances have logos and others do not. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
A table column cell is now rendered whether or not a an image has been configured in the Venue Configuration application Performances|Basic page's 'Logo 1' field. All table rows have a consistent number of columns. |
AVT-5337 |
When accessing AVTiki using Chrome, a JScript error occurs.
If third party cookies are not accepted (a common configuration for internet users) then a server error is being displayed instead of requesting that cookies be enabled. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
The server error no longer displays, and a proper no-cookie error message is being displayed. |
AVT-5372 |
|
Change AVTiki to render the reservation timeout value on a dynamic basis, and remove the hardcoded 1 from the seatSelect.asp and default.asp pages. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
The reservation timeout value is rendered dynamically. The hardcoded 1 has been removed from the default.asp and seatSelect.asp pages, and the default value of the Registry application Registry::Application::Tiki::Messages node 'reservation timeout interval' field is 1 hour(s). |
AVT-5373 |
Like gates can be bypassed.
When users arrive at a performance via a search, they can purchase tickets without having Liked the AVTiki page. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
Users cannot purchase tickets without Liking the page.
 |
Hint
It is recommeneded that you do not put links to the default.asp page in the 'Default Header' of the primary article. It just links you to the page you are on anyway. |
|
AVT-5777 |
|
Change AVTiki to display the venue 'Name' when the venue 'Description' is blank instead of the 'Performance Code'. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
AVTiki now displays the venue 'Name' when the venue 'Description' is blank instead of the 'Performance Code'. |
AVT-5885 |
|
When users first visit the AVTiki page, the Permission Authorization loads the same pop-up window twice. Users are then prompted to log in. Once the permissions have been authorized, the window does not close. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
The permission authorization is only being submitted once. The Permission Authorization pop-up only appears once. |
AVT-5974 |
|
Even when a user is logged into an existing account, the 'Cardholder Name' and 'Bank Account Name' on the orderContacts.asp page are not being auto filled. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
The cardholder name and bank account name on the orderContacts.asp page is being pulled from the customer account instead of the order. |
AVT-6273 |
Missing branding images.
A number of images referenced in the .CSS file for AVTiki are missing. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
The the header.jpg file in the UI/FB/branding folder has been updated, and the following images have been added in the new UI/FB/branding/images folder:
-
header_background.png
-
logo_avtiki.png
-
logo_audienceview.png
-
order_info_border.png
-
order_info_background.png
|
AVT-7130 |
|
The AVTiki is referencing the default 'Page Header' article set on the Content Management application Sites|Basic page instead of the brand specific article set in the 'Header' field on the Site|Branding page. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
The article set in the 'Header' field on the Content Management application Site|Branding page overrides the value set in the 'Page Header' field on the Sites|Basic page. |
AVT-7150 |
|
If Google Analytics is enabled on the Content Management application Site|Applications page, a 500 error occurs when customers are completing an order. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
The 500 error no longer occurs on the viewOrders.asp page, and order can be completed successfully. |
AVT-7490 |
|
The 'Delivery Method Charges' are not reflected in the 'Order Total'. When there are two delivery methods, one with a charge and the other without, and the user switches between the two available delivery methods, the grand total does not automatically update. The charge and fee display when a payment method is selected. |
This has been corrected in AudienceView 6.3.0 HotFix 5.
The page now refreshes page when the user switches between delivery methods, and the applicable charges are calculated and displayed correctly. |
AVT-7605 |