Islandora
  1. Islandora
  2. ISLANDORA-489

Form builder fails to print path to schema in warning message when NAT is disabled

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: XML Form Builder 7.x
    • Labels:
      None

      Description

      This is a bit of an edge case, but it came up while testing the Islanda VM Image with the NAT network adapter disabled.

      If you save a schema locally and then specify the correct location in the form properties, you still get a warning message that the schema could not be found. This is due to the fact that the schema imports two other schemas from online sources (xml.xsd and xlink.xsd) and without an internet connection these two schemas cannot be found.

      However, in this case the warning message prints out a blank string (rather than the path specified in the form properties):

      Failed to Find Schema. ''

      The expected string should be printed out in the warning message.

        Activity

        Hide
        David Wilcox added a comment -
        This has come up on the list a couple times as well. I talked to Jonathan, and we agreed that a good short-term fix would be to add a config option that disables form validation. That way, users with no internet access can still use forms without waiting for the validation check to timeout. Long-term we'll want to look at storing the schemas locally.

        I'm going to unassign this issue temporarily just so we have a chance to note it in this week's committers meeting.
        Show
        David Wilcox added a comment - This has come up on the list a couple times as well. I talked to Jonathan, and we agreed that a good short-term fix would be to add a config option that disables form validation. That way, users with no internet access can still use forms without waiting for the validation check to timeout. Long-term we'll want to look at storing the schemas locally. I'm going to unassign this issue temporarily just so we have a chance to note it in this week's committers meeting.
        Hide
        Jonathan Green added a comment -
        We are using the DomDocument load function, which has a 60 second timeout. We can potentially use the tuque HttpConnection to do with with a shorter timeout.

        xml schema api, which is in the api folder in xml forms.
        Show
        Jonathan Green added a comment - We are using the DomDocument load function, which has a 60 second timeout. We can potentially use the tuque HttpConnection to do with with a shorter timeout. xml schema api, which is in the api folder in xml forms.
        Hide
        Melissa Anez added a comment -
        Reviewed in Committers Call. Still an issue, but a tricky one to fix. Problems also occur when the schema itself is offline, a la Library of Congress during the US government shutdown, but this is how they are configured, so...
        Show
        Melissa Anez added a comment - Reviewed in Committers Call. Still an issue, but a tricky one to fix. Problems also occur when the schema itself is offline, a la Library of Congress during the US government shutdown, but this is how they are configured, so...

          People

          • Assignee:
            Unassigned
            Reporter:
            David Wilcox
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: