I think we need more information, for example:
- Have you created the Membership Options Page?
- Have you created a default Login Welcome Page?
- Have you created a level 0 Login Welcome Page?
- What code are you using to set the level 0 Login Welcome Page?
Thread Starter
Kay
(@edtxreviews)
Yes, all of those things are set correctly. The thing to note is that it WAS working until recently and the three other levels are still working.
Kay,
I realize it’s a pain, but just replying that everything is set correctly isn’t going to help anyone diagnose the problem. If everything were correct, this wouldn’t be happening. My questions were intended as examples of info you could supply; no-one but you can see what you have done.
Since you have another problem about which you’ve opened a thread, I’d suggest sorting that one out first, and see if that fixes this too. If not, then please do come back here with some more info.
Thread Starter
Kay
(@edtxreviews)
I have nothing else to add which is why I’m seeking help, I’m new to this and if you had a specific question I could answer it. But the point is, everything was set up and running fine until a few days ago after I used that members plugin.
If you need more clarity I can tell you:
1. Yes, I have created the Membership Options Page See here
2. Yes, I have created a default login welcome page for all levels.
3. Yes I have created a level 0 Login Welcome Page the slug is 0-welcome-page
4. The code I’m using to set all of the login welcome page redirect (which is what I think you mean here) is done is S2member and it is http://www.eatingdisorderstreatmentreviews.org/%%current_user_level%%-welcome-page
So, the point is, nothing has changed with the welcome page or s2member settings, it appears to be an issue with the roles that got messed up with the membership plugin. There are also a bunch of ccpas left over from the AP Questions plugin that I can’t seem to get rid of.
As far as the other problem you referring to, I’m not sure what your referring to but I have a series of things going on that are independent of this.
OK, let’s take it in steps.
1. If you were using the Members plugin, there’s pretty much no way that that will have messed up anything. I think that’s a red herring. (Of course, if you used another plugin that is not so well known for playing nicely with other plugins, then it could be a different story. In which case, it really would help to know what plugin it was.)
2. The bunch of ccaps won’t be doing any harm unless you are continuing to use them to protect pages.
3. The other problem to which I was referring is the security badge.
4. Have you set the 0-welcome-page page to be protected at level 0? It looks to me as though it’s public.
Thread Starter
Kay
(@edtxreviews)
The o welcome page is set to public and redirected (as the others are) because when I set it to 0 or above it wouldn’t load to the welcome page at all (for all levels) it was like the level permissions were not loading as fast as the page so it wouldn’t work. I had to set up a redirect from that to the landing page I want protected & that has worked well for all the levels until now.
OK, this is the basic problem, and it’s this that you need to fix. What you have effectively created is a system where you are redirecting twice, and that is never going to last. In fact, I’m a little surprised that you haven’t received an infinite loop warning.
it was like the level permissions were not loading as fast as the page so it wouldn’t work.
It certainly shouldn’t be like that. What you are describing sounds like a javascript problem (which is also likely to be the problem with the security badge), while the levels are set before such javascript should be loading.
You need to fix this and set the levels and Welcome pages in the way the plugin is designed to work.
You almost certainly have a theme or plugin conflict somewhere. Your site is running a ton of styles and scripts, which make it difficult to guess the cause, but I’d start by turning off WP Super Cache. Then set up s2Member as it is designed to work. Then test.
If it still doesn’t work, you’ll need to change to a default theme (eg 2015) and turn off all your plugins except s2Member. If it works now, you know you had a conflict.
You then turn things back on one by one and re-test until the problem recurs. Then you’ll know the culprit.
Thread Starter
Kay
(@edtxreviews)
I’ve already disabled all the plug ins several times and for whatever reason the problem persists. I don’t know how to get rid of those errors and google isn’t helpful. I’m going to change the theme tonight and see if that remedies the problem. I’ll update when it’s done.
Thread Starter
Kay
(@edtxreviews)
OK, so I’m back, I went through last night & striped the site down, I disabled each plugin one at a time & changed the theme to the WP standard 2016 theme. I also flushed the cache from the back-end after each action then refreshed the page. I was able to eliminate the “Deprecated TinyMCE error” buy disabling the TinyMCE Advanced plugin but the but the “JQMIGRATE: jQuery.browser is deprecated” wouldn’t budge no matter what.
So here I am tonight, I currently have the following plugins active:
Clicky Analytics
Clicky for WordPress
Democracy Poll
Facebook Video Embed
Forget About Shortcode Buttons
Google Analytics Dashboard for WP
Hide Admin Bar and Toolbar
Jetpack by WordPress.com (Contact Form, Custom CSS, Extra Sidebar Widgets, Site Stats & Widget Visibility)
JReviews
Login-Logout
Nav Menu Roles
Register IPs
Reveal IDs
SEO Redirection
S2Framework
s2Member Framework
TinyMCE Advanced
WordPress Hit Counter
WP Job Manager
WP Symposium Pro
WP Symposium Pro (Extensions)
Yoast SEO
The ones I require are: JReviews, WP Symposium Pro
WP Symposium Pro (Extensions), S2Framework &
s2Member Framework.
I’m fine with using other plugins if one of these stands out as a “problem” or if two of them do the same thing. I just need the features they offer.
So yea… Just a quick reminder of the actual problem… My subscriber/lvl 0 page is not following the s2member protocols (%%current_user_level%%-welcome-page) to it’s landing page.
You are trying to short-circuit the process and it won’t work. It’s unlikely that one of these plugins (or your them) is inherently bad. Instead, the problem is likely to be that there is a conflict between them.
I’m afraid that the only way to address this is what I said before: change to the default them and turn all the plugins off except s2Member. Then test. Then add things back one a at time and test again each time.
I know it’s annoying, but that’s just the way WordPress works.
Thread Starter
Kay
(@edtxreviews)
OK, maybe it wasn’t clear in what I posted above but I’m telling you this is what I did… I was able to isolate the TinyMCE error doing this but NOT the jQuery issue.
Well, first the good news: sorting that out and turning off Super Cache means it’s now possible to see what’s happening on your site.
Now for the bad news: despite what you think, you didn’t strip the site down. The problem is that you have a CDN set up. That is caching all your CSS and JS files, so it’s impossible to know if the error you continue to see is “really” there or just in the CDN cache.
The first thing you need to do is disable the CDN. Only once you know it’s off and not working can you troubleshoot all this. In fact, you should never enable a CDN until you have all your site working the way you want and aren’t planning on adding anything new except content (i.e. no plugins, no PHP code, no CSS, and no javascript.) Doing so beforehand is often part of what’s called premature optimization, and it’s a nightmare to deal with.
Once you are sure that the CDN is off, you need to re-organize everything so that the pages, including the Login Welcome Page, are set up the way that they are supposed to work. Kludges are just that: you need to do this in the manner expected.
If you still have problems, then go back to a vanilla site with just s2Member and the default WP theme. When that’s all working, you can add things back bit by bit — and keep testing! As soon as something breaks, identify the culprit and either eliminate it or notify the developer and wait for a response before going further.
Don’t even think about setting up caching or a CDN until you’ve had everything working 100% for at least a week. Then you can add caching. Wait at least another week before considering a CDN, and add it then only if you’re sure you aren’t going to be making any more changes.
Thread Starter
Kay
(@edtxreviews)
OK, please forgive my ignorance on this one, what is a CDN, and how does it get enabled/disabled?
Thread Starter
Kay
(@edtxreviews)
Actually, is it cloudflare? I looked on my cpanel & it says it’s inactive.
Cloudflare is a CDN, but that’s not it.
I have just taken another look, and it appears you are taking a ton of stuff from fbcdn. I don’t use Facebook, but I am guessing that’s Facebook. So maybe it’s just your Facebook Video Embed plugin. But I thought you said that you had turned all your plugins off, and were still getting problems?
Anyway, try turning that off, and then set up s2Member as it should be set up (i.e. without unnecessary redirects).
