I managed to map some fields.
But when I try to put schema.org property image at an image field I get a White screen of death.
PHP error message Fatal error: Call to undefined function _field_permissions_field_settings_form_submit() in /var/www/drupal/includes/form.inc on line 1414
and when I reload the same page at /admin/structure/types/manage/contenttype/fields/field_image,
then I see that the propery "photo" is there.

So the system insists that 'photo' must be there.
If I change to 'image', I get the WSOD.

CommentFileSizeAuthor
#7 1297168_schemaorg_image.patch606 bytesscor

Comments

dropbydrop’s picture

dropbydrop commented
Title: WSOD on image field mapping » Cannot alter image field mapping

1.Disabling field-module does not give me the error message, but still I cannot change mapping to 'image'.
The system insists on 'photo' !

2. should i report a bug for the php error, which is another issue, at the field-module tracker?

scor’s picture

scor commented

There is indeed a problem with the image mapping, I noticed it during the tutorial in Austin as well.

Yes, please open an issue for the field-module php error so we can track it down in a separate thread. thanks :)

dropbydrop’s picture

dropbydrop commented

Can I change photo to image somehow in the database? Is there any temporary solution?

dropbydrop’s picture

dropbydrop commented
Version: 7.x-1.0-alpha2 » 7.x-1.x-dev

The system still insists keeping "photo" schema.org mappings, when I write "image".
If I write "imagea"(an extra a) for example then it keeps it.
It is like somewhere the system is ordered to replace every instance of work image with word photo.

Checking the error log at that time and that page I saw some errors. I don't know if they are related.
Warning: uasort(): Array was modified by the user comparison function in token_get_info() (line 428 of *****/sites/all/modules/token/token.module).
Warning: strnatcmp() expects parameter 1 to be string, array given in token_asort_tokens() (line 462 of ******sites/all/modules/token/token.module).

dropbydrop’s picture

dropbydrop commented

If this module development has stoped, is there any other mature and stable semantic module to use and still follow the schema.org specifications?

At least is there any database hack to fix it? I didn't find where these mappings are saved.
Are they save inside a BLOB for each content type? If yes, can I edit it somehow?

Thanks

scor’s picture

scor commented

@dropbydrop this module is still under development. As you seem to have found out, the Call to undefined function _field_permissions_field_settings_form_submit() message is due to the field permissions module. Have you checked #1257286: Fatal error: Call to undefined function _field_permissions_field_settings_form_submit()?

Edit: actually, duplicate of #1230284: Fatal error upon field settings form submit which was fixed, so maybe updating field_permissions would fix that?

As for the mapping issue, let me roll a patch. stay tuned :)

scor’s picture

scor commented
Assigned: Unassigned » scor
Status: Active » Needs review
StatusFileSize
new 1297168_schemaorg_image.patch606 bytes

Could you try this patch and let me know if it works for you?

dropbydrop’s picture

dropbydrop commented
Assigned: scor » Unassigned
Status: Needs review » Active

@scor.
I don't have field-permission problem anymore.

The updated situation of the problem is at #4.
I updated token module to latest dev, but still I have the same.
I did it in case it is connected with schema.org, although as I understand it isn't probably.

The most funny thing is that there is somewhere automatic replacement of image to --> photo.
If I write imagea, the system does not care. I m wondering why this happens.

Thanks for your care. Hope to hear from you soon.

dropbydrop’s picture

dropbydrop commented
Status: Active » Patch (to be ported)

Yes my problem was at last resolved by deleting 'image' => 'photo'.
Please commit.

Thanks a lot.

It is a pitty that for something for small, the problem existed for 2 months.
I couldn't imagine it was that simple.

Was there a good purpose for this line?
Finally where in database the mappings are saved?

scor’s picture

scor commented
Assigned: Unassigned » scor
Status: Patch (to be ported) » Fixed

Yes, there is some legacy term support which I had placed in the module until Google supports all the schema.org terms. Now that they support image and jobTitle, we can remove their legacy support. The mappings are saved in the rdf_mapping table (maintained by the rdf.module in core).

Fixed with http://drupalcode.org/project/schemaorg.git/commit/a409fe3. thanks for your patience @dropbydrop. You will have to download the latest 7.x-1.x-dev tarball after it is recreated in a few hours, or you can leave the patch applied for now.

dropbydrop’s picture

dropbydrop commented

Thanks a lot.
If I knew this is a feature of the module, I would had delete this line already. :)

Status: Fixed » Closed (fixed)

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