Magento index page loads but 404 errors on all others - magento

Currently I am struggling with the categories and products showing 404 errors when I navigate away from the working home page.
I was able to install Magento and I am using a copy of an existing working site. The purpose is to use this new site as my dev sandbox. I am using Magento 1.11. This is also a multiple store site.
Things I have tried:
Reindex the Catalog URL Rewrite, this unfortunately never completes.
To try and solve this I have deleted all the lock files and then I have also deleted all the entries in the core_url_rewrite table.
I have also changed the Base URL in the core_config_data table to my new URL.
Thank you in advance!

Just like Fiasco Labs said, you probably turned on URL Rewriting:
System -> Configuration -> General -> Web -> Search Engine Optimizations -> Use Server Rewrites but don't have mod_rewrite Installed/Enabled.
Either Install/Enable it on your host, or just turn the server rewrites off.
Another reason, if you HAVE mod_rewrite Installed/Enabled, you might be missing .htaccess file in your Magento root.

even with mod_rewrite enabled, the error can be a misconfiguration of apache. Have a look at etc/httpd/conf/httpd.conf file. Find the part where is defined (standard Apache config dir). You should find:
AllowOverride All
If there is a
AllowOverride None
Change it to All and the magic happens. Then restart Apache with:
sudo service httpd restart

Related

How to enable module rewrite in Apache configuration

I'm trying to copy website made in Magento in my localhost and finished another steps:
copied whole website via flash drive,
import database from server,
change parameters for database in local.xml (post root for user and
empty field for password),
clear cache in Magento var folder,
change base_url value in database
When I try to open it in browser, Homepage looks ok, but any link in page give me Error 404 - Object not found. I can't access to admin panel. Anything what I type URL after localhost/nameOfMyProject, I get Error 404.
I have another Magento project in my localhost and they work correctly, but that I installed from fresh Magento installation and then add new themes for that.
Here is different situation. I need to add whole existing project from server in localhost. I can't add this website on same way, because developer who made it changed files into core section. Project is too big it's not possible at the moment to change that, so any way is to download whole project in localhost.
Does anyone has some suggestion what to do?
If you are using XAMPP or WAMP as your web server, you may face a common problem that is the rewrite module (mod_rewrite) does not work properly. It is because the rewrite module is not enabled by default in Apache’s configuration settings. But you can enable it manually by following some simple steps:
1- Open apache’s configuration file using your favorite text editor. The configuration file is generally located at:
{apache_dir}/conf/httpd.conf
If you are using XAMPP or WAMP package then you will find the file at:
{xampp_dir}/apache/conf/httpd.conf
{wamp_dir}/apache/conf/httpd.conf
2- Search for the following string:#LoadModule rewrite_module modules/mod_rewrite.so and uncomment it (remove the ‘#’ sign).
3- Now search for another string AllowOverride None and replace it by AllowOverride All
4- Finally save the changes, close your text editor and restart your apache server.

URL rewrites do not work after moving Magento installation to new server

