sipsniffa

Thanks for the reply. I did mention that I’m using two categories to help with the separation.

I’m afraid I didn’t mention .htaccess rewrites – my suggested solution would use the WordPress rewrite_rules_array filter to remove the category portion of the URI in order to give what appears to be a second (video) “posts page”. Any advice on its use would be very welcome.

By the way, I only want to remove the category portion of the URI for one category – i.e. video. I believe the Decategorizer plug-in you referenced removes the category portion of the URI for all categories and the plug-in has now been deprecated.

Thanks again, and any further suggestions would be welcome.

Paul.

Check out the codex documentation for wp_list_pages() to see why your theme isn’t listing all the pages.

I neglected to escape the HTML element in my second paragraph. I meant to say; “… replacing any spaces within menu names with a <br /> HTML element.”

Is there a question related to your post?

Let me have a stab at an answer: HTML comments should be closed with the character sequence “–>” (without quotes, of course), and not “–!>”.

Which pages are shown on the menu depends upon how the template is selecting the pages. There’s a good chance your theme is using wp_list_pages() – I guess you’re not the theme creator? Also, it might be that you’re using a plug-in that filters pages from being displayed.

You could use something like preg_replace() wherever your theme generates the menu, replacing any spaces within menu names with a HTML
element.

The template tag functions are used to get content and custom tag values on other ‘static’ pages without any problem, but the ‘page for posts’ page doesn’t return anything!! (btw, I’m the them developer.)

Could MichaelH, or anyone here, please confirm that content and custom tag values can be obtained from the ‘page for posts’ page using the template tags.

Thanks.

What purpose does a ‘dummy page’ for the page-for-posts provide?

The dummy page concept appears to be broken and a source of confusion. Custom fields on the page-for-posts page are unavailable to themes, unlike all other static pages. (The same is true of the page’s content.)

Can anyone suggest a workaround that allows custom fields (and content), set in the page-for-posts page, to be accessed by themes?