-
Hello! After your previous assistance everything seemed to be working just fine. Vids showing up as desired.
However, I just noticed an issue, I thought I had checked it previously and made sure all was OK. I was wrong. :(
Here’s the problem. The content on the site is protected for access by members only. We are protecting the videos using a membership plugin from Zaxaa who provide our payment platform.
The problem is that when a member logs in to see protected content what they actually see is the shortcode from Flowplayer on the page.
I tried various methods to see if there was a solution but wherever content is surrounded by the Zaxaa shortcode the Flowplayer shortcode falls over.I have used other players emedded within the Zaxaa shortcode but the players were not what I wanted to use. As a sanity check and to try to pin down the causative factor I re-added content using the Kimili Flash embedder plugin within the same protected block as the Flowplayer code.
Only one video worked and it was not the Foliovision version. :(
Any ideas, suggestions, proposals?
-
-
Hi, sorry to pester you all but finding a solution to this issue is holding up work as we move to a relaunch. Is there any additional info I can share with you to help with this?
Hi Andrew,
We will look at this and fix this.
Thanks for the additional notes.
Thanks very much.
Hello Andrew,
this is a problem, as our plugin works just fine with s2Member, so it might be a problem of your membership plugin.
1) I tried using [zm_upgrade] and put [fvplayer] inside of it. I see that the shortcode inside of it doesn’t execute. Notice that it doesn’t execute [gallery] either, so it’s a problem for your membership plugin.
You need to ask the developer of that membership plugin – Zaxaa Member.
2) However if the video is in [zm_protect], it’s not displayed, as user “tester” doesn’t have the permission. Can you try adding the permission and see if the video shows up?
What exactly are you trying to achieve? Do you need [zm_upgrade] at all?
Thanks,
Martin
Hi thanks.
The reason I am using this script (apart from Zaxaa running the sales back end) is that in common with relatively few scripts they enable protection of parts of content. So, I want to make sure that humans and search engines can see most of the content on the pages, rather than hide almost everything away. Then we charge to see the rest of the material. Once subscribed all the warnings go away. So, yes, we DO need the [zm_upgrade] shortcode.
If we did the normal thing then everything would disappear behind a pay wall and I could use any old membership script.
I have contacted Zaxaa with a full description and given them access to the site but it seems to me that this is a six of one half a dozen of the other thing. I am sure that either you or Zaxaa can individually make a solution but the fact of the matter is that something in both sets of code is causing an issue that can be replicated. Seems to me that if that is so then at some point the issue will come up again – just in a different context.
Thanks for your help,
Andrew.
Hello Andrew,
we are on the same page here – you want the whole post to be indexed in Google and only hide few paragraphs with videos from non-members.
I think that’s exactly what [zm_protect] does. I’m not sure about [zm_upgrade], as I wasn’t able to find any documentation. I could see that once it’s user, [fvplayer] shortcode is not parsed, but the same applies to [gallery], which is core WordPress technology – so it might be a problem of Zaxaa.
Could you please check the [zm_protect] in my test post? That should make things clear, if you can load that post as a paid user and see the video.
Thanks,
Martin
Hi Andrew,
Zaxaa has to be able to work with standard WordPress shortcodes for us to be able to support it (and for it to be a good idea for you to use Zaxaa). Please hit up their tech support for support for standard WordPress shortcodes.
If Zaxaa can’t do it, we’ve set up lots of similar membership sites using open source S2 Member (we have a developer license for pro) which work a treat and allow full WordPress functionality.
We look forward to hearing from you soon!
Guys, thanks for your help. We have a solution. It turned out that the Zaxaa short code could not handle html elements so anything with a URL in it failed. Seems odd that the issue had not cropped up before however if one uses their implementation of FlowPlayer then there is no problem but the functionality offered is very basic.
Over the weekend they made a fix for me that works just fine.
I am sticking with Zaxaa, although by the weekend I did start to think about moving over to S2 Member but every change is more learning, more mistakes and more time.
Thanks for your patience.
Hello Andrew,
that’s great news, we are glad it all works for you now.
Thanks,
Martin
