WordPress

From Cyclos4 Wiki
Revision as of 10:00, 9 October 2020 by Sboth (talk | contribs) (Note about custom template when using forgot-pw wizard)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Introduction

If you use WordPress to manage your website, there are currently two WordPress plugins you can use to let your website visitor interact with your Cyclos installation. The first is the Cyclos plugin. This plugins allows users to log in into your Cyclos installation directly from your WordPress website. The second is the Cyclos Users Map plugin. It lets you create a map on your WordPress website showing Cyclos users from your Cyclos installation.

Both plugins can be downloaded from the WordPress plugins repository. At this moment, this wiki page only describes the Cyclos plugin. In the future we might refactor the Cyclos plugin to integrate the Cyclos Users Map plugin.

Quick test

To setup your Cyclos instance to use the Cyclos WordPress plugin, you would follow the Setup Instructions. However, if you only want to do a quick test to see if the Cyclos plugin fits your needs, instead of setting up your own Cyclos instance, you can use our demo Cyclos instance. Of course, this is meant for a quick try-out of the plugin only. To use our demo Cyclos instance, go through the following steps:

Step 1 (Add temporary access client in Cyclos demo):

  1. Go to https://demo.cyclos.org and sign in with login name: wp_admin_demo, password: wp_admin_demo.
  2. Click 'Personal' in the top menu.
  3. Click 'wp_client' under the 'Settings' section in the menu on the left.
  4. Click 'Add'.
  5. Fill in a name, for example: wp_client_abc. It must be a name that does not exist yet, so maybe use your initials.
  6. Click 'Save'.
  7. Click 'Activation code' and Confirm, and copy the activation code you see on the screen.

Step 2 (Setup your WordPress configuration):

  1. Go to the admin part of your WordPress site, logged in as a user with administrative permissions and install the Cyclos WordPress plugin.
  2. Under the 'Settings' admin menu you should see a 'Cyclos' submenu item. Click this.
  3. Go to the 'Connection' tab and fill in the following:
    1. Cyclos URL: https://demo.cyclos.org
    2. Username: wp_admin_demo
    3. Password: wp_admin_demo
    4. Activation code: fill in the code you copied at the end of Step 1 above.
  4. Click Save.
  5. You should now see a green checkmark near the 'Connection status' at the General tab.

Now you can put the Cyclos login form on a Page in your WordPress website, by adding the [cycloslogin] shortcode. See the section Setup the Login form below for details. You should be able to login into the demo Cyclos instance via the loginform on your WordPress website, using one of the demo users available:
Login name: demo, demo2 or demo3, each with password: 1234.

Remember, the quick test is for temporary try-outs only. The access clients will be periodically cleaned up from our demo Cyclos instance. To start using the Cyclos plugin with your own Cyclos instance, follow the Setup Instructions below.

Setup Instructions

After you installed the Cyclos WordPress plugin on your WordPress website, please go through the following steps to setup your Cyclos system.

Setup the connection

First, you need to setup the connection between your WordPress website and your Cyclos system. To do this, you need administer accounts for both.

Step 1 (create access client for WordPress plugin):

  1. Login to Cyclos with an administrator that has sufficient permissions.
  2. Create an acces client: System > System configuration > User identification methods > New > Access client.
  3. Give the access client the name wp_client and the plural name wp_clients and the internal name wp_client.
  4. Under Permission level make sure to select All permissions and it would be a good practice to enable "Allow IP whitelist".
  5. Save the access client.

Step 2 (create admin and admin group for WordPress plugin):

  1. Create an admin group: System > User configuration > Groups > New > Administrators group.
  2. Give the group the name wp_admin_group and save.
  3. Go to the permissions tab (of the group wp_admin_group) and make sure this group has no permissions at all[1], except for:
    1. General: My profile fields > Login name > select "Enable" and "At registration".
    2. General: Passwords > Login password > select "At registration".
    3. General: My access clients > wp_client > select "Enable".
    4. User management: Accessible user groups > select "All groups".
    5. User management: Profile fields of other users > make sure for the Login name to select "Visible" and "User keywords" (or, if another user identification method is used to login the user, please make sure it is visible and has the user keywords option selected).
    6. User management: Login users via web services, make sure this option is enabled.
  4. Save the permissions.
  5. Go to the default configuration (of the network): System > System configuration > Configurations > default configuration > Channels > Web services > User identification methods > Select the access client wp_client (if you are connecting to a specific url use the configuration of that specific url). Save the configuration.

