1-- On your version the WYSIWYG is meant to be disabled for ipad, so the bug is the inconsistency of it sometimes actually coming on. However, now we allow it for ipad - so I have made that the case for you.

picup issues-- This has crept up rather. We wrote the code before the iPad, on the basis that iPhone users might be on some screen where they really needed to upload something (e.g. setting a photo), but it wasn't made robust/flexible for all cases. iPad changed things, because now doing more uploaderish tasks became reasonable/expected, but the code was not revisited. I have now made it support multiple upload fields, and attachments, although I have only been able to test in a simulated environment. picup support may be dropped (I think infact it already is commented out on the newer plupload addon), because of how iOS supports native upload now -- but I'd rather keep it working for now, so rather than disabling it for you I made those aforementioned changes.

Hello Chris,

I emptied the template cache before testing it out. Now, neither thing is working in iPad. In the single photo add screen, I get a photo (only 250k) and Picup says it uploaded to our site, but back in the CMS screen it doesn't show any file, and if I click Save it says Error, no file was uploaded.

Same issue in News entry screen as before. Doesn't show any file attachment code.

Sorry, I forgot I'd changed two files - I have just uploaded the other for you.

Hello Chris,

I emptied template cache again before testing. Still the same exact results with both cms screens as in previous test. The stack trace error I get when clicking save after uploading small-size image in the single-image-entry cms screen is--

File -> '/home/saiva/public_html/sources/failure.php'
Line -> 693
Function -> 'die_html_trace'
Args -> array ( 0 => 'You did not provide an upload, or you tried to upload a file that is too large (version: 9.0.2, PHP version: 5.3.3, URL: /cms/index.php?page=cms_galleries&type=_ad&keep_fatalistic=1&uploading=1)', )

My iPad is on iOS 6.1 now. I wonder if that's causing a problem?

Maybe the browser cache needs emptying. I can imagine the picup.html file caching (which is the second changed file I uploaded, as mentioned above).

The best test I can do at the moment is go to...

http://www.saivasiddhanta.org/data_custom/picup.html?field_name=file1&window_name=test&window_url=http%3A%2F%2Fwww.saivasiddhanta.org%2Fcms%2Findex.php%3Fpage%3Dcms_news%26type%3Dad#serverResponse={upload_id:51,upload_name:'example.jpg'}

That's just an example test URL, it won't actually work when submitting the news form (51 is a made up upload ID, the real picup would have generated a real one).


I could just disable picup, and let the new iOS upload functionality hopefully work without picup.

I tried emptying browser cache on iPad. Still not working. I noticed that the Picup app is saying it actually couldn't upload the file to the site. That's why no attachment details box or code is appearing.

I'm getting the sense that we should just disable Picup.

I went over to the iPhone to test a photo upload. The iPhone is on iOS 6.1.1. When I went to the Add Image cms screen, it didn't even show the option to use Picup. It just showed the 'Choose File' button. It let me successfully upload a photo, however it didn't quite work right. It produced a thumbnail (in the images carousel on front page) of the photo I uploaded, however when clicking on the thumbnail to go to the full view page, it was a different image altogether, not even from my iphone; it was one of the images I had test uploaded from the iPad some time back.

The re-use of a thumbnail could be if you accessed the add-image screen via the browser history - one of the old picup transfers could have got stuck in there. That's my guess, it doesn't quite tally with your situation to me, but I suspect it's something to do with picup's operation anyway.

I have now disabled picup. iOS should be just fine without it now, and a lot simpler all around.