Have helped maybe 3 or 4 ops 'clean up' sites that were formerly hosted with a Moodle Partner ... op/entity decided an MP hosted solution, while good, was not affordable any longer.
That having been said ... most MP's provide a backup of the DB (sql dump) and a tar ball of data directory. Understandable, the code probably contained their special addon stuff and an MP doesn't want to give away the store when a customer cancels.
Have take on a 'pro-bono' type project where op was hosted with Lambda Solutions and op had a tar ball of code directory - along with SQL dump and tar ball of data directory. Nothing wrong with files provided.
Ok, finally the question ... does Lambda Solutions change any core code? Reason I ask, the code directory was moved under git and the first git pull generated some interesting complaints about the first directory it finds .. that of admin ... provided a long list of files that would be changed by git should it continue - which it didn't. :\
Did manage to 'beat it into submission', BTW ... and it did take DB manipulation ... something one attempts to avoid most of the time (am almost certain there is something still lurking in there or just taking up space!)
For those reading ... think a good strategy for leaving a Moodle Partner is to ask the MP to remove any addon/plugin code from their site just prior to cancellation. While the MP still not provide a code directory upon official cancellation (still understandable) at least when attempting to bring up a locally hosted instance, one won't run into such issues.
And, as long as I am at it ... heard it said that 'customers are your best advertisers' ... yep, true ... even customers that leave you. Wonder how difficult it would be for the MP to un-install whatever first before providing an SQL dump. Tell the customer you've gone that extra step even if they didn't ask for that to be done. Part with them where they will still continue to be one of your greatest 'fans' ... and will relate to others, should they be asked, what the MP did to assure their continued use of the core product - minus the special stuff.
Since this has grown ... let me repeat the question on closing ...
does Lambda Solutions change any core code?
Thanks for reading ...
'spirit of sharing', Ken
Hi Ken -
"does Lambda Solutions change any core code?"
I think you'd need to ask them that. I'm sure an ex-client could ask that of them fairly easily.
I do know its not unusual for Moodle Partners to add code to their bases, especially when they supply extra plugins. And many of them also provide Totara, which would have a lot of changes. But, as someone who did that for years, we strove not to change core as it just creates maintenance headaches. That said, when performance improvements, security fixes or other bug fixes were available ahead of official releases, we would often apply them to the code base to make things better for clients.
Using git, you should be able to see any lines of code that have changed as well as the files that have changed. If there is a difference to core, it might be obvious what these changes were for by looking at that.
Thanks for reply ... well, yes, it's always best to go to the source, but the op, in this case, deparated LS over a year ago. So he, not I ... this is probono ... would have to take up that additional chore ... and from what I've been able to determine (so far this has been email only ... that has been a 'chore'), not up to that task - besides ... as a typical user of Moodle, one only wants to know is 'does it work or not' (yes, I know all about making the leap from user to true admin of one's own server).
This for myself ... maybe others ... so there's a git diff? Hmmmm ... need to check into that.
'spirit of sharing'. Ken
It shoud be possible to get git to show you what files changed non-distructively. Just don't use git pull until you know what the situtation is.
In the moodle code folder, try this:
(First look in the provided version.php file, to try to work out which version they started from, let us supppose it is version 2.3,4 so that wouild be git tag v2.3.4.)
git remote add upstream https://github.com/moodle/moodle.git
git fetch upstrem
git diff v2.3.4
If there are no changes, then you can do
git checkout -f MOODLE_23_STABLE
or something like that, to update to the latest code from that stable branch.
If there are changes, then you can do something like
git checkout -b my_custom_code
git reset v2.3.4
git add .
git commit "Original code customisation from MP"
or something like that, to get a git branch of your own, linked tot he right place in Moodle history, and with the code changes.
From there, you can probably do git pull, etc to update.
Many thanks, Tim! Had started digging into it and already confused. :\ But ... Tim to the rescue!
Have had customers moodle on another server since can't connect to the box inside his home connection. The other day, after installing, cleaning up, etc., etc. shared the link with 'customer' and this is what he sent ..
'I wonder whether you can imagine how relieved and happy I am to see the website again. I do miss seeing the front-page water scene thought but I'll fix that in due time.
I made myself unavailable for teaching so that I could devote my working time to completing this project, while I'm still breathing. I believe it's been seven months since I last saw it and as each month passes, the breathing time diminishes.
Thank you for restoring this old sailor's hope.'
Said 'customer' is 78 years experience and the site is donation only and for Fisherman in BC Canada.
So you've played a part in that! And I'll make sure he knows! ;)
Still has some miles to go ... hey, know anyone in BC Canada that host Moodles for very worthy causes? .... Anyone?
Again ... thanks.
'spirit of sharing', Ken
I've worked with few clients hosted at Lambda and, though I never seen the code, their sites are pretty clean from the admin point of view, with a mostly stock Moodle and well-known reliable plugins. They do a have a plugin of their own that does diagnostics and other things; if I recall, it is in local plugins. It's a proper plugin, too, so easy to remove in a generic install.
I'll be interested to see what you come up with.
Also, I don't know of a free hoster in BC, but I know several people in BC in edu who Moodle and they might know of one. Feel free to send me a message with details and I can get you connected.
Not sure now what git's issue was ... tried some things on a copy of original code acquired from Lambda Solutions and didn't find any local plugin (those I sorta expected to find - must have been removed prior to archiving for customer).
Did find one admin account that had special protections me thinks ... didn't remove ... just changed password and EMail address, logged on and didn't find anything 'special'.
Anyhoo ... site is now a 3.1.4+ under git (was a 2.9.4+) and not complaining about anything .... sooooo. ;)
'spirit of sharing', Ken
Lambda Solutions does not change core code. We do have some long-time Customers that might have changed core code many years ago and we continue to Support them, but our policy is to not change core code.
Did see one behavior I"ve not seen before though ... and it was present when the site was 2.9.4+ all the way through the 'moodle march'. When site admin clicked on any links in Site Admin menu, the menu did expand, and the center panel was also populated with the same links in the expanded menu. The center panel thang was the change to behavior observed in all other stock Moodle installs. Present in all themes that I checked. It's a minor thing (I hope).
Of course, I just might have overlooked some new setting also .. and hadn't discovered it ... yet.
'spirit of sharing', Ken