Warning: Illegal string offset 'callable' in rdf_rdfa_attributes() (line 181 of core/modules/rdf/rdf.module).
Warning: call_user_func() expects parameter 1 to be a valid callback, function 'd' not found or invalid function name in rdf_rdfa_attributes() (line 183 of core/modules/rdf/rdf.module).

REFERRER http://d8:8082/forum/1
MESSAGE Warning: Illegal string offset 'callable' in rdf_rdfa_attributes() (line 181 of /Users/acausing/Desktop/chocchip/drupal8/core/modules/rdf/rdf.module).

content 09/16/2013 - 23:21 forum: added This is a new topic. dev view <-- after adding topic
php 09/16/2013 - 23:21 Warning: Illegal string offset 'callable' in rdf_rdfa… dev <--- warning exist

Steps before this warning appeared:
1. Forum, Syslog
2. Post on forum (General) -> warning start to exist
3. Disabled Forum, and Syslog -> Still persist.
4. Uninstall Forum, and Syslog -> Still persist.
5. Under Content List when Forum topic is deleted the warning/error didn't exist anymore.

CommentFileSizeAuthor
#2 2090139-2.patch662 bytessidharthap
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sidharthap’s picture

Issue is reproduce able.
There is no callable function name defined on rdf.mapping.node.forum.yml file. More info is here https://drupal.org/node/2020001.

sidharthap’s picture

Status: Active » Needs review
FileSize
662 bytes

Patch for correction of rdf.mapping.node.forum.yml.

andypost’s picture

Status: Needs review » Reviewed & tested by the community

Awesome!

webchick’s picture

Title: Warning: Illegal string offset 'callable' in rdf_rdfa_attributes() (line 181 of core/modules/rdf/rdf.module). » Tests for: Warning: Illegal string offset 'callable' in rdf_rdfa_attributes() (line 181 of core/modules/rdf/rdf.module).
Status: Reviewed & tested by the community » Active
Issue tags: +Needs tests

Since this is just basically a typo and we're unlikely to introduce it again:

Committed and pushed to 8.x. Thanks!

However, it'd be great to write a Forum module test that could cause this error if the patch was backed out. Setting back to active for that.

webchick’s picture

Issue summary: View changes

added last step and warning is gone.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

  • webchick committed cbb1350 on 8.3.x
    Issue #2090139 by sidharthap, acausing: Fixed Warning: Illegal string...

  • webchick committed cbb1350 on 8.3.x
    Issue #2090139 by sidharthap, acausing: Fixed Warning: Illegal string...

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

  • webchick committed cbb1350 on 8.4.x
    Issue #2090139 by sidharthap, acausing: Fixed Warning: Illegal string...

  • webchick committed cbb1350 on 8.4.x
    Issue #2090139 by sidharthap, acausing: Fixed Warning: Illegal string...

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
quietone’s picture

Title: Tests for: Warning: Illegal string offset 'callable' in rdf_rdfa_attributes() (line 181 of core/modules/rdf/rdf.module). » Warning: Illegal string offset 'callable' in rdf_rdfa_attributes() (line 181 of core/modules/rdf/rdf.module).
Version: 9.3.x-dev » 8.0.x-dev
Issue summary: View changes
Status: Active » Fixed
Issue tags: -Needs tests +Bug Smash Initiative
Related issues: +#3270260: Test the callbacks in rdf.mapping.node.forum.yml

This issue was committed to 8.x and re-opened to add a test. Since it was committed, let's close this and open a followup.

This is the followup #3270260: Test the callbacks in rdf.mapping.node.forum.yml.

And restoring the version when this was committed and setting to fixed.

Status: Fixed » Closed (fixed)

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