Active
Project:
Content Optimizer
Version:
7.x-2.0-beta4
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Jul 2012 at 16:14 UTC
Updated:
26 Jun 2014 at 23:48 UTC
Jump to comment: Most recent
Comments
Comment #1
larjohn commentedSame goes for Greek! :(
Comment #2
lsolesen commentedCould you confirm this with the latest dev?
Comment #3
larjohn commentedyes it still happens
Comment #4
lsolesen commentedCould you report the exact steps to reproduce on a clean install. I cannot reproduce the problem.
Comment #5
larjohn commentedI am using Entity Translation and in the translated field I enter greek text. Then I get 0 words error.
Comment #6
spidersilk commentedI'm having a very similar issue, and it's not on a multilingual site at all. The site I'm encountering this one is only in English.
In this case, it keeps insisting the body of the node contains only five words, but it actually contains 4 paragraphs. The only thing I can see that contains five words is the node title. Maybe it somehow thinks the title is the body? But I don't know why it would make that mistake...
Comment #7
spidersilk commentedOK, figured out what was happening, in my case at least: if the machine name of the body field is anything other than "body", it doesn't recognize it. So if you have a content type that uses a different name for that field (like Description, Intro, Review, or whatever), unless you make sure the machine name is still "body", it doesn't recognize it. And curiously, if it can't find the body, it seems to default to thinking the title is the body for some reason.
Not sure if that's the case for the others who are having this issue or not... However, it would be helpful if maybe in a future version, it was possible to indicate in the settings what field(s) you wanted it to check for any given content type. Because apart from the problem of some content types having a different name for the body field, some complex content types may have more than one longtext field and it would be nice to have the option of checking all of them.
A couple of other things I discovered in the process of troubleshooting this:
1. If you have two node create/edit forms open in two different tabs, it can get confused between them and report one node's results for the other node.
2. If you change the content of a field and then click "Analyze Content" again, it doesn't show any changes. You have to save the node first and then analyze it again. That's not really a bug as such, but it might be helpful to indicate this somewhere so that people don't get confused and wonder why their changes aren't showing up in the report.
Also, I found a problem with the meta description checking, but that's unrelated, so I'll put that in a separate issue.
Comment #8
bzitzow commented@spidersilk:
For your issue, roll this patch:
Feature: Configure which field represents body
I do think that multi-lingual may be a different problem, however, this feature may help you solve that problem (although it was not intended or intentionally designed to solve the multi-lingual problem).
Please test it and let me know. Cheers!