Caching Problem?

Hi,

Any changes to files within the /plugins/simple-membership/views do not get reflected in the frontend.

What type of changes are you talking about?

Thank you

As I said, right now, the folder /plugins/simple-membership/views is empty but the login pages are still being presented correctly.

What I initially did, was commenting out the DIV block of class “swpm-logged-membership” (lines 13-16 in /plugins/simple-membership/views/loggedin.php).

Hi,

As I said, right now, the folder /plugins/simple-membership/views is empty but the login pages are still being presented correctly.

That does not make sense. Can you disable and then reinstall the plugin again. But before you do this, can you create a backup just in case something goes wrong. Let me know what happens once you complete these steps.

Thank you

I know it does not make sense…

Of course, I have removed and installed the plugin before:
– Deactivate the plugin
– Remove the plugin
– Install the plugin through wordpress

No change!
Not sure what removing the plugin is supposed to do. I expected all data and db-tables would be removed. After reinstalling the plugin, though, all my users are still there, db-tables did not get removed or purged, and even my plugin configuration is there.
Is there any way to REALLY remove everything so a completely new install is possible?

I still think it’s a caching issue… the only thing that wonders me: why is your plugin the only one that’s affected?

Hi,

Check to make sure your host is not using any cache system in your server. Are you using Cloudflare or something similar?

Thank you

I am in contact with the hoster who argues they do not support web development. They said, I should get in contact with the plugin support.
I am on a shared server (no Cloudfare).
I told them how disappointed I am… as this looks like a chaching issue.

But speaking of removing the plugin:
Should the db tables get purged and all configuration removed?

By the way:
When calling the file directly (/wordpress/wp-content/plugins/simple-membership/views/loggedin.php), the latest file is viewed. I just pasted a “echo ‘test’;” into line 2… works as expected.
When calling the file through the wordpress system, nothing is shown…

And with this, the hoster argues it’s not his problem.

Hi,

The following path has many files.

/plugins/simple-membership/views

Is there any way to REALLY remove everything so a completely new install is possible?

Try and delete all the tables related to our plugin in your database. But make sure you create a backup first.

Let me know if the above helps you.

Thank you

Sorry for my late reply!

What I did:
– Uninstalled ‘Simple Membership After Login Redirection’
– Uninstalled ‘Simple WordPress Membership’
– Manually dropped table ‘wp_swpm_membership_meta_tbl’
– Manually dropped table ‘wp_swpm_membership_tbl’
– Manually dropped table ‘wp_swpm_members_tbl’
– Manually dropped table ‘wp_swpm_payments_tbl’
– Installed ‘Simple WordPress Membership’
– Installed ‘Simple Membership After Login Redirection’

What I noticed:
– The plugin did not create the pages it created when I installed it the first time
– The plugin’s setting remained. For instance, “settings | Pages Settings” where I set, for instance, the ‘Edit Profile Page URL’ to ‘../membership-login/’ was there. All other settings changed by me are ‘remembered’ as well.

This implies the uninstallation does not work properly, right?

By the way:
I created a fresh user and loged in. Despite of the php-code of ‘/simple-membership/views/loggedin.php’, I still see the altered loggedin.php I created weeks ago.
Again: I can even remove all files within ‘/plugins/simple-membership/views’ and the plugin remains functioning.

To start with, I would like to understand why the plugin’s uninstall does not work correctly. This behaviour prevents an all-fresh installation.

Hi, thank you for providing more information regarding your issue. I have submitted a message to the developers to reply to your question above.

Thank you

Even after uninstallation, (among others?) the following fields within table ‘wp_options’ remain filled:
– swpm_db_version
– swpm-settings (containing all ‘Pages Settings’)
– swpm_private_key_one
– swpm_email_activation_lvl_2
– swpm-messages
– swpm_alr_settings

I found the following in the installation routine:

if (empty($installed_version)) {
  //Do fresh install tasks
  //Create the mandatory pages (if they are not there)
  ...

I will now remove all fields from ‘wp_options’ and install again…

Well, now the mandatory pages were created and ‘Page Settings’ are fresh as well but the rendered view of, for instance, loggedin.php remains as is and no code changes I make in this file gets reflected in the browser.

The database only holds the critical membership info and settings configuration. Those will not get deleted if you delete the plugin. This is to make sure someone doesn’t lose all their work if they accidentally deactivate and delete the plugin. You can manually delete the DB tables if you want. The DB tables DO NOT affect any PHP or CSS file customization related issues. Not seeing the changes on the front-end after you update PHP or CSS means you have some kind of caching happening somewhere. That is external to this plugin.

After seeing the response from your host, I can’t see how this will get resolved. So better to delete this one and try a different plugin. Hopefully another plugin will work better with your current server environment.

Thanks for your feedback.
After hours of testing, I have found the following workaround:
– I moved the files “loggedin.php” and “login.php” one level up
– I changed the login() function in ‘class.simple-wp-membership.php’ to load the moved files:

if ($auth->is_logged_in()) {
   //Load the template for logged-in member
   SwpmUtilsTemplate::swpm_load_template('../loggedin.php', false);
} else {
  //Load the login widget template
  SwpmUtilsTemplate::swpm_load_template('../login.php', false);
}

With the files in the new location, every change gets reflected instantly; just as expected.