wpforchurch_allen

Hello Laurie,

I sent an extended reply to this question to your other email but for the benefit of the community I am going to post part of the answer here as well.

It appears that your theme doesn’t know how to handle the Sermon Manager custom post types. Sermon Manager utilizes a WordPress feature called custom post types which allows sermons to be treated sort of like blog posts. Sometimes themes (usually free themes or poorly written themes) interpret custom post types incorrectly or do not incorporate them those elements at all.

Before investing any time into editing your theme consider experimenting with a different theme that you like to see the difference. Chances are if it is a free theme that there is another free theme out there that will work better and looks just as good to you.

If you are set on using your current theme, you will need to consult with the developer about the custom post types issue.

Unfortunately I don’t have an answer for that as I do not have a lot of experience with the server side of things. Perhaps someone in the community here can give you some pointers on that.

As for our code, the developer is working on coming up with a better way to calculate MP3 length which will be tested and released with future updates to Sermon Manager.

iTunes is skipping your podcast episodes that have 0 length. Sermon Manager code includes a script that automatically calculates the MP3 length during post creation but if security settings interfere with that process the post must be created with a length of 0. In our experience, hosting MP3 files on separate servers (Amazon, etc.) usually is the cause.

Whatever the reason, enter the MP3 length manually to satisfy iTunes requirements. Enter 60 minutes for every sermon if you don’t want to have your web person try to figure it out all the time.

We just now heard about this problem from a potential member. I have submitted this bug to the developer for resolution. I’ll post when this issue is resolved.

This problem was addressed and resolved in our 1.9.5 update.

Hello Ralf,

I updated to your latest version just now and there seems to be a little progress. When I click on the email image button it now launches my email client (Outlook in this case) and starts a new blank email. The problem is, however, the populated email address is only the first letter of the email address: “a”

I should also mention that I did not get the error message Stuart encountered.