Closed (fixed)
Project:
Recommender API
Version:
7.x-4.0-alpha3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Nov 2011 at 20:23 UTC
Updated:
3 Dec 2011 at 19:20 UTC
I'm installed the fivestar_rec module as well as a custom helper module. I have async_command and recommender up and running, but executing run.sh seems to do nothing:
Nov 10, 2011 3:15:59 PM org.drupal.project.async_command.CommandLineLauncher launch
INFO: DrupalApp VERSION: 7_1_1
Nov 10, 2011 3:15:59 PM org.drupal.project.async_command.CommandLineLauncher handleSettings
INFO: Set configuration file as: /home/msepjobs/public_html/sites/all/modules/recommender/../async_command/config.properties
Nov 10, 2011 3:15:59 PM org.drupal.project.async_command.DrupalConnection testConnection
INFO: Database connection successful: MySQL5.0.92-community
Nov 10, 2011 3:15:59 PM org.drupal.project.async_command.GenericDrupalApp runSerial
INFO: Total number of commands to run: 0
Nov 10, 2011 3:15:59 PM org.drupal.project.async_command.GenericDrupalApp run
INFO: Running the DrupalApp is accomplished.
How do I ensure that jobs are being added to the queue?
Comments
Comment #1
grasmash commentedLooks like this is happening because {recommender}'s cron column is NULL for all rows... Looking into cause.
Comment #2
grasmash commentedK, so after looking at the code I found the path for 'admin/config/recommender'
This does not show up on Drupal's configuration page. The README.txt suggests that the module can be configured at admin->configure->recommender, but this is not functional.
I believe that in order for this to appear on the configuration page, you first need to define a block on the config page usingsystem_admin_menu_block_page():
You may also want to add this to recommender.info:
Comment #3
danithaca commentedI'm investigating. It's really strange that my local dev has no problem, but I deploy it to a new Drupal installation, I can't see the admin/config/recommender menu.
Comment #4
danithaca commentedConfirmed the problem. Thanks for the report. Looks like this is something introduced by Drupal 7.9. My local dev is 7.8 and there's no problem.
Also, I tested Organic Group. Looks like OG also has this problem that admin/config/og does not show in the configure menu. I'm not sure if this is Drupal core's efforts to try move everything under admin/config to be under a sub-category.
I'll investigate more.
Comment #5
grasmash commentedSounds good. FYI- the code that I submitted does fix the problem. You just need to define a parent router item with a 'page callback' => 'system_admin_menu_block_page'.
Have you tried implementing that snippet?
Comment #6
danithaca commentedI used your snippet. But it doesn't work for me ...
Also, the problem seems to show only with newly installed modules that have admin/config/* items. This is really strange...
Comment #7
danithaca commentedcannot reproduce in newly installed Drupal 7.9. the patch is commited too, will be available in the 4.0-alpha5.
Comment #8
danithaca commented