peychaud

To answer my own question, I think I figured it out. Believe it or not, I just had to delete the “/home/[account name]/public_html/” before onerror.html.

I would’ve thought the full path would be fine, but I guess not. Anyway, success!

No, I’m not. Sorry. I screwed up.

Frustratingly, I’m still experiencing a 404 error when I use cPanel to password protect a directory. I followed your instructions and created a file in my public_html folder called “onerror.html” and inserted the following two lines at the top of the .htaccess file in my public_html directory.

ErrorDocument 401 /home/[account name]/public_html/onerror.html
ErrorDocument 403 /home/[account name]/public_html/onerror.html

It didn’t work.

Perhaps I’m confused about which .htaccess file to edit and where to place the lines.

My WordPress files are in the directory “/wordpress/” in my public_html directory, but I’ve got it set so that the wordpress installation comes up when people go to mysite.com/

There’s an .htaccess file in both my root public_html directory and in the wordpress directory. Which one should I modify with the “ErrorDocument” lines to avoid the 404?

Also, should i place those lines at the very top of the .htaccess file? Should I put them below the “# BEGIN WordPress” line of the file? Somewhere else?

It seems like I’ve tried every possible permutation to no avail, but perhaps I’ve missed one. Thanks in advance for any light you can shed on this irritating problem.

I just realized that all the pages with the /wordpress/?page_id=999 show up with “edit this entry” whereas the ones that I removed /wordpress/ from the URLs do not show “edit this entry.”

So obviously there’s something there (and that something likely has something to do with .htaccess). Any ideas?