Hi there:
Kindly refer the attached image. I am using the WPLMS S3 plugin and want to attach a video to the "landing page/sales page"....I uploaded the video (video uploads to AWS S3) and inserted the shortcode (you can see the shortcode in the image). However, the video doesn't show up on the landing page.
Following the same process within units, the video works fine.
Could you please check if this is a bug??
It appears to me that the WPLMS VIDEO and AUDIO Player shortcodes dont work on the landing page (single-course.php) template.
Is this correct? and if yes, is there a way to activate this?
No that is not correct. Shortcode code is same for all pages.
Try renaming your video file and make sure it does not have any spaces in it.
Nope ....just tried with a file with no spaces, the video doesn't show up (only the image shows up...which showed up previously as well.)
The video/audio works fine within units, just the landing page it is not showing up.
CAn you please confirm this :
Goto your Amazon account find that video.
Make the video public .
Try directly access the video from the url .
Check if it working or not .
this will confirm if the issue is in the video itself or not .
Hi there:
See the following images please:
https://cloudup.com/c8oiDMJVt-0
https://cloudup.com/cNrYJwGmmQM
https://cloudup.com/c8d8oOzqtdr
https://cloudup.com/cY_Zfgu0A-4 (this image also shows that vibe shortcodes is not working on the front end)
https://cloudup.com/cCD3ioAXyw3 (as you can see from this image, the video is working fine, it is not an issue with the video)
-----------------
ok, the video is working - as I mentioned previously
inserting the same s3 shortcodes within units works completely fine. It is
just for the landing pages that those videos/audio files are not showing up. please see attached images above.
------------------
I saw this post:
https://wplms.io/support/forums/topic/edit-course-vibe-shortcodes-logo-dissapearing/
where the Vibe Shortcodes is not working in the front end (which it is not for me - I have version 1.9.9.2 for vibe shortcodes) - the logo doesn't show and if I try to use any of the shortcodes it doesn't work on the front end. It does work on the backend. (Please see attached images)
https://cloudup.com/c0N-VHDEUCu
I am assuming that since WPLMS S3 inserts shortcodes, it has something to do with this.
I tried deactivating all 3rd party plugins and it still doesn't fix the issue.
I am pretty confident this is NOT an issue on my side but a BUG. I deleted all but the required plugins from WPLMS, activated the WPLMS parent theme and this issue still persists.
Hi I am awaiting a response on this, could you kindly confirm if this is a bug and, if yes, what is a solution to this? Thank you!
Hi there: still waiting on a response to this....
Your previous responses some how suggest that this issue is related to the video itself (name or the way it is uploaded on s3) which is clearly NOT the case, as I have checked it already.
Based on my tests, it clearly appears to be a bug....it would be great if you could quickly test it on your side and confirm this.
It will help me to plan accordingly (even if you are planning on fixing this in the version 2.0 of WPLMS).....a non-response just doesn't help me.
WPLMS s3 is independent of wplms 2.0 . I am not sure why this issue should appear because, WPLMS s3 shortcode is independent of any specific page/post.
However, I still need to check this. Can you share the following information :
a. Does this happen in any specific course or all the courses ?
b. Can you try making the video public (
screenshot) and embed it in course page via direct url.
p.s: Vibe Shortcodes not working in the front end is resolved in the upcoming 2.0 update.
1. It happens in ALL course landing pages (i.e. single-course.php templates)
2. Please watch this
1 minute video for demonstration. I have made the video used public in AWS s3.
Hi there:
Did you get a chance to look at this?
Hi everyone,
we have the same issue.
We did a fresh installation with up to date version of theme and plugin.
Thank you for any suggestions.
We've found the bug.
Fix coming up in version 1.2.2.
Thank you all for patience.
.
