Sermon Published without my permission

Why would anyone ever want automatic publishing... this is daft in my opinion. Publishing something is a deliberate act when you feel that something is worth publishing... you wouldn't even have this feature for a forum post... something as important as a sermon should never wind up published in draft... this is a terrible bug!

Wait a minute, I just noticed I  have 7.5 version and the check box for automatically publishing to sound faith is not  showing on my sermon editor.  Any idea why? Is that feature still in beta? My Spanish sermon published to soundfaith which I don't mind, but it'd be nice to have the option which one I want to publish and which one not.

DAL

OK, so it's showing on a new sermon when I open a blank sermon document, but the option is not available when I click on the edit sermon link on previously created sermons.  Now what? How do we fix this to unpublish and publish back and forth?

Thanks!

DAL

but the option is not available ... on previously created sermons

This is by design. Sermons created before the introduction of the autopublish feature do not have any autopublish options. If you'd like to publish those to SoundFaith, you can use the "Export... > Post to SoundFaith" option to manually publish.

If the option to publish a sermon to SoundFaith is already available in the Print/Export, then what is the purpose  of the auto publish button option? Why not simplify things and take the auto publish button out? 

In this typical workflow, there's not a convenient time to publish the completed Sermon after delivering it on Sunday.

Of course there is.  It's at 8:15 on Monday morning, right after you've poured your first cup of coffee and fired up your computer, and right before you open a new document for the following Sunday.

Opening a document and selecting "publish" just isn't that hard.

I apologize if this comes across as a bit harsh - I'm not trying to be combative. I'm just not seeing any significant user benefit here - certainly nothing that would outweigh my concerns about Logos publishing my work by default unless I explicitly tell them not to.  That seems fundamentally backwards.  I want to be able to trust my software tools. If they may do things that I don't expect - especially things with potentially public consequences - it's unsettling. And the last thing FaithLife should want would be for users to feel safer doing their work with other tools in part simply to be more confident that they can control if and when that work is published.

Use it or don't use it, nobody cares. This is why we can't have nice things.

Your precious sermon isn't that precious. I used to be a preacher. I hated gatherings with other preachers because all they talked about was how to save money (cheat) on taxes, what was wrong with their churches, and why they deserved better. It was quite disillusioning for a young preacher boy. This is just an extension of the same old thing.

It isn't auto-publishing.

With respect, mine did publish automatically with the box unticked.  

Software sometimes has bugs. Logos is good about fixing stuff quickly. I haven't bothered enough to read every post, but I'm pretty sure a way to make it not public has been given.

I agree...and...they will fix the bugs.  What is not being said is what they will do with the opt-in option rather than the opt-out default.  

BTW, it may be made "not public" but the document will not go away.

. 

We have a few regular "privacy hawks" on the forums. Although I don't fully agree with their position(s), I am sensitive to their desire/need for privacy. 

I'm offended at this statement ... hawks? I prefer eagles.

After the recent decision to give the world all the Americans' data and then some, I tried out Onion Browser, figuring the user servers would be only gigabytes away from crashing. The Logos sites refused Onion. I'm sure there's a reason but it was funny too.

Additionally, if people don't like it they don't have to use it.

That's absolutely correct. And there's value to FaithLife in explaining why you might not use it - especially if the fix is simply changing a default setting. They may, for a variety of reasons, choose not to change that setting. But at least they'll have a better idea of why they aren't reaching a segment of their user base.

There's another aspect of this that hasn't been discussed. Authors have certain legal rights to their work. This is not my area of expertise, but I'm surprised their attorneys gave them the permission to do it this way. If I were in effect the publisher of sermons, I'd want to have explicit permission from the authors before publishing anything. There may be some legal language covering this in the fine print somewhere, but they would seem to have a much better defense against someone saying "I never intended to give you permission to publish that" if this were an opt-in rather than an opt-out.

I have a different problem. I received an email that the message (photo attached) would automatically be published. However, when I open the Sermon editor, the checkbox does not even exist. I have 7.5.0.0045. The challenge I face is that this particular 'sermon' was a response to a congregant's theological challenge. The document contains personal information that I exported and emailed to him. Now that information will be published without my consent and I have no way to turn it off.

Any ideas as to why I don't get the checkbox?

Marc

I wrote it March 30. I received an email yesterday (Sunday) that is would publish today (Monday). Yet the document was created before the feature went live.