I did a Pyro test installation at mydomain.com/pyro, and now that I have the site configured, I wanted to move everything up to the root directory. It worked fine, except for when I leave off the "www" in my URL, so:
'www.mydomain.com' works fine, all of the navigational links point to the right pages
'mydomain.com' does not work, all of the navigational links still point to the '/pyro/' test directory
I can't find anything in the config files or the database to change this.
How can I fix this?
Have you tried clearing you page cache? Utilities > Maintenance then under Cache Maintenance
Have you checked the default_pages.uri and default_pages.slug columns in your database?
Related
Has opencart 2.1 a cache system apart from modification?
I'm trying to restyle an opencart 2.1 site.
I've modified catalog/view/theme/my-theme/template/product/product.tpl
but I'm not able to see my updates.
The site has only 1 modification that affects Admin area...I've also tried to disable it and update cache, but without success.
I've tried to open site in another browser, but nothing.
Finally I've tried to rename product.tpl to product111.tpl (also in view/theme/default/product)... but the original product page is still loaded.
Does someone know why this happens?
UPDATE : I haven't found a solution, so I made a fresh installation, applied custom theme and then copied modified files... everything is Ok now. If I modify product.tpl, all changes are visible in product page.
If you have vQmod installed there is a vqcache also.
You can check to see if you have vQmod installed like this:
yoursite.com/vqmod/install
It should usually clear itself, but if it doesn't then you can safely rename the vqcache folder to clear it.
The reason I say rename rather than delete is that sometimes a change to the cache will show an error which wasn't spotted when the original change was made and might prevent orders until it's fixed. If you rename then you can place the folder back and it will work again but of course you should fix the error when you can.
How is it with the img/p folder in Prestashop 1.6.0.9? Is it possible fully to clean it? Cause this folder went to big now, and FTP is almost full now, i need space. For example when i renamed it on FTP, all images on the website worked, and prestashop created automaticaly one new img/p folder, and all seems that works right (also when the initial img/p was out after renaming). Thanks in advance.
when you delete the folder you may see the images working, its from smarty cache, once you clear the smarty cache, presta default (not found) image will be shown.
I am doing some simple hooks and some more advanced ones for a customer. (CS-Cart 2.1.4)
I have 2 websistes (production site and test site)...the two environment are not exactly the same, sadly
If I edit anything in a TPL file in the test environment, I simply save+upload on FTP and the edits are immediately visible on test website...
If I do the same edits on production environment, then save+upload on FTP, nothing changes on the storefront...
I understand it has probably something to do with template caching, and i should run mysite.com/admin.php?cc
The problem is I am the new webmaster, the old one left arguing with customer, I don't know what he has left exactly and I am afraid of refreshing production cache and "destroying" everything...(the website makes about 1M Euros/year...just to tell you what...). what if he has made some changes on the template and never refreshed cache???
Any suggestion on how to see my edits to those damned .tpl files???
To avoid clearing cache manually (by &cc) you should to change the Store mode.
Open the Admin area (any page) and look at the page bottom: http://screencast.com/t/aS2aG7oYTg
Your Store is working in Live mode and the Smart Template Engine does not check the changes in file. Click once this link and the Store mode will be changed to the "Development". Cache will be updated automatically.
P.S. You can delete var/cache and var/compiled. Store will not be destroyed :)
I solved it, by creating a clone of the Virtual Machine , editing there, and then replicated edits on main production site after being 100% sure there were no issues when clearing the cache ;-)
This is my first time working with Magento and here is what happend: I spent two days reading the documentation and tweaking the settings to fit my needs. I then installed this theme:
http://themeforest.net/item/decostore-magento-theme/1876494?WT.ac=category_thumb&WT.seg_1=category_thumb&WT.z_author=8theme
The problem is that the theme didn't work the way I was expecting and now I'd like to rollback to the default theme and completely remove everything added by this theme to my installation.
Unfortunately, I didn't backup the installation and database before I installed the new theme and I have no idea where to start.
Thanks in advance.
1. Switching back to default theme
Go to the admin area and then system > configuration > design
Change "Current Package Name" to 'default' and make sure all inputs under the "Themes" section are empty. This will return you to the default theme.
2. Completely remove everything added by this theme
I take it from your question that you are not using any form of source control. Might be an idea to look into this for the future :)
Magento 1.7 has introduced backup and rollback features so you may also want to check that out.
If this is the case, backup everything before you start removing files and directories as described below
Anyway, to completely remove all files and directories added when you installed the module, unfortunately it will simply be a case of manually finding the files and directories deleting.
The easiest way to do this will be to find the original source code you received when you purchased the theme and removing the corresponding files from your site. When removing directories be careful to only remove those specific to the theme - It will have been sent to you structured so that you can easily drag straight in to your web root - so will contain some other directories required by Magento, simply to give it the correct hierarchy.
At the very least there will be files and folders specific to the theme located in the following directories:
app/design/frontend
skin/frontend
js
and also most likely some more in the following:
app/etc/modules
app/design/adminhtml
app/locale
I know the result for this can be different for everyone, but in case someone else comes across my specific case, it was the N98 folder under app/code/community/N98 that caused the problem. Particularly their CustomerGroupCheckout plugin as shown here: https://github.com/amenk/N98_CustomerGroupCheckout
Removing the N98 folder brought back the configuration page.
I have installed, configured and built a site on Concrete 5.5.2.1 and it is all working well. I have a problem that I have a URL of www.ayrshireminis.com/concrete5.5.2.1, for example, which is where the index.htm file sits. Is there a way that I can bring the code back up to the docroot without breaking all references such as image paths in the database for example?
Considering that the download of Concrete 5 includes this directory I am assuming that this is a common issue for some developers when using this CMS.
I'm not sure why you have an "index.htm" file -- there is no such thing in a concrete5 installation. In general, though, you should be able to move the site without problems. A few possible exceptions would be:
Depending on how exactly you're moving things, make sure you get every folder/file. For example, if you're using SSH and do something like mv concrete5.5.2.1/* ./, then you will miss the .htaccess file (because it's hidden). But if you're talking about index.htm files I am guessing you're on a Windows server instead of unix so perhaps this doesn't apply.
In older versions of Concrete5, there was a setting in the config/site.php file called DIR_REL that you would need to change when you move the site. For example, if moving from the concrete5.5.2.1 subdirectory up to the top level, you'd change define('DIR_REL', '/concrete5.5.2.1);todefine('DIR_REL', '');. So take a look in yourconfig/site.phpfile, but if you don't see thedefine('DIR_REL'...` line then don't worry about this step.
If you manually entered full URL's to page links or images, you'll need to update those. Usually this isn't an issue (assuming you use the Concrete5 toolbar that sits above the Rich Text Editor controls -- e.g. "Insert Link to Page", "Insert Image", etc.). But if you notice dead links after you move the site, then either manually update the links by editing the blocks in question, or if you want to make sure you update them all in one fell swoop, you can run the following queries on your database (via PhpMyAdmin, for example):
UPDATE btContentLocal SET content = REPLACE(content, '/old/base/dir/', '/new/dir/') WHERE content LIKE '%/old/base/dir/%';
UPDATE btContentImage SET externalLink = REPLACE(externalLink, '/old/base/dir/', '/new/dir/') WHERE externalLink LIKE '%/old/base/dir/%';
UPDATE btSlideshowImg SET url = REPLACE(url, '/old/base/dir/', '/new/dir/') WHERE url LIKE '%/old/base/dir/%';
Be careful with these queries!! You will need to change it so /old/base/dir/ and /new/dir/ make sense for your particular site. You should absolutely positively back up your database before running these queries otherwise you may completely and utterly destroy your site without any way to get it back!!!
It is actually possible to move the code from a ROOT/concrete5.5.2.1 directory back to the root without running the queries above. I simply moved the code up a directory and everything worked.