Import from Sermon Browser Fails
-
The import process indicated that it was successful. Sermon posts were created, but every sermon had a broken URL for the corresponding media file. Instead of the full path — for example, where it should be:
https://sitename/uploads/Sermons/TodaysSermon.mp3
they would have:
https://sitename/aTodaysSermon.mp3
As a result, sermons do not play, and my web logs show 404 errors every time it is attempted.
Jack
- This topic was modified 6 years, 10 months ago by Jack Rogers.
-
Thanks,Nikola. Looks like you’re on a roll today. ??
Jack
I can (privately) provide the URL of my dev/test site, if needed.
Incidentally, I added a single sermon manually, and it works as expected. It’s just the imported sermons that are broken.
Jack
Actually, I am more curious how is Sermon Browser storing the URLs in your case and where is upload directory.
If you are willing to help, please send the output of
SELECT * FROM wp_sb_stuff
andSELECT * FROM wp_options WHERE option_name = 'upload_path'
(you can put these SQL Queries in PhpMyAdmin) to [email protected]If you don’t know how to do it, you can just email me the WordPress admin access and I’ll check it for you instead
Nikola,
I’ll run these queries after work this evening. No need for phpMyAdmin, the MySQL CLI is the only interface I use. ??
Incidentally, I don’t recall seeing a table named “wp_sb_stuff” when I was poking around, but I may have just overlooked it.
If I recall correctly, sermons are uploaded to wp-content/uploads/Sermons. But I’ll confirm this evening (I’m on US CST).
Thanks for your help.
Jack
Hi Jack,
I was not sure about your skill level so I said PhpMyAdmin since most web developers at least know to use that one, and it’s also enough for these needs.
But CLI is more than enough as you know. ??Anyway, I am glad that you are knowledgeable; solving this issue will be easier and faster. ??
wp_sb_stuff
might have some other prefix on your end, I didn’t take that into account, but it will most definitely be${prefix}sb_stuff
.
And I’m pretty sure that it exists, since our importing script does not take mp3 data from any other source.Also, it would be the best if you could reply with exact path where file should be and the exact wrong path – it will be easier for debugging. (relative paths are fine, no need for host names)
I am in CET timezone, so I will check it out tomorrow.
Thank you for your help too, it’s nice to see a techie every once in a while.
If you prefer, you can email me on the previously mentioned email, but I’m fine with keeping the conversation public as well. However you like.
– Nikola
Nikola,
I limited the first query to 5, as I doubt there’s any benefit to showing the entire list of sermons.
mysql> SELECT * FROM wp_sb_stuff LIMIT 5 ; +----+------+------------------------------------+-----------+-------+----------+ | id | type | name | sermon_id | count | duration | +----+------+------------------------------------+-----------+-------+----------+ | 1 | file | 071909AM.mp3 | 1 | 80 | 27:06 | | 2 | file | Victory_7.26.09am.mp3 | 2 | 93 | 23:57 | | 3 | file | Set Apart_07.26.09.mp3 | 3 | 83 | 17:14 | | 4 | file | He Is Our Peace_08.02.09.mp3 | 4 | 82 | 23:26 | | 5 | file | What Does God Require_08.09.09.mp3 | 5 | 91 | 23:22 | +----+------+------------------------------------+-----------+-------+----------+ 5 rows in set (0.00 sec)
And…
mysql> SELECT * FROM wp_options WHERE option_name = 'upload_path' ; +-----------+---------+-------------+--------------------+----------+ | option_id | blog_id | option_name | option_value | autoload | +-----------+---------+-------------+--------------------+----------+ | 60 | 0 | upload_path | wp-content/uploads | yes | +-----------+---------+-------------+--------------------+----------+ 1 row in set (0.01 sec)
However, the actual Sermon Browser upload location on the server is:
wp-content/uploads/sermons/
This is confirmed both by browsing the server itself, as well as the Sermon Browser Options page in the WordPress Dashboard. I looked through the wp_options table as well as some wp_sb_* tables to see if I could find where this setting is stored, but did not find it.Hope that’s the info you were looking for.
Thanks.
JackHey Jack,
Thank you, that’s exactly what I needed.
Also, I am wondering, what version of Sermon Manager are you using right now?
There was an issue with file paths until 2.10 (so, in 2.9, 2.9.1, 2.9.2, and 2.9.3).
The issue was supposed to be automatically fixed as soon as you updated to 2.10+, but the function might not have executed.
My suggestion is to update to 2.10.2 (latest), and click on “Import” again. (sermons won’t be duplicated)
If that doesn’t work, please send me WordPress admin credentials of your dev instance or website where the import fails, so I can debug the code and create a patch for the tomorrow’s release.
Thanks for your cooperation ??
Nikola,
My current version of Sermon Manager is Version 2.10.2. I don’t recall when I updated it, but it was at this version prior to the import attempt.
Please let me know whatever else is needed for troubleshooting. Nothing personal, but as a matter of principle, I don’t share login credentials (seems like that could also put you in a risky position). I can gladly provide sql query output, httpd logs, and any Linux/httpd config and/or debugging info needed.
Jack
Hi Jack,
That’s completely reasonable, and it’s a smart decision.
One scary fact that you might find interesting is that you are the very first person who decided to not share their credentials. (among few hundred other people who shared them)
Fortunately for them, we have no malicious intents whatsoever, and all we do on their websites is to debug the issue(s), log out and never log back in – or else it would seriously hurt our reputation. (and as you know, it’s much easier to reproduce the issue on the server where the issue is occurring)
Also, I did not notice a section in WordPress legal documents that is against politely asking users for creating a temporary account for us to debug the plugin on their server, nor any moderator have made any contact whatsoever (like when they did when we used to ask for theme package files to debug the plugin – which was our mistake and we haven’t made it again since that moderator contact). If you know that this is forbidden, please let me know (with sources) and I will immediately stop doing it.
Anyhow, I will add debug code to the import script tomorrow, with clear comments on what it exactly does so you have peace of mind. And all you would have to do is to copy the anonymous debug output and send it here.
Would you prefer me to send a git patch as a reply to this thread? Or would you rather prefer that I create a GitHub gist of whole modified script and send it here? Or something else?
However you like. Just let me know in the next 8 hours since that’s when I will get to work tomorrow.Nikola
Nikola,
I’m not aware of any WordPress policies relating to developers having temporary access to users’ installations. It seems very few developers would offer to do that without getting paid for it (“consulting”). ?? I’m just too steeped in IT Operations processes and controls to be comfortable with it.
I’m not sure how to apply a git patch. If it doesn’t require installing git, then that’s fine. I haven’t installed git on this server, and I’d rather not install it just for this. Or, if you’d send the “whole modified script” I can retrieve it from here. I’m also on GitHub as “PainFreeComputing”.
Jack
Hi Jack,
Apologies for late response.
I’ve actually added debug script into Sermon Manager core, so it could be used in future as well.
And, I might have fixed the mp3 path issue, but let’s check.Please download the development version of the plugin from here and install it like any other plugin. (Note: you will have to deactivate and remove existing Sermon Manager install; no data will be lost and you will receive future updates normally). Then, go to Sermon Manager Settings -> “Debug” tab, and check the checkbox named “Show detailed data during import”. After that, just go to Import submenu item in Sermon Manager menu item, and click on “Import” button again.
After you do so, you can copy the log somewhere so I can take a look (https://gist.github.com/ is perfectly fine) or you can send it to me via email. Note: website URL will be visible in the log.
Thank you.
Nikola,
No worries about the delay, I’m just very happy to have help with this.
The debug produced no output, but the new version and new import seems to have resolved the issue completely. I checked several sermons, and they are now correctly linked.
Thanks for your work on this.
I still have a few more minor issues (possibly just config settings and CSS tweaks) to address, but this one was a show-stopper. I’m happy to be able to move on to the next issue. Once I’ve gotten up to speed on this plugin, I hope I can be of some help here.
Jack
Hey Jack,
Glad to hear it.
I’ll check the minor debug issue, and do an official release on Monday.
If there are any other issues, don’t hesitate to create a new thread here/contribute on GitHub.
Thank you for your help. ??
- The topic ‘Import from Sermon Browser Fails’ is closed to new replies.