Details
Bug
Minor
Description
The customer has responded with the steps used to reproduce the issue:
1. The user who installs the software is an admin (and local admin ofc). I.o.w.
you do a basic standard succesful installation locally on the harddisk of a
computer. Use default locations for installation folder(s).
2. You log a user with a floating profile on the PC (with a domain logon ofc,
not a local logon). Note that the user is not a local admin but given he ain't
installing anything, just running would think that should be ok.
3. When the user starts the software the following message pops
(translated from Dutch) :
"IcePDF Viewer-directory to save userdata cannot be created:
\\srghvlt-dc01\.icesoft\icepdf-viewer. Changes to the standard configuration
will not be saved."
Note that the location where the software tries to access a folder is actually
the name of the domain-logon server (\\srghvlt-dc01), and not the local user's
folder (C:\Documents and Settings\[username])
1. The user who installs the software is an admin (and local admin ofc). I.o.w.
you do a basic standard succesful installation locally on the harddisk of a
computer. Use default locations for installation folder(s).
2. You log a user with a floating profile on the PC (with a domain logon ofc,
not a local logon). Note that the user is not a local admin but given he ain't
installing anything, just running would think that should be ok.
3. When the user starts the software the following message pops
(translated from Dutch) :
"IcePDF Viewer-directory to save userdata cannot be created:
\\srghvlt-dc01\.icesoft\icepdf-viewer. Changes to the standard configuration
will not be saved."
Note that the location where the software tries to access a folder is actually
the name of the domain-logon server (\\srghvlt-dc01), and not the local user's
folder (C:\Documents and Settings\[username])
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Updated the properties managers to only show dialogues if there is s property value parsing issue when application.showLocalStorageDialogs=false. This should address the client side issues the client is seeing.
However if the properties files can't be created to do the floating profile issue or some other IO Exception then the PDF library will take slightly longer to load then if the property file values could be cashed after first launch.
Show
Patrick Corless
added a comment - Updated the properties managers to only show dialogues if there is s property value parsing issue when application.showLocalStorageDialogs=false. This should address the client side issues the client is seeing.
However if the properties files can't be created to do the floating profile issue or some other IO Exception then the PDF library will take slightly longer to load then if the property file values could be cashed after first launch.
As long as the user doesn't see any messages at all when application.showLocalStorageDialogs=false it's ok, that's all we need. Thank you very much 
Show
Jose Ortiz
added a comment - As long as the user doesn't see any messages at all when application.showLocalStorageDialogs=false it's ok, that's all we need. Thank you very much
I think there was probably some miss understanding as to how the property application.showLocalStorageDialogs should work. It appears the original code that implemented this new property went on the assumption that the end user didn't want to see the create folder directory. Where in fact I think the client wants to suppress all dialogues relate to the property classes.
The test case in question exposes other circumstances where dialogues will be shown during the properties file processing. If there are any IOEceptions when trying to create the directory and properties file the original code will report the error with a dialogue.
It's a known issue that user.home doesn't play well with floating profiles and as a result there isn't anything we can do to address this expect for suppressing all dialogues that come out of the propoerties classes when application.showLocalStorageDialogs=true;