Very nice block!

Hi, I'd love to play a bit with this block. But, when I try to obtain OER recommendations, I get the following error: "Retrieving OER data failed: 301 Moved Permanently 301 Moved Permanently nginx". Any hints?

I need to remove the OER service. I just found out that the system it pulls recommendations from has closed

can we use this block for personalizing a user's search or recommending him/her about new courses based upon his/her enrolled courses?????

You could write new services to extend the block to do personalised search. I'm not sure what you mean by "new" courses - the existing courses service might do this for you, or you could do something similar.

What a brilliant block! I can't resist trying this one...!!! This is the work of a creative genius! Do not disturb. Genius at work. I wonder what else you have up that creative sleeve of yours. Thank you jenny Gray. I highly recommend other to use your Recommender Block.

Actually I just found out that the Block was created by Lancaster University Network Services Limited in 2011. Simply, bril.

Yes, that's correct - designed and maintained by the Open University, but originally built by LUNS.

On our sites (using a slightly customised adaptable theme), use of this plugin seems to break things when there is a dock (i.e. when at least one block other than recommender is docked).

A JS error results from something within the call to M.core_dock.init - which causes JS execution to stop, and e.g. edit links within a course to remain inactive.

I can't see any other block except navigation (or simple_nav) calling M.core_dock.init, but I also can't find any docs on how block plugins should interact with the dock, so it's not clear to me whether recommender just should not be calling it or whether that "should" be ok (perhaps all the other block plugins "should" be calling it too?!) and some other interaction is causing it to fail in our case.

Any clues?

Sorry, I should say we're on 3.0.3...

Hi. This plugin supports only old logging type. What to change to code that it will work again on logstore_stantard? We used this and now when updated, it stopped working. We like to keep using new loggin, its more eficient.

Hello,
for anyone interested in using this on more recent versions, you can find the code at:
https://github.com/danielneis/moodle-block_recommender/tree/MOODLE_310_STABLE

please, Do you know what algorithm is used in this plugin?