Question Why Is KD placing a number in front of my articles?

Installed the package a couple of weeks ago and at some point an annoying little item began to appear.
The site is www.RoadsAndRiders.com - and at the beginning of each article the number 1 is placed into the html just before the headline.

<div class="item-page">
1
<h3>Oscar's Story</h3>

I suspect this is a KD issue, as I've not touched anything else. Can somebody confirm it is? And how do I get rid of it.

Thanks ....

The issue has been resolved - see Number thingy

Thanks for the steer, but that doesn't solve it. There's no CSS tag defined before that number appears in the HTML .... But just to be certain I placed that CSS class into my CSS file and updated. Nothing, nada, zero, zilch.

Any other suggestions?

----
Oops .. okay I see there's more to the thread than the CSS suggestion. Frankly, I'm lost. Is the fix to download that ZIP file and use it to replace the entire .php file?

LeeWonnacott wrote: Is the fix to download that ZIP file and use it to replace the entire .php file?

Yes.

Thanks again, Sozzled, but that didn't fix the problem. I'm still getting a number 1 where it's not wanted.

I'm surprised a known issue has not been addressed. Really like this plugin, it solves a problem but brings a new set along with it. It's worth the effort for sure, but my facial muscles are tiring from the constant grimace ....


.... update a few minutes later.

Okay, now I'm really confused. I have KD on two sites; www.SebagoSailors.org and www.RideAroundAmerica.com

I first tossed that new .php file to SebagoSailors and it's didn't take the number 1 away. Posted my message. Then thought, "what the heck?" and put it onto the RideAroundAmerica site ... it worked! Obviously there's a toggle somewhere I don't understand. I just celebrated another birthday with a 6 as the first number - am I getting too old for this kind of stuff?

Thanks to all who help with this program ....

LeeWonnacott wrote: I'm surprised a known issue has not been addressed.

We could have a 20-thousand word discussion on that. The topic Number thingy is exactly where this issue has been addressed. Unfortunately, one or two people tried to turn the topic into a discussion about a number of other, unrelated issues they were having and we had no other choice but to lock that topic. It was unfortunate that we had to lock that topic instead of ensuring that everyone else (who has this number "1" appearing on their articles as a result of using Kunena Discuss 1.6.4) is given the same opportunity to help to contribute to the resolution of the problem.

Now this is my dilemma: I haven't used Kunena Discuss myself. I haven't had time to test Kunena Discuss or to see how it works because of other matters. Therefore, I'm relying on secondhand information to advise you.

You asked why the solution works on one site but not on the other. You asked if there's a "toggle" somewhere. I doubt that there's any "switch"; more likely, the reason that the solution appears on one site (but not the other) is because of a difference in the way the two sites were setup. Every day, when I'm asked to look at other people's websites, I find a million reasons to wonder how people ever managed to keep their websites running. People have dozens of components, plugins, modules, templates (some of them disabled, others they've forgotten about) that are old, outdated, clunky or haven't been updated for four years or more. People are still using "legacy mode" two years after its "best before" expiry date. People still have an expectation that site mapping tools or search engine "optimisers" actually make a difference in the "ratings game"; or they try to reduce server load by running other software like caching. In the end they finish up with an alphabet soup of software that is indigestible as far as their webserver is concerned.

I'm not trying to suggest that this is your situation, Lee, but I do want to advise you that sometimes it's really hard trying to provide a catch-all advisory that meets everyone's needs. If there is a catch-all, it's the KISS principle . But sometimes solving these issues takes a bit of time and you shouldn't be turned off by that, either.

Here's a suggestion that might actually help: see Is the "Remember me" function controlled by the session lifespan?