Case in "Allowed extensions" for File Custom Field
By Altitudes on Wednesday, 20 May 2015
Posted in Technical Issues
Replies 9
Likes 0
Views 717
Votes 0
Hello

When you have a File field on a Profile Type, you can define what are the allowed extensions. The problem is they are case sensitive, that is if you define jpg as allowed, if a user tries to upload a file with extensions JPG then it fails...
It certainly should be case insensitive.

We maybe have the same issue for User, Group and Event File fields, User, Group and Event File apps, and for files in conversations...

Thanks
Hello

I tested this in ES 1.3.30, and the fix is not really what I expected (and suggested
media\com_easysocial\apps\fields\user\file\config.json was modified to add capitalized extensions in the list ("jpg,png,jpeg,JPG,PNG,JPEG"). Performing a case insensitive compare in code when checking extension would have been more clever :/

Despite this I mark this topic as solved, as I don't want to spend more time on it.

Note: I checked the User File app (as I suggested in my 1st message that User, Group and Event File apps may have the same issue). But it is working fine whatever is the case of the extension when uploading a file in stream.
Altitudes
·
Friday, 07 August 2015 20:55
·
0 Likes
·
0 Votes
·
0 Comments
·
Sounds like an interesting subject. Subscribed.
Josh Lewis
·
Thursday, 21 May 2015 17:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Altitudes,

Thanks for reporting this issue we will include this fix in our next release.

For the time being you can fix this issue by accessing this file

LocalJoomlaFolder\media\com_easysocial\apps\fields\user\file\config.json

and add JPG file (please refer to the screenshot)

http://screen.stackideas.com/customfile_s1.png

Once the JPG is added to the config.json the event and group will also be able to accept the JPG format.

After that login to your backend, Select->Components->Easysocial->Profile types->Select your default profile->Select Custom Fields->File->Edit->Basic

and add the JPG (please refer to the screenshot)
http://screen.stackideas.com/customfile_s2.png

Hope that helps .

Best regards
Chris
Christopher Chiam
·
Thursday, 21 May 2015 19:06
·
0 Likes
·
0 Votes
·
0 Comments
·
I must says I was more expecting that, when ES checks the file extensions, this check is case insensitive...

It would be the best solution. But if you consider that all possible cases should be added explicitely, then in the config.json you should at least have "jpg,png,jpeg,JPG,PNG,JPEG"... which will not prevent a "Jpg" extension from failing :-/
Altitudes
·
Thursday, 21 May 2015 20:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes, I'm agree with that

We will include this fix in next release version.
Arlex Wong
·
Friday, 22 May 2015 00:24
·
0 Likes
·
0 Votes
·
0 Comments
·
You mean you agree with the case insensitive compare in your code?
Altitudes
·
Friday, 22 May 2015 03:22
·
0 Likes
·
0 Votes
·
0 Comments
·
I'm thinking that is what Arlex meant.
Josh Lewis
·
Friday, 22 May 2015 04:09
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey guys,

Sorry, I have been away for the past couple of days, been extremely busy with 1.4 Anyways, this fix is already implemented internally!
Mark
·
Friday, 22 May 2015 13:16
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating Altitudes
Mark
·
Saturday, 08 August 2015 04:03
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post