Constantin Boiangiu

Hi again,

Honestly, I don’t see anything that could be conflicting with the video embeds in your plugins list. I see you got it working with FV Player, just use that until you have the time to look into this any further.

By the way, can you please tell me which plugins you have installed on your site? I managed to somehow duplicate this issue when using the Classic Editor plugin.

Hi,

When you deactivate a plugin you lose all the functionality provided by that plugin. Since you’re not an experienced WP user, I suggest to contact a WordPress developer (maybe the developer that helped you create the website) to help you with this issue since you could potentially make things worst.

I’m sorry I can’t help more but this issue could be related to a number of things that can’t be debugged by simply looking at your page.

I assume you use WordPress 6.5, correct? I just made a test with one of your links and everything went well. I suggest to edit that page, remove the embeds and add them again.

Also, this might be related to a conflict with other plugins, you might want to look into that as well.

After having a closer look it appears that you use the Vimeo Block Embed feature to embed your videos. Since you’re not using Vimeotheque, there’s not much that I can do to help here.

As a note, I tested one of your videos with the block embed from the block editor and everything went well. Most likely, you installed a plugin or updated something in the meantime and this causes the embeds to fail.

Hi,

Are the videos in your page imported using Vimeotheque? It seems to me that you used a different way of embedding the videos that does not involve the plugin.

Hi,

Thank you for the heads-up! Version 3.1.10 was released and solves this issue, please update when you have the time and let me know, thanks!

Hi,

Sorry for the delay, we had a bit of a queue on the support requests. Regarding your question, you can enable this options on all your embeds by using filter “vimeotheque\player\embed-parameters“. Here’s the code reference: https://code.vimeotheque.com/reference/hooks/vimeotheque-player-embed-parameters/

Here’s an implementation example: https://gist.github.com/constantin-b/94b1b6e9de1aada2fa83c52b69ba984b

Let me know if you have any questions.

• This reply was modified 1 year, 3 months ago by Constantin Boiangiu. Reason: Added url for code example

Hi,

Must have been a bug or a conflict with other plugins. Can you tell me which importer have you used? The one from “Import Videos” or the “Add new”? Also, does this happen with any video from Vimeo or is it just with your videos?

As a note, there’s an add-on for Vimeotheque that was developed for debugging. You just install it and it will log messages from the importer that can help us figure out what was happening. More details can be found here: https://docs.vimeotheque.com/debug-add-on/

Please let me know, thank you!

Hi,

Sorry to hear this! Can you please give me more details on what you tried and didn’t work? I might be able to help.

Let me know, thank you!

Hi,

I’m sorry but no, autoplay on page load is not supported on neither the free or the paid version.

Hi,

My apologies for replying so late! We updated the plugin and solved compatibility issues with WP 6.3.1. There are plans for updating the plugin, most likely a new version will be published by the end of the year which will be a complete rewrite. In the meantime, if you happen to find other issues with the current version, please post them here and they will be addressed in a timely fashion. Again, my apologies for the late reply.

Thank you for pointing the GET parameter issue, I missed that detail. We released version 1.0.13 which solves this, please update when you have the time and give it a try.

Hi,

Thank you for suggesting this, we released version 1.0.12 which adds support for YouTube shorts. Please give it a try and let me know.

Hi,

The only solution I found regarding this issue is to create a new project and generate new API keys from this new project to use in VideographyWP.

In my case, I had older projects in Google Console that I created some time ago (few years back) and for those projects, when using one of the API keys into the plugin, even though the quota was not exceeded, the error message was the same. I had to dump those projects, create new ones and everything started working again.