I wouldn't but still come on guys this is so frustrating. fix your software please. Or at least stop breaking it.
I appreciate it must be frustrating but please provide some more details.
I've just tried exporting a sermon (on Windows) to both PowerPoint and Proclaim and it worked fine.
So please outline the exact issue you are seeing and on which platform.
And it is best posting about this sort of issue in the Desktop App forum
Yeah the problem is documented over on the other boards I'm just publicly complaining about it again.
All you need to do to break the export feature is change one slide a little bit and then you can only export to powerpoint as backgrounds not editable text and Logos' ability to work with slides and formats is terrible.
so basically the work i did on my powerpoint this week was for nothing yet again.
It happens whenever they change background code or something it is not a big mystery what the issue is.
Anyway much like proclaim faithlife tv faithlife streaming the faithlife app and all the other extra projects Logos promotes without finishing it seems the money i spent on the premium preaching suite was pretty much wasted. And much easier to do in Word and Powerpoint.
You'd think I'd learn by now...
Yeah the problem is documented over on the other boards
Do you mean at https://community.logos.com/forums/t/215472.aspx
The problem Michael initially reported in that thread seems to be fixed
I know you commented on that thread but I'm afraid I still don't understand the specific problem you are referring to
I've just tried modifying a slide and I could still export successfully.
Yes they fixed it but it is broken in the same way again for me. Sorry I don't have time to show you and prove it to you I'm already behind thanks to my awesome bible software being broken again.
Hi John,
I understand how frustrating this is. I was able to replicate the issue exporting to Editable Powerpoint slides by having a blank content field in one or more of my slides. We have a fix for that going through testing now. If it helps, I was able to work around the issue in the meantime by adding a couple spaces to any empty content fields in my slides.
Hi John, I understand how frustrating this is. I was able to replicate the issue exporting to Editable Powerpoint slides by having a blank content field in one or more of my slides. We have a fix for that going through testing now. If it helps, I was able to work around the issue in the meantime by adding a couple spaces to any empty content fields in my slides.
Thanks Dustin, that sounds like a lot of extra work to try to make this work. I would need to make sure and check each and every slide and click every single empty box and add a space or two then I can export my sorta janky slides out of Logos to PowerPoint to try and fix them?
Hopefully the test is going well
Where are we at on the testing? I don't claim to be a software expert, but it seems like a week should be enough time to fix something that always worked previously on software that costs thousands of dollars.
This is a basic function that needs to be addressed quickly even if it means an update for only this issue.
I put in a request for a refund. I have not heard back. I am so shocked lol.
but it seems like a week should be enough time to fix something that always worked previously on software that costs thousands of dollars.
Only very small patches with a very clear cause that is independent of other features is a candidate for an emergency patch that can cut corners and be released in a week. When a bug is a side effect of a change to other features, you should expect a minimum of the standard coding/internal testing/beta testing/move to production cycle of 6 weeks for Logos. Depending upon where they are in the cycle when the bug is reported, this translates into 6-12 weeks wait on the users' end.
When, as in this case, there is a workable workaround, Logos would be foolish to break the discipline of the 6 week cycle.
Unless the request is in the 30 day refund period, the request would need to be kicked upstairs (perhaps multiple times) before a reply should be expected.
There are a lot of sermons and Bible classes in 6 to 12 weeks.
This is like having Microsoft Word that works perfectly unless you actually want to print something. 6 to 12 weeks is not OK for basic functionality.
Hi John, I understand how frustrating this is. I was able to replicate the issue exporting to Editable Powerpoint slides by having a blank content field in one or more of my slides. We have a fix for that going through testing now. If it helps, I was able to work around the issue in the meantime by adding a couple spaces to any empty content fields in my slides. Thanks Dustin, that sounds like a lot of extra work to try to make this work. I would need to make sure and check each and every slide and click every single empty box and add a space or two then I can export my sorta janky slides out of Logos to PowerPoint to try and fix them? Hopefully the test is going well
After looking through my last couple sermon files, I figured out how to apply his workaround. It was simple on mine. Maybe yours would be too?
The only slide in my sermon files that had any blank fields was the title slide. I right clicked on that slide and hit "edit." In the edit slide window, I added 2 spaces in the "subheader," "reference," and "body text" fields. I only had to change one slide.
Exporting editable slides now works like it did before for me.
Logos People: If you're reading this, it needs to be communicated to users somehow. I've gone weeks with a problem that could have been fixed in 30 seconds, because I had no idea what to do. That should never happen.
I just went through my email inbox. Since this thread began on May 14, I have received 46 emails from Logos. None of them were about this known issue or how to make this function work until the next update. Those are the kinds of emails I need. I should not have to search through a message board to figure this out.
That’s great hopefully it keeps going for you brother.
Especially in church traditions with daily services. But with an easy workaround, there are not enough to justify the risk of making things worse with a quicky out of cycle patch. What is needed is better communication of the work around. I used a version of Microsoft Word for several years where I carefully avoided one layout change that would crash the program. And I had great fun showing people that I could crash Microsoft Word at will.
What is needed is better communication of the work around.
And the church said, "Amen!"
It is an easy workaround, although it wasn't explained very clearly. I knew my slides did not have any blank fields, but I went through every one of them anyway. Then I noticed the title slide (which I always replace with a graphic after the export). That was the culprit.
Someone at Logos should make a step-by-step instruction and email it.
