500 Error When Saving Existing Model after 2.0 upgrade

Hi @dbdrupal, sorry to hear you're having such a problem. To see what's going on we would require done log information. Could you please check of there is anything in the Drupal or the php logs?

Otherwise, could you please export one of the models and send it to us for review?

Ah, and one more question: have you gone through the steps to update, that are described in the release notes? Has all that gone without issues?

Per Jurgen's suggestion, I ran something I did not initially which was the drush eca:update. This did not solve the problem and I am uploading an export of the module per his suggestion. Thank you.

Thanks @dbdrupal for sharing your model. I can report that the model can be imported, opened and saved without any issue.

That's a bit unfortunate, since reproducing the problem would have been much better, as it would have helped to find the problem.

It seems as if the problem is somewhere in your Drupal installation. To further analyse that, we need more information. The console output from above tells us, that there was a so called 500 error. That means, PHP ran into a severe problem. Usually, this writes some logs either in Drupal under /admin/reports/dblog or directly into the PHP error log. The location of the latter depends upon your system setup.

Any chance you could reach out and find more information in either of those?

I will keep poking around @jurgenhaas, but there is nothing in the dblog for this issue and I'm not finding anything in my PHP error log either. Very odd. I will try to find some time this weekend to look deeper and report back on my findings.

This is a great analysis. Does that mean that even if you start a new model and only add a Token: Set Value task and then save, that it already fails?

I've looked into that plugin and there isn't anything special with it.

Not sure if you could go as far as trying with a fresh Drupal installation and see if the same happens there?

In any event, you could add the following 3 lines to the end of your settings.php and see if you then get some error messages somewhere. Probably, the error message in the browser console may contain more detail after that.

error_reporting(E_ALL);
ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);

Thanks Jurgen. I added these to settings.php and it isn't capturing anything new nor is there more information on the browser console (I"m using Chrome). From what I can tell, while this is super annoying and I want to figure it out, it is not keeping my models from saving or running correctly so for the time being, I will just need to deal with it. At some point, I will stand up a new instance of Drupal 10.3 and see if I continue to have this issue. In the meantime, thank you for addressing this for me. I think it is fair to close out this issue as it is a non-issue for the code base and must be something with my environment.

Really sorry for this to happen. I wish we could address this more efficiently. I mean, with xdebug that would be fairly straightforward to get to the roots of this. But not many have an environment where xdebug is available. If in any way possible and you could dump your database into a file and let me get my hands on it, I'd be happy to debug that for you. But of course, I understand if that's not an option.

... it is not keeping my models from saving or running correctly ...

Are you saying it saves the model correctly and still comes back with an error message?

In any event, I'd like to keep this open so that we can always get back to it when possible. Marking as postponed and as a support request, though.

Marking as fixed as I don't know what else we can do.

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