Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Aleph
    Ex Libris Knowledge Center

    Meaningless System Messages in OPAC via Primo (OvP)

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Problem Symptoms:
    In OvP (OPAC via Primo) there are very strange messages that make no sense.
    These messages are from the file dlf_global (in error_lng). What is wrong here?

    Example
    Items on loan are renewed by a patron. After a successful renewal they see the message: "Client must be on localhost. IP must be 127.0.0.1."
    Obviously this message is not meant to be displayed in this place. The correct message would be the one that can be found in the file dlf_renewloan: "Renew successful"

    Cause:
    File global was copied to $alephe_root/error_lng

    Resolution:
    In the directory, error_lng, you find numerous files containing system messages from all Aleph modules. One of these files is called global. In the case where a message cannot be found in the module-specific file, it will be retrieved from the global file. The same is now valid with the dlf* files which contain the OvP messages: If a file cannot be found in a dlf_* file, it will be taken from dlf_global.

    Generally this works well but you will get problems in the following scenario:

    You have the option to copy some or all files from the a-tree to the alephe directory in your u-tree.
    If you copy a global file to the u-tree but leave the module specific files in the a-tree, the consequence will be that these global files take precedence over the module-specific files. This is because the system retrieves system messages in the following sequence:
    1. From a module-specific file in error_lng in the u-tree
    2. From a global file in error_lng in the u-tree
    3. From a module-specific file in error_lng in the a-tree
    4. From a global file in error_lng in the a-tree

    In the above example the message "Client must be on localhost. IP must be 127.0.0.1." as well as the message "Renew successful" have the code 0101. But only the message from the global file was copied to the u-tree.

    For these reasons you must not copy a global file to the u-tree because you will get a lot of meaningless system messages. Only if you decide to copy ALL message files to the u-tree, a global file will do no harm. Nonetheless it is not recommended as service packs may add more messages in the a-tree that may be missing in the u-tree.

    Category: Interoperability

    • Article last edited: 6/15/2015