htaccess conflict

Hello, Experts!  We are bringing a site from another web developer into our GoDaddy hosting account - it was a beta site, running successfully on their server, but for some reason isn't working on ours.  Here's the .htaccess file given to us by their team (with some modifications for anonymity)...

+++++++++++++++++++++++++

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /somedirectory/anotherdirectory/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /somedirectory/anotherdirectory/index.php [L]
</IfModule>

+++++++++++++++++++++++++

It seems that something in the file is "breaking" the site - when we use the "default" WordPress file...

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

# END WordPress
+++++++++++++++++++++++++

... most of the site works fine.  But when we try to go to certain pages in the WooCommerce shopping cart, we get a "page not found" error.  So I'm assuming that there's something about the directories they've put into the "rewritebase" that are necessary for cart functioning, but I can't figure out how to get them to work on my GoDaddy server.  Any ideas?  Thanks so much!!
Harrison WalkerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

William NettmannPHP Web DeveloperCommented:
I think your are looking for the problem in the wrong place - I doubt that your .htaccess file has anything to do with it. The WordPress default one normally works.

The "/somedirectory/anotherdirectory/" bit must have been to accommodate the server the developer was using, which may have had WordPress in a folder off the web root.

The first thing I would do is change the permalinks setting to default, and then back to what you want it to be. That will update the database, and write a new, correct .htaccess file.

If that does not work, then maybe the pages really do not exist - maybe the slug for the page has changed, and the menu entry has not, something like that.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Development

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.