Community Support Forums

Using S2 for membership options and SimplePress for forum at http://arts.uk.net/members-area/forums.

The page displays perfectly when the user is logged in. But when user is not logged in a block of inline css jumps in and breaks the page style sheet.

Here's the source from the correct setting of the page title to an h1 to the line of the S2 CSS that forces the page title back to 12px and strips out the bg image from the header block. I don't think this code has any business being there, there is no S2 content on this page, although there is of course a status check that has run prior to content load. Can you tell me please what is going on here?

<div id="PageOverlay">
<div id="PageOverlayContent">
<div class="contentArea">
<h1 class="pageTitle">Forums</h1>
<div class="pageIcon"><img src="http://www.arts.uk.net/wp-content/themes/parallelus-traject/images/icons/coffee-icon.png" width="" height="" alt="Forums" /></div>
</div>
</div>

</div> <!-- END id="PageOveraly" -->

<div id="Showcase">
<div id="ShowcaseContent">
<div class="contentArea">
<h2 class="pageTagLine">Forums for Members and Guests</h2>
</div>
</div>

</div> <!-- END id="Showcase" -->


<div id="MainPage">
<div id="MainPageContent">
<div class="contentArea">

<div class="breadcrumbs" >
<a href="http://www.arts.uk.net">Home</a> <span>&nbsp;\&nbsp;</span> <a href="http://www.arts.uk.net/members/">Members</a> <span>&nbsp;\&nbsp;</span> Forums </div>

<link rel="stylesheet" id="fluency-login-css" href="http://www.arts.uk.net/wp-content/plugins/fluency-admin/resources/wp-login.css?version=2.3.2" type="text/css" media="all" />
<style type="text/css">#login h1 a { background-image:url(http://www.arts.uk.net/wp-content/uploa ... artsuk.png) !important; }</style>
<script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/1.4.1/jquery.min.js"></script>
<script type="text/javascript" src="http://www.arts.uk.net/?ws_plugin__s2member_js_w_globals=1&amp;no-cache=5b396d6f6f72b421b2fcb0ed759aaa80"></script>

<style type="text/css">
html, body { border: 0 !important; background: none !important; }
html { background-color: #FFFFFF !important; }
html { background-image: url(http://www.arts.uk.net/wp-content/plugi ... ges/bg.png) !important; }
html { background-repeat: repeat !important; }
body, body * { font-size: 12px !important; }

I'd really appreciate a response to this one. This is the first direct confict I have found between S2Member and SimplePress forum. It would be a shame to have to find an alternative to either of two plugins that normally play very nicely together. I realise that there might be a theme issue lurking in the background but the principle at least seems clear.

S2, which has no exclusions set for the forum page, is checking if the user is logged in and finding that to be negative is inserting its CSS, expecting to be controlling the login. But because the login is not required to view the page, it is simply producing an overriding css style to the forum itself. What I don't understand is why it is trying to do this at all and how to stop it.

Feedback please

I think that because s2Member login may be implemented through a widget, the plugin drops its css 9and js) up front 'just in case' the widget is included later on (in a sidebar for instance). I've seen this in many plugins - as soon as oyu include them and activate them they'll start adding their own css/js to your pages, even those where their UI aspects may not appear.

Even if that's the case, I suspect there may be ways around the issue. I see you have some "!important" clauses in the CSS already (which was going to be my first suggestion). If that doesn't fix it... well, we got to figure out the actual conflict.
When you're looking at the page (in the scenario where there IS a problem) and you "Inspect Element" on the title element, which CSS rules are kicking in? (Chrome, Firefox with Firebug make this discovery easier).

I tried going to that page and finding out myself, but Members Area > Forum got me to a page entitled "Redirected" (rather than Forums, as in your example) and that title didn't seem to have any s2Member rule applied...

Thanks for this Francesco. You are correct, the problem does not appear when the visitor is logged in, and at present the page is set to require login to view, which avoids the problem. I will disable this for a while. I have something else that I am going to try to get rid of the problem but have to deal with some other sites before I can get back to this issue.

I am sure your assessment of the behaviour is very close to what is happening.