Home/ Questions/Q 8024267
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T22:49:03+00:00

I have a fresh magento 1.7 using a copied sql from a shop online.

  • 0

I have a fresh magento 1.7 using a copied sql from a shop online. The shop is using Mag 1.4 so the idea is to update the DB to 1.7. After linking the 1.7 shop to the DB on localhost, it is error free, however 127.0.0.1/shop redirects to the online store.

Changing base_url does not help.

The DB still has references to the online site, but I dont see any reference that would make a difference.

This seems to be a common problem with out any solutions?
http://www.magentocommerce.com/boards/viewthread/280257/#t387542
http://www.magentocommerce.com/boards/viewthread/224658/#t313216

UPDATE –

The question at http://www.magentocommerce.com/boards/viewthread/280257/#t387542
has been updated with a comprehensive answer by chiefair, like the one given by Fiasco Labs below – if you are in need of more info

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Changed your base URL settings in the Magento database and it’s still going to the old base URLs. You started Magento once before changing them and it cached the old configuration and now you’re locked onto the old site.

    For Linux, change your var/ directory structure to chmod -R 777. You don’t have write permissions there and Magento has established a cache in /tmp as it needed somewhere to write the cache files. It’s cached the config settings and will not reread them until the cache is in the right directory location. If there are subdirectories in var/cache, delete them all. You might have to go hunting for /tmp/*/var/cache and delete those as well.

    Edit: Same goes for Mac and Windows, if you’ve got the database changed and can see the changes took in phpMyAdmin, you have manually cleaned out your var/cache subdirectories, given Apache a restart, and the system is still redirecting, you early on, had a misconfiguration that wrote Magento’s cache elsewhere. That is why it’s persistent. Usually a machine reboot will clear it on Mac and Linux as they do housekeeping on their temp folders when the OS restarts.

    Here are screenshots of the system /tmp Magento cache storage in action on a Linux server with bad file permissions.

    Pay attention to the top address bar in both images…

    Pay attention to the top address bar in the image...

    And here’s your hidden cache that’s causing you difficulties.

    And here's your hidden cache that's causing you difficulties.

    • 0