After the last update (not dev), I got:
Fatal error: Class 'PaymentMethodController' not found in /home/{site}/public_html/sites/all/modules/payment/paymentmethodbasic/paymentmethodbasic.module on line 88

I had to disable the Payment module to re-activate the site.

Any feedback is appreciated.

Comments

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented
Status: Active » Fixed

This is a problem with your Drupal site, and not with Payment. This type of error message is not uncommon in Drupal 7, which has its own mechanism for autoloading classes that sometimes fails. Look up the error message online and you will find several possible ways to solve the problem.

Status: Fixed » Closed (fixed)

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

vako’s picture

vako commented

Well, I did a search for Class 'PaymentMethodController' not found on Google and Drupal.org and couldn't find any other post other than this one.
If anyone has a link or suggestion, please post it here. Thank you.

Xano, if you definitely sure that it's a general Drupal issue, you must have a link or something that you might have seen.

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented

The problem is not related to this particular class. There are three reasons why Drupal's class autoloader cannot find a class (any class):

  1. The class autoloader is broken. If you don't see this error for any other class, this is not the case.
  2. It does not exist. In this case, the class exists and the code works fine, as there are 1600 sites running without a problem.
  3. Some code needs to load the class before the autoloader is fully initialized.

I don't know the exact cause of the problem, but I do know it's not Payment.

Anonymous’s picture

Anonymous (not verified) commented

Having this problem with version 7.16, I made these steps:

1. temporary remove the code that generated the problem
2. clear cache, result: a lot of warnings complaining about changes in Payment and a warning about de removed code of step 1
3. clear cache again: result: warnings only about de removed code of step 1
4. placed the removed code back in position
5. cleared cache: no warnings.

Hope this helps others.

vako’s picture

vako commented

Hi Jaapx, which code did you remove?