|
It seems to have been temporary because I can properly reply again. But the bug was definitely alive for at least 10 minutes. Between 5:15 PM and 5:25 PM EST on Mar 31, 2009.
I hope you were not testing out some April-1 joke code that auto deletes replies after a short time interval
|
|
|
|
|
Has anyone else managed to get this to work yet?
I've modified our RSS feed to add the necessary category tags (on a post by post basis) and submitted it OK, but so far the aggregator is not finding any posts (there should be three marked for CP consumption).
If anyone would like to look at the RSS source (http://www.riverblade.co.uk/rss.php[^]) and tell us what we're missing, I'd be happy to listen and tweak accordingly.
|
|
|
|
|
The aggregator currently only runs once a day. We didn't realise so many would jump onboard so we're increasing the frequency in a few minutes and adding more info explaining when aggregation runs occur.
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
Hi Chris,
Thanks for the info. That'll be it, then!
Looking ahead a bit, is there any way authors will be able to view diagnostic information if it fails to find anything when we know it should?
|
|
|
|
|
What would suit you? An email each time a blog was grabbed (This should happen already) and maybe an email if nothing was grabbed or there were errors?
We don't want to pester. If you go dark for a few weeks then the emails could be annoying.
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
Rather than sending more emails I think a button which let authors view the logs from recent polls would be more than sufficient.
There is a case for an email if an error was detected by the aggregator, but I certainly wouldn't do that if but no new posts were found but no errors were detected.
|
|
|
|
|
I like the idea of your list of blogs showing the latest download results. I'll add this to our TODO.
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
Cool.
FWIW our blog is still showing an update status of "Never", so either the aggregator hasn't polled it yet (which I would think would be unlikely by now) or it didn't find anything for some reason. That being the case, we need some help figuring out why...
|
|
|
|
|
Hi Anna, sorry for the late reply.
So I looked into this and the problem was that your blog content's html was not escaped. I think the simplest way to fix this is to surround your <description> elements with <![CDATA[]]>.
Before:
<description>
<div>Lorem ipsum doler..</div>
</description>
After:
<description>
<![CDATA[<div>Lorem ipsum doler..</div>]]>
</description>
|
|
|
|
|
Hi Thiru,
Thanks for letting me know!
I've updated our feed accordingly, so if you could take a look at it and let me know if it's OK now I'd appreciate it.
|
|
|
|
|
Yep looks good! Should be pulled down shortly.
|
|
|
|
|
|
|
I knew there'd be a trick to it. Thanks Chris!
|
|
|
|
|
It looks like it's still failing (the status is showing as "Updated: Never"). Given that there should be quite a few posts marked in the feed, what errors are you seeing now?
|
|
|
|
|
Sorry about that. Our polling service was accidentally shut down. It's up now and your articles are in the queue. Sean will be looking at them very shortly.
|
|
|
|
|
Thanks for letting me know. I'veactually just found that out by accident through an "article deleted" message!
Observations so far:
1. You really need a status/error view on the poller (visible to authors for their feed only) to mke troubleshooting easier.
2. The aggregator is putting blog posts into a specific section (C#) by default, which isn't really a good idea. How about using an "Uncategorised Blog Posts" section by default?
3. Given that articles are being deleted by Sean as they are posted, some better guidelines on what you are looking for are obviously required (e.g. two out of four of our posts on last year's European Software Conference got through, but the other two didn't). That's a little odd, as the content is comparable.
4. The transcribed articles should really include an auto-generated link to the original post (which would avoid reader confusion if the post is one of a series and appears out of context).
That's all I can think of for now. Hope the above is useful!
|
|
|
|
|
Hi All/Chris,
Observing common mistakes from a first time submitter, it really seems like article formatting is a recurring problem. Others, such as Dave Kreskowiak, appear to feel the same (judging from his comments).
Would CodeProject consider FORCING a preview for those whose articles might go to 'Pending Approval'. If you don't trust an author to submit an article correctly, you probably should not trust him/her to properly format it. I'd also recommend sizing the Preview window at 800x600 (is this still considered a standard for UI design?), or perhaps 1024x768.
Finally, some article are so bad I can't tell if it is a legitimate article or someone testing the Submission system. Perhaps a step (or check box) to indicate that "This is a Test" would be in order. For example, at Step 1 (or something similar):
* This is a Test
* This is a Submission
Jeff
|
|
|
|
|
I'll add these to the todo list.
In terms of having a "this is a test" button, unfortunately it will not be used. People post rubbish just to post rubbish sometimes.
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
> I'll add these to the todo list.
I think you'll see a benefit. If not, then scrap it later (why keep it around and maintain it if it does not work?)
> In terms of having a "this is a test" button, unfortunately it will not be used
You can lead them to water, but...
|
|
|
|
|
Nice idea putting the news items in individual tweets, much easier for me to manage than reopening the mail app to open the next one in a new safari tab (TwitterFon embeds an instance of safari) but the links don't get added to the tweet, so you just get an interesting subject title I think those responsible for the sacking of the hamsters responsible need to be sacked
He who makes a beast out of himself gets rid of the pain of being a man
|
|
|
|
|
Jeff is about ready to tear his hair out on that feed. I forwarded this message to him because I know he loves to perform under pressure.
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
As per the subject - pasting a URL into a text used to create a nice set of <a> tags, with the selected text as the displayed link text. That no longer happens, on Chrome or Firefox (Windows) or Safari or Firefox (OS X).
Sorry if it's a repost/known issue, but it's one of those features you really miss when it disappears.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Which browser are you using? Can you give me an example?
I've revamped the copy/paste in order to make it a little nicer but I may have busted something.
(If you're using FireFox 2 then you could be in trouble: Paste on that was flaky and has been discontinued on the assumption that Firefox makes it painfully difficult to stick to an outmoded version)
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
Chris Maunder wrote: If you're using FireFox 2 then you could be in trouble: Paste on that was flaky and has been discontinued
WTF!?!
It's always worked fine for me on FF2. Why did you have to turn it off? So just tell people it's flakey on FF2 and leave it at that. Tell them you won't listen to any complaints on FF2. But please turn it back on. I have no choice about what browser I use for most of the day. Please!
|
|
|
|