Hello there,
I'm having trouble installing users with a CSV file. However, I cannot register manually. I cannot upload with a file.
Moodle 3.6.3
Have never run across:
undefined method cachestore_dummy::find_by_prefix()
What version of Moodle? and other details about setup ... OS moodledata ownerships/permissions ... etc. ... the typical stuff.
Can see on the bottom box looks like it's trying to purge cache session for current user.
You!!! Interesting.
Go to:
Site administration -> Development ->Purge caches
Try either or bth ... all caches or selected.
Also check ...
Site administration -> Plugins -> Caching -> Configuration
If that doesn't clear the error and sessions still shows.
From command line, go to moodledata/sessions/ and manually remove all files
there. That will kick you out and you'll have to login again.
'spirit of sharing', Ken
We got the error:
"Exception - Call to undefined method cachestore_dummy::find_by_prefix()"
For us the error was caused by having no cache stores in the Caching configuration page
> Site administration > Plugins > Caching > Configuration
In the 'Stores' column the counts were all 0.
To fix it we:
1. Went to the .../moodledata/muc/ folder (via shell or ftp)
2. Renamed the 'config.php' file to 'config.php.old'
3. By doing this the system created a new 'config.php' with default settings
4. When we returned to > Site administration > Plugins > Caching > Configuration screen the following were set
| File cache (Ready) (1 store)
| Session cache (Ready) (1 store)
| Static request cache (Ready) (1 store)
When we added a new user no exception message was displayed and the confirmation email was sent.
Hope this helps.
A big thank you Dom for this solution.
Since updating from Moodle 3.5.4 to 3.5.5, on one of my Moodle sites, the CAS synchronisation task failed with the same error, blocking other scheduled tasks
And i had no cache store defined.
With your solution, the cache where defined, and the error disapeared, allowing all scheduled tasks to run well again
But thinking more, i think Moodle should ensure these cache stores are well defined, or better handle the case when they're not, to avoid such blocking error and things.
Séverin
