That error is nothing. Its saying "Went looking for ..../jrCore-release-5.1.41/contri.... but couldnt find it".
Which suggests that the the $_SESSION thinks the latest version is 'jrCore-release-5.1.41' where what it really is after the rebase is 'jrCore'.
So we need the system to use what is actually there, which is /jrCore/
To clear the cache manually on the file side of things, FTP to:
/data/cache
and there will be a bunch of things in there like:
/jrAudio
/jrCore
/jrElastic
/jr......
Its fine to delete all of those directorys if they exist. (I would expect them to have been deleted by rebase.)
Leave the /index.html file there if its there. Just stops anybody getting a directory listing of files in that folder if they look.
To clear the database side of things, the table name is jr_jrcore_cache and can be cleared by either doing it manually via phpmyadmin or the easy way:
FTP into the root of your site, look for the file /repair.php.html rename it to /repair.php and open it in the browser.
you will see:
Quote: Jamroom Database Repair
This script will:
run TRUNCATE TABLE your session and cache tables (which will empty them)
run REPAIR TABLE on all Jamroom database tables
Press the start repair button to begin.
only fair that I help fix it, I built the module. Thought it was all working though. If we find the root cause of this happening, ill add in a check for it.
---
One other thing to check for is that there are files in the modules/jrCore directory. The guess is that perhaps the latest version didn't get copied before the -release-'s were deleted.
That shouldn't happen, but its worth checking.
JAMROOM
