Support for SermonSpeaker 5.x is in bugfix mode only, the same as it is for Joomla 3.10.
I will not add any new features to this releases.
Please upgrade to SermonSpeaker 6.x and Joomla 4.x, which is better anyway.
I will not add any new features to this releases.
Please upgrade to SermonSpeaker 6.x and Joomla 4.x, which is better anyway.
http:200 error on sermon uploads
- Thomas Hunziker
-
- Offline
- Administrator
-
Less
More
29 Dec 2016 09:54 #6375
by Thomas Hunziker
Replied by Thomas Hunziker on topic http:200 error on sermon uploads
Does your editor user has permissions to run scripts? Check the SermonSpeaker options in the "Permissions" tab if that action is allowed for that user group. If the user group is allowed to "Create" and "Run Scripts", it should work.
Please Log in or Create an account to join the conversation.
29 Dec 2016 16:46 #6377
by Radovan
Replied by Radovan on topic http:200 error on sermon uploads
Hi,
Joomla has no "Run Scripts" for users. "Edit State" should be something like "Run Scripts" but for unpublished sermons (after automatic upload) you need disallowed "Edit State" ...
These are Joomla User actions:
Configure ACL & Options, Configure Options Only, Access Administration Interface, Create, Delete, Edit, Edit State
My user has allowed:
Create, Edit
What to change? Thanks
Radovan
Joomla has no "Run Scripts" for users. "Edit State" should be something like "Run Scripts" but for unpublished sermons (after automatic upload) you need disallowed "Edit State" ...
These are Joomla User actions:
Configure ACL & Options, Configure Options Only, Access Administration Interface, Create, Delete, Edit, Edit State
My user has allowed:
Create, Edit
What to change? Thanks
Radovan
Please Log in or Create an account to join the conversation.
- Thomas Hunziker
-
- Offline
- Administrator
-
29 Dec 2016 17:48 #6378
by Thomas Hunziker
Replied by Thomas Hunziker on topic http:200 error on sermon uploads
Please Log in or Create an account to join the conversation.
30 Dec 2016 04:05 #6379
by Radovan
Replied by Radovan on topic http:200 error on sermon uploads
Hi Thomas, thanks and yes, now it works. I didn't realized that there are also permissions (in options of Sermon Speaker) for users too...
In language file "/components/com_sermonspeaker/language/en-GB/en-GB.com_sermonspeaker.ini" (and in the all other for other languages) is missing this string:
; New with 5.1.2
COM_SERMONSPEAKER_ID3_NO_MATCH_FOUND="The following ID3 tags were present, but no matching entry in the database was found"
In language file "/components/com_sermonspeaker/language/en-GB/en-GB.com_sermonspeaker.ini" (and in the all other for other languages) is missing this string:
; New with 5.1.2
COM_SERMONSPEAKER_ID3_NO_MATCH_FOUND="The following ID3 tags were present, but no matching entry in the database was found"
Please Log in or Create an account to join the conversation.
- Thomas Hunziker
-
- Offline
- Administrator
-
01 Jan 2017 19:26 #6386
by Thomas Hunziker
Replied by Thomas Hunziker on topic http:200 error on sermon uploads
Added to frontend strings with
github.com/Bakual/SermonSpeaker/commit/9...6ade64320eb631787d81
As for the other language files, those need to be translated by the translators (see www.sermonspeaker.net/11-sermonspeaker/n...opentranslators.html ). If they are not present, the english string will be used.
As for the other language files, those need to be translated by the translators (see www.sermonspeaker.net/11-sermonspeaker/n...opentranslators.html ). If they are not present, the english string will be used.
Please Log in or Create an account to join the conversation.
- Nick Lauren
-
- Offline
- New Member
-
Less
More
- Posts: 10
- Thank you received: 0
28 Mar 2017 20:40 #6600
by Nick Lauren
Replied by Nick Lauren on topic http:200 error on sermon uploads
Hey Thomas, quick update:
As a method of troubleshooting, I re-encoded one of the troubling MP3 files using Adobe Media Encoder. The file size ballooned to 46mb, but after re-encoding the same file I could never upload, it uploaded the 46mb file fully and that file works.
Why would that ever be? Especially since I didn't think it could be an error within the file itself because it uploaded fine to your server?
Nick
As a method of troubleshooting, I re-encoded one of the troubling MP3 files using Adobe Media Encoder. The file size ballooned to 46mb, but after re-encoding the same file I could never upload, it uploaded the 46mb file fully and that file works.
Why would that ever be? Especially since I didn't think it could be an error within the file itself because it uploaded fine to your server?
Nick
Please Log in or Create an account to join the conversation.
Time to create page: 0.166 seconds