Just updated appr. 4 modules:
* Services from 2 to 3.0-alpha;
* Taxonomy Super Select 6.x-1.3
* Drpager (Minimax pager) 6.x-1.11
* Computed Field 6.x-1.x-dev

The error shows up in > 50-fold and as far as I can see on all pages, also for anonymous users.

rebuilding permissions has no effect.

167  * Implementation of hook_forms(). We reuse code by using the
168  * same assignment form definition for each node-op combination.
169  */
170 function trigger_forms() {
171   $hooks = module_invoke_all('hook_info');
172   foreach ($hooks as $module => $info) {
173     foreach ($hooks[$module] as $hook => $ops) {
174       foreach ($ops as $op => $description) {
175         $forms['trigger_'. $hook .'_'. $op .'_assign_form'] = array('callback' => 'trigger_assign_form');
176       }
177     }
178   }
179
180   return $forms;
181 }

Comments

ClearXS’s picture

ClearXS commented
Project: Drupal core » Services
Version: 6.19 » 6.x-3.0-alpha1
Component: trigger.module » Code

OK, so most likely this has been caused by the change from 2 to 3 version of Services.

=> ticking off all its components and many dependent modules
=> uninstalling

due to instability of /admin/build/modules because of a huge module list, I had to do this 4 times over with every-time a 10 minute wait for processing...

=> only Content Distributor and Content Retreiver modules show up to uninstall
=> error disappears

I don't know what happens when I tick Services and Content modules on again and won't try it for now as it costs me up to hours to repair due to Drupals systematic instability on my huge module list.

Is the new 3 version already supposed to work with these modules?

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented

There is no upgrade path or backwards compatibility between Services 2 and Services 3, so when you tried to upgrade everything fails. You should revert your Services version back to 2 and wait for the dependent modules to update their code. I will be contacting module developers this week to give them information about the upcoming changes.

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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

Obsidian1269’s picture

Obsidian1269 commented

I just did a first fresh install of this module with the current dev version and I have the same problem.

kip.themann’s picture

kip.themann commented
Issue tags: +invalid, +argument, +line 174, +trigger.module

I'm new to drupal and thought this would be a piece of cake like joomla. Keep getting this darn warning message all over my site though. It says the issue is fixed, but I have just installed services 3 alpha as was suggested. Still get the same message though. Could anyone break this down for a newbie? Thanks a lot for your help.

bsenftner’s picture

bsenftner commented
Version: 6.x-3.0-alpha1 » 6.x-3.0-beta2
Status: Closed (fixed) » Active

I'm seeing this error in Services Beta 2, but only once and only when I go to create a new node of a custom content type I created in a module.

Now, I did have Services 2 installed, but unused in this installation. After disabling Services 2.x, I ran the 'uninstall' procedure from the tab on the modules page before installing and enabling Services Beta 2. After that uninstall, shouldn't the database be as if Services never touched my Drupal installation?

Do I need to start with a completely fresh version of Drupal? (Never been touched by Services 2.x?)

Actually, I'm seeing the error with every node edit (after working with the site for a bit.)

kylebrowning’s picture

kylebrowning commented

I still have not been able to reproduce, can someone give me a DB dump and list of modules to recreate?

bsenftner’s picture

bsenftner commented

I simply disabled the trigger module. Wasn't using it anyway, and if necessary I can always use Rules, right?

kylebrowning’s picture

kylebrowning commented
Status: Active » Closed (cannot reproduce)
dave_robinson’s picture

dave_robinson commented

Just for reference, I hit this problem myself. It's actually because 6.x-3.0-beta2 has a broken implementation of hook_hook_info. It's missing one level of nesting in the array structure. It looks like the hook has been removed in the 6.x-3.x HEAD so I assume that it's not needed anymore anyway.