latest stable versions: v150827 (changelog)

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

About: Jeff Starr

Sorry, I've not written a description yet. I'll get to it soon!


My Latest Replies (From Various Topics)

Viewing 16 replies - 1 through 16 (of 16 total)
Author Replies
Author Replies
Posted: Tuesday Nov 19th, 2013 at 4:47 pm #61232
Jeff Starr
Username: JeffStarr

Thank you Dan that’s very helpful. To reciprocate, here is the response and workaround that the s2 team shared via their new private support system:

====

A recent update to s2Member changed the way s2Member loads the CSS/JS so that it’s more efficient. Unfortunately, in a few cases, such as when the Pro-Forms are called with the do_shortcode() function, this causes problems.

If you call do_shortcode() from a Post/Page that’s not a problem. The problem comes in whenever do_shortcode() is called from a custom PHP include file or WordPress template file.

s2Member has no way to auto-detect and lazy load under this scenario (at least, not yet). For now you can revert to the old behavior like this:

Inside the following file, /wp-content/mu-plugins/s2-hacks.php, add:

<?php add_filter('ws_plugin__s2member_lazy_load_css_js', '__return_true'); ?>

====

I’m using this at one of my sites and it seems to be working great, so another potential solution.

Thanks again!

Posted: Tuesday May 21st, 2013 at 3:06 pm #50303
Jeff Starr
Username: JeffStarr

Thank you Bruce, that is very informative and helpful. It sounds like everything will be okay and that the URL variations in the log files aren’t an indication of an issue in and of themselves. I’ll continue forward while keeping a close eye on things. Thanks again.

Posted: Tuesday May 21st, 2013 at 5:15 am #50276
Jeff Starr
Username: JeffStarr

Yes I understand what you are saying, thanks for taking the time to help us understand.

Where a problem runs into is where your site is actually located at http://example.com/wp/, but you have your site’s URL set to http://example.com/,

Is this explained to potential s2 customers somewhere? (I haven’t seen it) As mentioned, a LOT of s2 customers will need to know about this issue, as the subdirectory/root configuration (as described) is very common. I’m glad to post and tweet about this if it will help get the word out.

…where s2Member attempts to connect to your site by grabbing the Site’s URL, and is sent to something like http://example.com/wp-login.php when it should be sent to http://example.com/wp/wp-login.php.

I use .htaccess to redirect all requests for wp-login.php to the correct file (which may explain why s2 seems to work fine); so which additional URLs is s2member looking for that could be redirected to the actual file? If there are only a few, perhaps this could be a simple workaround for people who are in this situation.

Posted: Tuesday May 21st, 2013 at 4:41 am #50263
Jeff Starr
Username: JeffStarr

Thanks for the response.

So based on what you are saying, installing WP in a subdirectory and then setting the “WordPress Address (URL)” to serve WP from the root directory (i.e., example.com) is an issue? Can you elaborate?

I find that surprising because such configuration is very common among WP sites.

It’s also surprising because there are no errors and s2member is working fine on several sites where WP is installed in a subdirectory (example.com/wp) and served via root (example.com).

But if that is the case, is there a workaround or way to resolve whatever issue you’re referring to? Otherwise, it sounds like s2member isn’t suitable for subdirectory installations of WP, which of course would mean a LOT of customers would be effected.

Thank you again for your help.

Posted: Thursday May 16th, 2013 at 3:06 pm #50084
Jeff Starr
Username: JeffStarr

For “WordPress Address (URL)”, I have this:

http://example.com/wp

And for the “Site Address (URL)”, I have this:

http://example.com

Is this why I am seeing the two different URLs in s2 logs? AND more importantly, is it normal and/or OK for s2member? Usually such discrepancies indicate or lead to issues. Just want to make sure nothing needs changed before going live with the site.

Thanks for your help.

Posted: Thursday Apr 11th, 2013 at 8:35 pm #47256
Jeff Starr
Username: JeffStarr

Thanks Eduan. I had posted the same question in another forum and Jason helped to clarify things. I appreciate all the work you guys do with s2member, thank you for your continued support.

Posted: Tuesday Apr 9th, 2013 at 4:53 pm #46940
Jeff Starr
Username: JeffStarr

That is what I needed to hear, thank you Cristián! :)

Posted: Sunday Apr 7th, 2013 at 8:44 pm #46827
Jeff Starr
Username: JeffStarr

Yes, that is very helpful, thank you.

To further clarify, I have disabled logging via s2member, but I also want to restrict permissions on the server. Unfortunately doing so results in s2member displaying this warning:

