Please Log in or Create an account to join the conversation.
That sounds like a bug. It should remove them when they unsubscribe. Are you doing this test from backend or frontend? Backend might be a bit wonky in this regard due to a user store and subscription update happening at same time.When I unsubscribe from those subscriptions the user & pass are not removed.
Please Log in or Create an account to join the conversation.
As a part of their subscription, they get access to little programs written in livecode.com coded by another developer. So the subscribers get a link to a folder on a subdomain calling up the index.html file running it's own page/site sourcing assets from that folder. At the time, the .htpasswd method seemed to be the best.As a side note is there a reason you need to use this plugin still? We now offer ways to better access files that don't require using htaccess auth logins, which are not very user friendly. CB Package Builder for example can build out files from directories and CB Gallery supports storage of files so files could just be uploaded and downloaded from there both of which would let you use normal Joomla ACL.
OK, so when I test it, I'm doing it from the admin, I add them to a plan (a paid plan) and then logging into their account using a plugin ( extensions.joomla.org/extension/login-as-user/ ). So this won't activate the password update in the .htpasswd file as I'm not submitting their actual password on the login page. I have now checked this, and I can confirm it is adding their username and password to the htpasswd file.They can only be added to the password file when we're able to get the password in plaintext. So basically when they login, update their profile password, or register (only works with free plans a paid plans move away from registration).
Please Log in or Create an account to join the conversation.
A better solution might be to actually just execute that code from within Joomla and block direct root access to that folder using htaccess entirely. So one way to do this is to use CB Auto Actions. A Code action can be used to do a PHP include of your code and then it can output the results directly inside of Joomla. You can then use ACL on the auto action. Now the user just needs to login to your Joomla site and access your menu item that points to the auto action with no extra work from them and no need to deal with htpasswd problems.As a part of their subscription, they get access to little programs written in livecode.com coded by another developer. So the subscribers get a link to a folder on a subdomain calling up the index.html file running it's own page/site sourcing assets from that folder. At the time, the .htpasswd method seemed to be the best.
Please Log in or Create an account to join the conversation.