Notifications
Clear all

wpForo 1.x.x [Closed] Disable the dynamic loading of the Add Topic TinyMCE box?

3 Posts
2 Users
0 Reactions
1,953 Views
Posts: 2
Topic starter
(@elizabeth)
New Member
Joined: 7 years ago

I have a conflict with my theme wherein when a user clicks the "Add Topic" button, the following happens:

 - TinyMCE interface opens up as it should

- The cursor's autofocus is on the Topic Title as it should be

BUT 

 - if the user clicks to the message part without entering in the Topic Title (or tries to go back to it to edit), they can't click back in the field. It won't accept the focus.

 - interestingly, the user can use keyboard shortcuts (shift+tab) to resume the cursor focus in the Topic Title field.

It's not quite exactly this problem, but pretty close.

I've spent way too much time trying to figure this out, and I'm still stuck with ¯\_(ツ)_/¯ so I'm wondering if there's a workaround where I can just disable the ajax that pops down the Add Topic form, and either show the form by default, or force a page reload, or even show a simpler Add Topic form. 

I'm not really sure how to move forward at this point, because I love my theme and I love this forum, and I really hate to not let them play together because of this tiny frustrating bug. (I know it's a conflict with my theme- I ruled everything else out.)

Would love any thoughts! Thank youuuuu!

2 Replies
Robert
Posts: 10591
Admin
(@robert)
Support Team
Joined: 9 years ago

Hi elizabeth

I've spent way too much time trying to figure this out, and I'm still stuck with ¯\_(ツ)_/¯ so I'm wondering if there's a workaround where I can just disable the ajax that pops down the Add Topic form, and either show the form by default, or force a page reload, or even show a simpler Add Topic form. 

The Add Topic button doesn't have AJAX request. Also there is no way to use wpForo editor with text mode, it must be loaded View (rich) mode. We'd debug and try to find the conflict point if you leave the forum URL.

 

Posts: 2
Topic starter
(@elizabeth)
New Member
Joined: 7 years ago

Aha! I finally figured out that it was the class .wp-editor-wrap that was causing me grief. When I changed the position from relative to inherit, the form works as it should. 

Thank you!