Fixed XF 2.0 & ios 7
- Thread starter Edrondol
- Start date
It’s actually over 4 years old since its original release and coming up to 5 years.
It’s correct that technically we only support iOS 10 and 11 officially. There’s likely going to be a myriad of issues on iOS 7 and likely iOS 8. Mostly related to flex box CSS and how things are laid out on screen.
There has to be a cut off point somewhere. That said, posting is fairly fundamental. I’d bet that even older IE versions that we do not support can probably post, at least. If we can have more details of the specifics of “unable to post” then it might be something we can address - such as perhaps disabling the rich text editor for that advice or some other graceful degradation.
I’ll test it on the Simulator too but more details from the user would be useful.
It’s correct that technically we only support iOS 10 and 11 officially. There’s likely going to be a myriad of issues on iOS 7 and likely iOS 8. Mostly related to flex box CSS and how things are laid out on screen.
There has to be a cut off point somewhere. That said, posting is fairly fundamental. I’d bet that even older IE versions that we do not support can probably post, at least. If we can have more details of the specifics of “unable to post” then it might be something we can address - such as perhaps disabling the rich text editor for that advice or some other graceful degradation.
I’ll test it on the Simulator too but more details from the user would be useful.
Actually, I can't do this due to its age it's unavailable, so we're certainly working blind here. As I'm sure you can appreciate, we can't exactly debug or support anything where we can't reliably reproduce issues and test fixes.
If you could ask your user to visit this URL from their iPad and report back their User Agent string, that will be a good start.
https://www.whoishostingthis.com/tools/user-agent/
The bit we need will look a little like this:
Well our usual course of action here is that we would often just disable the rich text editor, as usually there would be some incompatibility there.
We currently disable the rich text editor in iOS 6 and below. We could add iOS 7 to that, but Froala is supposed to be able to run iOS 7 and iOS 7 should still support jQuery 3.x, so I'm somewhat at a loss as to what the specific problem is. You've also not really elaborated much aside from "unable to post", so if you can provide more details on the specifics, then we might have a better idea on how we should proceed.
Finally, could you ask if he can use the rich text editor on the following site without issue?
https://www.froala.com/wysiwyg-editor
We currently disable the rich text editor in iOS 6 and below. We could add iOS 7 to that, but Froala is supposed to be able to run iOS 7 and iOS 7 should still support jQuery 3.x, so I'm somewhat at a loss as to what the specific problem is. You've also not really elaborated much aside from "unable to post", so if you can provide more details on the specifics, then we might have a better idea on how we should proceed.
Finally, could you ask if he can use the rich text editor on the following site without issue?
https://www.froala.com/wysiwyg-editor
As a temporary measure, there's a code edit you can make.
You have to open the file
And replace with:
(It's just changing the 7 for a 6).
It will disable the rich text editor, and he should be able to type in that without issue.
You have to open the file
src/XF/Template/Templater.php and find:
PHP:
if (preg_match('#(iphone|ipod|ipad).+OS (\d+)_#i', $ua, $match) && intval($match[2]) < 7)
PHP:
if (preg_match('#(iphone|ipod|ipad).+OS (\d+)_#i', $ua, $match) && intval($match[2]) < 6)It will disable the rich text editor, and he should be able to type in that without issue.
Well, it could potentially affect more than that. Posting is pretty fundamental so if we can make sure that works, or at least there's workarounds in place that don't totally break it on older browsers, then I think that's reasonable. We don't officially support IE9, but I think even on there things (like posting) should generally work. Also, given that the most likely culprits, jQuery 3.x and Froala, specifically report compatibility with iOS 7+ then we should make some effort there.
It would seem to be a Froala issue so we've reported it to them:
https://github.com/froala/wysiwyg-editor/issues/2585
I've also committed the code change I gave you, so if they take some time to resolve it (or can't) then that should at least make posting functional.
It would seem to be a Froala issue so we've reported it to them:
https://github.com/froala/wysiwyg-editor/issues/2585
I've also committed the code change I gave you, so if they take some time to resolve it (or can't) then that should at least make posting functional.
You know I'm not sure what my brain was thinking for a sec there. I gave you the wrong change.
The line of code mentioned above should be changed to:
(Changing the 7 for an 8).
Sorry about that.
The line of code mentioned above should be changed to:
PHP:
if (preg_match('#(iphone|ipod|ipad).+OS (\d+)_#i', $ua, $match) && intval($match[2]) < 8)Sorry about that.
Similar threads
- Question
