Parse Error and Fatal Error

I can confirm this issue. Started to happen after upgrade to 1.6 to nodes with custom views.

It doesn't happen on every node though, some of them just work fine.

Similar problem here, except I didn't upgrade. This is my first install:

Parse error: parse error, unexpected T_STRING in /home/mysite.com/httpdocs/modules/nodewords/nodewords.module(812) : regexp code on line 1

Fatal error: Failed evaluating code: 632.jpg in /home/mysite.com/httpdocs/modules/nodewords/nodewords.module on line 812

632.jpg is a real file, and it appears normally in the View just preceding (including) this Node.

Again, most nodes are fine. Just this one freaky one so far.

What PHP version do you use? You can see that on admin/logs/status.

4.3.9.

And here's some more info: I just managed to replicate this bug on a node that had previously been working fine.

I uploaded a picture to it via CCK imagefield. No problem. Then I deleted that picture and uploaded another one where the filename (preceding the .jpg) was a NUMBER, and it choked.

In every instance of failure, the filename is a number.jpg

[duplicate post removed]

Try to replace:

 $pattern = '/<img\s[^>]*alt=["\']([^"\']*)["\'][^>]*>/e';
 $replacement = '${1}';
 $text = preg_replace($pattern, $replacement, $text);

with

 $pattern = '/<img\s[^>]*alt=["\']([^"\']*)["\'][^>]*>/i';
 $replacement = '${1}';
 $text = preg_replace($pattern, $replacement, $text);

around line 812 (in function function _nodewords_check_content($text) {) of nodewords.module.

In the first line: replace "e" with "i" at the end.

Tell me if that worked.

YES. You nailed it.

Yeah, stupid typo. Only tested it with non-number filenames.

When I get home later today I'll release a new version.

Was having same problem after the upgrade, solved editing the pattern too, the "e" modifier makes preg_replace treat the replacement parameter as php code.
The error was present also with "alt" containing non-php valid chars like " " and "!", for example
<img src="xxx" alt="blank space" />
and
<img src="xxx" alt="exclamationmark!" />

Fixed in 5.x-1.7.