Forum Replies Created

Viewing 15 replies - 1 through 15 (of 19 total)
  • Thread Starter rlpublishing

    (@rlpublishing)

    Great – I have just updated my ticket as well ??

    Let’s see what happens …

    Thread Starter rlpublishing

    (@rlpublishing)

    Hi CoolDavidoff – apologies for not picking up on your question earlier, I have been busy on other projects and am only just returning to this question.

    Yes, I have tried it, but as far as I can tell, the version 6 shortcodes do not work with the version 7 software. As an example …
    [s2Stream player="jwplayer-v6-rtmp" player_path="/jwp7/jwplayer.js" file_download="video.mp4" playerkey="MyJW7licensekey" /]
    This fails with a message about invalid license key, so even though I point to my JWP7 software with a valid key, s2 seems to assume it’s v6 because of the shortcode.

    Next, I thought that I would try a different s2stream short code using jwplayer-v7-rtmp – maybe it’s an undocumented feature ?? … err, no ??

    Them I tried the sample code in the Pro doc for RTMP + fallback code, substituting JW7 path & key. As with JW6, trying this on Chrome (Flash enabled) gives “Error loading Stream: ID not found on server”. On Firefox without Flash plugin we get “Error loading media: file could not be played”,

    At that point, I realised that I should really have used the s2member support centre to pursue this problem. They suggested that those problems were down to Cloudfront distributions not propagating properly and that I should reset these via s2member and try the whole set up again. I have done this but still have the same problems. It was at this point that I had to temporarily stop working on this project. Now that I am back on the case (at least for a short while), I will go back to them on that and see if I can get any further.

    Because I am sure that many people would love to be using the latest version of JWPlayer, it would be really great to have this update. My particular interest is getting this to work with RTMP as the primary delivery option with HTML5 fall back. So I suggest that you (and anybody else in this category) register your interest in this feature with s2 via their support center and then maybe we can get it as part of the product itself ??

    Let me know how it goes or if you have cracked it somehow else – I will do the same. Once again, apologies for the delay in getting back to you. All the best …

    Thread Starter rlpublishing

    (@rlpublishing)

    Hey Ulrich, likewise sorry for the delay. I have updated to the latest release (v1.11.1) and I seem to have a new problem: not autoplaying on mobile devices – it doesn’t seem to matter whether there is a splash image or not.

    Any ideas ?

    Thanks.

    Thread Starter rlpublishing

    (@rlpublishing)

    Ulrich, you have email ??

    Thread Starter rlpublishing

    (@rlpublishing)

    OK, a little bit more detail on the desk/laptop version 6 problems referred to in my last post – in the configuration …

    1. If I choose autoplay, all is well, the video loads and plays fine. If I switch autoplay off, it is as described before … I just get the three dots and nothing happens.
    2. Regardless of whether the video plays, if I choose to hide the embed button, it still gets shown. If the video does not play, it is still shown but it is empty

    I hope that this helps.

    PS: there seems to be no difference in these facts between videos that have signed URLs and those that don’t. Likewise, deactivating Nathaniel’s plugin does not seem to make a difference.

    (Edited for clarity.)

    Thread Starter rlpublishing

    (@rlpublishing)

    Very quick first look suggests that both vanilla & s3 signed videos work correctly on phones but strangely NOT on my linux box or old Mac (firefox & chrome) where all I get is the “3 dots” … no time to do more right now. Theme is latest version of standard Customizr. As the site is not yet in the public domain, if you want access for debugging, please advise how I can provide you with credentials.

    Thread Starter rlpublishing

    (@rlpublishing)

    Thanks – I will give it a go as soon as I can.

    Thread Starter rlpublishing

    (@rlpublishing)

    Awesome – can I add that I am using it with Nathaniel Schweinberg’s S3 plugin so it would be cool if it could continue to work with that ?? Likewise, I for one would very much like to see support for Cloudfront signed urls.

    But even as it is, thanks so much for your work on this plugin: it’s a good one ??

    R.

    Thread Starter rlpublishing

    (@rlpublishing)

    Hi – yes, after I wrote my last update, I wondered if the code could be placed in a little plugin, so this is perfect. I tried it and it works. Wonderful – thanks ??

    R.

    Thread Starter rlpublishing

    (@rlpublishing)

    Thanks again Gabriel – I did as you suggested and this is what happened.

    1. ‘this one’ appears at the top of the screen.
    2. ‘correct filter’ does not show up.
    3. Added the second filter: success !
    4. Just to check, I removed the first one and it still worked.

    So many thanks.

    It’s a shame that this is a hack to the theme itself: I guess that if you update the theme or change to a new one, you have to re-apply this.

    (It would be nice to have this function built in to the basic plugin: no fancy redirects, juts this one, after registration.)

    Anyway, thanks very much for your help ??

    R.

    Thread Starter rlpublishing

    (@rlpublishing)

    Hi Gabriel, thanks for responding so quickly.

    I have copied and pasted your code to the bottom of functions.php (vanilla Twenty Twelve theme) but if doesn’t seem to have any effect ??

    Is this correct ? Should I be doing anything else ?

    Thanks,

    R

    blynnerobson, if you’re using 3.0 beta, it may all get worked out by the time the code is finalised. But if you are using 3.0, you probably know a lot more about WordPress than I do ??

    However, the feeling from my host was that the WP_MEMORY_LIMIT “fix” may be something of a Band-Aid. There may be a bug underneath all this, but experimenting with Safe mode may be worth trying if you haven’t done so already.

    So I’d really recommend anybody still having this problem to look in to that, or at least, get their host to do so.

    R.

    OK, I am now sorted ! Kudos to my host for sorting this out. Here’s the story …

    1. I contacted my host support and explained what had happened, referring him to the previous problem that I referred to in my last post (which was something they sorted for me) and to this thread.
    2. Since this definitley seemed to be a memory leak of some kind, I also pointed out that I had installed the TPS! Memory Usage for WordPress plug-in. I have seen several other posts elsewhere in connection with this problem and some claim to have divined the solution by using this. If nothing else, it provides a lot of useful info, especially on the security front. (More details here.)
    3. Today, my host has come back and he feels that the problem was that although the server config had Safe Mode OFF in php.ini, the control panel settings (Plesk) showed it as ON.
    4. He changed this AND made some of the other changes suggested by the TPC! plug-in and all is now well. Hurrah !

    I have seen the "define('WP_MEMORY_LIMIT', '64M');" solution suggested above by samboll in other places for people having similar problems. It seems to work for some and not others – maybe this is why: perhaps it’s more to do with safe mode than anything else. But I’m no expert – but what I DO know is that a good tech guy at your host is really what you need when it gets this esoteric.

    Hope that this helps anybody else suffering from the same type of problem.

    All the best !

    Hmmm – I got something like this some time ago (here) after upgrading to 2.8. That seemed to be an apache config problem and my host sorted it out.

    But now I am getting the problem described here too and it seems to be in the same piece of code, though on a different installation and under 2.9.2 ??

    Attempts to raise the memory limit to 64M as suggested here and elsewhere do not seem to work and I have referred it to my host. It doesn’t seem to be harming the site itself although traffic is very low at the moment and I’d want to see things fixed before t gets ramped up, so if anybody else has any bright ideas, I’d be glad to hear them.

    Thanks.

    OK, my host has solved the problem, saying “The trouble with WordPress was resolved by upgrading mod_auth_mysql on the server.”

    I no longer get all messages as described in bubblehelp’s initial post.

    Hope this helps.

    Roger

Viewing 15 replies - 1 through 15 (of 19 total)