fitJaime

I’m right there with you — I know it can be done just don’t know if it’s in the Personality Quiz Add-On plugin or in the other 3rd party plugin that we are integrating with.

Just installed on a client site and same issue.
PHP 5.2.17

The site is running Headway Themes 2.0.13 and the following plugins (although because I can’t access the dashboard, they might not all be active):

• wp-tables-reloaded
• wp-fb-fan-box
• wp-db-backup
• twitter-anywhere-plus
• simple-image-widget
• sexybookmarks
• meteorslides
• gravityformspaypal
• gravityforms
• google-sitemap-generator
• font-uploader
• commentluv-premium
• akismet
• add-image-src-meta-tag

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.

Yes – that’s exactly what I’m trying to do.

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)

Did you follow all the steps in the codex?

Set it as:
wordpress address: https://site.com/wordpress
site address: https://site.com

Copy the index.php file and .htaccess files to the root

Open your root directory’s index.php file in a text editor
Change the following and save the file. Change the line that says:
require(‘./wp-blog-header.php’);
to the following, using your directory name for the WordPress core files:
require(‘./wordpress/wp-blog-header.php’);

My client was able to provide me with the logon credentials for ftp (which i’d asked for before).

I’ve reverted to Twenty Ten ??

Did you follow the instructions to update the .htaccess from the codex?

https://codex.www.ads-software.com/Giving_WordPress_Its_Own_Directory

Any advice on where in the stylesheet to look to identify this issue? I think it’s all stype related.

Thanks.

Everything looks good according to validator.w3.org but it’s still not spacing correctly.

–Jaime

Thanks for the suggestion.
I changed from strict to transitional which resolved the problems on the contact form but not the issues on the products-page.

Any specific errors jumping out as to why the products-page is still having issues?

Thanks!
–Jaime