After duplicating our web store onto a new server, copying the database over and changing the base url/safe base url in the db, all we get from the copied installation is the front page. That is, no custom url redirects work (for products, the admin panel, etc.), they all result in a 404 (and not the magento 404, the server default). Do you have any ideas what I could check out? Could there be an issue with one of the libraries included in magento?
I tried reindexing with /shell/indexer.php - which executed successfully but didn't fix the redirects.
Any ideas? Note I cannot access the admin panel via /admin because of this issue.
Edit: solution was .htaccess file missing in root directory
I added the sample htaccess file from the magento installation (I uploaded a copy in case someone finds it useful: http://sdrv.ms/13mw8Ok), and mod_rewrite was activated the next time I visited the site.
Make sure your vhosts file is setup correctly to allow mod_rewrite
Make sure your .htaccess file is setup correctly
How to enable mod_rewrite for Apache 2.2
You can access your admin through /index.php/admin in the meanwhile.

Magento Use Web Server Rewrites in Multi Domain Setup

I have to two stores each having different domain. They are hosted on dedicated server with SuExec disabled. I have copied the .htaccess and index.php and everything works fine.
The problem I am having is with my 2nd store Web Server Rewrites. As soon I enabled this for the 2nd store which is using symbolic link to the root directory, it starts giving page not found error.
domain2.com/index.php/abc.html ----- Works Fine with Use Web Server Rewrites Turned Off
domain2.com/abc.html ----- Does not work with Use Web Server Rewrites Turned ON
The base store works without any problem.
Any help is much appreciated.
Farrukh Khan
-> Flush The Magento Cache
Goto System->Cache Management
Refresh the catalog rewrites
Goto All Cache and change drop down to Refresh.
Click save
On most server, this should take out the index.php in your URL’s.
If you are getting a 404 error, continue reading.
-> Fixed Mode_Rewrite Errors
Please check you webserver configuration.
Do you use Apache? Maybe there is something like "AllowOverride none" in your configuration which disables .htaccess-files (the .htaccess-file in your magento-root-directory defines the rewrite-rules).
The most common cause for this is that you have an incorrect .htaccess file in your ftp.
Goto the magentocommerce.com site and download the magento files again.
Extract the files, and ONLY upload the .htaccess file to your Magento root directory.
This should fix any problems related to enabling the use of web server rewrites in Magento.
I was facing the same problem above, but now i solved already. The main reason for that problem is .htaccess file. By replacing .htaccess file with magento default .htaccess file solve all the problem. Web Server Rewrites Turned on or off, you can do as you like.
After saving the configuration, don't forget to clear cache.

Eliminating index.php from URL in Joomla 2.5

I am using Joomla 2.5. The problem is, every link has 'index.php', like:
www.mysite.com/index.php/contact
www.mysite.com/index.php/about-us
How do i remove the '.../index.php/...' from my URLs?
My SEO settings under Global Configuration are:
==================================
Search Engine Friendly URLs Yes
Use Apache mod_rewrite Yes
Adds Suffix to URL No
Unicode Aliases No
Include Site Name in Page Titles No
==================================
I have changed htaccess.txt to .htaccess. I have tried everything, but still can't remove 'index.php' from the URLs. Please help me. My apologies if this exists elsewhere.
Go into your Joomla administration panel.
1. Select Site > Global Configuration
2. Under SEO Settings set Use URL Rewriting to Yes
3. Click Save
The next step is to rename the htaccess.txt file that came with the installation to .htaccess
thats it. Hope this helps .
Did you change the setting on the administrator backend or the actual configuration file? Sometimes if you directly modify the configuration.php this wont work. If you did it from backend panel then check your configuration.php to make sure the changes are reflecting.
Also check with your hosting to have mod_rewrite available on the Apache server.
Very unlikely but it could be a small mistake on renaming process of the htaccess.txt , double check the renamed file.

Moved Joomla 1.7 Site to New Server. Admin works fine. No pages display

I've just moved a Joomla 1.7 site to a new server.
Administration back-end works fine. Configuration.php seems fine. Get "The requested document was not found on this server." for every page other than Home.
Must be talking to the database OK or I'd get an error. Could this be a problem with the PHP?
Thanks,
Andy
Did you clear joomla cache ?
Disable page and/or module caching.
Disable any plugin that optimizes "loading speed".
Try removing SEF URLs (Joomla! and any 3rd party extension).
If you are using a custom .htacess, then use an unmodified joomla one.
Disable some system plugins.
Disable modules in the homepage.
Have you tried using another template (site) ?
You have Seach Engine Friendly URLs enabled in /administrator/ area's global configuration settings. You have probably enabled the option to use the mod_rewrite function which removes the /index.php/ portion of the urls.
It is a requirement of this mode that you have the .htaccess file in place in the root of your site. You probably had this correctly configured on your development server but perhaps forgot to move the file across when you went live. Some FTP programs hide dot files (files starting with a leading dot in the filename) so depending upon how you transferred the files (I'm guessing manually with FTP rather than Akeeba backup or similar) the file may have been missed. Look through your FTP client's options/preferences for an option to show/hide hidden files.
Failing this - the file could be correctly in place - but if you were developing in a sub-folder on your development server you would have set the RewriteBase line to your /sub-folder/
RewriteBase /sub-folder/
Now you've moved to the live server this line could be incorrect. If this is the case, edit the file to Read
RewriteBase /
Chances are it is one or other of these issues - missing .htaccess file or incorrect RewriteBase. A third and nowadays somewhat more unlikely option is that your server doesn't have mod_rewrite enabled - but I think that would result in server 500 errors.
Check whether you are using any modules that is calling database and you have not changed DB details in that module after migration. If admin panel is working fine then I think problem with some modules that are used in front-end. You can do debugging by disabling few suspected modules and check whether your site works fine or not. Else provide some more information about your site so that I can check further.

Resources