PriMoThemes

I’m sorry, we ask that you submit questions regarding s2Member’s functionality in our official support forum for s2Member: https://www.primothemes.com/forums/ucp.php?mode=register

I’m sorry, we ask that you submit questions regarding s2Member’s functionality in our official support forum for s2Member: https://www.primothemes.com/forums/ucp.php?mode=register

I’m sorry, we ask that you submit questions regarding s2Member’s functionality in our official support forum for s2Member: https://www.primothemes.com/forums/ucp.php?mode=register

I’m sorry, we ask that you submit questions regarding s2Member’s functionality in our official support forum for s2Member: https://www.primothemes.com/forums/ucp.php?mode=register

I’m sorry, we ask that you submit questions regarding s2Member’s functionality in our official support forum for s2Member: https://www.primothemes.com/forums/ucp.php?mode=register

I’m sorry, we ask that you submit questions regarding s2Member’s functionality in our official support forum for s2Member: https://www.primothemes.com/forums/ucp.php?mode=register

Thanks for the reply.

It can be accomplished in WordPress? like this.

<?php
$user_id = "123";
/* ^The User's ID. */
$user = new WP_User($user_id);
$user->add_cap("new_capability");
?>

These examples may also help you.

<?php
$user->remove_cap("old_capability");
print_r($user->allcaps); /* All Capabilities array. */
?>

Thanks for bringing this to my attention Cristián.

Hi there Elizabeth.
I was saddened to hear about the trouble you encountered with database connectivity on our web sites. This sounds to me like it may have had something to do with a temporary issue affecting some nodes on our server cluster. Can you confirm please that you are now able to access our web sites? If not, please reply back and we’ll take a closer look at your specific accounts to ensure nothing is affecting IP connectivity.

I’m sorry, we ask that you submit questions regarding s2Member’s functionality in our official support forum for s2Member.
https://www.primothemes.com/forums/ucp.php?mode=register

If you are having trouble receiving the email confirmation link, please send an email directly to our support dept. using this private contact form: https://www.s2member.com/contact/

* Note. There is nothing jumping right out at me about your configuration that sounds like anything is misconfigured. You might try this same configuration with the default WordPress theme and no plugins just to make sure you’re not dealing with a plugin conflict somewhere.

If this problem continues, please write directly to support and we’ll investigate this further for you. https://www.s2member.com/contact/

Thanks for reporting your experience with s2Member. Can you please post your question here? We’ll be happy to help you: https://www.primothemes.com/forums/viewforum.php?f=4

In the mean time, you might try re-installing the latest version again. It sounds like you still have some files in the /wp-content/plugins/s2member/ directory from your previous installation.

Thanks for the kudos!

Thanks for the kudos Tom!

Thanks for the kudos!

Quick Cache is extremely reliable, because it runs completely in PHP code, and does not hand important decisions off to the mod_rewrite engine or browser cache. Quick Cache actually sends a no-cache header ( yes, a no-cache header ) that allows it to remain in control at all times. It may seem weird that a caching plugin would send a no-cache header :-). Please understand that the no-cache headers are the key to the whole concept behind this plugin, and they will NOT affect performance negatively. On the contrary, this is how the system can accurately serve cache files for public users vs. users who are logged in, commenters, etc. That is why this plugin works so reliably.

== ‘Quick Cache’ vs WP Super Cache ( Main Differences ) ==

* Quick Cache uses a combination phase ( with less code ) and NO mod_rewrite rules ( no .htaccess file is required ). Super Cache requires an .htaccess file with mod_rewrite rules that serve GZ files. Quick Cache works right out of the box, so it is MUCH easier to install. All you have to do is activate the plugin and enable caching. All of its other options are already pre-configured for typical usage. Using an .htaccess file is 100% optional, and it’s for GZIP compression only.

* Quick Cache provides a complete set of decision engine options for its entire methodology. Super Cache offers On, Half On, and Off. It has fewer options on the back-end panel. Even though Quick Cache is pre-configured for typical usage, it is important for a site owner to have full control at all times. Even those advanced settings that tend to scare novice users away; those have all been included with Quick Cache. Quick Cache teaches you advanced techniques with its examples and built-in documentation for each option.

* Quick Cache maintains absolute control over who sees cached pages. Super Cache allows browsers to cache - the - cache. In other words, some control is lost, and people who ARE logged in may see (not-logged-in) versions of pages. This technique gives Super Cache its name though. It makes things Super Fast. However, that may not be practical for some database-driven sites that are updated all the time and have lots of different plugins installed. If you offer membership or provide special content for members, you may want to try Quick Cache.

* Quick Cache provides you with the ability to customize the Salt used in cache storage. Super Cache does not provide this capability. It could be done with instruction, but you would need to dig into the code for that. The ability to easily customize the Salt used in cache storage is very important. Many sites offer unique services and serve special versions of certain files. The ability to control how different versions of pages are cached, is critical to advanced webmasters that need to tweak everything and customize the caching engine to their specific needs.

Just a minute after I posted this I ran into an error where it was displaying the cached pages of ME logged in to any user who visited the page. So there’s something weird going on with the logged in user caching and I had to disable that. Which means that the site will run fast for any casual visitor, but still slower for any of us who comment or log in. Frustrating!

Yea, I don’t recommend turning that option on. Depending on your theme, and other plugins that you have running, this can have negative results.