Blog privacy error

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
1/4/2010 11:27:14 PM
Gravatar
Total Posts 3

Blog privacy error

Not sure if this is a known error or not, I thought I'd just let you know my experiences. When writing blog entries "in the future" to indicate they should not be published, it is still totally possible for an unauthenticated user to navigate to these blogposts using the Archive and the "Next" and "Previous" post-links on the individual posts. In practice, this means that it seems mojoPortal has no way of juggling unpublished blog-posts. As a sidenote: A simple "bit" to indicate whether or not a blog post is published or not would be far superior in my opinion.

Running on latest Windows Server, SQL Server as a DB platform and the 2.3.1.6 MSSQL version of mojoPortal.

Thanks! :)

1/5/2010 1:15:31 PM
Gravatar
Total Posts 18439

Re: Blog privacy error

Hi,

I agree with you, that is a bug. I fixed it in my copy today so it will be fixed in the next release.. I added an IsPublished field, but I also enforced not showing posts with a future publish date even if they are flagged as published.

So basically a post is now considered a draft if it either has the IsPublished flag set to false or if it has a future start date. The default is for IsPublished to be true. This way users who use tools like Windows Live Writer can make posts with future publish dates without having to worry about the bit flag which is not available from the Live Writer UI.

Best,

Joe

1/5/2010 8:14:51 PM
Gravatar
Total Posts 3

Re: Blog privacy error

Thanks a lot, I really appreciate it!

From a user point of view, I find the way WordPress does this is pretty good, however I'm not sure if it's compatible with Live Writer. Basically it has two buttons, "Save" and "Publish". Saving the entry doesn't change the IsPublished-flag (if it is published, it stays published, if it hasn't been published, it stays unpublished). The Publish-button turns into an "Unpublish"-button if the IsPublished-flag is set to true. In this scenario, IsPublished defaults to being set to "false". This works great with my typical workflow, which is to create a draft when I find inspiration for it, browse drafts for something to finish and publish.

Also, it would be great if the "Edit drafts" was a "View drafts" instead; the little edit-icon is present anyway. I really like seeing howthe article looks with the current theme enabled. How I find myself copying the URL from the edit page and punching it into whatever browser I'm using to preview it. 

Again, thanks a lot for the quick reply. :)

Cheers, LT.

1/7/2010 4:33:37 AM
Gravatar
Total Posts 18439

Re: Blog privacy error

Hi,

I have added a "Save and Preview" button when editing unpublished blogs, so you will be able to see how it will look when published.

Thanks for the beers!

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.