No special requirements for the upgrade.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0","1.0.1","1.0.2","1.0.3","1.0.4","1.0.5"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":2516414,"resolution":"1","location":"assets","locale":""},"screenshot-2.png":{"filename":"screenshot-2.png","revision":2516414,"resolution":"2","location":"assets","locale":""}},"screenshots":{"1":"A screenshot of the template edit using WordPress classic editor.","2":"A screenshot of the post NP Twig setting"},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[2211,2010,1578,198216,17809],"plugin_category":[],"plugin_contributors":[198206],"plugin_business_model":[],"class_list":["post-139022","plugin","type-plugin","status-publish","hentry","plugin_tags-acf","plugin_tags-custom-fields","plugin_tags-display","plugin_tags-fron-end","plugin_tags-timber","plugin_contributors-miniindustry","plugin_committers-miniindustry"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/np-tiwg.svg","icon_2x":false,"generated":true},"screenshots":[{"src":"https:\/\/ps.w.org\/np-tiwg\/assets\/screenshot-1.png?rev=2516414","caption":"A screenshot of the template edit using WordPress classic editor."},{"src":"https:\/\/ps.w.org\/np-tiwg\/assets\/screenshot-2.png?rev=2516414","caption":"A screenshot of the post NP Twig setting"}],"raw_content":"\n
tpl-{{post_type}}<\/code><\/li>\n- or add a custom field to your post name it twig<\/strong>\u00a0and store the template name inside it<\/li>\n<\/ul>\n\n
Custom Fields and ACF<\/h4>\n\n\n- WordPress supports custom fields, and you could add them directly to your post,<\/li>\n
- and ACF plugin gives more power to the custom fields<\/li>\n
- Use the Advanced Custom Fields plugin to take full control of your WordPress edit screens & custom field data.<\/li>\n
- Read more about ACF on https:\/\/wordpress.org\/plugins\/advanced-custom-fields\/<\/a><\/li>\n<\/ul>\n\n
Template Syntax: a quick guide for WordPress Front End for Custom Field<\/h4>\n\n
Note: WordPress Classic Editor<\/a> is preferred to edit templates<\/p>\n\nComments<\/h4>\n\n\n- Use
{# comments #}<\/code> for comments, and comments will not render to the user,<\/li>\n<\/ul>\n\nVariables output<\/h4>\n\n
Variables in templets are post title, post object, and custom fields. To output post title you can use {{ title }}<\/code>. If your post has a custom field called price. We use {{ price }}<\/code> to output the price. Use a dot (.) to access attributes of a variable (methods or properties of an object, or items of an array: {{ foo.bar }}<\/code><\/p>\n\nConditional output<\/h4>\n\n
The\u00a0if<\/code> statement in Twig check if a variable has a value or an expression evaluates to\u00a0true<\/code> We can add conditions to display any text. Let's say that we have a custom field named \"agent\" and want to display a text when the field agent contains a text. We can write<\/p>\n\n{% if agent %}\n We have an agent in your area\n Our agent: {{ agent }}\n{% endif %}<\/pre>\n\nanother example; let's say that we have a field named price. We want to display a text if the price is zero<\/p>\n\n
{% if price == 0 %}\n <p>This product is free<\/p>\n{% endif %}\n<\/pre>\n\nPlease note that we use the operator ==<\/code> to check the equality You can also test if an array is not empty:<\/p>\n\n{% if meanings %}\n <p>The array or repeater field **meaning** contains some values<\/p>\n{% endif %}<\/pre>\n\nClosing condition block<\/h4>\n\n
Always use {% endif %}<\/code> to close the previous if condition, Read more about if keyword in twig<\/a><\/p>\n\nRepeater field and arrays<\/h4>\n\n
If our field or variable is an array or a repeater field we can loop over each item in a sequence using for keyword<\/p>\n\nThe for\u00a0statement\u00a0code example\n\n
{% for m in meanings %}\n Meaning: {{ m.meaning }}\n{% endfor %}<\/pre>\n\nThe for statement format\n\n\n- We use\u00a0
{% for m in meanings %}<\/code> to loop over an array or repeater field called meanings<\/code> using m<\/code><\/strong> to mention for each row<\/li>\n- Inside the loop starts the subfields or array items with the variable name
**m.**<\/code><\/li>\n- Always close the loop use
{% endfor %}<\/code><\/li>\n- Read more about the
for<\/code> keyword in twig<\/a><\/li>\n<\/ul>\n\nImportant notes for templates code<\/h4>\n\n\n- In WordPress classic editor show source and ensure there are no tags inside the template code; ex
{% <del><span><\/del> endfor <del><\/span><\/del> %}<\/code><\/li>\n- For more details, see: https:\/\/twig.symfony.com\/doc\/2.x\/<\/a><\/li>\n<\/ul>\n\n
Power templating with only 4 keyword<\/h4>\n\n
Using if, endif, for and endfor<\/code> allows to generate a powerful template; however, twig contains many other useful keywords to see other keyword and how to use them visit twig documentation<\/a><\/p>\n\nShort template example<\/h4>\n\n<h2>Meaning of {{ title }}<\/h2>\n{# This is a comment and will not render #}\n{% for m in meanings %}\n {% if m.meaning %}\n Meaning: {{ row.meaning }}\n {% endif %}\n {% if m.example %}\n Example: {{ m.example }}\n {% endif %}\n{% endfor %}\n<\/pre>\n\nOutput post data<\/h4>\n\n
We can access the post using the post keyword. to access any property of the post we put a dot (.)\u00a0 and then we put the property name for example use post.content<\/code> to access post content<\/p>\n\n{{ post.title }}\n \n{{ post.content }}\n<\/pre>\n\nread more about accessing post content on timber documents<\/a><\/p>\n\nWhy templating engine and not a raw PHP programming language<\/h4>\n\n\n- More Simple; so templating is more readable, and very easy that allows users to learn quickly,<\/li>\n
- and Limit the allowed function to prevent bad mistakes,<\/li>\n
- and easy to edit using WordPress classic editor<\/li>\n<\/ul>\n\n
About Twig templating engine<\/h4>\n\n\n- The twig template engine process templates data, and output a webpage.<\/li>\n
- and it is a flexible, fast, and secure template engine for PHP.<\/li>\n
- We use Twig a template language, and we allow users to modify the template design.<\/li>\n
- It is fast because Twig compiles templates into optimized PHP code.<\/li>\n
- Get flexible, so it allows the developer to define its own custom tags and filters.<\/li>\n
- Read more about Twig<\/a><\/li>\n<\/ul>\n\n
Timber and Twig<\/h4>\n\n\n- Timber helps to include Twig in WordPress,<\/li>\n
- with Timber, you write your HTML using the Twig Template Engine separate from your PHP files,<\/li>\n
- and this cleans up your template code so, for example, and your Twig template can focus on the HTML and display.<\/li>\n<\/ul>\n\n
License and use<\/h4>\n\n
This plugin is distributed in the hope that it will be useful, but without any warranty. See the GNU General Public License for more details. http:\/\/www.gnu.org\/licenses\/.<\/p>\n\n
For Developers<\/h3>\n\nAdd custom data to fields<\/h4>\n\n\n- Edit the file user-functions.php<\/li>\n
- Create a function and name it
get_fields_{{post_type}}<\/code><\/li>\n- If your custom post type contains \u2018-\u2018 replace it with \u2018_\u2019<\/li>\n
- I include a sample function in user-functions.php<\/li>\n
- Backup your functions, and keep in mind that the file user-function may be replaced on upgrade<\/li>\n<\/ul>\n\n
Add custom data for each singular page<\/h4>\n\n\n- Edit the file user-functions.php<\/li>\n
- then create a function and name it np_content_singular<\/li>\n
- I include a sample function in user-functions.php<\/li>\n
- Backup your functions, and keep in mind that the file user-function may be replaced on upgrade<\/li>\n<\/ul>\n\n\n
\n- Install Timber plugin<\/a><\/li>\n
- Upload this plugin folder to the
\/wp-content\/plugins\/<\/code> directory, or install it through the WordPress plugins screen directly.<\/li>\n- Activate the plugin through the \u2018Plugins\u2019 screen in WordPress<\/li>\n
- and you will more benefit from our plugin if you could install \nAdvanced Custom Fields<\/a><\/li>\n<\/ol>\n\n\n
This section may be added in the next version<\/p>\n\n\n
1.0<\/h4>\n\n\n- Plugin initial release<\/li>\n<\/ul>","raw_excerpt":"NP Twig Front End for WordPress Custom Field and Advance Custom Fields. Renders data using a twig template. It supports both free ACF and ACF pro.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/scn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/139022","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/scn.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/scn.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=139022"}],"author":[{"embeddable":true,"href":"https:\/\/scn.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/miniindustry"}],"wp:attachment":[{"href":"https:\/\/scn.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=139022"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/scn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=139022"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/scn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=139022"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/scn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=139022"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/scn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=139022"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/scn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=139022"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}