Another error 1054 on updating to SS 5.0.3

Ahh Thomas - thank you SO much. Your precise instructions got me sorted on that issue at least and I truly appreciate the walkthrough.

Left with just one other problem now which is somewhat confusing again - on the frontend the menu item is set to show as Sermons List but it won't reveal the sermon titles and for some strange reason it's only showing 6 sermons from 2 years ago . The sermon series & speaker lists seem unable to show anything either. Is this likely related to what you'd mentioned on the categories/permissions issue perhaps?

Sounds exactly like an issue with categories/permissions.
You may also want to open the menu items and save them again. That makes sure the parameters are updated correctly. Especially since you uninstalled and reinstalled the component.

Oops - sorry - that wasn't actually the post I meant to leave- had edited it shortly after but must have forgotten to save it.

You were quite right - I figured out the category issue ok & got everything showing on the front end ok - the problem (which was what I meant to ask last time) is that the Titles still won't show up & the Sermon list page shows a path in the upper right corner that I can't find a source for in the back end.

It's the same link to use as in the first post.

Hopefully once I get those sorted that will be finished worrying about it :lol:

The issue comes from your templates CSS rule:
Also the console shows an error for the tooltip method. Looks like it doesn't support the tooltips used by the layout.
You may want to update SermonSpeaker to the latest version and see if that fixes it. I think I have switched those tooltips from MooTools to the Bootstrap (JQuery) version.

That's great - I'll have a look at it all again tomorrow.

Can I maybe just take this opportunity to extend a HUGE thank you to you for all the immense amount of work you've put into this component - I've zilch programming knowledge but only have to look at some of the php files involved to see it's a tremendous amount of work. Plus you're unique in giving so much of your time to sorting out all the sundry problems users encounter, and all for FREE!!! I use another Christian component which I value too but sadly the guy who created it has no time to give to support as he's also working alone. All of this just make me value you guys all the more as I know from just my regular website updates how long things can take to do.

Anyway - just know your work is truly appreciated - I've not yet looked, but do you have a means of accepting donations towards your costs?
=================================
Saturday: Ok - again, you were quite right in that the update to V5 did indeed solve that problem with the CSS etc, but still a few problems to fix. You'll be glad to see the end of me with this no doubt LOL!!

The player's extending past the template div - I did have a look at the player CSS but changing parameters there didn't help, and unsure where else to look. Plus it's saying Resource not found (top right of player) - what's it looking for?

And could you possibly point me in the right direction for making CSS font changes for the likes of the Series page? Couldn't find it in the SermonSpeaker.css file tho no doubt it's there. Thanks again

Thanks for your kind words. As for donations, there is a PayPal "Donate" button at the bottom of each page

For the player try with this rule: This way the div for the player is forced to 100%. By default it uses a "span10" class which seems to have some wrong value from your template. Not sure why that is but the rule above solves it

"Ressource not found" usually means that there is no file referenced in the sermon. Thus the player can't play anything. Looking at that specific sermon you even wrote it in the notes

With the current releases of SermonSpeaker, there are almost no CSS rules coming from SermonSpeaker itself. Most of it should come from the template. I have tried to follow the Joomla standards for the output, which means it uses classes from Twitter Bootstrap. So if you want to change anything, you likely need to change something in the template CSS.