Hi,
I get an "Oops" error when I click "save but don't publish" after I've tried to create a blog in the MS V8i Programming Blogs section. If I try it again with the same subject/body I get a message "Your blog does not allow duplicate posts".
Am I allowed to post there? I couldn't see the error in the list of things being worked on that hasn't been fixed.
Cheers,
Steve
Yes, this is one of the known issues and is being investigated. Although the initial error happened, the article should have been saved (in your case, not published). In fact, in the MicroStation V8i - Programming blog, I see 5 different articles from you that have not been published -- "Microstation's GATTE", "GTAGE - Global Tag Edit", "Test", "Test2", and "Test3".
Yep they're all mine, I tried a few times I don't want to directly click publish but does that work? And can you delete those not published blogs for me since I can't see them? thanks. I guess I will wait until you have an update.
Yes, it should work -- there have been plenty of folks blogging -- see http://communities.bentley.com/b/ for an "overall" article listing. I cleaned out the "Test..." articles, but you should still be able to get to Microstation's GATTE and GTAGE - Global Tag Edit.
Sorry, how do I get to my saved blogs? They are not under Programming Blogs and they are not under Blogs in my profile.
Hmmm... I stand corrected, it does not look like you can get to your own articles. I will send the content to you through conversations. Apologies for the confusion there.
Thanks Phil. If you can delete all my current saved blogs and from now on I'll publish directly (until there is a fix).
Regards,
Okay... cleaned up. Again, apologies for the inconvenience.
Ok, Phil I just published a blog to the general V8i forum, and I got an "Oops" error, but it's there. However I also attached a file with it as well, but I can't find where that is available?
Hmmm... good question. Maybe the space in the file name caused that? Dunno... just grabbing at straws as to what might be the problem there. Have you tried reattaching the file to the blog article?