Continuing the discussion from Nothing Uploading:
Continuing this from @timtsuga’s original failure to upload post. @Rita’s response seems to indicate a change in the way the GFUI deals with text in a file. Previously it would warn us and ignore the text similar to the way clipping paths are treated. Now it looks like it just won’t load the file. If this was a deliberate change it deserves mention in a Support Announcement update so we know we can’t leave instructional text (providing notes about the file for instance) that’s not intended to be cut/scored/engraved unless we convert that to paths and then ignore them in the GFUI.
If it was intentional tightening up of file handling then it deserves a dedicated error message. It would also suggest that similar tightening around handling clipping paths might be coming. I know GF won’t comment on work in process, but if it is and you’re going to do the same with clipping paths so it’s no longer simply a warning message, would you post that in a Support announcement update when you release it and provide a specific message rather than the generic fail so we know how to correct our files?
Thanks in advance for considering it.