Support Forum
Hi,
Simple:Press isn't working correctly for me on Avada's child theme, the add reply and add topic buttons are broken, would I be able to get some help on it as Avada tell me that it's an issue with Simple:Press not Avada...
Also, I noticed this on my old themes but it wasn't really an issue but its more noticeable on Avada. If I browse to /membership/ for example at the top of the page it will show the title of "Membership", if I go to the forum on a computer, it will show "Fourm" as seen:
But now if I load the forum on a mobile that "Forum" is gone and is just a blank space, same for the menu when I am on the forum page the menu is just blank... I can give you access (via pm) to my test site if you wish to have a look at it.
Thanks
Isn't it a little odd that the two buttons you mention worked before, work here and just about everywhere else yet - if all you have done is changed your WP theme the authors say it can't possibly be the WP theme at fault 🙂
I would need to see it to diagnose. I would assume there are script conflicts showing up in the web console - so you could look if you know how.
forum admin > themes > mobile phone theme... - do you have it turned on and if so have you turned the page title off there?
YELLOW
SWORDFISH
|
Yellow Swordfish said
Isn't it a little odd that the two buttons you mention worked before, work here and just about everywhere else yet - if all you have done is changed your WP theme the authors say it can't possibly be the WP theme at fault 🙂I would need to see it to diagnose. I would assume there are script conflicts showing up in the web console - so you could look if you know how.
forum admin > themes > mobile phone theme... - do you have it turned on and if so have you turned the page title off there?
Hey,
Yeah, exactly. It works on my old theme using Thematic, but not on Avada (it also doesn't work on their adult theme, I thought it was only child theme at first)
You're right about the title, didn't see that option before. It's just the add/reply not working now. 🙁 the only errror I see in console is:
Very strong chance that that is the problem. Perhaps send it to your theme authors.
Please note that I see from this the theme is using the BootStrap library. BootStrap is NOT a supported WordPress script library at this time. The equivalent supported library is the jQuery UI which is what theme and plugin authors use to strictly meet WP standards.
And the main problem with BootStrap is that it can stomp all over the jQuery controls. Simple:Press uses the jQuery Tooltips component and there is a possibility based on this console report that your theme is using the BootStrap Tooltips which quite possibly collide and cause problems. Buttons that are created by jQuery are definitely destroyed by BootStrap so there are sure to be other conflicts.
One possible thing that might improve things is to load the jQuery UI script AFTER the BootStrap script. The theme authors may be able to advise on doing that.
YELLOW
SWORDFISH
|
They replied with:
The conflict occurs with Avada, that doesn't necessarily mean the problem is with Avada. We do not guarantee compatibility with all plugins, particularly if the plugin loads its own version of bootstrap.
The particular problem is coming from the bootstrap JS used for popovers.
After some extra research I have found the cause of the problem.
Check here - https://simple-press.com/suppo.....tegration/
The problem is the same as in this discussion.
The workaround to fix this was to set the tooltips variable to false in spFunctions.php:
if (!defined(‘SP_TOOLTIPS’)) define(‘SP_TOOLTIPS’, false);This is plugin specific but the fix above is what you need to do.
Is there an option in the settings for this rather than editing the spFunctions file?
No - that's the only place. Just install the child theme version of your theme (free from the store) and add a functions file to that with the changed define.
I would like to protest and emphasis however that this is NOT an SP issue no matter what your theme authors say. As already stated, Bootstrap in unsupported and as such can cause conflicts with ANY WP plugin that uses the correct UI scripts. So that is not just SP of course.
Bootstrap is actually very good (developed by the Twitter team) bit until it gets full WP support it should NOT be used.
YELLOW
SWORDFISH
|
1 Guest(s)