When clicking the Mapping link on the default mailhandler feed, I receive the following error:

Fatal error: Call to a member function getMappingSources() on a non-object in /home/quickstart/websites/new.dev/sites/all/modules/contrib/mailhandler/plugins/MailhandlerParser.inc on line 129 Call Stack: 0.0003 330540 1. {main}() /home/quickstart/websites/new.dev/index.php:0 0.3239 4061284 2. menu_execute_active_handler() /home/quickstart/websites/new.dev/index.php:21 0.3250 4063148 3. call_user_func_array() /home/quickstart/websites/new.dev/includes/menu.inc:503 0.3250 4063464 4. feeds_ui_edit_page() /home/quickstart/websites/new.dev/includes/menu.inc:0 0.3415 4445112 5. drupal_get_form() /home/quickstart/websites/new.dev/sites/all/modules/contrib/feeds/feeds_ui/feeds_ui.admin.inc:314 0.3416 4445844 6. drupal_build_form() /home/quickstart/websites/new.dev/includes/form.inc:189 0.3416 4447936 7. drupal_retrieve_form() /home/quickstart/websites/new.dev/includes/form.inc:316 0.3419 4449144 8. call_user_func_array() /home/quickstart/websites/new.dev/includes/form.inc:772 0.3420 4449524 9. feeds_ui_mapping_form() /home/quickstart/websites/new.dev/includes/form.inc:0 0.3425 4452792 10. MailhandlerParser->getMappingSources() /home/quickstart/websites/new.dev/sites/all/modules/contrib/feeds/feeds_ui/feeds_ui.admin.inc:497

I tried using the latest Mailhandler 7.x dev as well, with the same result. How can I troubleshoot this further?

Comments

narayanis’s picture

narayanis commented
Priority: Normal » Critical

Changing to critical, as an inability to set up the feed makes the module totally unusable.

tthomas48’s picture

tthomas48 commented

I was able to fix this by adding the following lines to mailhandler.info, seems only the default plugin was being loaded so the ctools_plugin code couldn't find the class file (it only loads the .inc not the .class.php):

files[] = plugins/commands_plugin/MailhandlerCommandsFiles.inc
files[] = plugins/commands_plugin/MailhandlerCommandsFiles.class.php
files[] = plugins/commands_plugin/MailhandlerCommandsHeaders.inc
files[] = plugins/commands_plugin/MailhandlerCommandsHeaders.class.php

I don't mind submitting a patch for this, but is the intention that these are dynamically loaded somehow that I'm missing?

santam’s picture

santam commented

Thanks http://drupal.org/node/1241502#comment-4858130 I was able to get my mapping screen. After adding those Lines to the info file you will need to clear your cache once.

narayanis’s picture

narayanis commented

That fix worked for me as well. Thanks tthomas48!

danepowell’s picture

danepowell commented

FYI I am trying to make a pass for beta2 soon...

thebenp’s picture

thebenp commented

I edited the mailhandler.info file as per #2, but I am still getting the same error.

PHP Fatal error: Call to a member function getMappingSources() on a non-object in /Library/WebServer/Documents/lsa/sites/all/modules/mailhandler/plugins/MailhandlerParser.inc on line 129, referer: https://lsa/admin/structure/feeds/edit/mailhandler_nodes/settings/FeedsN...

Any other steps to take? This happens when I try to import mail. I am on PHP 5.3.6 and mysql 5.0.67
I am running on OSX server 10.5, one interesting this is PHP is running with the flag --with-imap=/Users/Shared/unix/imap-leo' and that folder does not exist. It claims to be using IMAP c-Client Version 2007e so I am guessing it is getting this from somewhere else?

Thanks.

EDIT: After being unable to reply to this thread from google chrome, switching to Firefox worked.
I tried Importing from the mailhandler from Firefox, and it appears to work fine. Not sure if this is totally normal or if I should submit a report elsewhere?

danepowell’s picture

danepowell commented

I suspect this will be resolved by, or at least be similar to, #1173372: Improve loading of include files with ctools

danepowell’s picture

danepowell commented
Status: Active » Fixed

Yes, I think this was fixed by #1173372: Improve loading of include files with ctools. Please try the latest dev release and let me know if you are still having problems.

Status: Fixed » Closed (fixed)

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