CLUEVO

Hey mlapl1,

we currently have a basic security feature via .htaccess in place. You can activate this on the CLUEVO settings page. What this does is it places a .htaccess file inside the module directory prevents direct access to the files. Someone very determined can probably circumvent this by forging the requests to the files but for the majority of users this should prevent undue access.

We do have something more in-depth planned, but this will need some more time to implement. It will probably be something along the lines of what you mentioned with storing the files outside the root directory. We’re currently exploring options for this though, because this will need to be optional as a lot of users don’t actually have hosting that allows this sort of solution.

Greetings,

Chris

Hi Fihir,

thanks for sharing your module. We’ll run it through our dev environment and get back to you.

Hello adsmar87,

thanks for bringing this to our attention, it seems like the ordering is bugged in the current version. This will be fixed in the next update.

Hi adsmar87,

you should be able to edit the translation with something like locotranslate. Just make sure you backup your translation as updates to plugin will probably overwrite your changes.
And a heads up: We are planning to make the names of the tree levels customizable, we don’t have an eta for this yet though.

If the upload fails on all module types we can probably rule out the missing extension, as only the scorm upload relies on that functionality.
Would it be possible for you to provide us with a WordPress site report? If you are not comfortable sharing this here publicly you can always open a ticket via our ticket system at cluevo.happyfox.com/new

Hi zenoxable,

does this error only concern uploads of scorm modules or do other module types work? A common issue is that the php zip archive extension is not activated. We rely on that to validate and unzip the scorm packages.

Greetings,

the CLUEVO team

I can’t promise anything but I think this will probably be released within the next one or two months.

Hello bextiyart,

thanks for getting in touch and great to hear your liking our plugin. We do actually have an extension in development that provides users and trainers with a dashboard to view their own or their students’ progress. It’s currently in beta testing but shouldn’t take too long to finish up.

Greetings,

the CLUEVO team

Hi zenoxable,

we’re aware of the issue and there should be an update available later today that will hopefully fix this.

Greetings,

the CLUEVO team

Hi molecule1,

yes, we do have a certificate extension that is a paid addon-on to the LMS. I’m not sure how deep into paid stuff we can go here in the forums, but feel free to open a ticket via our support system if you’d like some more details.

Greetings,

Chris

We’ve resolved this via our ticket system. The problem seemed to be related to the hosting company. The user has since changed server and the problem has gone away.

Привет Портасс,

lms не должен создавать пользователей сам по себе. Это похоже на ошибку, которой не должно быть. Если вы не возражаете, не могли бы вы создать заявку через нашу форму поддержки на cluevo.at? Один из наших инженеров свяжется с вами, чтобы разобраться в этом

Hi kjah456,

there should be an option on the CLUEVO settings page where you can enable basic module security. This places .htaccess files into the module directories that disable external access to your modules. A determined person may still be able gain access, but they’d still have to know the path to your module files. Alternatively you can delete the archived module files via ftp as they’re generally not needed. The next version (1.7.0) will allow you to archive and delete archived files via the module ui though.

For video files specifically there is not much we can do at the moment. We use the native browser video player and that generally needs the url to the video somewhere and that can always be read by users. There may be a way to disable right click -> save as but any determined person can still get the url via numerous other ways.

Hey moussa,

this is Chris, I just sent you an e-mail as well. But for others who might be interested: We store the parameter value the module reports, so if a module sets the time to 01:00:00 we store that, if at a later time the module sets the time to 00:00:00 it overwrites the previous value. I have added a new feature to our backlog that let’s you configure how to handle the session time. We’ll try to make it so you can configure the lms to add any module reported session time to the current time or use the reported session time directly.
This feature won’t be ready for the next release though. There are various types of modules out there and we’ll have to do some more planning and testing to get this right.

Greetings and stay healthy,

Chris

Hey Andrew, I’m really sorry this is taking so long, but I’ve been heavily involved in some other projects and I’m having a hard time dedicating the amount of work to this that it deserves.

I’ve just installed both your modules and with the ‘continue’ module I can’t reliably trigger the resume function (prompt inside the module). From what I’ve seen though: This module does not seem to set the scorm parameter for suspend data, we use that to determine if we can let the user resume or start a new attempt. This module seems to store it’s state inside the browser and it looks like it uses that to show the continue screen from within the module independent of any scorm parameters.

What’s happening with the ‘new’ module is, I think, that the module properly sets the lesson_status to completed. On the next attempt the user /should/ be asked whether they want to continue or not, but it looks like the lms skips the prompt because there is no suspend data and defaults to just opening the module with the current scorm parameters. I think the exact behaviour is something that we can probably make customizable through settings. I think there is a case for both defaulting to the current state or just starting a new attempt. Because the way some modules store resume data (like yours in the browser) there is a need to allow multiple ways to handle this. Some modules enter a view-only state when loading them as ‘completed’ and I think this is something people might still want to do.

What I couldn’t replicate were duplicate progress attempts. If I configure to let the user select between resume/start new it always seems to re-use the current attempt. If I configure to always start new attempts I get an attempt for every time I start the module.

Again, I’m really sorry it’s taking this long to get back to you, but it looks like things are improving around here and I can properly dive in again soonish. In the meantime, I’ll start planning to add some settings to customize the behaviour for these cases.

Greetings,

Chris