Was Creating/Editing KB Articles... Then They Stopped Showing on the SupportCenter

[nmorse]

Everything was working great... Decided to spend some time today adding a few articles to the KB, went back to refresh the support center to see the new articles flow in to the front page and all the articles vanished. Weird, cuz they were refreshing/working just 10 minutes earlier.

Any ideas? Nothing changed in the settings...

Thanks,
- N

** Update... So, it seems to be related to the tag/RSS... As suggested before, I created a "catch-all" category tag called "all articles" (without the quotes). However, when I click on the tag, the RSS button doesn't appear, nor can I simply navigate to xyz.edu/helpdesk/kb/rss/tags/all%20articles as I get a blank page. All my other individual tags seem to work, but not this one. Any ideas? **

[jstanden]

Hey there!

Are you able to provide a link to this symptom somewhere I can see it?

If not, even a screenshot of the tags will do so I can attempt to reproduce it.

Thanks!

[nmorse]

Hey there!

Are you able to provide a link to this symptom somewhere I can see it?

If not, even a screenshot of the tags will do so I can attempt to reproduce it.

Thanks!

Sure, if you don't mind, I'll private it to you...

[jstanden]

Understandable. :)

I'm grabbing some quick lunch, but I should be around all day. I'll take a look in a couple minutes.

Thanks!

[nmorse]

Understandable. :)

I'm grabbing some quick lunch, but I should be around all day. I'll take a look in a couple minutes.

Thanks!

No problem... It's in your PM.

[nmorse]

Hey Jeff,

Didn't hear from you yesterday -- any word on this?

This appears to nearly solely be related to RSS... As the "recent changes" and "most popular" RSS bring up pages that say:+

A CDATA section was not closed.
Line: 15 Character: 33

[gibbscam]

Hey Jeff,

Didn't hear from you yesterday -- any word on this?

This appears to nearly solely be related to RSS... As the "recent changes" and "most popular" RSS bring up pages that say:+

A CDATA section was not closed.
Line: 15 Character: 33

This illustrates one of my long-standing complaints about WGM. On occasion there are long delays on responses. I have a thread in another part of this board where they did the same thing.

[jstanden]

This illustrates one of my long-standing complaints about WGM. On occasion there are long delays on responses. I have a thread in another part of this board where they did the same thing.

There are occasional delays because the people who write the software are the ones who are directly answering your questions. That's not as common as you'd think. ;)

We could hire more people to just post silly replies and give you guys the run-around ("Try this... try that...") but we've never believed in that approach.

[jstanden]

Hey Jeff,
This appears to nearly solely be related to RSS... As the "recent changes" and "most popular" RSS bring up pages that say:+

A CDATA section was not closed.
Line: 15 Character: 33

Ah! That explains that.

Would you mind sending me the broken feed output (saved from the browser)? I'll have somebody clean that up.

jeff AT webgroupmedia.com

[nmorse]

Sent. Thanks Jeff.

[jstanden]

Just got it, thanks!

Looks like we just need to be escaping the CDATA content better. A couple brackets would prematurely close it.

That explains why it suddenly stopped working for you -- it's just a specific text fragment.

I'll bump this up on my list today so you aren't stranded. ;)

[nmorse]

Wonderful! Thank you!

[jstanden]

Alright, I managed to reproduce the issue right away on my development helpdesk with your sample.

The error we're getting is:
Warning: DOMDocument::saveXML() [function.DOMDocument-saveXML (http://localhost/website/kb/rss/article/function.DOMDocument-saveXML)]: output conversion failed due to conv error, bytes 0x93 0x53 0x61 0x76 in

Those invalid characters came from the text block, though we should be able to convert them to a compliant format easily enough. They likely just came from a Word document or something.

I just committed my Watchers plugin a couple minutes ago, so I have a clean slate again to get this into SVN. I'll post an update shortly.

Thanks!

[jstanden]

Alright, this is fixed in SVN (Build 389).

I just tweaked the KB RSS feeds to properly use UTF-8 encoding, instead of ISO-8859-1. This was needed for future translations anyway.

Thanks for the report!