Not compatible with D6.13 :(

Comments

markDrupal’s picture

What is the problem?

I'm using TAC_lite 6.x-1.3 with 6.13 and I don't notice any issues

keesje’s picture

Might not be related, but my search ended here :-).
Had the same problem (custom module).
solution: .info file had "dependencies =" instead of "dependencies[] =".

If it does not help you, it might help others landing here with the same problem.

Cheers,

Kees

Armbanden online

Dave Cohen’s picture

I'm looking at the DRUPAL-6--1 branch, and I see the proper dependencies[] in the info file. So to those of you with a problem, where are you getting the module from?

socialnicheguru’s picture

Status: Active » Closed (fixed)

I was using the patch to upgrade from version 5 to version 6.

Dave Cohen’s picture

What patch? Is it published somewhere?

socialnicheguru’s picture

it is in the bug queue and entitled "Drupal 6" or something along those lines (don't have time to find it now but will if you can't).

I just pdated to the actual dev release so this should remain closed.

keesje’s picture

"Had the same problem (custom module)"

This means I had the same problem with another module ;-)

earl_lefebvre’s picture

I had the same problem creating a custom module and it turned out to be that I used Microsoft Wordpad instead of Notepad. It turns out that the format of the Wordpad text files causes the problem. Once I switched to using Notepad everything worked fine.

almaudoh’s picture

Thanks kees. Mine was a "dependencies" instead of "dependencies[]" on fb_actions.info in the DFF Actions module.

drupalshrek’s picture

I was having a similar problem, and the problem was also the .info file. In my case, I was trying to use a v5 module with Drupal 6. By comparing the .info file for the v5 module with the .info file for a v6 module I was able to find the key missing items. Basically I had to add the following line to the .info file:

core = 6.x 

See also:
http://drupal.org/node/171205