Closed drmalex07 closed 9 years ago
This was partially because non-ascii feature-related sample data were fed to the dialog template (fixed as of e100e00d72acf68b36091e48470f0a73a87a7cfd).
Another case that would trigger a silent failure is of course a wrong encoding, but at least this kind of error will eventually show up as "Publish Failed".
Closing for now, will reopen on a specific case.
At several cases, when the ingest source is malformed, the configuration step (ingest dialog) can fail without any useful feedback message (both to the user and to the application logs).
A common case for this to happen is a SHAPEFILE with a unexpected/unknown encoding.
This behavior is also buggy (to my opinion), because if an ingest source is unusable this should be discovered at the "identification" step (as deep as possible).