Hi,

with last dev version (26th january 2012), there are "div" surrounding raw value. Since these value are used in a href with mailto tag, it breaks all the rendering. The same happens also on a raw text used to create a link inside the template.

There was no problem with previous version.

Regards,

Comments

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Not sure I understand what you mean. What raw value? Where is it replaced/displayed?

Can you post a screenshot or make an example to explain the problem?

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Postponed (maintainer needs more info)
tahiticlic’s picture

tahiticlic commented
Status: Postponed (maintainer needs more info) » Active

Raw value is the text, but it is <div class='...'>the text</div> that is rendered.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

I still don't know what you mean? Is "the text" a field or where is it coming from?

tahiticlic’s picture

tahiticlic commented

Ok, in the "Simplenews" content type, which is used to create simplenews issues, I define a textfield field technically named "my_field".

On "Display fields" tab (or something like that, in french it is "Affichage des champs"), I choose to render "my_field" as a "raw text".

Then, I expect to have a raw text, without any surrounding div, but there are surrounding div.

For instance, if I have a content where my_field field contains "My Text", in the rendered value I'll get <div class="...">My Text</div> even if I was expecting My Text.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Postponed (maintainer needs more info)

What classes are exactly on that div? That might help finding our where they are coming from. If it would be us, there should actually be multiple div's. Also, we do not check the display mode (e.g. Plain text, which is what you meant with raw text I guess).

I do not know which commit could have possibly changed to result in this as I'm not sure which version you used before. For example, can you try it with beta1?

What you could also do is use git to try each single commit that happened since 26. january (and possibly before) to find out which change exactly causes your issue. There is a nice feature called git bisect that can help with this. Google should be able to tell you more about it :)

One thing that actually might have caused this indirectly is the support for the mail_theme so maybe it is using another template than the one you used before.

JRZ-2’s picture

JRZ-2 commented

Hello,

Doesn't seem to be a simplenews issue…

Are you using Display Suite for displaying your content types ?

If yes, on your page, go to 'manage display', and then to 'custom wrapper'. Try to change the wrapper tag from "div" to "article".
The "p" tags magically reappeared!

Let me know if it worked for you.