Tabs Missing in Admin

I just installed the latest version of s2member and the tabs do not show in the admin menu.

I’m not sure why, it is a fresh install. The normal tabs do not show; the admin content is not formatted.

Hi Skyrie,

This is related to a JavaScript conflict between s2Member and another plugin, or between s2Member and your installed theme. Please try disabling all other plugins to see if that fixes it and if not, please try switching to the default WordPress theme (TwentyEleven).

You may also want to clear your browser cache.

I have disabled all plugins, switched to the default theme, cleared my cache, and tried in three browsers (FireFox, Chrome, and IE). Firebug reports no errors, but the issue remains.

So you basically had just WordPress with the default theme and just the s2Member plugin and you still didn’t have the s2Member panels show up properly in the its admin pages?

Could you post a screenshot of the whole General Options page? The one in the first post seems to just be the Email Configuration panel. Thanks!

I can’t really post a screenshot of the whole page because, without tabs, it is several screens long. But it looks like that all the way down, with none of the normal accordian tabs. I’m going to try and install s2member on a new website and see if the same problem happens.

Got it. Yeah, please let us know how it works in the other site.

Normally that happens when a theme or plugin affects the JavaScript, but if you’re using the default theme and aren’t using other plugins, then I don’t know.

I just installed on a new site and I have the same issue. It’s not my browser, as anyone else I ask sees the same thing. It was a blank install. I’m not sure what to try now.

In that case this sounds like a server configuration issue. Could you try modifying your .htaccess file as explained here and let us know if that fixes the problem?

Hm. That doesn’t seem to help, and I don’t have Mod Security or PHP Suhosin installed. I run my own dedicated server and I have installed s2member before without problem. I’m not sure what (if anything) I have changed since my last install.

• This reply was modified 4 years, 8 months ago by  Skyrie.

Hi Skyrie,

Have you tried installing it on a different server? If you’re seeing this with a blank WordPress install using the default WordPress theme, then I cannot think of anything except something on the server that’s causing the problem. Since you have a dedicated server, you might want to try checking the web server logs to see if there are any clues there.

I do have the same problem. at very first day everything seems ok. tabs are working I did some changes on some of the pages when I’m going to generate PayPal buttons, I realized that without tabs buttons did not generate new code. Actually my main problem is PayPal button generator is not working… I have installed wordpress in a different folder for test. I installed my theme and s2 member. They worked together and then I don’t why tabs disappeared again…
I want to use this theme cos I paid it and I want to use s2 member cos I paid it too. I’ll be glad if you find us a solution…

Regards
Eddie

Here is my screenshot:

Hi Eddie.

If you go back to the default theme, does the problem go away? If so, then it is the theme. You can tell the developer to look into it and improve it. Or you can try doing it yourself if you know how to do it.

This is part of a conversation I had with Jason some months ago regarding JavaScript conflicts.

Cristián: I still don’t understand how the JS conflicts work… If the library is the same in both plugins, why is there a conflict? Same var names?

Jason Caldwell: Well, I call it a conflict. Sometimes it’s a conflict in jQuery because of a bad plugin, which attempts to load jQuery on it’s own, instead of doing it the WP way. Or sometimes, it just a bad plugin that causes a JavaScript error, which may result in all JavaScript failing (the nature of JavaScript). Not really a “conflict” in that case, really an error due to a bad plugin/theme.

Jason Caldwell: I’ve also see some conflicts between frameworks. That’s rare, but there are some plugins that use the ProtoType framework, and combined with another framework like MooTools, there is a possibility for a conflict to arise. Rare though, and it’s usually attributed to the way their loaded (i.e. by a bad plugin/theme).

Cristián: Does WP load JQuery already? If so, why do plugins load it too?

Jason Caldwell: Yea, WP already loads it. But some plugin authors don’t know that, or they just hard code it into their plugin not realizing that. Other times they’ll try to include a dependency on jQuery, but they name it wrong, and WordPress gets confused.

Cristián: Does s2Member load it again or uses WP’s?

Jason Caldwell: Hmm, not really, because in the Dashboard, it’s already loaded by WordPress. s2Member enques scripts that is uses, which rely on jQuery being present. In the call to wp_enqueue_script(), s2Member will list jQuery as a dependency, which forces WP to load it, though it’s already loaded in the Dashboard anyway. That’s the proper way to handle it.

On the front-end of a site, s2Member will load jQuery if it’s not already loaded, but again, using the same technique. A call to wp_enqueue_script() with a dependency on jQuery forces WP to load jQuery. If 10 plugins all do it this way (i.e. the right way), WordPress loads jQuery in the proper order and only one time.

Cristián: Ah, got it. I understand WP has a QC team, don’t they check this?

Jason Caldwell: Not in my experience. They look mostly for security issues and really bad code. They usually don’t catch minute details like this.

Cristián: I see. Well, they do look at how the db is used, iirc.

Cristián: I see, but these details do cause trouble for the users. Maybe it’d be good to write an article about JS conflicts as you explained above and post it in the forums, and then show it to the QC guys for consideration to include in their quality checklist.

Jason Caldwell: Yea, that’s a good idea. On the WP side though, they’re aware of this problem, and that’s why they created the wp_enqueue_script() wp_enqueue_style() functions. Although, I wish this were more prominent in this article: http://codex.wordpress.org/Writing_a_Plugin#Plugin_Development_Suggestions

It is mentioned, but it’s all the way at the bottom:

Try not to echo [hilite code]