You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
Using a legacy viewer, create a new sky & save it with the name: Whirly 1.0 (or any name that includes the . character.
Observe the windlight sky xml file is saved on your computer with the name Whirly%201%2E0.xml
The dot (.) is encoded as %2E
I attached an example windlight sky file to this issue named Whirly%201%2E0.xml to save you doing the above steps.
On an EEP viewer, create a new sky & edit this sky & attempt to import the Whirly%201%2E0.xml sky.
Observed Behaviour
Attempting to import the sky Whirly%201%2E0.xml into an EEP viewer will give the following error message
*Alert: Unable to import legacy Windlight settings Whirly 1.0 from \nC:
Users
Whirly
Desktop
Whirly%201%2E0.xml.\n\nMissingString(SettingImportFileError)
See attached image.
Bug will reproduce no matter the path that the sky xml file is located.
Bug will reproduce for all windlight xml imports that contain %2E in the name.
Expected Behaviour
User should be able to import windlight xml that have %2E (the . character) in their name.
Other information
Bug reproduces on latest EEP nightly: Second Life Release 6.2.2.526976 (64bit)
Bug reproduces on the current EEP-RC viewer: Second Life Release 6.2.0.526104 (64bit)
Bug still reproduces on latest EEP nightly: Second Life Release 6.2.3.527370 (64bit)
[EEP] Importing certain legacy windlights give the upload error: MissingString(SettingImportFileError)
Type
Bug
Priority
Unset
Status
Closed
Resolution
Accepted
Labels
whirly-eep
Reporter
Whirly Fizzle (whirly.fizzle)
Created at
2019-05-09T14:55:53Z
Updated at
2020-06-15T15:23:24Z
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
'Date of First Response': '2019-05-09T19:23:52.183-0500',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Viewer',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'Filling in...',
'What were you doing when it happened?': '...',
'What were you expecting to happen instead?': '....',
'Where': 'Any region.',
}
The text was updated successfully, but these errors were encountered:
Forgot about this issue, sorry.
Updated now will full repro.
It doesn't matter where the xml file is located, if the xml was originally named with the . character in the file name & the . has been encoded to %2E in the name, the xml will not import.
Steps To Reproduce
Using a legacy viewer, create a new sky & save it with the name: Whirly 1.0 (or any name that includes the . character.
Observe the windlight sky xml file is saved on your computer with the name Whirly%201%2E0.xml
The dot (.) is encoded as %2E
I attached an example windlight sky file to this issue named Whirly%201%2E0.xml to save you doing the above steps.
On an EEP viewer, create a new sky & edit this sky & attempt to import the Whirly%201%2E0.xml sky.
Observed Behaviour
Attempting to import the sky Whirly%201%2E0.xml into an EEP viewer will give the following error message
*Alert: Unable to import legacy Windlight settings Whirly 1.0 from \nC:
Users
Whirly
Desktop
Whirly%201%2E0.xml.\n\nMissingString(SettingImportFileError)
See attached image.
Bug will reproduce no matter the path that the sky xml file is located.
Bug will reproduce for all windlight xml imports that contain %2E in the name.
Expected Behaviour
User should be able to import windlight xml that have %2E (the . character) in their name.
Other information
Bug reproduces on latest EEP nightly: Second Life Release 6.2.2.526976 (64bit)
Bug reproduces on the current EEP-RC viewer: Second Life Release 6.2.0.526104 (64bit)
Bug still reproduces on latest EEP nightly: Second Life Release 6.2.3.527370 (64bit)
Attachments
Original Jira Fields
The text was updated successfully, but these errors were encountered: