I do have a number of updates to push to the github version, and as I said, I believe that there was at one point a reverse logic applied to the file check. I've added two significant features that I need to be sure to test before posting the full change to the ZC site. One is using the admin sanitization during import of the file data, another is the use of identifying a language by its two letter designation instead of using its languages_id, while maintaining the possibility of the old method. Ie. Once again expanding on the capability to maximize existing processes.
Not sure if I purposefully left that issue as the current load or not. Wouldn't put it past me to do that so that the use of the incomplete code wouldn't bungle someone's database. I can take the heat for there being software that doesn't "do" anything better than it knowingly messing up someone's database.



Reply With Quote
