Known Issues
Current Issues
Add/Edit Artist - Role/Character fields displayed regardless
Issue
Regardless of the combination of the union/role selections, the 'Character' field is displayed. Should it be labelled 'Character/Description' and be enabled/disabled depending on what union/role is selected?
At the moment, the fields purpose feels some what ambiguous.
Found in version 1.x.x (June 2023).
Programme delivery form item status is not correct
Issue
It was found that despite not having provided presentation requirements, content advice phrases, advertising data and contributor data for an episode of a series, the programme delivery form suggested that these had been completed.
Users must therefore be aware that they may be allowed to complete the form despite not all requirements for completion being met. This could result in S4C refusing the programme delivery form bundle.
Advice
Manually check that you have submitted everything required of you before completing the programme delivery form.
Found in version 1.x.x (June 2023).
Changing artist contract type can yield strange results
Issue
Attempting to change the contract type of an artist is likely to fail with unpredictable results and as such should be avoided.
Advice
If you need to change the contract type of an artist, you are advised to delete the existing entry and recreate it from scratch. This will of course require the recreation of the links between the artist and episodes in the case of a series.
Found in version 1.x.x (June 2023).
In Test
Possibility for user data to be exposed
Issue
Internally, the PAC server application used the same data structure to store information about the logged in user (during the log-in process) and the user being edited/created. As the amount of data required about the logged in user expanded, and it's lifetime was extended, there was a possibility this data could leak into the pages seen by users.
Fixed - June 2023
Internal changes have been made that separate the two uses into two different structures, thereby completely removing the possibility that details of the logged in user could leak into pages seen by users.
Found in version 1.x.x (June 2023). Fixed in version 2.0.0.
Sometimes the navigation tree doesn't scroll
Issue
The navigation tree is supposed to scroll so the item being opened is in view (this functionality was added in this version). For the majority of the time, this works as expected and the item is scrolled into view correctly, but some times this fails, resulting in the tree being redrawn and staying at the top of the page.
Fixed - June 2023
The fix was to change how the scrolling was achieved. In the original version, it was done by the draw script after it had dropped the updated HTML into the DOM. At that point, there was no guarantee the document had been processed and fully loaded. So, the scroll to element code has basically been moved into the onload handler of the tree document. That way, it's guaranteed to be executed when the document has been fully loaded. Initial tests seem to indicate it's working fine, so we'll have to see if the glitchy behaviour still occurs.
Found in version 2.0.0 (June 2023). Fixed in version 2.0.0.
User sessions could be hijacked by a bad actor
Issue
There is no proper validation of user sessions, therefore it is possible for sessions to be hijacked by a bad actor.
Fixed - June 2023
Found in version 1.x.x (June 2023). Fixed in version 2.0.0.
Fixed Issues
Navigation tree does not entirely switch language
Issue
If a user configured to use Welsh, switches to English, whilst the navigation tree will appear to reload and on some level will appear to be entirely in English, due to how some parts of the text are provided they will continue to be in Welsh.
The same issue manifests when an English user switches to Welsh.
Fixed - June 2023
All instances where this has been found to be a problem have been updated to use a language code passed into the data source.
Found in version 2.0.0 (June 2023). Fixed in version 2.0.0.
Changing username without updating password will lock the user out
Issue
If a users login name is updated and their password is not changed at the same time, they will no longer be able to login. The security enhancements introduced to prevent passwords being stored as plain text use the username as part of the process and as such, the secure password is dependent on their username. If the username is changed, all future attempts to validate the password against the one stored in the database will fail.
Fixed - June 2023
Usernames can now be changed without having to update the users password.
Found in version 2.0.0 (June 2023). Fixed in version 2.0.0.
Presentation requirements information not saved correctly
Issue
The multiline edit field on the Presentation Requirements form is not saved correctly if it contains multiple lines that have been seperated using a carriage return (i.e. the user has pressed
Fixed - April 2024
Changes have been made to the server software to correctly handle the incoming data to ensure that all lines are saved. It should be noted that this issue was not limited to this one field and that the fix addresses the issue for any multi-line field
Found in version 1.x (March 2024). Fixed in version 2.0.0.
Forms using multiple checkboxes fail to save all selected items
Issue
Forms that use multiple checkboxes (add episodes to contributor, add episodes to artists and grant rights to freelance users) are not saving all selected items properly, with only the last items being used for the saving process
Fixed - June 2024
Changes have been made to the server software to correctly handle the incoming data to ensure that all selected items are properly processed
Found in version 2.0.0 (June 2024). Fixed in version 2.0.1.
Password reset facility allows users without email addresses to try resetting their password
Issue
The password reset process requires a user to have an email address (to which the verificatio email can be sent). Many users (such as the admin users for each production company) do not have email addresses but the system still allowed them to try and reset their password
Fixed - June 2024
The reset process has been updated to detect and report the lack of an email address, giving clear guidance to users as to how to proceeed
Found in version 2.0.0 (June 2024). Fixed in version 2.0.1.