Quote Originally Posted by brittainmark View Post
Thats great. Thanks. If i find anything else shall i post here or raise issue on git-hub.
For me to respond, either would work; however, generally in the spirit of the community, I would suggest posting here. If that is then determined better to capture/address in github such can be then be done.

I want to also say that the above posted "solution" considers the admin directory to be only one directory deep away from the "public" folder being used. E.g. if a store were found in https: // DOMAIN / sub-folder / 2nd sub-folder and the file were located at https: // DOMAIN / filename.csv Then I suspect/expect that the CSV unknown delimiter issue would occur... That also said, I was just about to indicate how I might change the message to reflect the condition causing this issue; however, I'm not so sure that I want to offer up that additional piece of info that the file is being retrieved from a location considered to be unauthorized...

The general principle behind the check is to consider the actual file path (location on the server) and in a way to ignore or not use database and/or constant related information when considering likeness.