at the moment I don’t know if it’s a real bug or a bug in programming, so an example with WP-PageNavi installed and integrated in page template:
site 1 <!--nextpage--> site 2 <!--nextpage--> site 3
sample text after clicking html button:
<p>site 1</p> <p><!--nextpage--></p> <p>site 2</p> <p><!--nextpage--></p> <p>site 2</p>
correct result in frontend if you put it in wp standard content field:
site 1 Pages: 1 2 3
result in frontend if you put it eg. in ACF WYSIWYG field:
site 1 site 2 site 3
I use normal code in template to output acf field like this:
Thanks for the debugging info.
I think the wp-pagenavi plugin is hooking into the the_content filter and modifying the value based on the comments.
In fact, I’m 99% sure it is.
All you need to do is run the the_content filter on the ACF value, and your output will render correctly!
echo apply_filters('the_content', get_field("pagenavi-site"));
Are you sue WP Page navi has a shortcode for this?
I just looked at the installation guide, and can’t see any shortcode functionality.
I also searched the source code and found no reference to the_content, !–, or shortcode.
Are you assuming this functionality exists?
I don’t think that it is working with a shortcode. For making a page break you must use
which is’nt a shortcode, or I’m wrong with it? It’s like the standard
of WordPress. This isn’t working, too, how I tested after writing about
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!