"Immediate sending" stopped working after 2.x-dev to 4.x-dev upgrade, even though "Immediate sending" box is ticked.

Comments

skyredwang’s picture

Title: Immediate sending stopped working after 2.x-dev to 4.x-dev upgrade » issues with upgrade path from 2.x-dev to 4.x-dev
Priority: Normal » Critical

after upgrading from 2.x to 4.x (installed Autoload and no SQL errors), go to /admin/messaging/notifications/queue/operations/test, no subscription is there! All zero; and Test Run also confirms there is nothing to send.

zeezhao’s picture

Title: issues with upgrade path from 2.x-dev to 4.x-dev » Immediate sending stopped working after 2.x-dev to 4.x-dev upgrade

#skyredwang, its better you enter a separate issue, so that it is captured and tracked. I have changed title back to original issue.

zeezhao’s picture

This seems related to the fact that content types now need to be "Enabled" via: admin/messaging/notifications/events

Note that selecting admin/messaging/notifications/events/configure via menu (Notifications Settings -> Events -> configure) gives an error:

Fatal error: require_once() [function.require]: Failed opening required 'sites/all/modules/notifications/notifications_tools/notifications.admin.inc' ... in ....includes\menu.inc on line 346

The way aaround this is to go via: admin/messaging/notifications/events

jose reyero’s picture

Status: Active » Postponed (maintainer needs more info)

Right, if you enable the 'content type extension' you need to check events. So is that the issue?

zeezhao’s picture

Yes, that appears to be the issue but it was not immediately obvious.

Please note the error I found in #3.

drupal_hhp’s picture

I'm experiencing the same problem. I have the content type extension module enabled. I have enabled the events at admin/messaging/notifications/events and immediate sending but can only get my notifications when cron runs and not when the event has occured.

jose reyero’s picture

@drupal_php,

Does the issue go away when you disable the 'content type extension'?

SchwebDesign’s picture

I am getting error above in #3 as well, using the admin menu link directly to Notifications Settings -> Events -> configure

Fatal error: require_once() [function.require]: Failed opening required 'sites/all/modules/notifications/notifications_tools/notifications.admin.inc' ... in ....includes\menu.inc on line 346

guidot’s picture

Status: Postponed (maintainer needs more info) » Active

I have a similar error when I try to go to admin/messaging/notifications/events/configure:

Fatal error: require_once() [function.require]: Failed opening required 'sites/all/modules/notifications/notifications_content/notifications.admin.inc' (include_path='.:/usr/share/php:/usr/share/pear') in [...]/includes/menu.inc on line 346

I tried putting a symbolic link in place:
ln -s 'sites/all/modules/notifications/notifications.admin.inc' 'sites/all/modules/notifications/notifications_content/notifications.admin.inc'

I emptied all caches by invoking drush cc all and also selecting Flush all caches in Admin menu. I also cleared the XCache I am using.

I tried that again after disabling the Content Type extension, to no avail.

eighthourlunch’s picture

subscribe

anea02’s picture

I am experiencing the same issue but I have not enabled 'content type extensions'. Will try workaround in #3

jim kirkpatrick’s picture

Subscribe...

Getting "Fatal error: require_once" error on admin/messaging/notifications/events/configure as per #3 and others. Had it before and after enableing content type extension module...

Have re-saved the admin/messaging/notifications/events and hope that fixes it.

jim kirkpatrick’s picture

Anyone got it to work?

We get 'web' notifications, and comment ones, but node create seems to not be working...