<p><strong>Update: This bug is fixed as of Craft 2.4.2697</strong></p>

<blockquote>
  <p>Images uploaded from iOS now get renamed to
  “image_YYYYMMDD_HHMMSS.ext” (from “image.ext”), fixing a bug where iOS
  uploads would fail after the 51st image due to Craft’s limit on
  allowed same-name uploads.</p>
</blockquote>

<p>iOS uploads images from the camera roll with the name image.jpg, and if this happens multiple times then an incremental number is appended to the filename, similar to what happens with slugs. I have found that after 50 such instances though, the error message you reported starts to appear and images cannot be uploaded. </p>

<p>This is a bug in Craft and P&amp;T will hopefully release a fix soon, but a temporary solution is to rename some uploaded files so that the 50 limit is not reached. Alternatively, you could make the entry slug part of the upload path to avoid reaching the limit. </p>

CC BY-SA 3.0
2015-10-10T23:18:41.943Z
To avoid the renaming maybe you could make the entry slug part of the upload path? That way you would only hit the wall if there are 50 img per entry. Could make life with all the image.jpg files easier as well.
Wolfram Gehring
CC BY-SA 3.0
2015-10-11T07:16:24.307Z
That's right, I've added your suggestion to the answer, thanks!!
Ben Croker
CC BY-SA 3.0
2015-10-12T09:40:30.610Z
Ah of course! Well spotted Ben. Okay, I think my client will sit tight for a Craft update on this one.
Ian Ebden
CC BY-SA 3.0
2015-10-15T21:16:35.523Z
Thanks @BenCroker for adding my suggestion,the latest Craft version (2.4.2697) however makes that obsolete. The problem should be history now.
Wolfram Gehring
CC BY-SA 3.0
2015-10-16T08:49:27.790Z
yup cheers, added that too
Ben Croker
CC BY-SA 3.0
2015-10-10T21:12:01.487Z
2015-10-16T08:45:51.743Z
2015-10-16T08:45:51.743Z
Ben Croker
<p>Got a client who uses his iPhone and iPad to update his site (he doesn't have a laptop!). Craft does a much better job than most as a mobile CMS, but he's running into issues with file uploads. When uploading from his Camera Roll he gets the following:</p>

<blockquote>
  <p>Upload failed for image.jpg. The error message was: "Error uploading
  the file: This file type is not allowed"</p>
</blockquote>

<p>I've tried too and get same response. In config.php jpeg and jpg are set in allowedFileExtensions, and maxUploadFileSize is ample if that matters. Wondering if there's some weird proprietary stuff with iOS files that's causing this? Anyone else experienced this before?</p>

CC BY-SA 3.0
2015-07-31T08:27:11.023Z
Also check your field settings to make sure 'Images' are selected under the allowed file types option.
Jamie Wade
CC BY-SA 3.0
2015-07-31T09:17:47.400Z
Hi Jamie. Yep, definitely set to 'Images' already.
Ian Ebden
CC BY-SA 3.0
2015-07-31T16:27:47.640Z
FWIW, I'm not able to reproduce this locally.  Not that it should matter, but can you try removing the `allowedFileExtensions` (jpg is allowed by default) and `maxUploadFileSize` config settings just to narrow things down?
Brad Bell
CC BY-SA 3.0
2015-08-03T08:35:17.513Z
Hi Brad. Yeah tried that too. Wonder if it's a host thing? I'll drop them a line and see what they suggest.
Ian Ebden
CC BY-SA 3.0
2015-10-06T06:46:43.583Z
@IanEbden did you ever solve this? I'm having the same issues for a client.
naboovalley
CC BY-SA 3.0
2015-10-06T10:58:10.217Z
Nope. I don't know if it's still an issue for client. Haven't heard back.
Ian Ebden
<assets>
File upload issues on iOS
# File upload issues on iOS

(Asked by: username_0 on 2015-07-31)

Got a client who uses his iPhone and iPad to update his site (he doesn't have a laptop!). Craft does a much better job than most as a mobile CMS, but he's running into issues with file uploads. When uploading from his Camera Roll he gets the following:

> Upload failed for image.jpg. The error message was: "Error uploading
> the file: This file type is not allowed"

I've tried too and get same response. In config.php jpeg and jpg are set in allowedFileExtensions, and maxUploadFileSize is ample if that matters. Wondering if there's some weird proprietary stuff with iOS files that's causing this? Anyone else experienced this before?

**Tags:** assets
> **Comments:**
> **username_1**: Also check your field settings to make sure 'Images' are selected under the allowed file types option.  
> **username_0**: Hi Jamie. Yep, definitely set to 'Images' already.  
> **username_2**: FWIW, I'm not able to reproduce this locally.  Not that it should matter, but can you try removing the `allowedFileExtensions` (jpg is allowed by default) and `maxUploadFileSize` config settings just to narrow things down?  
> **username_0**: Hi Brad. Yeah tried that too. Wonder if it's a host thing? I'll drop them a line and see what they suggest.  
> **username_3**: @IanEbden did you ever solve this? I'm having the same issues for a client.  
> **username_0**: Nope. I don't know if it's still an issue for client. Haven't heard back.  

---

## 1 answers

### Answer by username_4 on 2015-10-10. Score: 2

**Update: This bug is fixed as of Craft 2.4.2697**

> Images uploaded from iOS now get renamed to
> “image\_YYYYMMDD\_HHMMSS.ext” (from “image.ext”), fixing a bug where iOS
> uploads would fail after the 51st image due to Craft’s limit on
> allowed same-name uploads.

iOS uploads images from the camera roll with the name image.jpg, and if this happens multiple times then an incremental number is appended to the filename, similar to what happens with slugs. I have found that after 50 such instances though, the error message you reported starts to appear and images cannot be uploaded.

This is a bug in Craft and P&T will hopefully release a fix soon, but a temporary solution is to rename some uploaded files so that the 50 limit is not reached. Alternatively, you could make the entry slug part of the upload path to avoid reaching the limit.

> **Comments:**
> **username_5**: To avoid the renaming maybe you could make the entry slug part of the upload path? That way you would only hit the wall if there are 50 img per entry. Could make life with all the image.jpg files easier as well.  
> **username_4**: That's right, I've added your suggestion to the answer, thanks!!  
> **username_0**: Ah of course! Well spotted Ben. Okay, I think my client will sit tight for a Craft update on this one.  
> **username_5**: Thanks @BenCroker for adding my suggestion,the latest Craft version (2.4.2697) however makes that obsolete. The problem should be history now.  
> **username_4**: yup cheers, added that too  

---

