Sorry, but I wasn’t able to understand what your question or request is. Are you saying that your site is working with size m18 but not m22 and you want it to work with m22? If that is the case, it is probably happening due to your videos not being available in the larger size. There is no way to get around this sort of a limitation, which is imposed by Google itself.
Hi there! Thanks for your reply. I am not able to get the videos to work at all. It seems like even with the shortcode, they are staying at m37.
In looking at your website for the current shortcode you have in place, it seems like you are passing m22 to the video size. Can you pass m18 instead?
Hi,
I apologize for being unable to understand your statement earlier. When I revisited your website today I can now see what you mean. When I visited it earlier and clicked on your “videos” thumbnail, I got an error, then saw that the shortcode was saying m22. I didn’t realize that the “Videos” thumbnail was really an album (I somehow kept thinking that it was a standalone video).
Basically what happens is this: when you pass the m22 or m18, it applies to the gallery that is immediately on display. In this case, it applies to the albums (though albums are not videos). When you click on a thumbnail for an album, that gets treated as its own new shortcode invocation, and the m22 or m18 is no longer passed to it.
Unfortunately there is no easy way for me to get around this requirement with the video feature within Google’s API being unsupported. And the only way to get it to behave the way you want is to do some non-trivial code surgery.
Here’s what will work though: if you are simply trying to display a single album with all your videos (i.e. all videos show up directly on the page like this example), you can pass the m18 parameter to the shortcode and that will work just fine.
Hi,
Version 2.20 of Photonic (released today) should solve this problem for you. If you pass m18 to the shortcode your videos will open with that size specified.
Thank you so much for all of your help!! I just updated the plugin and everything is working perfectly! 🙂
