khornberg

I’m not sure if this plugin still works

I no longer maintain it

I now recommend churches use Mere Agency

Hi @cfoster15,

I currently don’t have time to continue to develop the plugin or update it.
I’m sorry it is not working for you.

Hi @hermie777,

I’m the author of the sermon manager import plugin. I’ve not done much with WP For Church since I made it years ago now. It sounds like it still works which is good but I don’t have time currently to develop a fix.

If you or anyone else wants to develop the solution, I’d be happy to merge the code and publish.

?? I don’t think you’ll need to go to MySQL to do anything.

When you uninstalled it, does your plugin dashboard work correctly?

To delete all of the uploaded sermons that are not imported, go to the wp-content/uploads/sermon-manager-import directory and delete the files. You can do this the normal way you access the files on the server.

Ok.

Before you FTP’d the files to the sermon-manager-import folder, did you upload them within Sermon Manager Import? Or did you upload them using the normal media manager?

By default the date field is taken from the file name. The best date format is explained on the Sermon Manager Import options page under Import Settings. Additionally, if your date is stored in a single ID3 field (other than the file name) you can set that in the settings too.

Are the sermons available in the media library?

Are the sermons in the upload folder that you specified in the Import Options?

SMI is not finding any sermons in the folder it is looking at.

Maybe

Can you try the updated code (0.2.4)?

I believe that will take care of that error.

I’ve not set up support for multiple languages.

I’m welcome to pull requests.

Are you having this problem still?

In my tests, I can get to files uploaded either through the media tab or through the smi upload dialog. (They use the same backend).

Based on the picture the error follows from the description.

If you have access to the web server logs (httpd/apache, ngnix) and PHP logs, if logged separately, those would help you pin point the problem.

An error code of 500 means there is an internal server error. So code on the server is not liking something.

Have you validated that the post size and max upload size are capable of handling the data you are sending it?

Have you validated that the processing time is long enough to handle the different clients?

What is the HTTP error message?
Since it is working on some and not others and you are getting an HTTP error message instead of a PHP error message, it seems likely the problem is not within word press or sermon manager.

This list may be helpful if you know the error number.

That is a bibly thing.

One positive aspect is that people somewhere are hovering over verses on the Internet.

You are correct, it has not been translated.

I don’t know the exact tools to do so but you need to produce a .po file. There are several other translations that have been done so that could be a starting point.

If you’ve not already, check your browser’s console (usually F12). This should have some error messages that may point you (and those viewing this post) in a direction to go.