hi,
i wish to make visible a course only in our house, so only from our stable IP address. (Let's say it is for a internal-dev until the course is ready to be "external"...)
we can't afford to have 2 moodle servers (1 for prod, one for test&dev), so it is the only way i think about.
is there any solution to do that ?
it would be a great help if we can add a filter to anything (users, courses, categories,groups...) by ip address.
thanks for help or suggestion.
Not at course level.
But there is this plugin:
https://moodle.org/plugins/auth_ip
can't afford to have 2 moodle servers
but is server hosting capable of virtual apaches - two moodle instances by
a different FQDN? IF so, one could have dev.site that's not in DNS
Persons needing to use dev would need an entry made in their host file
that maps ip address to none existent in DNS FQEN of the dev.site.
How many persons would need access to this course before it went live?
And from where are those folks accessing this under-development course?
What abilities would those persons need?
What If one were to create a special roll ... devsonly ... and then grant that role capiblities to see hidden courses, etc.?
One does options but one size doesn't fit all ... catch 22's etc.
'spirit of sharing', Ken
thank you for your reply.
Activities can have a date AVAILABILITY filter.
it would be super to have an IP AVAILABILITY filter in courses, activities level.
Activities can be available with hidden feature too, it would be perfect if the courses could be hidden but been accessible when we (us, the testers, administrators) know the url...
Best regards.
Pierre
Why not just hide the course? Anyone enrolled as a teacher or above will still see it “greyed out” and will be able to access it and edit content, but it will be invisible to learners and guests - see https://docs.moodle.org/36/en/Course_settings#Course_visibility
I usually go one further and have such hidden courses in a hidden “In Development” category, and move them to their proper category when everything is finished and it’s ready for students.
This was one thing I never saw improve from moodle 1.8 to 3.1 (SLT moved us to canvas a couple of years ago, so we didn't put any time into upgrades beyond that).
What we found was that if we 'hid' a course, so only staff to get to it, moodle's built in 'should this user see this hidden course / activity / resource' check was occasionally refusing staff the access to it. So we switched to using the enrol_auto plugin which let us say 'if this user is a member of staff, let them in' (by looking at certain user attributes in their profile - we have the Staff or Student flag in AD, and the LDAP connector is set to pull the most recent value of this flag in every time someone logged in to moodle). It's a great plugi
