Support Forum

Reply Buttons Not Working on iPhone/iPad

22 Answers

New Answer
JC James Chartrand
James Chartrand
Member
Member since Aug 2012
33 posts
Jul 14, 2017 · 6:46 am

Here’s what my website developer came back with:

I can prove this is not specific to our site – the same issue is reproducible for Safari in the SimplePress support forums too.
 
> Hold on a minute…! That function is actually a tinyMCE function that 
> is showing the error. Safari clearly has not loaded the TM scripts yet.
 
TinyMCE has loaded, but is generating an error due to ‘c.item’ not existing: http://d.pr/i/yDNeX.
 
> However a question… That SP function is specific to the Threading 
> plugin which uses the ‘reply’ button within each, individual post – as 
> opposed to the Add/Reply button at the bottom of a post listing. I 
> have been working on the assumption that we have been talking about 
> the latter but are we really talking about the threading reply button 
> here? And does the main reply button and editor work OK?
 
The “Add Reply” button works and the editor loads when that’s clicked. It’s just the “Reply to this post” button that fails in Safari in my tests: http://d.pr/i/aR96g
 
I see the same error in Safari when clicking “Reply to this post” on the SimplePress forum topic here: https://simple-press.com/support-forum/pre-membership-queries/can-i-test-simplepress-while-leaving-bbpress-installed/
 
Screenshot of error: http://d.pr/i/7b8hL
 
So this does not appear specific to our site only.
 
Deactivating the “Editor TinyMCE Rich Text” SimplePress plugin solves the issue, but we obviously lose TinyMCE in the process for all users.
 
YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Jul 14, 2017 · 6:58 am

I had replicated already. Really just needed to know that it was ONLY the threading that was affected. It is maddening as opening the editor inline like we do for threading was a real problem to code up – and just typical that Safari is the one browser in which it fails.

We tend to hate Safari here… it has always been the problem browser – at least since Microsoft joined the standards!

I have opened a ticket so we will see if we can locate the issue.

JC James Chartrand
James Chartrand
Member
Member since Aug 2012
33 posts
Jul 14, 2017 · 11:02 am

Okay, great, thanks so much, and please keep me posted on a fix!

YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Jul 15, 2017 · 5:20 am

To explain the issue a little – the threading plugin, unlike standard/core SP – opens the editor inline to the post being replied to. You will have noticed this I am sure. This was actually quite difficult to achieve although in the end the code was quite simple and small.

This works in all Windows/macOS/Android/IOS browsers tested with (and that includes some more obscure ones as well as the main big 4) with – it appears – the exception of Safari. I feel pretty sure it did work when it was first tested – although some other things did not that are now supported.

When it is just the one browser like this it is pretty obvious that it is the browser that is causing the problem and indeed the Safari JavaScript engine has always left something to be desired as far as standards go. It has been getting so much better in the last year or so but clearly it has failed over this issue.

It does mean a fix may not be something we can quickly knock out as we will not jeopardise the code as far as all other browsers go. Hopefully we will be able to work it but that remains to be seen of course. The worst case scenario would be to just let Safari open the editor at the bottom of the posts as with a normal, non-threaded reply.

YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Jul 16, 2017 · 5:05 pm

Threaded reply sent from my iPhone using Safari …

Looks like we may be in business ?

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Jul 17, 2017 · 9:24 pm

an update to the threading plugin was pushed out this evening…

JC James Chartrand
James Chartrand
Member
Member since Aug 2012
33 posts
Jul 18, 2017 · 8:06 am

Awesome, just noticed that this morning, and have updated.  I’ll let members know and post any feedback – thanks SO much for helping out with this!

YS Yellow Swordfish
Yellow Swordfish
Member
Member since Nov 2008
16,437 posts
Jul 18, 2017 · 8:25 am

Fixing bugs – always a priority of course.

It all checks out in our tests. Make sure you advise users to clear their browser cache if they can and also, if you are using the SP combined JS cache you would do well to reset it in the forum admin > toolbox > housekeeping panel. Let us know how it goes.