kalleaume

Thanks for your reply @kasperrander! I appreciate the tip. I’ll check out that plugin also. If it doesn’t solve the issue, perhaps we could look at teaming up and paying a developer to make this code change…

@pierrelannoy, do you have any plans to possibly increase the limit to allow for up to 30 or more? My use case is exactly the same as described above by @meteofun.

@kasperrander and @meteofun, did you ever find an alternative way to set concurrent sessions to more than 9?

Hello, and thank you for trying to help me. Unfortunately, that solution won’t work as I don’t want the profile page to have the URL of ‘login’. I want the page with the ‘profile’ URL to be the profile page and the page with the ‘login’ to be the login page. That’s why I was following the instructions on that post to make a custom login page. I was not wanting to make a custom profile page. I hope that makes sense. Thank you again, and I will try to find another workaround.

My question was about creating a custom login page using the [learn_press_profile] shortcode at a custom URL, e.g. https://example.com/login

As referenced in the first sentence of my post, I followed the instructions from your team about how to set up a custom login page by using the above shortcode. That’s when I found the two issues mentioned above. 

So unfortunately your response doesn’t answer my question. You are saying that the only workaround for the two issues I identified is to not use a custom login page. In that case, why does the [learn_press_profile] shortcode even exist? And why did your team suggest using this shortcode to set up a custom login page??

Oh, I was only aware of the paid version of that plugin that costs US$149 per year. It looks like the free version works but without full screen mode or a lightbox display. I will explore the free version some more. Thank you!

Hi @jessik, can I please ask how you even imported a SCORM package into Learnpress in the first place? I couldn’t find any way to do this.

Hello Golam, thank you so much for making this update! I have installed the latest update on my site and can see that it now has a new setting: ‘Flip Behaviour’, which allows us to choose if we’d like it to flip on hover or on click. I really appreciate your team taking the time to implement this improvement to the block!

I have tested it out on my site using a screen reader (NVDA), and just came across two small issues:

1. The flip box is not announced to the screen reader as “Clickable”. As an example, you’ll notice that in the Accordion block, the clickable accordion item is announced by the screen reader as “Clickable Heading Level 4…”. The same thing would need to be implemented for the clickable Flip Box in order for it to meet accessibility guidelines.
2. The back content of the flip box in announced by the screen reader before the user has even revealed the content by clicking the box. As an example, you’ll notice that in the Accordion block, the content inside the accordion item is not announced until the accordion item is clicked (expanded) to reveal that content. The same thing would need to be implemented for the clickable Flip Box.

If these two things could be updated, then this flip box block would be fully compliant with accessibility guidelines. Thank you again for taking this step to support web accessibility!

Hi Darko, thanks for the update. I can confirm that this is now working perfectly.

@shresthauzwal Actually, I have found that this password criteria does not consistently require 11 characters. It seems to depend on the combination or order of characters selected.

In my testing of 8-character passwords, I could not find any that are accepted. Do you have an example of an 8-character password that is accepted?

In my testing of 9-character passwords, I found that the following password is not accepted:
‘Happy581!’
But this 9-character password is accepted:
‘H5a8p!py1’ (same characters as above, but in a different order).

Are you able to clarify please what the exact password requirements are for a strong password?

• This reply was modified 1 year, 8 months ago by kalleaume.

@shresthauzwal, following on from your post here, I understand that the code snippet you provided above is not compatible with the current version of the plugin (Version 3.0 onwards) as it causes the Auto login feature to stop working.

I’m just updating this thread here so that others following this issue are made aware of the Auto login issue. I have also marked this issue as ‘not resolved’, so that we can mark it as resolved once a new solution is provided. I understand from your other post that you will be updating the documentation here once a solution is found. Would you kindly update us in this thread also once that occurs please?

The code snippet is the same one that you provided here: https://www.ads-software.com/support/topic/use-full-email-address-as-username/#post-16731490 (Also see below)

Looking forward to your response!

add_action( 'user_registration_after_register_user_action', 'ur_insert_username', 1, 3 );
function ur_insert_username( $valid_form_data, $form_id, $user_id ) {
global $wpdb;
$user_email = isset( $valid_form_data['user_email'] ) ? $valid_form_data['user_email']->value : '';
if( !empty($user_email)) {
$wpdb->update(
$wpdb->users,
['user_login' => $user_email],
['ID' => $user_id]
);
}
}

Thanks for your advice. I followed all of these steps and have found the conflict!

The conflict is caused by the code snippet that you provided in this thread which creates the username based on the user’s full email address (not just the first part of their email address before the ‘@’ symbol).

When I deactivate your code snippet, the Auto login feature of your plugin works again! But now this means that that usernames are only created with the first half of a user’s email address. Unfortunately, this means that if ‘[email protected]’ tried to register an account after ‘[email protected]’ registers an account, the form freezes because it detects a duplicate username (as described in the original thread).

So can you please advise how we can have both issues fixed at the same time?

I followed these steps to insert an ‘Organisation size’ dropdown into the form, using this code:

		tml_add_form_field( 'register', 'organisation_size', [
    		'type' => 'dropdown',
    		'label' => 'Organisation size',
    		'options' => [
        		'0' => '0–200',
        		'1' => '201–500',
        		'2' => '201–500',
        		'3' => '501–1,000',
        		'4' => '1,001–5,000',
        		'5' => '5000+',
    		],
			'priority' => 15,
		] );

The field appeared fine in the form, but when the Register button is clicked, nothing happens. That is, no Auto login occurs and and no success message is shown. The registration is successful, even though nothing appears on the screen and the auto login doesn’t work. I know this because when I click the Register button again, it says “Error: This email address is already registered. Log in with this address or choose another one.”

Is the issue because I also need to add a ‘validate’ and ‘save’ function for this field?

Or is the issue caused because this ‘organisation size’ field is unacceptable because it is not one of the standard WordPress user profile fields? If it si acceptable, where can I access the data collected by this form?

When I tried doing this in theme-my-login-custom.php instead of using Code Snippets, it did not erase the fields that I had added. But it also did not remove the Confirm password field.

I tried adding it before and after the add_tml_registration_form_fields function, and had the same result.

Thanks for your reply! I am not sure whereabouts I should be adding this. Should I add it directly after this line of code below?

add_filter( 'registration_errors', 'validate_client_registration_form_fields' );

• This reply was modified 1 year, 8 months ago by kalleaume.