WordPress.org

1. ssjaime
   Member
   Posted 1 year ago #
   

   I'm building a WordPress front-end for a client.

   The bulk of the site is static pages (generated outside WordPress) to which we've added:
   

   <?php include('wp-blog-header.php'); ?>
   <?php get_header(); ?>

   at the top and
   <?php get_footer(); ?>
   at the bottom.

   I am using Headway Themes (have posted this in their forum too: http://support.headwaythemes.com/showthread.php?p=17332#post17332

   The issues I'm having are that these pages are outside WordPress and therefore are mapping to the 404 page layout and fall outside the SEO capabilities & breadcrumbs.

   Any recommendations on how to map these pages to a layout/structure that WordPress can use/understand?

   Thanks!
   --Jaime

   Oh, the site is temporarily at http://beezidreports.com/wordpress and "Top Items" is a custom menu item linking to one of the static pages.

2. stvwlf
   Member
   Posted 1 year ago #
   

   Suppose the obvious question should be asked, "why not integrate the static pages as WordPress content if you want to build the whole site in WordPress?" That's no more complex than resolving the issues you are encountering.

3. ssjaime
   Member
   Posted 1 year ago #
   

   This project involves a membership component, and frankly I don't want to re-invent the wheel, and have chosen to use a WordPress membership plugin!

   (Using the free version of S2Member, which works fine on these static pages)

4. gxxaxx
   Member
   Posted 1 year ago #
   

   Is the idea to create/store/manipulate the static pages outside the wordpress system, but use the wordpress system to navigate the data?

5. ssjaime
   Member
   Posted 1 year ago #
   

   Yes - that's exactly what I'm trying to do.

6. gxxaxx
   Member
   Posted 1 year ago #
   

   I was wondering about adding pages one for one.
   One wp page for each static page.
   The content of the wp page could be a shortcode something like
   [grabstatic url="/folder/pagename.html"]

   Then the plugin could grab the static page with either a include or perhaps one of the http functions in wp.

   I am quite new to hacking wp, so I can't say which of these options would be the fastest to code or the best for stable running.

   Just a thought. I think you should be able to grab the static pages from behind a .htaccess password protection scheme as well to prevent non-members from lurking your content.

   Just a thought.

7. ssjaime
   Member
   Posted 1 year ago #
   

   we're using the s2Member (basic) plugin to protect the content and the content is in a subdirectory of our wordpress installation so it's adequately protected.

   The reason for the static/non WP pages is because there are thousands generated by an offline program and then loaded onto the server. The one-for-one idea isn't feasible :)

   I had thought of the .htaccess route, but am not sure how to tackle the file... and if it will even work to be able to force WordPress to realize these are "good" files instead of 404 pages.

Topic Closed

This topic has been closed to new replies.