Question cb.wall.php causes RSS feed error: XML Parsing Error: junk after document element

I found where this ".stupidIE" CSS class is loaded: "forum #3", but this isn't a file. A Joomla extension (component, module, plugin, template or language) is creating dynamic CSS. As LittleJohn wrote:

You can maybe search all files in your Joomla folder for "stupidIE" to see where it's coming from.

The usual suspect is, unfortunately, RocketTheme. You might have some success if you asked your question at the RocketTheme support forum. Please let us know how you get along. I'm sure, if they have any information about this ".stupidIE" CSS they will be very keen to help you fix the problem that you're having with Kunena RSS feeds.

Damn, i'm sure i've seen it somewhere in the code couple of days ago and now tried opening all files i've edited since last week without success. Anyway, i'll wait for the beta and i'll install it on the live site so if the problem with the rss persists there too, i'll continue my quest again


p.s. the username and pass to rt forum is from a friend of mine who is on vacation currently and cant send it to me, but i'll have it in a couple of days.

The error is gone in 1.6 beta

If anyone has the same problem, the "stupidie" css class which was causing the problem is located in youriste/components/com_comprofiler/plugin/user/plug_wall/cb.wall.php

So, you mean to tell us, this is something caused by Community Builder? Which version of CB are you using? Is this a product that's developed and supported by Joomlapolis and what do the folks at Joomlapolis have to say about this matter?

I'm using cb 1.2.3, but i'm not sure it's joomlapolis plugin. I've used awdwall previously and i've uninstalled it completely.. also the plugin info just says:
Description: WALL.
Folder / File: user/cb.wall.php

Whatever cb.wall.php is (I've never heard of it), wherever it originated, it's what caused your RSS feed error. I'm pleased we got that problem sorted out. :woohoo:

Do you have any other Joomla extensions (components/plugins/modules/templates/languages) that might cause a problem for Kunena in the future? Anything else you can get rid of? :whistle: