Watermark images could be in any extension

[eab-andy]

Mimic the ezimage() template operator and find a file that matches the given image name.

Without this PR, you can only store watermarks inside the ezie extension.

[andrerom]

cs

should be the following according to ez v1 coding standard used in legacy:

if ( !$fileInfo )
{

[andrerom]

+1

[eab-andy]

Updated.

[andrerom]

looks good, just one more cs comment open, I updated it to specify what I implied, up for it before we go ahead and create issue + squash and update commit messages + merge?

[eab-andy]

Thanks for clarifying that. I've edited again.

[andrerom]

Ok, looks ok. remain part is create an issue, rebase the branch to squash commits into one referring to the issue and force push and you should be done :)

something like

git rebase -i master
# a interactive screen will allow you to put a 's' in front of each line but the first one
git push eab-dev WatermarkSubfolders -f