Page 1 of 2

HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 5:15 pm
by pwallin
Just uploaded the unzipped S2member-Pro folder to /wp-content/plugins, using Filezilla.

Here's what the dashboard looks like now:
afterpro-dashboard.jpg


It also messed up the website. Here's what it looks like after I logged out:

header-post-pro.jpg

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 5:35 pm
by frankjath
Some times plugins may interfere with other plugins. What I would do is disable all plugins except s2members plugin and then reenable them one at a time to see which one might be causing the problem. I have been in a similar situation where two plugins have caused my site to go blank and I could not login to my back end. Hope this helps, let me know the out come.

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 5:54 pm
by Cristián Lávaque
Pauline, try this, see if it helps you viewtopic.php?f=36&t=247

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 5:57 pm
by pwallin
I had to restart Firefox, and now I have no dashboard at all. Will it hurt anything to delete S2memberPro through my site's control panel? That is, if I delete the folder that I uploaded, will everything go back to normal?

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 6:05 pm
by Cristián Lávaque
Yes, the thread I pointed you to explains how to do it. Deleting the folder should be enough.

It's weird that that happened to you, though. I may have been an incomplete upload, or maybe the FTP transfer mode was incorrect when you uploaded the files the first time.

When you say you have no dashboard, is it a blank page or does it at least have the navigation?

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 6:13 pm
by pwallin
It's just this, with nothing underneath:

screenshot_16.jpg

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 6:21 pm
by pwallin
Whew! I deleted the S2member Pro folder and everything came back.

From the directions that I got after paying for Pro, it didn't mention anything about deactivation.

Now that I'm calmer (6 cookies later, thankyouverymuch...) I'll read the directions.

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 6:39 pm
by pwallin
Now that I'm back, I checked the S2member/General Options/Deactivation Safeguards. It was already set to "Yes" (safeguard all data/options)

The S2member that is installed in my wordpress is 3.5.8. Is that the latest version?

Wordpress version is 3.1.2
Theme is twenty ten, with modified header.

I backed up my database.

Anything else I should do prior to re-installing S2member Pro?

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 7:09 pm
by rossagrant
Sounds good to me, give it a try! To be on the safe side, why don't you re download the pro module and then install it.

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 7:26 pm
by pwallin
Where would I find the download link, please?

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 7:32 pm
by rossagrant
Hi!

Simply go to www.s2member.com and login to get access to your downloads.

Grab the pro module again and try reinstalling it! Let us know how you get on!
;)

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 7:50 pm
by pwallin
Nope. Still the same problems. Active plugins include:
Akismet
CalendarPress
Exclude Pages from Navigation
Google Analytics
S2member
Shockingly Simple Favicon
The Events Calendar
Wordpress Database Backup

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 7:51 pm
by pwallin
(see above) - I redownloaded, re-unzipped and re-uploaded S2member Pro

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 8:00 pm
by Cristián Lávaque
Hmm...

OK, when you delete the directory again (or just rename it to save yourself the hassle), try deactivating the other plugins one by one and try s2Member Pro again after each, see if you get it to work properly after one of the others deactivated.

It sounds like a conflict with another plugin if you did all the installation of s2Member properly. Once we locate what the conflict is, we can try to solve it.

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 8:20 pm
by pwallin
I deactivated all plugins. Things returned to normal.

Then I reactivated S2member => messed up again.

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 8:28 pm
by Cristián Lávaque
OK...

Is your s2Member Framework the latest (3.5.8)? When you did the delete/re-upload thing, did you do it with the s2member directory too or just s2member-pro?

And when you upload, is your FTP client set to auto-detect to avoid binary and ASCII problems?

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 8:40 pm
by pwallin
I deactivated all plugins. Things returned to normal.

Then I reactivated S2member => messed up again.

I just noticed that I didn't have the latest update of Filezilla. Did that and am now reuploading the S2member Pro folder.

I didn't see a setting for auto-detect in Filezilla. I'm just using the default settings. The transfers have all been "successful" according to the progress log in Filezilla

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 8:42 pm
by pwallin
Same problem with Filezilla latest update.

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 9:56 pm
by Cristián Lávaque
pwallin wrote:Then I reactivated S2member => messed up again.


s2Member or s2Member Pro? When you deleted/re-uploaded, did you do it with both directories or just s2Member?

This is so weird...

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 10:06 pm
by pwallin
I didn't change anything with S2member - just S2member pro.

Looking at the error messages in the screenshots above, is it possible that the custom header is messing things up? We have the twenty ten theme installed. Otherwise, no other customization.

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 13th, 2011, 10:11 pm
by Cristián Lávaque
It could well be... Why don't you try the default TwentyTen to rule out that possibility?

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 14th, 2011, 5:51 am
by pwallin
I really don't want to mess with my header. All we did was change the image and resize it to be narrower top-to-bottom.

If S2memberPro cannot live with that, then I guess we can't use it.

I'll be away from the computer for the next couple of days. Jason is welcome to go in an look around. (Same login info as I sent earlier this week.)

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 14th, 2011, 6:42 am
by rossagrant
Headers are incredibly sensitive files to edit and if a piece of markup is even slightly out of place or White space is present it can cause issues like this. I expect it is something like this causing this problem. In the next post I'm going to upload a clean twenty ten theme. Install it and activate it see if the problem goes with the default header.

I expect it will and that through editing the size of the header, there is some conflicting/ invalid code.

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 14th, 2011, 6:45 am
by rossagrant
Here's a fresh Twenty Ten theme, latest version.

Re: HELP - Upgrade to Pro messed up my Wordpress

PostPosted: May 18th, 2011, 12:34 am
by Jason Caldwell
I'm not a MAC guy, but I ran a quick search on Google for:
"This resource fork intentionally left blank".
( appears in one of your screenshots )

You might take a look at some of these articles and see if anything jumps out at you:
http://bugs.dokuwiki.org/index.php?do=d ... sk_id=1289
http://mail-archives.apache.org/mod_mbo ... tle.net%3E
http://gigaom.com/apple/disabling-launc ... uarantine/

This sounds like a server issue to me. Possibly a file in the s2Member distribution was inadvertently quarantined by an application and/or malware detection system on your server?