Support » Fixing WordPress » Page management looking good!

  • I just installed the latest nightly (Oct. 6) and the new Page management showed up. Looking very good, I’m excited to see it develop! Some first impressions and questions…
    Great idea to be able to create child pages to a parent page! Will this eventually develop in automatic navigation generation for Pages, along the lines of how categories and subcategories work maybe?
    Is the post slug going to turn up for Pages too?
    Will it be possible to manage Pages outside of the WP directory? Say I have WP in the http://domain.com/blog/ directory, can I still manage the domain’s index at http://domain.com/index.php with WP?
    Let me just say this is very exciting. WP is a great blog tool, but this imho pushes it into another class of tools all together.

Viewing 15 replies - 1 through 15 (of 17 total)
  • Can you update the permanent links structure with the current nightly of WP 1.3?
    I created a static page and wanted to view it but I got an error 404. So I tried to update the permanent links structure what resultet in the following error message:
    Warning: Invalid argument supplied for foreach() in /home/blog/public_html/blog/wp-admin/admin-functions.php on line 524
    Warning: Invalid argument supplied for foreach() in /home/blog/public_html/blog/wp-includes/functions.php on line 1253
    Warning: Invalid argument supplied for foreach() in /home/blog/public_html/blog/wp-includes/functions.php on line 1253

    Hmm, I had no such problems. The Pages I had already created displayed fine and updating the permalink structure worked okay. A new Page created showed up fine too.
    Previously the Pages were ‘published’ under the /site/ directory, but that limitation has been removed.
    One slight problem remaining is that once you save a new Page, WP returns to the Write screen instead of the Manage/Page screen. I’ll plug that into the buglist.

    OK, problem probably solved: The error messages mentioned above no longer appear since I created a static page! 🙂

    Moderator Ryan Boren

    (@ryan)

    WordPress Dev

    Those initial warnings should be fixed now.

    Slug editing will be available. Not sure if we’re going to include “menu” code with 1.3 but the fields are in the DB for menu ordering.

    Thanks 🙂 The “menu” thing is just icing on the cake though, but the post slugs will be nice for fancy titles and simple URLs.
    I think it would be a really powerful feature if you can have your blog in a subdirectory (/blog/) while still being able to use WP to edit Pages in higher directories (like root).

    I tried creating a page with the edit-pages.php and when I try to view the page, I get a 404 file not found.

    Fixed, had to edit the .htaccess to get it to work.

    Next problem, it looks just like a post and I am unable to put things in it that are out of the post loop. Little problem if I want an expanded links list or stats.

    Only way to add those is thru a themes and there it would need to be an option for a template_redirect in wp-blog-header.php although the page feature would be perfect for stories.

    You can choose different templates to be used for different pages, so you really have infinite flexibility as to what’s on the page.

    Ah, ok, just have to figure out how to make the templates. That makes sense.

    It doesnt require a redirect. By default 1.3 first looks to see if there is a file then if not it loads its default. So you just put your stuff in its path.

    Nother problem, when I used templates, ie single.php in the main directory, it didn’t work with Themes as the the default overrided the theme. How does this work with Themes?

    Very nice feature, will finally eliminate the need for my index.php file hacking I use (well, some of it). I don’t wish to hijack the thread, but for those interested, once the pages feature solidifies I’ll work on making a breadcrumb for it in my breadcrumb plugin.

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Page management looking good!’ is closed to new replies.