linknacional

Fields ACF & SCF for Elementor and Divi bridges the gap between ACF/SCF and popular page builders like Elementor and Divi. It allows users to create dynamic connections between custom fields and visual components, enhancing the flexibility of their WordPress websites.
<h3>Key Features:</h3>
<ul>
<li>Elementor Integration:
<ul>
<li>Dynamic fields powered by ACF or SCF.</li>
<li>Shortcodes for displaying galleries and custom fields.</li>
</ul>
</li>
<li>Divi Integration:
<ul>
<li>Gallery component with grid or slider styles.</li>
<li>Loop component for posts or pages, dynamically filtered by ACF or SCF fields.</li>
</ul>
</li>
<li>Dynamic Fields:
<ul>
<li>Seamless connection between ACF/SCF fields and visual components.</li>
</ul>
</li>
<li>Shortcode Support:
<ul>
<li>Flexible shortcodes for Gutenberg and other editors.</li>
</ul>
</li>
</ul>
This plugin is ideal for users who want to extend the functionality of ACF or SCF and integrate it with Elementor and Divi for advanced customization.
<h3>Short Description</h3>
A plugin that connects ACF (Advanced Custom Fields) or SCF (Secure Custom Fields) with Elementor and Divi, enabling dynamic fields, gallery components, and loop functionality.
<h3>Usage Instructions</h3>
After the installation process, locate the LKNSCF Settings option in the WordPress admin bar and select the plugin(s) you want to work with.
Create the fields in SCF and define them on the Gutenberg editing page. After filling in the fields, proceed to the Plugin editing page (Elementor or Divi).
<ol>
<li>
In the Elementor editor:
<ul>
<li>On the Elementor page, use the plugin’s own components and insert the created fields through dynamic tags.</li>
</ul>
</li>
<li>
In the Divi theme editor, there are 2 components:
<ul>
<li>Performs the Loop and filters the posts inserted in it through the SCR Object component.</li>
<li>Creates a gallery in grid or slide style, allowing the user to customize the set of images coming from SCR.</li>
</ul>
</li>
</ol>
<h3>External Libraries</h3>
<ul>
<li><a href="https://kenwheeler.github.io/slick/" rel="nofollow ugc">Slick-carousel</a>: Library that creates sliders or grids dynamically.</li>
</ul>
<h3>Shortcode: [lknscf_field]</h3>
Use this shortcode to display a text field or a checkbox. Minimum required parameter: [lknscf_field name=”SCF Field”].
Parameters for [lknscf_field]:
name: The name of the SCF field to retrieve the field value. This is a required parameter.
type: Optional. The type of field (e.g., “text” or “checkbox”). The default is “text”.
label: Optional. The label to be displayed next to the field (e.g., “Name:”).
tag: Optional. The HTML tag to wrap the field. Can be “h1”, “h2”, “h3”, “p” or “span”. The default is “p”.
font_size: Optional. The font size for the field text. The default is 16px.
color: Optional. The color of the field text. The default is (#000000).
background_color: Optional. The background color for the field. The default is transparent.
border_radius: Optional. The border radius for the field. The default is 0px.
checkbox_size: Optional. The size (height and width) of the checkbox. The default is 16px.
<h3>Shortcode: [lknscf_gallery]</h3>
Use this shortcode to display a gallery. Minimum required parameter: [lknscf_gallery name=”SCF Field”].
Parameters for [lknscf_gallery]:
name: The name of the SCF field to retrieve the gallery items. This is a required parameter.
gallery_style: Optional. The style of the gallery, can be “grid” or “slider”. The default is “grid”.
width: Optional. The width of the images in the gallery. The default is 250px.
height: Optional. The height of the images in the gallery. The default is 250px.
images_count: Optional. The number of images per slider. The default is 1.
dots: Optional. Whether to display navigation dots in the slider. The default is “true”.
autoplay: Optional. Whether to autoplay the slider. The default is “true”.
arrows: Optional. Whether to display navigation arrows in the slider. The default is “true”.
delay: Optional. The delay between slides in autoplay mode, in milliseconds. The default is 7000ms.

Fields ACF & SCF for Elementor and Divi

WordPress.org

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.
Easily create fields on demand. 
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.
Flexibility in placement. 
Fields can be applied throughout WordPress—posts, pages, users, taxonomy terms, media, comments, and even custom options pages—organizing your data how you want.
Display seamlessly. 
Using SCF functions, you can display custom field data in your templates, making content integration easy for all levels of developers.
A comprehensive content management solution. 
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.
Accessible and user-friendly design. 
The field interface aligns with WordPress’s native design, creating an experience that’s both accessible and easy for content creators to use.
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).
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>.
<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.

Fields ACF & SCF for Elementor and Divi vs Secure Custom Fields