At the very least, we need to know the Moodle version and you'll need to enable Debugging (in your case, in your config.php file.
Howard Miller
مطالب مطرح شده توسط Howard Miller
Moodle in English -> General help -> limitation problem with choice activity -> Re: limitation problem with choice activity
از Howard Miller در
I've certainly seen it. There's no "lock out". So if two people complete at exactly the same time they can both be recorded. Even if it exceeds the limit.
Moodle in English -> General help -> Security checks Check all public / private paths -> Re: Security checks Check all public / private paths
از Howard Miller در
You only have vendor and node_modules directories if you have installed dev/test software. Which you wouldn't do on a production site.
Moodle in English -> Hardware and performance -> Redis as session handler or session cache? -> Re: Redis as session handler or session cache?
از Howard Miller در
This is my understanding / experience...
- If you set up Redis as the session handler in config.php, then your session data is stored in Redis. It does not use PHP's native sessions which would be stored in a 'sessions' folder. That folder is not created. Nor will sessions be stored in the database (e.g. MySQL).
- There is no such this as 'caching' sessions. The MUC/Cache has a 'session cache' but that just means caches that have a lifetime of the session. Nothing to do with 'Sessions'. If you see what I mean.
- Returning to the (e.g. MySQL) database, there is a 'sessions' table and this gets populated with the session id, userid and IP address for each user (presumably it's needed for something). However, it does NOT store the sessions if Redis is used. You should find that the 'sessdata' field is NULL.
- If you set up Redis as the session handler in config.php, then your session data is stored in Redis. It does not use PHP's native sessions which would be stored in a 'sessions' folder. That folder is not created. Nor will sessions be stored in the database (e.g. MySQL).
- There is no such this as 'caching' sessions. The MUC/Cache has a 'session cache' but that just means caches that have a lifetime of the session. Nothing to do with 'Sessions'. If you see what I mean.
- Returning to the (e.g. MySQL) database, there is a 'sessions' table and this gets populated with the session id, userid and IP address for each user (presumably it's needed for something). However, it does NOT store the sessions if Redis is used. You should find that the 'sessdata' field is NULL.