yolise

Perfect – that’s it. Not sure why that’s it, but it is. ??

Given that WP doesn’t come with a “clients” post type, what happened here is that someone made a post type with the same slug name as the page.

As you can see from above, it was intentional, and only a change to 3.4.1 made this not work.

As it happens, I’ve come up with my own workaround (which admitedly is probably how I should have done it in the first place, but when one technique works, one doesn’t usually keep rooting around for a new solution – it’s not really cost-effective).

It also means I have to re-engineer more than one theme that I’ve written.

OK, I may have found a solution, however, I’m not sure what has changed or why. Actually, a reason for the behaviour rather than a solution, sadly.

In the functions file, I’ve changed the slug from “clients” to “clientpages” and it works. It seems that it has a problem with the slug that’s defined in the post-type function having the same name as a page where it didn’t in previous versions of WordPress. This is unfortunate as I’ve used this structure before to create pages like:

https://lisadearaujo.com/clientaccess/TNC/wordpress/clients/ for the main client index and
https://lisadearaujo.com/clientaccess/TNC/wordpress/clients/companya/ for the individual client listing.

Changing it means messing with some of my other customer’s SEO and links in, so I am going to either have to create HTaccess rewrite rules or simply not update their installations unless someone has another solution to this?

So, not really resolved, actually… at least not for any of my established sites.

Yes, I’ve tried that a couple of times, actually.

Maybe I should I explain again in a different way:

I have a custom post type (this may or may not be relevent). The posts are called via a page called “clients” which has a lower-case slug – both in the custom post types and on the post itself: https://www.tnc-branding.com/wordpress/clients/. Every mention of it everywhere is lowercase. However, when I try to access the page, lowercase does not work. It only works when I call the page via the uppercase url: https://www.tnc-branding.com/wordpress/Clients/.

Now, this page worked before I updated my installtion to 3.4.1. This has happened on two different servers.

This is the custom post type:

add_action( 'init', 'create_post_type' );
function create_post_type() {

	register_post_type( 'clients',
		array(
			'labels' => array(
				'name' => __( 'Clients' ),
				'singular_name' => __( 'Client' )
			),
		'public' => true,
		'has_archive' => true,
		'rewrite' => array('slug' => 'clients'),
		'hierarchical' => true,
		'menu_position' => 5,
		'supports' => array('title', 'editor', 'author', 'thumbnail', 'excerpt', 'page-attributes')
		)
	);

This is the page code:

<?php
			$args = array( 'post_type' => 'clients', 'posts_per_page' => 10, 'orderby' => 'menu_order', 'order' => 'ASC' );
			$loop = new WP_Query( $args );
			while ( $loop->have_posts() ) : $loop->the_post();
			get_template_part( 'content', 'clients' );
			endwhile;
			?>

Can anyone see why this would work in 3.4.0, but not in 3.4.1?

Got it. Theme was missing wp_footer!

I’m still struggling with this. Could someone explain how I call the fields array in my function file?

OK – I think that author and email are probably in the $fields array or something, but I can’t figure out where or how to call that. Can anyone help? That’s where the codex just sort of fades away with regard to explanation…

Ah, that’s the ticket! Thanks – I’m sure this will all make sense to me one day.

I notice that your add_action init comes after the function. Mine’s before and it still seems to work. Does it matter?

To clarify a little:

I’m rebuilding a custom theme to work with the latest release and previously the devs had used plugins that hadn’t been updated for years, so I’m pretty much working from scratch, but trying to retain the old url structure for SEO reasons. It appears that “insights” is the category name so I think I can probably figure out how they created this structure. ??

D’oh.

Thanks very much – for both!

Works perfectly!

I’d like to find a solution to this as well. Currently this function only adds a class to the first nav element.

nevermind. I neglected to search properly and see it’s not possible. I’ll have to find a different solution/plugin…

Right – figured it out. It had to do with two errors on my part: mistyping is_front_page as is_frontpage and not realising the difference between front_page and home.

That’s perfect. Thank you!