Note:

  1. It is very important to give the Cyclos user no other permissions than needed for the WordPress plugin to work. If your WordPress website would ever get hacked somehow, the hacker would not be able to do much harm within Cyclos because the Cyclos user used in WordPress is very limited.

Step 3 (give permissions to manage the access client):
Now go to the permissions (tab) of the admin you are logged in with: System > User configuration > Groups > Your group > Permissions (tab), and do the following:

  1. Make sure the admin you are logged in with can manage the group wp_admin_group: User management > Make sure "Accessible administrator groups" is set to "All groups" or "wp_admin_group" is selected under "Specific accessible administrator groups".
  2. Make sure the admin you are logged in with can manage the access client: User management > Access clients > Select here all options for wp_client (View, Manage, Activate, etc.).

Step 4 (create user and activate access client for WordPress plugin):

  1. Create an admin for the WordPress plugin: Users > Management > Users > New > wp_admin_group.
  2. Give the user the name wp_admin_user.
  3. Make sure to give the admin a strong password (enough characters and numbers) and remember this password, you will need it later on. Save the form.
  4. Now logout Cyclos (or use another browser) and login with the user wp_admin_user. If you can login successfully (if set, answer the security questions) you can logout again and login with administrator your where previously logged in with.
  5. Go to the profile of the user wp_admin_user.
  6. Assign the access client: User management > wp_clients > Add. You can call it for example: wp_client_1.
  7. It would be a good practice to use the IP whitelist (if you allowed IP whitelist in Step 1). You may have to check your Cyclos log files to determine the exact IP address the WordPress server uses to connect.
  8. Click on: Activation code > Confirm, and copy the activation code you see on the screen.
  9. Go to your WordPress website and make sure you are logged in as a WordPress administrator.
  10. Go to Settings > Cyclos and click the 'Connection' tab. Fill in the activation code together with the other information (use the password and username of wp_admin_user).
  11. Save your changes and the 'Connection status' on the 'General' tab should show a green checkmark. Congratulations, you are done!

Important: In live versions always use https for both Cyclos and the WordPress site!

Setup the Login form

After you have setup the connection, you can add a Cyclos Login form to your WordPress website.

Add the Login form to your website
To add a Cyclos Login form to your WordPress website, you can do one of the following:

  • Create a Page (or edit an existing Page) and add a shortcode.

If you use Gutenberg, you can add a Shortcode block and fill in: [cycloslogin] in the block (make sure to include the brackets).
If you use the classic editor, you can simply type [cycloslogin] somewhere in your text (you probably want this on a new line).

  • Use the Cyclos widget.

If you would like the Login form to be visible on a sidebar in (each page of) your website instead of on one Page only, you can use the Cyclos Widget. Go to Appearance > Widgets and add the Cyclos Widget to the sidebar of your choice. Of course, your theme should include widget positions for this to work.

Now, check your website (either the specific Page containing the shortcode or any page if you used the Widget) to see how your login form looks and make sure to test whether you can login to Cyclos via the form, using a normal Cyclos user (no admin user).

Settings for the Login form
On the 'Login Form' tab of the Cyclos plugin Settings, you can use several optional settings. For example, you can choose whether you want the Login form to have default styling or not. And you can use custom labels in your form if you like. None of these settings are required, though.

