A field that “Load data” does not fill from the markup
fld-no-import="1" “Load data” copies the texts of your markup into the fields, and it can be run again. For a field the client fills in themselves, such as a notice, the manager’s phone or today’s menu, the fld-no-import mark protects the text: the field exists and works, but loading leaves it alone.
Where it goes
Next to the field mark, on the same element: fld-area="Opening notice" fld-no-import="1".
The scope in the spelling does not matter: opt-no-import and tax-no-import mean the same. On a list or a group the mark protects all of it; on a field inside a row, only that field.
The field appears in the admin only if the page has a group name: wp-fields-group on its <body>.
Example: a notice on the home page
<section class="hero">
<h1 fld-text="Hero title">Coffee for slow mornings</h1>
<p class="notice" fld-area="Opening notice" fld-no-import="1">Closed on Monday, 12 October.</p>
</section>Open until 22:00 on Friday.
The client wrote their own notice; loading again did not replace it.
What matters
- The field is created and shown as usual; only “Load data” changes.
- A value of
0,false,offornoturns the mark off. - It works with any version of the theme: the field’s text simply never gets into the data to load.
Common mistakes
The build log is the “Logs” tab of your project on themeforge.pro; the free markup check shows the same notes.
<p class="notice" fld-no-import="1">Closed on Monday, 12 October.</p>The mark on an element without a field: there is nothing to protect, and the build logs the attribute.
<p class="notice" fld-area="Opening notice" fld-no-import="1">Closed on Monday, 12 October.</p>The mark goes next to a field mark.
Alternative spelling
opt-no-import, tax-no-import works the same: the build gives an identical theme.