Creating Report Output causes "navigation_menu" dependency error (site goes down)

On the latest version of dataprocessor, on WordPress with Civi 5.71.1, if I create a new data processor and I add an output of Search / Report, I get the following error and the whole site goes down (cannot navigate anywhere without that error and nothing else shows):

The parameter "navigation_menu" has a dependency on a non-existent parameter "2Fdataprocessor_search".

This happens on any type of data processor where I select Search / Report as an output. Other outputs I've tried (ex. dashlet) seem to work. And it's only happening on WordPress, my Drupal 7 site seems fine.

mentioned in commit 1136250a

mentioned in merge request !126 (closed)

@pbarmak I have created a fix in !126 (closed) can you see whether that fix solves your issue?

I just tried to patch and reenabled the extension. Unfortunately, this did not solve the issue. The second I try to create a Report, it crashes with the same error. If I delete the row from the civicrm_data_processor table, I can get my site back. Not sure if that helps track it down.

I do see some more in my apache error log, not sure if this will help:

PHP Fatal error: Uncaught CRM_Core_Exception: [undefined: The parameter "navigation_menu" has a dependency on a non-existent parameter "2Fdataprocessor_search".\n\n thrown in /var/www/civicrm/wp-content/plugins/civicrm/civicrm/api/api.php on line 138, referer: https://example.org/wp-admin/admin.php?page=CiviCRM&q=civicrm%2Fdataprocessor%2Fform%2Fedit&reset=1&action=update&id=8

I see in your log file this parameter 2Fdataprocessor_search but that parameter I could not find in the code. And you are saying the data processor crashes as soon as you add sear/report output to the data processor?

Yes, it crashes as soon as I add Search / Report output to any data processor.

If I delete the data processor from the backend MySQL database table, everything works again.

I'm going to create a completely fresh instance of Civi on WordPress now just to see. But you might need to create one on your end, as I'm not sure how helpful my information may be, but I'll try to help as this extension is critical to our work.

OK, I just went on my dev machine and created a brand new install of WordPress 6.4.3 and CiviCRM 5.71.1.

I then ran cv en legacycustomsearches per your readme file. I then went to my new Civi install, went to Extensions, then New, then Downloaded Data Processor v1.101 from there. It installed fine.

I then applied the fix you mentioned above, just in case.

I then went to Administer / Data Processor / Add Data Processor. I created a new test processor. I picked Contacts as the Data Source and then picked two fields (Contact ID and First Name). I saved and all was fine. I then created a Dashlet output and saved, and the Dashlet was fine (shows up on my dashboard, no problem).

I then wen to create a Search / Report output and when I clicked Save, my WordPress site had an unrecoverable error. I check the apache logs for PHP errors and found the exact same error.

PHP Fatal error: Uncaught CRM_Core_Exception: [undefined: The parameter "navigation_menu" has a dependency on a non-existent parameter "2Fdataprocessor_search"

I'm not sure what else I can do to help, but please let me know.

I just tried a fresh install of the data processor on a clean civicrm + drupal 10 installation. And I created the same data processor as you, however I could not reproduce the behaviour.

I am also a bit confused by the name of the non-existent parameter. Because it starts with 2F... When I search for that in the code I could not find such a parameter name.

Have you tried it on a fresh install of WordPress? That is where I see the error. My Drupal instances are fine.

No I did it on Drupal as I had a fresh Drupal install available for other purposes. So probably the issue is then only occuring in Wordpress.

I did a check in wordpress and could reproduce it and found the issue and it has now been solved in the development version the data processor extension. Can you test again?

Yes, it looks like it's working now. I did a quick test with a fresh install and I'm able to use the steps above and save the data processor without any errors. Thank you! I'm sure I'll see when this gets rolled into the next release, I'll be happy to test it more on WordPress then.

mentioned in commit 5590fe61