Our print CMS is on a Unix server and does not allow slugs with characters in them. So if a reporter makes a story slug like TYDOLLA$IGN or AR-15, Ellipsis will tell you the story was successfully sent to print even though our print system will reject the file.
Two proposed solutions to this problem:
- Build in a two-way notification so that if the story is sent but does not arrive in the print system, the Ellipsis user is notified of a failure
or
- In Ellipsis organization settings, add a control to disallow characters from the slug field. There is already a control to impose a max character count, so this could work the same way. This is the preferred solution because it would prevent any such errors in the first place.