If you manually delete all copies of example.xml that are within the files/patterns/ directory so that Patterns thinks it has never seen or run this particular file, and then change the content of the sites/all/modules/patterns/patterns/example.xml file so that it becomes invalid XML, and then attempt to run it at admin/build/patterns, you will not see the xml file. Presumably, this is because the xml is invalid.

It should at least show up. This is a UI fail.

Perhaps once the http://drupal.org/node/353652 issue regarding a patterns_xml_validator() function gets farther along, this 'error' could be made to look more like a pattern that has been disabled due to error, and the drupal_set_message could contain the exact error along with the line number at which the error was discovered?

Comments

senpai’s picture

senpai commented
Status: Active » Postponed

Strike that. The third time I tried this, it actually showed an error in the drupal_set_message. I must have been seeing a cached somethin' somethin'.

Soo, rethinking the above, the admin/build/patterns page shows an error if the file contains invalid XML. It does not, however, show the file itself. This could eventually be made to happen as a UI improvement, but such is for a later time once the code becomes more stable.