Support Forum

Hello:

Can you clarify - are you saying that someone in pre-sales promised you free customization?

Thanks.

"Simple addition of code" is free customization.  We have a strict policy against writing code for free because its never "simple".  While that may have been something done in the past, its not something we do now - some hard lessons were learned there. So I dug into the email communications to see what was discussed.

What we said to the memberpress question was this:

"For any membership plugin, the answer is the same.  If they use WordPress roles to control their membership then you can control access to the forums using those same roles - including making the forum read-only for some roles and read-write for others."

And that makes sense.  Since we don't have a license for Memberpress nor are we MemberPress experts, we can't provide detailed guidance on what to do on their screens.  Hence the "if" part of that answer. 

So, assuming that the MemberPress plugin assigns normal WordPress roles to users based on their memberships, you can link those roles to Simple:Press.

So, for example, lets assume that you configure MemberPress to assign the WordPress role "PREMIUM" to a certain class of members.  On the Simple:Press side of things, you would go to FORUM->USER GROUPS->MAP USERS TO USER GROUP.

In that screen you should see a section for the PREMIUM WordPress user role.  You can assign that role to a Simple:Press group.  Now, when users are added to that role, it should grant them the membership in Simple:Press (assuming that MemberPress uses the WordPress APIs when assigning roles and not going directly to the WP database).

Thanks.

Hi:

For the issues with clicking and formatting, have you tried clearing the browser cache? Its likely that some old JS or CSS is stuck in there.  The fastest way on most browsers is to use the CTRL-F5 key combination.  It will clear out the browser cache for that site and force the browser to retrieve all elements from the server.

Also, please make sure that you are excluding the FORUM page from all WordPress, Webserver and CDN caching.  Caching that page can also result in some similar symptoms to what you're describing.

If these suggestions doesn't work then we'll have to assume there's a conflict somewhere with another plugin or theme.  I can describe the steps for checking for conflicts if the first couple of ideas above don't remedy the issue.

Thanks.