brendan_balwebco

Stupid me, didn’t read the documentation thoroughly enough. I’ve made my own theme and there are instructions on how to import custom styles in the WP 4.1 dashboard under settings>tinymce advanced>advanced options

SOLUTION FOUND

If anyone is having the same problem I resolved this issue by adding a wp_reset_query:

<?php wp_reset_query(); // Restore global post data stomped by the_post(). ?>

…after each loop. For example:

// Display ACF content for category a
<?php the_field('category_title_a'); ?
<?php the_field('category_content_a'); ?>

// Display posts from category a
<?php $my_query = new WP_Query( 'category_name=cat-name' );
while ( $my_query->have_posts() ) : $my_query->the_post(); ?>
//extra stuff here
<?php endwhile; ?>

<?php wp_reset_query();  // Restore global post data stomped by the_post(). ?>

NB according to the wp_reset_query it would seem that WordPress encourage use of a different method so have a read of that page first.

I have just removed the query_posts(‘category_name=cat-name’); from each query and it works fine – obviously this means that it’s now pulling in the same info on all modals

…This of course means that when creating a new site and all its pages you then have to setup a menu and re-do the parent-child relationships as when you add all the pages in the menu pane it inserts them all as top level items by default.

I would have assumed that the functionality would be such that when one defines a sitemap, akin to the UI in the menu pane, each menu item then has its own attributes including those that define whether or not it is included in the navigation.

I don’t see the benefit of having two separate methods for controlling page positions within the sitemap hierarchy e.g. changing the parent of a particular page in the ‘edit page’ pane to then have to repeat the action in the ‘edit menus’ pane in order to keep the sitemap and navigation consistent; why would you want the option of having the navigation different to your sitemap? If it’s simply to control whether or not certain pages are included in the navigation then why not just have the menu adhere to the sitemap but have an extra attribute for each page, in addition to the ‘page parent’ attribute, that says ‘included/excluded from navigation’, rather than having to create an entire custom navigation?

Hopefully I’ve completely missed the point.

Any WP experts?

It can’t be the case that such a comprehensive CMS would omit such a simple feature surely? It doesn’t make sense that you should have to maintain two lots of parent-child relationships between pages, that’s madness. There must be a way around this.