1.5.1 new feature : structured data
Permalink Browser Info Environment
Dear Devoda team,
I have just upgraded to the latest version, with the please of noticing that schema.org markup can now be used. This is a great addition !
However, this can't be used, with or without chosen value (at page level).
I'm getting the following error, whether I do leave it empty or input something :
The query doesn't look like it encompasses the actual parameter save.
Will there be a next update to fix this ?
Thanks,
Christian
I have just upgraded to the latest version, with the please of noticing that schema.org markup can now be used. This is a great addition !
However, this can't be used, with or without chosen value (at page level).
I'm getting the following error, whether I do leave it empty or input something :
An exception occurred while executing 'INSERT INTO atMetaDevodaSeo (robots_advanced_type, robots_noodp, robots_noimageindex, robots_noarchive, robots_nosnippet, robots_notranslate, open_graph_title, open_graph_description, open_graph_image, google_plus_title, google_plus_description, google_plus_image, twitter_title, twitter_description, twitter_image, twitter_card_type, avID) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)' with params ["0", 0, 0, 0, 0, 0, null, null, "345", null, null, "345", null, null, "345", "", 81449]: SQLSTATE[HY000]: General error: 1364 Field 'structured_data' doesn't have a default value
The query doesn't look like it encompasses the actual parameter save.
Will there be a next update to fix this ?
Thanks,
Christian
| Type: | Ticket |
|---|---|
| Status: | Archived |
Hi,
thanks for your quick reply and response...but it seems that still doesn't work.
Here's what I'm getting when trying to save some details into the field :
(and I'm not seeing "structured data" in this query ?)
Plus, I'm trying to get back to editing another page where I did try before to add structured data, to no avail.
Checking the log gets me this :
Thanks for your time,
Christian
thanks for your quick reply and response...but it seems that still doesn't work.
Here's what I'm getting when trying to save some details into the field :
Exception Occurred: /var/www/(private)/concrete/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php:115 An exception occurred while executing 'INSERT INTO atMetaDevodaSeo (robots_advanced_type, robots_noodp, robots_noimageindex, robots_noarchive, robots_nosnippet, robots_notranslate, open_graph_title, open_graph_description, open_graph_image, google_plus_title, google_plus_description, google_plus_image, twitter_title, twitter_description, twitter_image, twitter_card_type, avID) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)' with params ["0", 0, 0, 0, 0, 0, null, null, "33", null, null, 0, null, null, "33", "summary_large_image", 81734]: SQLSTATE[HY000]: General error: 1364 Field 'structured_data' doesn't have a default value (0)
(and I'm not seeing "structured data" in this query ?)
Plus, I'm trying to get back to editing another page where I did try before to add structured data, to no avail.
Checking the log gets me this :
Exception Occurred: /var/www/(private)/concrete/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php:115 An exception occurred while executing 'UPDATE CollectionSearchIndexAttributes SET ak_meta_devoda_seo = ? WHERE cID = ?' with params ["", "565"]: SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect integer value: '' for column 'ak_meta_devoda_seo' at row 1 (0)
Thanks for your time,
Christian
So you did the update and got different errors, correct?
I guess I can't replicate this, without a dump of your database/website... Everything I try works. So can't really do anything without. Did you check the atMetaDevodaSeo database table if the column "structured_data" is there and what it's options are?
Kind regards,
Ramon
I guess I can't replicate this, without a dump of your database/website... Everything I try works. So can't really do anything without. Did you check the atMetaDevodaSeo database table if the column "structured_data" is there and what it's options are?
Kind regards,
Ramon
Hi !
Indeed I did update.
Going to the db table does get me this column, with parameters :
longtext utf8_unicode_ci, not null and no default value.
Should I change something ?
Christian
Indeed I did update.
Going to the db table does get me this column, with parameters :
longtext utf8_unicode_ci, not null and no default value.
Should I change something ?
Christian
Should be nullable... otherwise you'd always have to enter something. Anyways, it would still have to save if you enter something. Which it doesn't? So that's pretty weird!
Kind regards,
Ramon
Kind regards,
Ramon
Well, right now the issue with this :
is the query that's supposed to build the properties form errors on the controller assembling an array, so the properties never show up.
Did this get updated lastly ? what kind of thing would be likely to trigger the error ?
I was thinking of removing the addon altogether and do a clean install, but that would mean setting it up all over again.
Is there some halfway point to be found ?
Thanks for any support you can provide.
This has gone from "yay, new feature" to "editing any attribute on some pages is completely broken".
On the plus side : on those pages where editing works, I was able to successfully add and save structured content.
It seems those of the pages where editing fails were the ones I tried to edit before you issued the update. Shall I go and delete the "attributeValue" items in the database to reset this ? The aforementioned logged error only happens when fetching db data to prepare for attributes edition.
Cheers
Christian
Exception Occurred: /var/www/(private)/httpdocs/packages/devoda_seo/attributes/meta_devoda_seo/controller.php:140 Call to a member function getOpenGraphTitle() on null (0)
is the query that's supposed to build the properties form errors on the controller assembling an array, so the properties never show up.
Did this get updated lastly ? what kind of thing would be likely to trigger the error ?
I was thinking of removing the addon altogether and do a clean install, but that would mean setting it up all over again.
Is there some halfway point to be found ?
Thanks for any support you can provide.
This has gone from "yay, new feature" to "editing any attribute on some pages is completely broken".
On the plus side : on those pages where editing works, I was able to successfully add and save structured content.
It seems those of the pages where editing fails were the ones I tried to edit before you issued the update. Shall I go and delete the "attributeValue" items in the database to reset this ? The aforementioned logged error only happens when fetching db data to prepare for attributes edition.
Cheers
Christian
Christian,
Weird stuff... That function didn't get updated lately, no. So weird things happening there. Even weirder is the fact that stuff is working for some of your pages. It should either work or not work at all haha. You can try some things out, but be sure to make a backup before you do that. I could take a look if I have a dump of the site + database, but I'm not sure if you're able to share that.
Kind regards,
Ramon
Weird stuff... That function didn't get updated lately, no. So weird things happening there. Even weirder is the fact that stuff is working for some of your pages. It should either work or not work at all haha. You can try some things out, but be sure to make a backup before you do that. I could take a look if I have a dump of the site + database, but I'm not sure if you're able to share that.
Kind regards,
Ramon
Hey,
since this looked to only affect those pages where a Devoda attribute was there between 1.5.1 and 1.5.2 and not where there was none, I just went to the DB, deleted the CollectionAttributeValues entry matching the package akID with the affected cID in the latest collection version, and it did the trick !
Pages saved :-)
since this looked to only affect those pages where a Devoda attribute was there between 1.5.1 and 1.5.2 and not where there was none, I just went to the DB, deleted the CollectionAttributeValues entry matching the package akID with the affected cID in the latest collection version, and it did the trick !
Pages saved :-)
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.
To re-open this issue, reply to this message.
To re-open this issue, reply to this message.
Oh indeed, this column was missing. Thought the ORM would fix that, but apparently, it did not. So update to version 1.5.2 and it should be available for you! Let me know if that worked out for you.
Kind regards,
Ramon