The helper module 'Variablecheck' requests me to inform you (the module maintainer) about following issue:

smtp_library	s:44:"sites/all/modules/contrib/phpmailer/phpmailer.module";

Thank you for your acknowledgement!

Comments

sun’s picture

Status: Active » Closed (works as designed)

Sorry, I've spent a couple of minutes trying to understand the purpose and point of http://drupal.org/project/variablecheck by looking at its code, but I've no idea what it is good for.

That said, the serialized value you mentioned is clearly wrong, it's 53 characters in length. However, I don't know how you managed to get that bogus value into your {variables} table.

Saving the module settings once again should resolve the issue.

However, please note that PHPMailer is not functional for D7 right now, the code is still ported in #811774: Port to D7 -- which actually confuses me even more, since that could only mean that you have this variable value from an upgraded D6 installation, and if that is the case, then it would be a system module update in Drupal 7 core that wrongly converted/serialized the value (which is a bit unlikely).

Anyway, there are too many unknown and confusing factors in this issue, so I'm closing it.

Thanks anyway.

cafuego’s picture

@sun

variablecheck.module tests if entries from the variable table can be unserialialized properly. It lists any entries it can't unserialize. The aim is to help users get rid of variables that weren't originally serialized - ie: ones left from D5 or older installs that weren't properly uninstalled or upgraded. Those generate warnings that can't be turned off via the Drupal UI, as they're generated before that UI setting can be applied.

@the_phi

Though variablecheck found this problem, the format of the entry is fine ... it just not the right length :-) I hadn't intended for it to find those, but in retrospect I suppose it makes sense. As sun says, the issue would be to find out how core would've managed to save this entry with an incorrect length.