CiviCRM Community Forums (archive)

I'm working on a Wordpress implementation (Civi 4.4.11), and all seems to be well apart form when running a depupe, e.g. wp-admin/admin.php?page=CiviCRM&q=civicrm/contact/merge&reset=1&cid=9&oid=1699&action=update&rgid=11

This displays the following Notices and Warnings:

Notice: Undefined variable: title in /wp-content/plugins/civicrm/civicrm/CRM/Dedupe/Merger.php on line 141

Notice: Undefined variable: userRecordUrl in /wp-content/plugins/civicrm/civicrm/CRM/Dedupe/Merger.php on line 143

Warning: Cannot modify header information - headers already sent by (output started at /wp-content/plugins/civicrm/civicrm/CRM/Dedupe/Merger.php:141) in /wp-includes/option.php on line 750

Warning: Cannot modify header information - headers already sent by (output started at /wp-content/plugins/civicrm/civicrm/CRM/Dedupe/Merger.php:141) in /wp-includes/option.php on line 751

My assumption is that the Warnings are being generated by the fact that the Notices are being displayed on screen. what I don't understand is why the notices are being displayed at all.

My Debugging and Error Handling settings are off.
The Wordpress wp-config.php file has  WP_DEBUG off
the php.ini is set to display_errors = Off

Not sure what more I can do to stop these notices from appearing?

There are sometimes multiple php.ini files. Use phpinfo() to check which one is "active".

I've now migrated the site to a Civihosting.com server and availed myself of Hershel's excellent assistance.

I have updated the CiviCRM install to 4.4.14.

We've double-checked all of the settings in the global php.ini file and checked what wp-config.php is doing in relation to error reporting and display.

The upgrade appears to have resolved an issue where a whole string of notices and warnings were being displayed when trying to add a tag to a contact, but the original problem, of having notices displayed when trying to apply a deduplication rule as noted above, remains.

In my view this is a bug.

I can see your point Erik, and I'll check that out.

However, at the same time, if the release exists for Wordpress, it seems reasonable to assume that if it doesn't work properly with a standard Wordpress install with no other plug-ins activated then there is an issue.

If Wordpress is the source of the issue then we can aim to get that fixed through those channels, but in the meantime surely we should still report the issue as a bug, if nothing more than to enable users and developers to be aware of it.