frugan

<p><strong>Upload Field to YouTube for ACF</strong> is a WordPress plugin that allows you to upload videos directly to YouTube via API from the WordPress admin area and/or select existing videos on your YouTube channel based on playlists. It is particularly useful for managing “unlisted” videos that may be associated with Custom Post Types (CPT).</p>
<p>To use this plugin, you need to configure Google oAuth credentials so the plugin can authenticate with the user’s YouTube channel.</p>
<h4>Requirements</h4>
<p>@see https://github.com/wp-spaghetti/upload-field-to-youtube-for-acf?tab=readme-ov-file#requirements</p>
<h3>External Services</h3>
<p>This plugin connects to the <strong>YouTube Data API v3</strong> provided by Google LLC to upload and manage videos on YouTube.</p>
<h4>What data is sent</h4>
<ul>
<li>Video files selected by the user through the ACF field</li>
<li>Video metadata (title, description, tags, privacy settings, category)</li>
<li>OAuth authentication tokens for YouTube channel access</li>
<li>User’s YouTube channel information</li>
</ul>
<h4>When data is sent</h4>
<ul>
<li>During video upload operations initiated by the user</li>
<li>When retrieving video information from YouTube playlists</li>
<li>During OAuth authentication and token refresh processes</li>
<li>When fetching playlist data from the user’s YouTube channel</li>
</ul>
<h4>Service Information</h4>
<ul>
<li><strong>Service Provider:</strong> Google LLC</li>
<li><strong>API Endpoint:</strong> https://www.googleapis.com/upload/youtube/v3/</li>
<li><strong>Terms of Service:</strong> https://developers.google.com/youtube/terms/api-services-terms-of-service</li>
<li><strong>Privacy Policy:</strong> https://policies.google.com/privacy</li>
</ul>
<p>This information is provided for legal compliance and transparency. Users should review Google’s terms and privacy policy before using this plugin to upload content to YouTube.</p>


Upload Field to YouTube for ACF

WordPress.org

<p>Secure Custom Fields (SCF) extends WordPress’s capabilities, transforming it into a flexible content management tool. With SCF, managing custom data becomes straightforward and efficient.</p>
<p><strong>Easily create fields on demand.</strong><br />
The SCF builder makes it easy to add fields to WordPress edit screens, whether you’re adding a new “ingredients” field to a recipe or designing complex metadata for a specialized site.</p>
<p><strong>Flexibility in placement.</strong><br />
Fields can be applied throughout WordPress—posts, pages, users, taxonomy terms, media, comments, and even custom options pages—organizing your data how you want.</p>
<p><strong>Display seamlessly.</strong><br />
Using SCF functions, you can display custom field data in your templates, making content integration easy for all levels of developers.</p>
<p><strong>A comprehensive content management solution.</strong><br />
Beyond custom fields, SCF allows you to register new post types and taxonomies directly from the SCF interface, providing more control without needing additional plugins or custom code.</p>
<p><strong>Accessible and user-friendly design.</strong><br />
The field interface aligns with WordPress’s native design, creating an experience that’s both accessible and easy for content creators to use.</p>
<p>Installing this plugin will deactivate plugins with matching function names/functionality, specifically Advanced Custom Fields, Advanced Custom Fields Pro, and the legacy Secure Custom Fields plugins, to avoid code errors (this is the same behavior as ACF Pro).</p>
<p>Read more about Secure Custom Fields at <a href="https://developer.wordpress.org/secure-custom-fields/" rel="nofollow ugc">developer.wordpress.org/secure-custom-fields</a>.</p>
<h4>Features</h4>
<ul>
<li>Clear and easy-to-use setup</li>
<li>Robust functions for content management</li>
<li>Over 30 Field Types</li>
</ul>


Secure Custom Fields


In case anyone is not clear - this is a "nulled" plugin - an exact copy of the paid support Pro version of Advanced Custom Fields, with the code to handle licensing and updates stripped out. This clearly part of the petty high school drama playing out between two multi million dollar for-profit companies, and it is going to wreak havoc on the entire WordPress ecosystem.



Who's going to invest in creating great Pro plugins if everyone's always afraid that Wordpress.org itself is going to just rip them and put them up on the main plugin repo if they don't like you today.



The "freemium" model has created great jobs for a lot of small development shops and many individual designers and developers depend on the quality and support you get from paid Pro level plugins to do their jobs.



I have no particular love for WP Engine, but this sets a horrible new precedent that is going to put the livelihoods of may less powerful individuals at risk. It must be stopped now!


Unprecedented bad behavior


Hello, WordPress contributors,



I am using WordPress as a developer more than 5 years.



And I have also contributed. There are some plugins in the Repository WP Adminer, Library Viewer, Gift Wrapping for WooCommerce, with old these plugins have 100% 5-stars reviews.



But this behaviour is Unacceptable.



What are the GPL requirements? Here you just took Advanced Custom Field Pro, removed their license system, changed the plugin author details without copyright anywhere WP Engine (the author of ACF Pro) and you released it as yours.







Such other "marketplaces" do in the Web...



Is all this ethical?



I have also paid plugins! Are you going to take them also?



Trust in WordPress is being cloned with your actions...


Unacceptable behaviour


ACF disabled gallery field and broke few sites, changed to SCF and everything started to work again. Thank you!


Great replacement for ACF


I am pleased to observe the addition of numerous valuable features without the frequent reminders about upgrading to a premium version.


Work great, no add for premium

Secure Custom Fields boosts content management with custom fields and options. It deactivates Advanced Custom Fields to prevent duplicate code errors.

Upload Field to YouTube for ACF vs Secure Custom Fields