Configure login and logout redirect (optional):
If you like, you can configure Cyclos to redirect users to your WordPress site whenever they need to login or logout of Cyclos. The login URL is used by Cyclos to redirect the user when their session expires and a new login is needed, or when the user navigates directly to some URL in Cyclos (as a guest). The logout URL is the URL where the user will be redirected after clicking "Logout" in Cyclos.
Note: admins can't login using the WordPress login form. If you use the login URL redirect setting, please make sure your admins have another configuration, so they can still login to Cyclos.

  1. Login to Cyclos as an administrator (not via the WordPress login form, but via the Cyclos frontend directly) and go to the default configuration (of the network): System > System configuration > Configurations > default configuration.
  2. Display: Redirect login to URL > enter the full URL (including https://) of the page in your WordPress site that contains the login form.
  3. Display: URL to redirect after logout > enter the full URL (including https://) of your WordPress site. This may be a specific page or just the homepage.
  4. Save the configuration.

Additional step if your Cyclos installation uses a custom frontend
If your Cyclos installation uses a custom frontend (as explained in New front-end), you need to use one more setting in the WordPress plugin. In your WordPress admin, go to the Cyclos plugin settings (via Settings > Cyclos). On the 'Login Form' tab, you will see a setting 'Custom Cyclos frontend URL'. Here you can enter your Cyclos frontend URL. If you leave this empty, the plugin will use the 'Cyclos URL' setting in the Connection tab to redirect a user after they logged in. If you enter a custom Cyclos frontend URL, the plugin will use this to redirect the users and it will use the Cyclos URL in the Connection tab for the REST API only.
If you also configured Cyclos to redirect users to your WordPress site whenever they need to login into Cyclos, as described earlier, you can use %s for the sessionToken and %p for the return path variable if you need the redirect to contain this information in another format than the default.
For example, let's say a user is visiting your Cyclos custom frontend on a URL like: https://your-cyclos.org/accounts when their session times out. Cyclos will then redirect them to your WordPress site passing the path the user was on during the timeout in a query parameter 'returnTo' - in this case: ?returnTo=/accounts. In the WordPress login form, the user would enter their login credentials. On succesfull login, the WordPress plugin would redirect the user back to Cyclos, using by default a URL of the format: https://your-cyclos.org?sessionToken=TOKEN&returnTo=/accounts. But your custom Cyclos frontend needs it like this: https://your-cyclos.org/accounts?sessionToken=TOKEN. For this situation you can enter your custom Cyclos frontend URL format in the plugin setting, using %s for the TOKEN and %p for the path variable. In this example you would enter: https://your-cyclos.org%p?sessionToken=%s.

Frequently Asked Questions

I updated the Cyclos plugin from 1.x to 2.x and now something is wrong. What should I do?

The 2.0.0 version of the Cyclos plugin includes some major changes, not all of which are backwards compatible. When you update the Cyclos plugin from 1.1.x to 2.0.0, possible problems are:

  • The website shows [cycloslogin] instead of the login form.

This is probably because the Cyclos plugin deactivated itself after the update. This happens when your PHP version and/or WordPress version are lower than the minimum requirements for the 2.0.0 version of the Cyclos plugin. To check if this is the case, log in into your WordPress admin with a user with permissions to administer plugins. Go to the Plugins screen and look at the Cyclos plugin. If it is not active, try to activate it. When either your PHP or WordPress version is too low, the plugin will deactivate itself again and show you a message explaining which version you have. If you use a PHP version lower than the minimum requirement, seriously consider updating your PHP version, because using an old PHP version can be a security risk. If you use an older WordPress version, also consider updating.

  • The login form on my website looks weird.

You might use custom CSS on your website to add styling to the form. In version 2.0.0, the HTML of the form changed, so you might have to update your custom CSS as well.

  • The login form does not work; I get an error message.

Please check your Cyclos version. We tested the Cyclos plugin with Cyclos version 4.12 and above. If you have an older Cyclos version, the Cyclos plugin might still work, but it might give problems. If you cannot update your Cyclos instance, you might consider using the old Cyclos plugin version.
Also, please check the connection status in the Cyclos plugin settings (Settings > Cyclos in your WordPress admin). It should show a green checkmark. If it does not, please read the Setup Instructions above and verify the permissions are correct for the group the user you connect with belongs to.

If you cannot solve the problems and would rather use the old Cyclos plugin version:

  1. Go to the Advanced view of the Cyclos plugin page on the WordPress plugin repository. Scroll down to the ‘Previous Versions’ section at the bottom of the screen. Select the 1.1.6 version in the dropdown and click Download. Save the zip file on your computer.
  2. If the Cyclos plugin deactivated itself and you have FTP access to your WordPress site: Unpack the zip file on your computer, so you have a ‘cyclos’ folder containing the plugin files. Open an FTP session to your WordPress site, browse to the plugins folder (wp-content/plugins/) and delete the ‘cyclos’ folder that is there. Next, upload the ‘cyclos’ folder from your computer. This way, the settings from the old plugin should still be there. Close the FTP session. Now check the login form on your website and the Cyclos plugin settings in the WordPress admin.
  3. If the Cyclos plugin is still active, or if you do not have FTP access to your WordPress site: log in into your WordPress admin with a user with permissions to administer plugins. Go to the Plugins screen and remove the Cyclos plugin. Note: this will erase the Cyclos plugin settings. If the plugin was active, this is the recommended way, because this will erase the specific settings the new version uses, you no longer want to use. However, if the Cyclos plugin deactivated itself, it did not touch the old settings yet. So in that case, if you can, use the FTP method above, because this will keep the original Cyclos plugin settings from the old version. Next, click New and upload the zip file from your computer. This will install the old Cyclos plugin version. Then, activate the Cyclos plugin and go to Settings > Cyclos. If needed, set up your connection again. This means you will also have to generate a new activation code for the wp_admin_user in Cyclos.

Note that the old Cyclos plugin version will not receive security patches. Therefore, we do not recommend using an old version. Use at your own risk and only if there is no other way.

Users cannot login via the plugin login form. What could be the problem?

If users get the error “The username / password combination is not correct.” even though the correct username and password are used, there might be a problem with the permissions of the wp_admin_user used to connect to Cyclos. The plugin settings show a ‘Connection status’. This should show a green check mark, along with the message that the connection was set up successfully. Still, the permissions in Cyclos may be incomplete. Please check in Cyclos: System > Groups > wp_admin_group (the name of the group the wp_admin_user used for the connection belongs to). Check the Permissions tab. It should show at least the following permissions:

User management
Accessible user groups: All groups
Profile fields of other users: Login Name > ‘Visible’ and ‘User keywords’ should be checked.
Login users via web services: Yes

The plugin tries to check these settings for you and if it finds one of them is incorrect, the Connection status will show an orange exclamation mark, telling you which permission you should correct. But, depending on the Cyclos version, the plugin can not check all permissions. Therefore, if one of the permissions is not set correctly, the plugin might still show a green mark for the Connection status.

If users get the general error “Something is wrong with the login form setup”, please check if your WordPress site is using a caching plugin. If so, check if the error is resolved when you deactivate the caching plugin. If that solves the problem, check the documentation of your caching plugin on how to avoid caching your login page.

Can admin users login into Cyclos via the WordPress plugin login form?

No. They should use their normal Cyclos URL to login.

Can a user login into Cyclos via the WordPress plugin login form when there is a pending agreement?

Yes. The WordPress plugin redirects the user to Cyclos, where Cyclos presents the user the pending agreement.

Can an operator login into Cyclos via the WordPress plugin login form when there is a pending agreement?

No, unless the operator has full permissions. If the operator is part of an operator group, the operator will not have permissions to accept a pending agreement.
Note: In Cyclos 4.12 and earlier, the redirect to Cyclos will result in an error (OperatorWithPendingAgreementsException). When the WordPress plugin setting has a custom frontend URL, there might not be a visible error, but the login will simply not work. This is fixed in Cyclos 4.13.

Can a user request a forgotten password reset via the WordPress plugin login form when a security question is required?

Yes. When you use the WordPress plugin with a Cyclos version of 4.12 or lower, the request for a forgotten password reset in the plugin does not require answering the security question. After the request, Cyclos sends an e-mail to the user containing a link. Only after clicking the link, the user must answer the security question. This is a Cyclos screen; the WordPress plugin is not involved in this.
With a Cyclos version of 4.13 or higher, the WordPress plugin shows the visitor a small wizard, part of which is a request to answer the security question.
Note: If a security question is required and the user did not set this, the user is not allowed to request a password reset. Neither directly via the Cyclos frontend, nor via the WordPress plugin Login form.

What happens when a visitor makes several incorrect login attempts via the WordPress plugin login form?

When a visitor fills in an incorrect password for an existing Cyclos user in the WordPress plugin login form, the Cyclos API request returns a 401 status code and the plugin shows a message that the username / password combination is not correct. When a visitor does this three times in a row, Cyclos changes the user password status to ‘temporarily blocked’. This means the Cyclos user cannot login anymore for 15 minutes. The plugin then shows the message that the user was temporarily blocked by exceeding the allowed attempts.

When a visitor fills in a wrong password with a different username each time in the WordPress plugin login form, or uses a non-existing username, Cyclos also returns a 401 status code and the plugin shows a message that the username / password combination is not correct. When a visitor does this ten times in a row, Cyclos blocks access from the IP-address of the visitor for one hour. The plugin then shows the message that the IP-address of the visitor is blocked by exceeding the allowed attempts.

Note: The number of attempts and the block period can be changed in Cyclos, either in the password type (for attempts with the same username each time) or in the configuration (for attempts with several usernames). The password type can be configured in the global administration, via System > Password types > Login password. Here you can change the “Invalid attempts”, “Invalid action” and “Block time”. The settings in the configuration can be changed in the network administration, via System > Configuration > {Configuration used} > Details tab, by changing the “Maximum user identification attempts (login) per hour” and “After failing login names, block remote IP for” settings.

Note: the plugin sends along the IP-address of the visitor in the login request to Cyclos. This is how Cyclos can determine which address to block, namely the visitor’s address and not the IP-address of the web server running WordPress.

Where can I see what changed in different versions of the WordPress plugin?

To see changes in the Cyclos WordPress plugin, please check the changelog below.

To see changes in the Cyclos software, please check the changelogs on the Cyclos license server.

How do I translate texts in the Cyclos plugin?

The Cyclos plugin uses the general WordPress translation mechanism. This means WordPress will automatically show translations of texts used in the plugin, as long as a translation exists for the active language (locale) of your WordPress site. The translations are kept in a site called Glotpress, where anyone can contribute to translating texts in different languages.

If you find one or more texts in the Cyclos plugin that have not yet been translated in your language, or if you would like to improve an existing translation, please contribute to Glotpress. The WordPress translator handbook contains detailed instructions on how you can contribute.

Note: the old version of the Cyclos plugin (1.x) did not yet use Glotpress. In those older versions you could add custom labels for the login form in the plugin settings. In the new 2.x version of the plugin you can still use those custom labels, but you only have to use those if the Glotpress translation of a label is not to your liking (or not existing yet).

When the Login Form setting to use the Cyclos styling is active, the Cyclos login stylesheet is loaded on all screens in my website. How can I have it load on our login Page only?

By default, when you check the 'Use Cyclos styling' setting on the Login Form tab, the plugin includes the Cyclos login stylesheet on each screen of your website. This way, the styles are active everywhere, which is good if you use the Cyclos Login widget to show the login form in a sidebar throughout your whole site. However, if you use the shortcode instead of the widget and you have the shortcode on just one or two of your Pages, you might not like it that the stylesheet is loaded everywhere. You can change this behaviour in your theme or custom plugin if you use one. For example, let's assume you've put the Cyclos login shortcode on a Page called 'Login'. To have the Cyclos login stylesheet load only on that Page, you could add something like the following to your theme's functions.php or to a custom plugin:

/*
 * Only load the Cyclos login CSS on our Login Page.
*/
function example_conditional_cyclos_login_styles() {
    // On our login Page, do nothing, so the Cyclos login CSS will still be there.
    if ( is_page( 'Login' ) ) {
        return;
    }
    
    // On all other pages, remove the Cyclos login CSS, using its handle: 'cyclos-loginform-style'.
    wp_dequeue_style( 'cyclos-loginform-style' ); 
}
// Add the hook with priority 11, so it will be loaded after the hook in the Cyclos plugin, which has default priority 10.
add_action( 'wp_enqueue_scripts', 'example_conditional_cyclos_login_styles', 11 );

You can use any condition you need. For example using is_page() based on the Page title, Page slug or Page ID and you can also target multiple Pages when you pass an array. See the WordPress developer reference on is_page or the handbook on other conditonal tags.

How do I use a custom template for the login form?

The Cyclos plugin version 2.x uses HTML for the login form that is a bit different than in the 1.x version of the plugin. If you like, you can however create your own HTML template for the login form. To do this:

  • First copy the file {YOUR WORDPRESS FOLDER}\wp-content\plugins\cyclos\templates\login-form.php to a new directory in your theme: {YOUR WORDPRESS THEME FOLDER}\cyclos\login-form.php.
  • Adjust the login-form.php in your theme folder to your likings, with the following restrictions:
    • There must be a div containing all other tags with a CSS class 'cyclos-form-box'.
    • There must be a div with a CSS class 'notice', to show possible errors or messages.
    • The form-tag containing the login form must have a CSS class 'cyclos-login-form'.
    • The form-tag containing the forgotten-password form must have a CSS class 'cyclos-forgotpassword-form'.
    • Both forms must have an input tag of type 'submit'.
    • To handle toggling the login form and the forgotten-password form, they must have a clickable element with CSS class 'cyclos-forgot-link' and 'cyclos-forgot-cancel' respectively.
    • The login form must have input fields for entering the username/email and password with a name property of 'principal' and 'password' respectively.
    • The login form must have a (hidden) field with a name property 'return-to'.
    • The forgot-password form must have input fields for username/email and captcha (if captcha is enabled in Cyclos) with a name property of 'principal' and 'captcha' respectively.
    • The img element in the forgot-password form to store the captcha image must have a CSS class 'cyclos-captcha' (if captcha is enabled in Cyclos).
    • The clickable element in the forgot-password form to let the visitor see another captcha image must have a CSS class 'cyclos-newcaptcha' (if captcha is enabled in Cyclos).
  • Make sure you thoroughly test your new login form and - if you use it - also the forgotten password form before you use your custom template file on your production website.

Note: since 2.1.0 the forgot-password might consist of a small wizard, depending on your Cyclos version. Please check the original login-form.php template and adjust your local version accordingly if needed.

When I enter the Connection information to my local Cyclos instance, I get 'A valid URL was not provided'. What can I do about that?

The WordPress method used to validate the URL, does not accept local addresses by default. Also, it does not accept addresses on ports other than 80, 443, or 8080. If you need to use a local Cyclos URL and/or if your Cyclos URL is on a different port, you can use the 'http_request_args' WordPress filter hook to tell WordPress your Cyclos URL is safe to use.

For example, if your Cyclos instance runs on http://localhost:8888/england, you could add a filter hook in your WordPress website like this:

/*
 * Allow requests to the local Cyclos server.
*/
function example_allow_local_cyclos( $args, $url ) {
    if ( strpos( $url, 'http://localhost:8888/england' ) === 0 ) {
        $args['reject_unsafe_urls'] = false;
    }
    return $args;
}
add_filter( 'http_request_args', 'example_allow_local_cyclos', 10, 2 );

You could place this filter hook in your theme or in a custom plugin if you use one.

I found a bug in the plugin. Can I help make the plugin better?

Yes! The development of the Cyclos WordPress plugin is done in GitHub. If you have the skills and time to fix issues, please follow the Contributing guidelines.

If you don't have the skills or time, you might still consider creating an issue on GitHub. Someone else might be able to fix it. Just make sure you do not use GitHub for support questions, only create issues on GitHub if you found a bug.

I have another question, where do I go?

If your question is specifically about the WordPress plugin, please make a post on the Cyclos plugin support forum on WordPress.

If your question is more about Cyclos, please use the Cyclos forum instead.

Please note that both forums are meant for users helping each other. The Cyclos team can not offer individual support, so there is no guarantee you will get an answer to your questions. If possible, please help others if you can.

Changelog

2.1.0
[2020-10-09]

  • For Cyclos versions 4.13 and up, the plugin will show a wizard to handle forgotten password requests. This also means the login-form.php template contains additional HTML. If you use custom CSS, please check if that needs to be updated.

2.0.0
[2020-05-05]

  • Complete rewrite to adhere to several WordPress plugin coding standards and refactoring of the Cyclos services to use the Cyclos REST API.
  • The Cyclos plugin now requires at least PHP 7.2 and WordPress 5.0.
  • If you used custom translations in the 1.x version of the plugin, they should be migrated automatically to the new custom labels in the 2.x version. You might want to check if they are still needed. The plugin now automatically uses translations from translate.wordpress.org, so if the texts for your language there fit your needs, you don't need to use custom labels in the plugin settings anymore.
  • You can now choose if you would like the login form to use the Cyclos styling (colors, font, sizes) or if you prefer the login form to use the default form styles of your WordPress theme. This will make the login form look like other forms on your WordPress site. But it may not look good on all themes, so if you disable the Cyclos styling on the new 'Login Form' tab in the Cyclos Settings, please check on your website if the login form looks the way you want it to. And if not, adjust your theme accordingly.
  • If you used custom CSS to style the login form, please check how the form looks in the new version of the plugin. The new version of the plugin uses a strongly revised HTML structure for the form elements. Some div-tags were removed, some CSS classes were removed or renamed, so you probably will have to change your custom CSS. If you really want to keep part of the original HTML structure, you can now use your own custom template for the form. Note however that you must use some of the new elements or classes, otherwise the JavaScript that takes care of the form functionality no longer works. Please check the instructions about using your own loginform template and make sure to thoroughly test before you use this on your website.
  • Added redirect URL setting for custom Cyclos frontends. You can now configure a custom Cyclos frontend URL if you use the Cyclos login redirect and have a custom Cyclos frontend.

1.1.6
[2018-10-03]
We added support to go to a specific page in Cyclos instead of the home after a successful login.

1.1.5
[2018-01-25]
We updated the plugin to be compatible with PHP 7.2.

Previous versions
We updated the PHP4 style constructors in WordPress (see https://make.wordpress.org/core/2015/07/02/deprecating-php4-style-constructors-in-wordpress-4-3/) and therefore Wordpress version 4.3 (or higher) is required. If you wish to run the plugin on an older version of wordpress or a php version 5.2 or below please use version 1.0 of our plugin.