I must have spent at least a dozen hours trying to get this module to work. I've installed different versions, installed Mahout and Async, run crons, enabled all 4 Views, edited Views, enabled blocks...this is all one server. I've run this on four different browsers but still cannot see the recommend Blocks. I changed it to where I can see the Blocks even if there is no information in the Blocks and I still cannot see the Block Title. I've cleared Drupal and browser cache. I cannot think of a single thing that I have not tried other than signing up for a second hosting plan and running Recommend API on it.

Please help. Thanks.

Comments

danithaca’s picture

danithaca commented
Status: Active » Fixed

A few points from the developer:
1. you have to use this module together with one of the helper modules such as "browsing history recommender" to make it work.
2. you need to have at least some data (e.g., browsing history) so that the algorithm can compute recommendations on.
3. i'm working on a new release 7.x-5.x, so it's not likely that i'll provide a single fix for this (if there's a bug). the new release is expected to get finished somewhere around March/April as i'm working on my dissertation to graduate.

other people have reported being able to run it though. i'd recommend you to check back in March/April. thanks for trying.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

cheyer’s picture

cheyer commented

I would like to give some other hints as I was fighting with it as well before I got it working.

When you let the cron run in Drupal does ist say something like: "Your request "Compute recommendations: Browsing History Recommender" in the queue. It will be executed asynchronously. Please refresh the page to see the update"

If not then configuration on Drupal site is still no yet correct done.

If you get this success message above, do you fire up then manually or also with a server side cronjob "run.sh" as described in installation manual? If yes do you get then in ssh client success message(s) like:

"Feb 04, 2013 3:12:21 PM org.drupal.project.async_command.Druplet runSerial
INFO: Executing command: RunRecommender
Feb 04, 2013 3:12:21 PM org.drupal.project.recommender.RunRecommender processTable
INFO: Using {recommender_preference_staging} table. Loading data.
Feb 04, 2013 3:12:21 PM org.drupal.project.recommender.RunRecommender$AlgorithmImpl run
INFO: Initializing data model, similarity and recommender.
Feb 04, 2013 3:12:21 PM org.drupal.project.recommender.RunRecommender$AlgorithmImpl initDataModel
INFO: Initializing data model.
Feb 04, 2013 3:12:21 PM org.drupal.project.recommender.RunRecommender$AlgorithmImpl initDataModel
INFO: Switching to MEMORY mode. Load all data from database into memory first.
Feb 04, 2013 3:12:21 PM org.drupal.project.recommender.RunRecommender$AlgorithmImpl run
INFO: Using similarity class: org.apache.mahout.cf.taste.impl.similarity.LogLikelihoodSimilarity
Feb 04, 2013 3:12:21 PM org.drupal.project.recommender.RunRecommender$AlgorithmImpl run
INFO: Using recommender class: org.apache.mahout.cf.taste.impl.recommender.GenericBooleanPrefItemBasedRecommender
Feb 04, 2013 3:12:21 PM org.drupal.project.recommender.RunRecommender$AlgorithmImpl run
INFO: Computing and saving similarity data.
Feb 04, 2013 3:12:21 PM org.drupal.project.recommender.RunRecommender$AlgorithmImpl genericComputeSave
INFO: Start computing recommendation and saving results in serial.
Feb 04, 2013 3:12:22 PM org.drupal.project.recommender.RunRecommender$AlgorithmImpl genericComputeSave
INFO: Computing done. Records#: 3294"

If you don`t see this kind of message(s) but instead for example java exception error messages, then you need to deal with the configuration file about path settings etc.

burgermeister’s picture

burgermeister commented

I took a break; I just started looking at my project again.

I don't get an error. Previoiusly, I was trying to get FiveStar to work.

I reinstalled everything. Now I'm trying to get Browsing History to work. I just need to create some accounts and run a test. If this works then FiveStar may be the problem.

I tested 9 different accounts with about 12 different pieces of Content and I still don't see the Recommend Block.

burgermeister’s picture

burgermeister commented

I can think of three possible things that is preventing me from getting this to work.

1. Maybe I'm using the wrong version of Mahout. I'm using the second to last download. "mahout-distribution-0.7.zip "
http://mirror.cogentco.com/pub/apache/mahout/0.7/

2. I'm using one server(through a host.) Is it possible to get Recomender API working without setting up my own server?

Are all three of these absolutely necessary?
I set up a cron job in cPanel to run.sh.
Click "Run recommender now" button. /admin/config/search/recommender/admin
Click "Run Cron" button. /admin/config/system/cron

3. Not enough test data.

danithaca’s picture

danithaca commented

I'm about to finish my dissertation, and soon I'll work on the new release of this module which will improve on user experience for admins. Thanks for hanging in there.

WoozyDuck’s picture

WoozyDuck commented
Priority: Normal » Major
Status: Closed (fixed) » Active

Same situation for me, I get similar errors and I don't know how to get this to work.
Please help

danithaca’s picture

danithaca commented
Issue summary: View changes
Status: Active » Closed (won't fix)

The new release 7.x-6.x should have fixed the problem if you use the Java agent. You won't need Java if you use the PHP engine for small site. Release 7.x-4.x is not supported anymore. See #2377503: Upgrade Recommender API helper modules to be compatible to 7.x-6.x if you use other helper modules.