I'm using Drupal 6.4 and just updated my ubercart installation from 6.x-2.x-dev 21-aug-2008 (or thereabouts) to 12-sep-2008.

After doing that I got
"Missing argument 1 for uc_authorizenet_menu() in /hsphere/local/home/ronald/repository/drupal/modules/ubercart/payment/uc_authorizenet/uc_authorizenet.module on line 13."
on every page.

In the modules list, the Authorizenet module has a big red blob over the "enable" checkbox and says that it's not compatible with the 6.4 codebase. Because of that I am pretty sure that it was not enabled before upgrading the ubercart, but either way it seemed to be enabled afterwards with no way to disable it. Other than digging into the database, or completely removing the "ubercart/payment/uc_authorizenet" directory, which may be a bit rough but has solved the problem for me.

So would it be possible to make sure that modules that shouldn't be enabled due to known incompatibilities, aren't?

Comments

rszrama’s picture

rszrama commented
Status: Active » Closed (won't fix)

You could've had it enabled, but on a merge from the D5 branch the whole module was changed and was downgraded to not compatible w/ D6 in our list of completed modules. It will have to be re-ported to D6 from scratch due to the significant changes. There's no way to handle that for sites that already had it enabled... you can just disable it through the DB. Part of the pain of using a dev version. : )

rondp’s picture

rondp commented

Not sure if I understand you right - this site was a fresh install starting with Drupal 6.3 and then upgraded to 6.4.
So if the module did not have the "incompatible" flag for 6.3 or if the previous developer version for 6.4 didn't have it then yes, it may have been enabled. But that would make me wonder why I did not get any errors before upgrading. If what you are saying is that the change was from Drupal 5 to 6, then that should not affect me because the site never ran Drupal 5.
Either way, what I don't understand is how a module can be able to show a message in the modules list and place a blob over the "enable" checkbox, and at the same time not be able to just disable itself.

Cheers,

Ronald

rszrama’s picture

rszrama commented

Real quick... Auth.Net was ported for D6 and fully able to be installed. On a merge in bazaar the .info file was overwritten and the module is no longer compatible. Drupal doesn't have a category for that happening, so you can't disable it through the UI. The issue will resolve itself in the near future.