I found out what it was. Actually I think this might be caused by a bug in WordPress (or perhaps one of the add-ons I’m using).
In the content editor I had blocked out some of the code with “<!–” and “–>”. For some reasonthe closing markup “–>” didn’t get registered, so in the code anything after the_content(); got blocked out.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users