Hi,
It looks like in PP2017R2 some .js files are now being named according to the pp version, whereas before they were consistent across all PP versions (e.g webportmain.js)....
# The Javascript file that makes Web Port tick.
TEMPLATE_WEBPORT_JS_FILE javascript/webportmain.17_2_0_1361.js
# The path to the login page JavaScript
TEMPLATE_LOGINPAGE_JS javascript/loginpage.17_2_0_1361.js
This can cause problems when creating packages that use the customise webport.bat during package install - which requires settings to be provided in the 'tokens' file.
Before this change one token file could be used for all versions of PP. Now a separate one will need to be maintained for each version of PP (possibly SP and Hotfixes as well?) and added to the package as I believe you cannot deferentially execute lines from the .conf file depending on the PP version detected (e.g to copy across and rename the relevant tokens file).
So my question(s) are,
(1) why has this change be made and had the effect on customise webport.bat been considered?
(2) Is there any way to deferentially execute lines in the package.conf depending on PP version (in a way that's compatible with PP 9.5 onwards)
I think the same will apply to people using the customise webport functionality outside of packages as they upgrade to PP2017R2, they will need to amend the tokens files they had previously, as some webport functionality such as the advance file chooser in PP2017R2 need the new webportmain.17_2_0_1361.js to work correctly, even if the older webportmain.js is still present (e.g from an upgrade).
Thanks
Joe
It looks like in PP2017R2 some .js files are now being named according to the pp version, whereas before they were consistent across all PP versions (e.g webportmain.js)....
# The Javascript file that makes Web Port tick.
TEMPLATE_WEBPORT_JS_FILE javascript/webportmain.17_2_0_1361.js
# The path to the login page JavaScript
TEMPLATE_LOGINPAGE_JS javascript/loginpage.17_2_0_1361.js
This can cause problems when creating packages that use the customise webport.bat during package install - which requires settings to be provided in the 'tokens' file.
Before this change one token file could be used for all versions of PP. Now a separate one will need to be maintained for each version of PP (possibly SP and Hotfixes as well?) and added to the package as I believe you cannot deferentially execute lines from the .conf file depending on the PP version detected (e.g to copy across and rename the relevant tokens file).
So my question(s) are,
(1) why has this change be made and had the effect on customise webport.bat been considered?
(2) Is there any way to deferentially execute lines in the package.conf depending on PP version (in a way that's compatible with PP 9.5 onwards)
I think the same will apply to people using the customise webport functionality outside of packages as they upgrade to PP2017R2, they will need to amend the tokens files they had previously, as some webport functionality such as the advance file chooser in PP2017R2 need the new webportmain.17_2_0_1361.js to work correctly, even if the older webportmain.js is still present (e.g from an upgrade).
Thanks
Joe
