Templates (PrintTemplates) overwritten on PC

Description

The .\Alephcom\files\xxx01\PrintTemplates files are being overwritten on every PC.  We have changed these files locally
and don't want them overwritten.

Resolution

As described in the article " Print templates not being updated on workstation as expected ", util i/6 creates a new
./form_eng/html.pck file.  When a GUI module is started, the date of the html.pck file is compared to that of the
PrintTemplates files.  If the html.pck is newer, then the client overwrites the PrintTemplates files with the form_eng
html.pck files.  
  That is how it's intended to work.  The PrintTemplates files are not supposed to be updated locally: they are
supposed to be maintained on the server and downloaded from the server.  The GUI checks the ./xxx50/tab/path_convert, and if there's a line like this:

$xxx50_dev/xxx50/form_eng             $xxx01_dev/xxx01/form_eng

it will use the xxx01 form_eng, but, if there is none, then, by default, it will use the xxx50 form_eng.  Thus, in a multi-ADM situation, each xxx50 ADM *could* have its own form_eng files.

In this case, the users had been modifying their own PrintTemplates files directly on the PC and allowing an updated html.pck to overwrite them was a  problem.  To prevent this, the $aleph_proc/util_i_06 was renamed to ./util_i_06.notused and the $aleph_proc/util_i_06b was renamed to ./util_i_06b.notused, so that, when util i/6 was attempted, it would fail with an error, thus, preventing any new html.pck from being created. 

• Article last edited: 06-Sep-2016