Donna Peplinskie (a11n)

the french translation is on line but it is not automatic in the block. i got an error message

Hello. I’m not sure I understand which text is not being translated. Would you mind clarifying? Also, could you please share the error message you received?

Hi @kzncraig,

I can reproduce the error my side.

Are you able to share steps to reproduce? Are you viewing a lesson or quiz when the error occurs?

By looking at the code, I’m guessing that you may have the Classic Editor plugin activated. Can you confirm? If so, can you please share screenshots of the Quiz Settings and Quiz Questions meta boxes for the problematic lesson / quiz?

When I open this file line 38 shows php?comments?within a class called “class Sensei_Lesson {” – not code. So it is very confusing.

In your original message the fatal error indicated the issue was on line 3834, which does call array_rand.

Hi Nicole,

Jetpack is definitely a culprit, other candidates are Matomo and Mailerlite.

Thanks for the additional info. I’ve seen this occur without Jetpack as well, so something strange is definitely happening. For me, a refresh solved the problem.

Given we’re struggling to reliably reproduce this, I’ve created an issue which we’ll use to capture additional reports going forward, and hopefully get to the bottom of it.

back when we had widgets, not blocks, there was a Sensei widget for the modules and lessons of a course (same as is now in the template), and a progress widget (same as the elements x of x lessons plus the progress bar); these could be added to the sidebar. It would be nice to have these available again.

You should already be able to search for and add the “Course Navigation” block to your template. For the progress bar, you’ll need to use the one named “Course Progress Bar” in the site editor. Please let me know if you encounter any trouble with either of them.

Thanks.

Hello Nicole,

Re. Learner Mode Template, I am experiencing issues in the FSE editor:
Your site doesn’t include support for the “sensei-lms/ui” block. You can leave this block intact, convert its content to a Custom HTML block, or remove it entirely.

Thanks for the report! I have seen this issue a couple of times myself as well, but was having difficulty reproducing it consistently. Sounds like you had the same trouble. ??

Basically, I have to deactivate several plugins, including Jetpack, access the template to edit it, and then reactivate the plugins.

Do you know which plugin in particular is the likely culprit?

I am still searching the classic Lesson navigation block.

I don’t recall Sensei having a Lesson navigation block. The only navigation block we have is Course Navigation.

Thanks.

The plugin already has a Release Date field which is the same as your Published field, so you can change the label directly in the editor if you like.

For ISBN-13 and ISBN-10, you can also add those yourself. I’m not going to add them to the plugin though, as I don’t think this is information is generally useful to the majority of users.

Closing as this was fixed in version 2.2.1.

Thanks, this was fixed in version 2.2.1.

I saw there is no lang directory for this plugin. Does that mean it is not ready for translation and so explain why the french is not available ?

No, the lang folder is the old way of doing translations. Now they are handled by www.ads-software.com language packs.

The translation review process is documented here.

Closing.

Hello,

First, ensure the Book Review block is selected in the editor. When selected, you will see ISBN and API Key sections in the Block sidebar. You’ll need to create an API key first via the Google Console (click the link below the API Key field to go there). Once you’ve saved your key in the editor, you can then enter an ISBN and click the Get Book Details button to fetch any details that Google may have about the book.

Cheers.

Happy to hear it’s working for you!

No reply in over a month, so I’m marking as resolved.

Hello,

I’ve just tried creating a child theme named Course Test and my changes were applied without issue. Here are the contents of my child theme’s style.css file:

/*
Theme Name: Course Test
Template: course
*/

 body {
	color: yellow;
	background: black;
}

get_stylesheet_directory_uri() returns https://mysite.com/wp-content/themes/course-test/style.css, which is the correct CSS file.

So I’m not seeing an issue with the code in its current form.

I don’t like you close the post when you answer to it . In 20 years of job, I never saw that,?It is the user who can close the post when he think so !!

I resolve the post once I feel it has been properly replied to. This is because it has a negative impact on the plugin’s ranking in WP.org’s search results when forum posts are left open for too long.

none Gutenberg block need admin rights, only yours and if you agree to the above remark , the API KEY is not in the block , only ISBN with normal rights.

I will consider reinstating the ISBN field for all user roles, however, it probably won’t be for a few weeks. I would like to reiterate that the automated functionality for fetching the results from the Google Books API will still only work for admins.

And I’m marking this as resolved because I feel that I’ve adequately replied to your questions that directly relate to this plugin.

enthalpie,

I implemented this restriction based on your initial feedback in this forum thread. I cannot easily solve the issue with editors not being able to use the API key (due to it being stored in WordPress settings, which editors don’t have access to by default). And if they don’t have access to the API key, then they cannot use the automated functionality to fetch the results from Google Books API using the ISBN either.

Given the functionality doesn’t work for editors, it makes no sense to surface either the ISBN or the API Key in the block settings, so I’ve removed them. They are now only available for admins. Should I find a solution that works in the future, I will reinstate this functionality.

I must say that I don’t appreciate the multiple posts in this thread and your excessive use of exclamation marks to express your frustration. I maintain this plugin in my free time as a hobby, and would suggest that if you aren’t happy with the free level of support I provide or how the plugin works, then perhaps it’s best for you to look for an alternate solution.

Thx.