WordPress Email Notification Plugin v2.3.1 Error

I am also having problems with this plugin. I have installed 2.3.0 with WordPress 2.0.

I have followed all instructions but I am getting this error on the front page of my blog:
Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/servaas/public_html/wp-content/plugins/wp-email-notification/email_notification_2.3.php on line 369

Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/servaas/public_html/wp-content/plugins/wp-email-notification/email_notification_2.3.php on line 372

And on the Admin page for this plugin I have the following error report:

Warning: main(): open_basedir restriction in effect. File(/maillist/wpemn_config.php) is not within the allowed path(s): (/home/servaas:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/servaas/public_html/wp-content/plugins/wp-email-notification/index.php on line 19

Warning: main(/maillist/wpemn_config.php): failed to open stream: Operation not permitted in /home/servaas/public_html/wp-content/plugins/wp-email-notification/index.php on line 19

Warning: main(): open_basedir restriction in effect. File(/maillist/wpemn_config.php) is not within the allowed path(s): (/home/servaas:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/servaas/public_html/wp-content/plugins/wp-email-notification/index.php on line 19

Warning: main(/maillist/wpemn_config.php): failed to open stream: Operation not permitted in /home/servaas/public_html/wp-content/plugins/wp-email-notification/index.php on line 19

Warning: main(): Failed opening ‘/maillist/wpemn_config.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/servaas/public_html/wp-content/plugins/wp-email-notification/index.php on line 19

And guidance appreciated.

I had a look at the developers website, where I have also posted a call for help. It seems there were minimal changes made between 2.3.0 and 2.3.1 so I am not sure that upgrading will help. Also, can you upgrade a broken plugin?

The alternative is to pgrading is to uninstall 2.3.0 and do a fresh install of 2.3.1. Normally you can just delete the files but with this plugin I had to run install.php on the server, and there is no uninstall.php so how do I uninstall this?

OK, I upgraded to 2.3.1 as per the install.txt

One thing I noticed was that there was no /wp-content/plugins/wp-email-notification/block_reports.php to delete.

The outcome is that the error in the admin area > manage > email notification is gone, but the error on the front page remains:

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/servaas/public_html/wp-content/plugins/wp-email-notification/email_notification_2.3.1.php on line 369

Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/servaas/public_html/wp-content/plugins/wp-email-notification/email_notification_2.3.1.php on line 372

So, anyone know what makes it an invalid MySQL result?

For other people: make sure your WP and maillist share the same database… That’s part of what caused the error for me.

I still am dealing with errors and have tried renaming the wp prefix to my normal prefix but no avail. Those are the instructions I followed (found at Watershed Studio Blog) ….

—-

The “future� database for the plugin uses the prefix, but the install creates a database with a “wp_� prefix. If your prefix is “abcd�, you need to either rename wp_email_list_future to abcd_email_list_future, or create a new table:

CREATE TABLE abcd_email_list_future (
post_ID bigint( 20 ) NOT NULL default ‘0′,
post_date char( 12 ) NOT NULL default ‘0′,
notification_sent char( 1 ) NOT NULL default ‘’,
PRIMARY KEY ( post_ID )
) TYPE = MYISAM

Thanks for the link Chelsea. I have followed your lead and installed Skippys plugin instead.

It was much eassier for me to configure (no database knowledge required) and is working great.

Ok, I figured out the problem. The function you are supposed to insert into your template header, “email_notification_future_send()” calls a function in email_notification.2.3.php which tries to use the WordPress global $table_prefix to access the wp_email_list_future table. However, $table_prefix includes your blog’s prefix (if you installed the blog with one) so my table (created by the email notifier) was wp_email_list_future but the $table_prefix directive was wp_myblog_ so it tries to access the table wp_myblog_email_list_future which does not exist. To fix this, simply rename the wp_email_list_future table to wp_YOURBLOGPREFIX_email_list_future and it should work great. (If you’re not sure what your blog prefix is, it’s the prefix that is used in all of the other tables for your blog).

Fowie