The fix for GDPR issue https://www.drupal.org/project/gdpr/issues/2972188 causes the field to fail when trying to add it to a subscription form (or maybe another change - this was tested against alpha11 or alpha12).

[Mon Jun 04 09:51:22.442383 2018] [fcgid:warn] [pid 4397] [client 81.44.111.95:46906] mod_fcgid: stderr: Uncaught PHP Exception Drupal\\Core\\Entity\\Query\\QueryException: "'status' not found" at /var/www/clients/client1/web201/web/core/lib/Drupal/Core/Entity/Query/Sql/Tables.php line 348, referer: http://netuxo20.netuxosandbox.co.uk/en/admin/config/people/simplenews/se...

Comments

Anonymous’s picture

Anonymous (not verified) commented

Andreas Speck created an issue. See original summary.

Anonymous’s picture

Anonymous (not verified) commented

So, the problem seems to be with:

public function fieldSettingsForm(array $form, FormStateInterface $form_state) {

$agreement_ids = \Drupal::entityQuery('gdpr_consent_agreement')
->condition('status', 1)
->sort('title')
->execute();

What did change on gdpr_consent_agreement? No longer has status? Nor title?

Or what is causing it to fail?

Anonymous’s picture

Anonymous (not verified) commented

The problem was caused by gdpr_consent.

Fixed in alpha14: [FIX] Add missing data_table to the gdpr_consent_agreement entity annotation.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Closed (outdated)
mgstables’s picture

mgstables
Primary language Dutch
commented

Does that mean, i can safely upgrade the GDPR module? I had to downgrade it after failure of this module. And thank you so much that you have put your time in this module.

Anonymous’s picture

Anonymous (not verified) commented

Sorry for the delayed response. I was on vacations last week. We are running this module on a multilingual site together with gdpr-8.x-1.x-alpha14. We have not yet tested it with the new 2.0 branch of the GDPR module.