so i installed simplenews, enabled related content for the newsletter content type, and went about selecting some contents from my enabled views. updated. went back to view the node, and the css is VERY messed up!!

the font size gets bigger and bigger as you go down the page.

if no relatedcontent is added this does not happen, but the more nodes are added, the larger the font gets (one increase for each node teaser)

I have not used any templating/css, this is simply using the default install.

my theme is marinelli

Comments

tallsimon’s picture

tallsimon commented

it also messes up the styles of administration menu (font size changed and drop downs no longer have dark background) and adds external link styles to all my links!

hokumboy’s picture

hokumboy commented

Same here.

It seems that the modules opens a lot of html tags (mostly header tags), but doesn't close them.

karol haltenberger’s picture

karol haltenberger commented

I ran into something like this after enabling absolute links.
In my case all slashes ('/') became prefixed with the base_url string thereby destroying the element closing tags.

Replacing a line in relatedcontent.theme.inc seems to have fixed the problem in my case.
It may or may not work in other cases.

//      $contents = str_replace(base_path(), $base_url.'/', $contents);
      $contents = str_replace('href="'.base_path(), 'href="'.$base_url.'/', $contents);
zilverdistel’s picture

zilverdistel commented

I had the same problem. Disabling the setting for altering urls to full absolute urls "fixed" my problem ...

hs@henrikstrindberg.se’s picture

hs@henrikstrindberg.se commented

Disabling "Create absolute links" looks fine but creates double path prefixes (.../sv/sv/...) on a multi lingual site.

Changing the code (#3) worked for me. Thank you :-)

The problem doesn't appear on my local installation or on my test site, but on the production site which is on yet another web hotel.

hs@henrikstrindberg.se’s picture

hs@henrikstrindberg.se commented
Version: 6.x-1.0 » 6.x-1.x-dev

Same error in the dev-version. Would be great if this was fixed in the next release!
Thanks