Permissions error. The security-enabled logs directory (/wp-content/plugins/s2member-logs) is not writable. Please make this directory writable (chmod 777).

So I guess it’s normal that s2member needs write access even if logging is explicitly disabled..? It seems that it would make more sense to not display that warning when logging is disabled.

In other words, users should be able to lock down permissions on the log directory when it’s not being used for anything. Seeing that warning implies that some log activity is still happening even when it’s explicitly disabled. If not, then why is s2member concerned about the permissions of the log directory?

Thank you for any further insight into this :)

Posted: Saturday Apr 6th, 2013 at 3:35 pm #46777
Jeff Starr
Username: JeffStarr

Hi Eduan,

Thank you for your reply.

Please, let us hear your response for both of the two scenarios you mention. Both scenarios are likely to be encountered by s2 users, and thus both will be valuable to help the community.

Thank you!

Jeff

Posted: Friday Dec 21st, 2012 at 2:16 pm #35266
Jeff Starr
Username: JeffStarr

Hi Jason,

Thank you for the infos! Good to know I didn’t break anything by deleting 1000’s of s2m transients. I didn’t think it would be a big deal to delete them, but this thread led me to think otherwise: http://www.s2member.com/forums/topic/transient-s2m-orphaned-options/

..there, Bruce says this:

It would be unwise to delete transient data of any kind (especially s2Member’s IPN transient data), as it is important for the time that it is there, and when it’s not needed WordPress will delete the data automatically.

Further, when searching for answers or clues to this issue, that Bruce thread is the only thing available. Hence this new post to clarify. Hopefully it helps others in the same situation.

Posted: Wednesday Dec 19th, 2012 at 5:46 pm #35104
Jeff Starr
Username: JeffStarr

Thanks for the information, Cristián. I went ahead and deleted all 4,310 of the s2m transients and everything seems to continue to work great. I’ll report back if anything weird happens or if something breaks.

Note to anyone reading this thinking about deleting their s2m transients: make a backup of your options table and entire database before deleting anything, just in case.

Thanks again for the help.

Posted: Tuesday Dec 18th, 2012 at 3:31 pm #34964
Jeff Starr
Username: JeffStarr

I’ll try to do as much of the troubleshooting as I can and as time allows.

I just hope that s2m isn’t using transients as long-term storage. At some point the transients should be fine to delete, I just need to know when that is.. for example, all of the users have registered and successfully created accounts, so why are the transients needed after that point? From the WP Codex:

WordPress Transients API, which offers a simple and standardized way of storing cached data in the database temporarily by giving it a custom name and a timeframe after which it will expire and be deleted.

Based on this, at some point it should be fine to delete all of the s2m transients.. ultimately they are meant to be temporary, correct?

Posted: Sunday Dec 16th, 2012 at 11:44 pm #34804
Jeff Starr
Username: JeffStarr

Thanks for the reply. Yes everything (cron, user registration, etc.) is working perfectly fine with no issues whatsoever.

The information you posted is interesting, but does not resolve anything. What I need is a actionable way to remove the 4000+ (and growing) transients from my database table. They are consuming an ever-increasing amount of space that will eventually cause serious problems.

Please let me know exactly how to remove the transients from the options table, or other solution for resolving this issue.

Thank you for your help.

Posted: Friday Aug 17th, 2012 at 12:11 am #22296
Jeff Starr
Username: JeffStarr

Hey guys,

Apparently a protected post/page is an s2 requirement, so my workaround won’t work.

How do I stop the registration notification from happening, or how do I prevent the URL fields from being auto-populated?

Thanks for any help!

Posted: Thursday Aug 16th, 2012 at 1:44 pm #22265
Jeff Starr
Username: JeffStarr

Correct, I remove one or both of the notification URLs and they keep coming back. I’ve tried everything including the save button (lol) but no luck. I thought Jason might have a way of either disabling one of the notifications or preventing the auto-inclusion of the affiliate URL.

An easy workaround/solution is to let WP handle access to the “Specific Post/Page” in question, but I would rather let s2Member do it if at all possible..

So to sum up: How do I disable/prevent one of those API Notifications from happening?

Posted: Sunday Jun 24th, 2012 at 6:35 pm #17309
Jeff Starr
Username: JeffStarr

Hi – just an update that this was user-error on my part. Everything is working fine no reason to respond. Please mark this case as resolved and Thanks for an awesome plugin :)

Jeff

Viewing 16 replies - 1 through 16 (of 16 total)

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

Contacting s2Member: Please use our Support Center for bug reports, pre-sale questions & technical assistance.