When attempting to save a content type with SEO Compliance Checker with the keyword rules module enabled a 500 server error occurs with the following message from the server log:

PHP Fatal error: Cannot use object of type stdClass as array in [path removed]/sites/all/modules/seo_checker/keyword_rules/keyword_rules.module on line 198,

The content from the node add page does not get written to the database.

On refreshing the page the following error is written to the screen
Notice: Undefined index: body in basic_seo_rules_alt_attribute() (line 43 of [path removed]/sites/all/modules/seo_checker/basic_seo_rules/basic_seo_rules.module).

Comments

Anonymous’s picture

I also get this error in the 7.x-1.6 release, but on an edited Page content type.

miruoss’s picture

Assigned: Unassigned » miruoss
Status: Active » Needs review

Hi there,

Thanks for the report. This should be fixed on the development branch and released soon.

Michael

makokis’s picture

same issue here, suscribbing

Notice: Undefined index: body en basic_seo_rules_alt_attribute() (línea 43 de /home5/teleinfo/public_html/sites/all/modules/seo_checker/basic_seo_rules/basic_seo_rules.module).
Notice: Undefined index: body en basic_seo_rules_alt_attribute() (línea 43 de /home5/teleinfo/public_html/sites/all/modules/seo_checker/basic_seo_rules/basic_seo_rules.module).
Notice: Undefined index: body en basic_seo_rules_title_attribute() (línea 63 de /home5/teleinfo/public_html/sites/all/modules/seo_checker/basic_seo_rules/basic_seo_rules.module).
Notice: Undefined index: body en basic_seo_rules_title_attribute() (línea 63 de /home5/teleinfo/public_html/sites/all/modules/seo_checker/basic_seo_rules/basic_seo_rules.module).

please help

bakedbeanjk’s picture

I also get this error - see part of error msg pasted below

sites/all/modules/seo_checker/basic_seo_rules/basic_seo_rules.module).

Can I safely ignore this error msg until a fix can be done or should I disable the module for the time being?

Thanks

miruoss’s picture

Issue summary: View changes
Status: Needs review » Fixed

Fixed in 7.x-1.7

Status: Fixed » Closed (fixed)

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