Vincent

To be honest I haven’t tested it beyond 10 videos or so. It may be a limitation with WordPress’ select list, but I’ll have to look into it.

If so I can potentially use a search field instead of a normal select, but this will take a little time. Will get back to you.

@robertdoets I’ll have to get back to you on that.

@vegetablesalad You’d have to make a custom email template or thank you page to deliver the link to the user after purchase. This requires adding an email/thank you template to your theme. You can see how to do that in the FAQ on the main plugin page.

• This reply was modified 4 years, 2 months ago by Vincent.

I’m only making use of Vimeo’s freely available APIs with this.

Anyone is allowed to make a video on Vimeo, and anyone is allowed to distribute that video (i.e. link to it) however they’d like.

You also have the ability to password protect a video, and distribute that password however you please as far as I know. I can’t see how this would violate any of their Terms of Service, but I also haven’t read them to be perfectly honest.

@dot4all probably not within the next week or so unfortunately :/

But if you really need this functionality now you could always use some sort of Product Bundles plugin and sell multiple products as a bundle.

@svijany I haven’t tested this on anything higher than PHP 7.2 unfortunately.

I’m hearing some people having issues with 7.3 so there’s a potential you’re in the same boat.

I’ve updated dependency libraries of the Vimeo API that this plugin uses in my Github repo. WordPress won’t let me upload the updates, I haven’t fully deduced why yet. Something in Vimeo APIs libraries it doesn’t like.

Anyway, try this:

https://github.com/vastolf/woocommerce-vimeo

https://github.com/vastolf/woocommerce-vimeo

You can download the latest there

One of the Vimeo API’s dependencies is using a method that the WordPress plugin repo doesn’t like. But you can get 0.0.4 there for now until they update, have contacted the maintainers of the dependency.

@braquopronos and @devoctopix I have updated the library where the error was occurring. It looks like the Vimeo API was out of date. This should work now on 7.2, let me know if you are still having issues.

@svijany I will try to get this fixed for you if you can provide me a little more information. What version of WordPress are you running and what version of PHP?

@rcontreras27 you would need to delete all of the sections of the template inside of the <tbody> tag if you are talking about the example in the FAQ.

Here I have highlighted the section you would KEEP if you wanted to ONLY show the password:

https://gist.github.com/vastolf/42cc9359d6b616675d70659e6de6f7a4#file-customer-completed-order-php-L70-L76

You would delete this section:
https://gist.github.com/vastolf/42cc9359d6b616675d70659e6de6f7a4#file-customer-completed-order-php-L77-L83

And also delete this section:
https://gist.github.com/vastolf/42cc9359d6b616675d70659e6de6f7a4#file-customer-completed-order-php-L77-L83

@devoctopix @braquopronos Sorry about that. I never got notified about these posts and haven’t checked back here in a while. I’ll try to get this updated for you so it can work with PHP 7.2.

@cotillardq would you be willing to give access to a Vimeo On Demand account for testing purposes? I do not have an account and it doesn’t look like they have a free trial. Would be much easier to test with one, and in that case I’d be happy to look into supporting it. Sorry for late response.

@dot4all There is not currently a way to add more than one video to a product. But I don’t think that would be too difficult to add. I will try to get around to adding an update for this as soon as possible and tag you when I have it ready.

Thanks so much @kkatusic ?? Glad you got some use out of it!

I just wanted to comment to confirm that the suggestion by bcworkz is in fact the solution.

wp_editor( html_entity_decode(bankruptcy_details_get_meta('bankruptcy_details_case_details')), 'bankruptcy_details_case_details', $settings = array() );

I had to insert that html_entity_decode() function both when I was calling the meta box wpeditor’s content in the backend (on the post type’s post edit page itself) AS WELL AS when displaying it on the front end. I’ve also got it running when it saves the data in the database, using the update_post_meta function, just to make doubly sure that the database is storing the data as HTML.

Thanks for this I’ve been looking everywhere for a solution!

Thank you very much!

Haha, sorry I thought that might be a bit confusing. The “main php” file I was referencing was that of the plugin (but I was speaking to the plugin author). That file would be the plugin’s “jquery-html5-file-upload.php” file, I was requesting he drop that function in that file and commit his changes as an update to users.

As for where YOU should put the function for now, that really depends. If you update your theme a lot, that change will go away when you update. The same is true for the plugin, though I’m not sure how often it is updated. If you never update your theme, the second way is safer, and if the plugin is rarely updated then the first option is king.

-Vincent