StevenP94

thanks, meanwhile I used a workaround:
// register_uninstall_hook(FILE, [$this, ‘uninstall’]);
register_uninstall_hook(FILE, ‘uninstall’);

I don’t know if is correct but is working while waiting for a new release.

thanks for your support

Hi Joseph,

Some messages are translated and some not. For example the title of the course builder is:

Course information

Fill out basic information about a course to make it attractive to potential students.

but the label of the course name is correctly translated in italian (my language) as:

Nome corso

The placeholder inside the field instead is still in english:

Enter course name

and the validation is in english (This field is required)

Sample image https://ibb.co/1Xv5z7j

• This reply was modified 1 year ago by StevenP94.
• This reply was modified 1 year ago by StevenP94.

Hi,
I can see how to use Custom Fields in your new Course Builder here https://docs.stylemixthemes.com/masterstudy-lms/developers-guide/course-builder-custom-fields the problem is that there is no date fieldtype. How to add a date field with a calendar?
For further customization, the new Course Builder is using the language files ? I see that something is translated and something not.
Thanks in advance.

In addition: I can see how custom fields are managed, there is a way to have a date type with calendar?

Hi, thanks for your kindly reply. There is a way a simple way to add some custom fields into course? I use them a lot!

You’re welcome!

My environment:
Apache/2.4.41 (Ubuntu)
PHP 7.4.3
WordPress 6.1.1

This happens on remote host, probably when someone try to get access and is not authorized (security drop the connection).

$session->get_data() returns null but $session is not null.
I think that my solution can be a ‘safety’ change that increase the code solidity, just don’t know if there is something better, I’m not so experienced in PHP

Thanks for your time

Yes, it seems so

I’m happy to see that my changes was implemented into current version of plugin (2.4.1)
No ‘thanks to StevenP for this’ neither a line on changelog, but the important things is that there is no need to make manual changes anymore.

I’m happy this worked!
I hope they will implement this in future versions

I’ve changed this:

Integration/Plugins/ContactForm.php

line 323 (for the _mail part)

   ====>        if ( empty( $matches ) ) {
                        return;
                }

changed in

		if ( ! empty( $matches ) ) {
                        return;
                }

and then
line 426
$value = $this->getAcceptedDate( isset( $data[ $this->getFieldTag() ] ) && $data[ $this->getFieldTag() ] === 1 );
changed into
$value = $this->getAcceptedDate( isset( $data[ $this->getFieldTag() ] ) && $data[ $this->getFieldTag() ] == 1 );

In this way the tag for the mail part works, and the gdpr acceptance is displayed
Hope that this can help

• This reply was modified 2 years, 2 months ago by StevenP94.

Great!
Just hope that there is a better way than the foreach to get the correct tag, I’m not so usual to work in php.
I’m really happy that this solve the problem.

Thanks for your work on this amazing plugin!

I found a patch: inside ‘skip_validation_for_hidden_fields’ instead of passing the field name to new validation, the corresponding element of $tags should be passed.
I’m not so skilled in php so this is a rough soultion, probably cen be better implemented

foreach ($invalid_fields as $invalid_field_key => $invalid_field_data) {
                if (!in_array($invalid_field_key, $this->hidden_fields)) {
                    foreach ($tags as $tag) {
                        if ($tag['name'] === $invalid_field_key) {
                           $return_result->invalidate($tag, $invalid_field_data['reason']);
                        }
                    }
                }
            }

but in this way all works as it should

Hi, thanks for your reply. At this moment I can’t use your solution because my plugin was written just to test this issue and I can’t modify the wp-gdpr-compliance plugin that suffers of this problem.
I hope that further changes in upcoming version will solve this problem. I’m still diving in code triying to figure what is the problem and how to solve it.
I’ll write here if I’ll found something.
Thanks for now

@jules-colle Thanks for all your work, have a nice vacation!