The error just means Wolf CMS is unable to find data online on what the current version is. You can safely ignore that.

What is your problem? Have you checked and completed all of the settings for the plugin?

Hi, just wondering if you managed to get an update for this plugin or not since it was a couple of months ago now when you posted this? Is it still in development?

Thanks.

Just make a page in the administration panel called "register", and make sure that that page contains the code

<?php ru_register_page(); ?>

There are no real pages created. You create the pages by adding them to the page system and populate it with some Registered Users Plugin functions calls.

The documentation is pretty clear in my opinion. It's all on the about page in your administration backend.

Last edited by s.meijer (2011-12-15 15:54)

after a while trying to implement edit page by role, I found out that Registered users in permission_page is actually storing the role_id ,so the table could be better renamed to role_page...
I was trying to modify the code of RegisteredUsers to do this

If I am correct I would like to make a suggestion for future releases. Maybe change the table name to better reflect this ...

Last edited by trister (2012-02-23 10:59)

You are correct sir. It's a side effect of the CSRF token check that's been added to the logout function to prevent unauthorized logouts. Technically its was a CSRF vulnerability. I was a little hesitant whether I'd treat it as such but decided to do so anyway.

You can temporarily achieve the same effect as the normal logout function by replacing the content of the ru_logout() function in the plugin's index.php by this:

        // Allow plugins to handle logout events
        Observer::notify('logout_requested');

        $username = AuthUser::getUserName();
        AuthUser::logout();
        Observer::notify('admin_after_logout', $username);
        redirect(get_url());

Ok, got it working with recaptcha, turns out it's quite easy.

Here are a few thoughts about this plugin:

Issue 1: Lost pass function doesn't check if a user with the typed address really exists. It sends the mail with a new pass even if there is no user with that email.

Issue 2: Lost pass is not really working, as it just updates the password field and not the salt field. I fixed it by simply emptying the salt in the query, so that Wolf falls back to the simple sha1 password encryption.

Issue 3:  The template parts (on the settings page of the plugin) could use some kind of "template variables", for example the welcome message consists now 3 parts: header text + random key + footer text

// now it's like:
$message = $welcome_email_pt_head . $code_url . $welcome_email_pt_foot;
// I would do:
$message = str_replace('[confirm_url]', $code_url, $welcome_email_body);

Issue 4: I noticed that when I register with an email containing a "+", something goes wrong when confirming. The script creates a user with empty username and email, and it doesn't get deleted from the registered_users_tmp table.