Forum Replies Created

Viewing 15 replies - 1 through 15 (of 17 total)
  • Forum: Fixing WordPress
    In reply to: Custom page names?
    Thread Starter meegwell

    (@meegwell)

    thanks moshu – so it sounds like an SE friendly redirect would need to be put in place for each of the old pages…i believe thats a 301…

    I do, but it is not used – I put the .htaccess in all my WP sites’s roots now and was able to remove the one on the server root. I was confused for a while on the location but I worked through that.

    Still get 404s every time I try to access a non-wp file though…

    thank you for the response otto. here is my .htaccess, located in the root of the site (/public_html/site/.

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On

    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    note that the site is on a server with many other sites (including other wp sites). At the root of the server (public_html/) is another htaccess file:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress

    For others with this problem, I have recently tried this solution I found in another post:

    ADDED: Thanks to Teli’s comment below, I’ve implemented the TPX solution (from TextPattern), and all is solved. I created a myerror.html page and, in the .htaccess, removed the above “fix” (and the fix in the index.php) and added the following:

    ErrorDocument 401 /misc/myerror.html
    ErrorDocument 403 /misc/myerror.html

    I also rebooted, which was causing my first fix above to stop working; this one works fine. Hats off to TextPattern.

    This did not work for me either.

    In a nutshell, I need to access some non-WP pages on the WP site but WP throws a 404 everytime I try to access them.

    I created a directory, TestDirectory, and a file, test.html. So along with the normal wp directories (/wp-content/ etc) there is /TestDirectory/test.html.

    When I try to access test.html, even though I know its there, I get a 404.

    Thread Starter meegwell

    (@meegwell)

    Thanks. So this code, which is located at my server root (above the wp site in question), is controlling the permalinks and redirects (ie 404 for access outside of WP folders/files):

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress

    What are my other support options to resolve this?

    Through my research I actually installed the plugin to deactivate canonical redirects.

    This did not fix the problem of accessing non-WP files in non-WP subdirectories.

    Sorry moshu. I was just surprised to see how many folks have had the same exact problem and no resolutions posted for it…and it seems that there should be a simple solution to this issue.

    Eiland,

    Can you clarify where these lines go? within the Begin/End WOrdpress? My current .htaccess looks like this:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    I have this same issue. Appently there is a way to modify .htaccess to allow certain subdirectories to be accessed. Can anyone help out here?

    I have this same exact problem. Anyone?

    Thread Starter meegwell

    (@meegwell)

    I’ve searched and found this issue to be very common. There was one solution that sort of makes sense – to add some lines of “allowable” subdirectories in .htaccess:

    # stuff to let through (ignore)
    RewriteCond %{REQUEST_URI} "/folder1/" [OR]
    RewriteCond %{REQUEST_URI} "/folder2/"
    RewriteRule (.*) $1 [L]
    #

    Does this mean that my .htaccess should look like this:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond %{REQUEST_URI} “/directory/”
    RewriteRule (.*) $1 [L]

    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    …or do I do it separate from the # WordPress section?

    I clicked Activate and the screen went blank (WPAU 1.1) WP 2.1

    Now my whole blog is blank and the php error is:

    [Wed May 7 13:38:33 2008] [error] PHP Parse error: syntax error, unexpected $end in …/public_html/nashville95/wp-content/plugins/wordpress-automatic-upgrade/lib/pclzip.lib.php on line 1762

    Thread Starter meegwell

    (@meegwell)

    thanks jeremy, mrkingid.

    whooami: :And I told you how it happened. It happened because your version is exploitable.”

    um, that’s why, not how. No matter. Im fine. Got it.

    “You accidentally didnt upgrade? OK, whatever.”

    I never said that, check the posts.

    “Like I said, over a year old..”

    You didn’t say that.

    “You want a virtual hug? Come back after you have upgraded.”

    Thanks. I’m running 2.5 on several other sites. This site was purchased and transferred, I did not do the install….but I’ll be looking for that big great virtual hug and a wet sloppy virtual kiss when I return!

    Thanks again all. Have a great day!

    Thread Starter meegwell

    (@meegwell)

    whooami,

    thanks for you insight. I am aware this was some sort of exploitation. My question was how? You offer no information. I know what version IM running on that sight, I entered it when I posted.

    I never said I couldn’t be bothered either. I’m just a humble sap looking for some information. Maybe you got some use or feel-good-moment out of your post?

Viewing 15 replies - 1 through 15 (of 17 total)