Support Forum

its not fundamentally a genesis framework issue... I use genesis on numerous sites just fine...  but the child theme could be introducing other js that is conflicting...

a link to the site would help understand if there is some obvious conflict... and this gives bit more insight:  http://codex.simple-press.com/.....-conflict/

short answer is yes, you can fix the forum tools icon to always display rather than hide..  if the issue is the popup itself vice the appearing button, may not help...  are we talking in forum view here or topic view?  or both?  lets start with forum view...  in your sp theme you are using, the spForumView.php template file has the template tag... find this line:

                                sp_TopicForumToolButton('', '', 'Open the forum toolset');

and change it to always be open like:

                                sp_TopicForumToolButton('hide=0', '', 'Open the forum toolset');

there is a similar template tag in the spTopicView.php template file for the topic view...

As always, we strongly recommend you make a child theme or your own theme instead of editing our provided theme as you will lose your changes if you ever update our theme...

reset them all?  sorry,not following...

do you have link to site so we can look at what might be conflicting?

do other popups work?  like profile (if using popup) or the credits?  or other...

so yeah, need a link if possible to site or need more js debugging info from you (ie errors from the browser console when trying to open a popup)...

that's the html markup, not js debugging info...  but one can see that the html is corrupted (if that is truly what is in the page source)...

I see the wishlist comment headings plugin is in play and they are adding jquery tooltips...  I wonder if that could be conflicting and causing the dorked up html...   since the forum itself is behind a paywall, cannot see the actual error...  and what other js might be loaded...

are you using a forum translation?  if so, can you try it real quick without it and see if still an issue?  want to make sure a translated language character isnt messing it up (doubt it as many, many folks translate sp)...

also, might want to run down the conflict...  try a temp switch to the default wp theme... work now?  if so, will have to find the conflict there...  if not, then disable all other wp plugins and see... then re-enable one by one until it breaks...