The following procedure describes the basic needs for moving your magento-shop to another server. There might be additional things to consider (changing domains, DNS, PHP-Configuration, tools & programms on your server) which need to take care of on your own.
1. Backup files in your Magento directory on your old server:
You might empty your var/cache, ...
Follow this i think it will help you to solve your issue :-
now add the following to the magento-logrotate.conf file:
execute your configuration now:
logrotate -f /etc/logrotate.d/magento-...
The Magento requirements check is a decent script to run to confirm your server meets the requirements (you need to change the opening PHP tag to <?php if your server doesn't support short open tags), and if you open it is has a list of PHP extensions needed, which it lists as:
So I'd say you ...
The reason for this error is that store_id and website_id for admin should be set to 0 (zero). But, when you import database to new server, somehow these values are not set to 0.
Open PhpMyAdmin and run the following query in your database:-
UPDATE `core_store` SET store_id = 0 WHERE code='admin';
UPDATE `core_store_group` SET ...
Please check and verify below steps:
Check if your server is compatible with Magento. Download file from this link Magento Server Compatibility check and follow the instructions given.
Check for the .htaccess in each folder and in root too. Magento has .htaccess in almost all folders. Verify it for media folder in case the problem is with image
Execute the ...
The official system requirements (or rather: recommendations) are:
Increase the PHP memory limit to at least 768MB for normal operation or 2GB for testing.
Source: Recommendations for CentOS and Ubuntu
I would only increase it to a higher value if you encounter problems where the memory limit is hit. Then debug and fix these problems, and set the memory ...
Seems there's no curl installed on your server. Check your phpinfo() for curl.
If not present, you or your provider can enable it in the PHP config:
/etc/php5/apache2/php.ini (or similar)
You don't need to have multiple directories for multiple domains if you are using single magento instance to fulfill your requirements.
Step 1: Point all domains to Magento root directory, i.e. same document root in the webserver (Apache or Nginx) configuration.
Step 2: Configure domain names as base URLs for each website in System Configuration in ...
Since Why does Magento POST to its own app/etc/local.xml? might not have been clear enough, I'll add this as an answer:
Actually these messages are a good thing, Magento would warn you in the admin panel if it could access the file via HTTP. If you see this log message, everything is fine. Magento tries to access app/etc/local.xml via HTTP, which fails, so ...
There is a security risk to this. First start with...
Yes, this is possible
As your question does not specify anything, I'll list some things that are necessary to achieve this:
You'll need two document roots, two directories on the server, one to store the M1 code and one to store M2 code. I think it would even be possible for one of the applications to ...
1) You need to get the sql dump from the old database and import the sql file in the new database.
2) You need to make change in the local.xml. To do so goto app/etc/local.xml
Enter the username, password and dbname of the new database you created.
NOTE : Normally host name as localhost works. But for some servers you need to get the host name from the ...
In .htaccess on your server config file.
RewriteRule "^(.*/)?\.git/" - [F,L]
RedirectMatch 404 /\.git
Place this both method in .htaccess file.
It hides any file or directory whose name begins with .git Like .git directory or .gitignore file by returning a 404.
For Magento CMS and the like (that aren't cleaning old sessions up), I just use cron jobs based on php.ini settings.
The system cron.d setup for php5 does not clean Magento ./var/session (or anything besides default session folder (/var/lib/php5 for Ubuntu and /var/lib/php5/sessions or /tmp/ for most others Linux dists).
But you ...
moving files and database
I assume these two steps are obvious:
copy all of your local files to production server
dump your magento local db and import it into your production server db
editing in production server
now on your production server you need to follow these two steps:
edit app/etc/local.xml file and change database info
in production db,in ...
if you want to boost your magento2 performance it's mainly about caching.
First, be sure you are in production mode for performance tests
Next step would be to use a cahe storage server instead of file caching. For xample a redis server
Setting up a test environment:
Copy and modify local.xml
Maybe you want to copy the media folder.
The point is, you want all your files in VCS, you want branches for every instance (test, stage, live, ci, ...) so you have full control over what you deploy and know what your CI or customer is testing.
How not to
Please check if your FTP and SSH user are in the www-data group.
Your files and folders belong to the www-data user and group:
-rw-rw-r-- 1 www-data www-data 2642 Nov 26 2013 index.php
drwxr-xr-x 13 www-data www-data 4096 Jun 18 07:29 media
Your FTP error message (I'm not able to override any file) makes me believe your FTP user is not in the ...
At your discretion, you should either assign all web server files to the www-data user and group, or just the group. It is often convenient, and still secure, to make the owner of the files yourself so you can more easily edit them, especially if you wanted to manage such files via a repo.
If you decided to make all web server files owned and group-owned by ...
I've run into a couple of things myself that could cause this
make sure the .htaccess is in place in the root directory
make sure mod_rewrite is enabled on the new server
check the Base urls in the core_config_data table
make sure caching is off or refreshed
check file owner and permissions of the files
Install Wordpress in a different location, ideally outside of the Magento root and add this rule to the .htaccess file of Magento:
RewriteRule ^/de/blog/(.*) /path/to/wordpress/$1 [QSA]
This way the server redirects requests like /de/blog/anything internally to /path/to/wordpress/anything (Note that the former is a URL, the latter a path on the server)
Traditionally, KeepAlive was a good thing because it significantly reduces the TCP overhead of an overall page load, where many requests (like all the images, css, js) are being served from one server. If your page has 85 assets, that's 85 extra three-way TCP handshakes, and the latency adds up. Many years ago with slower Internet ...
To share absolute numbers with you, hosting providers will ask you few questions in order to determine the perfect server configuration for a Magento store. These questions include:
How will many unique visitors visit the stores daily?
How many products, catalogs, the number of categories, attributes,
attributes sets are there? What would be the future ...
you need to change the php configure script to include --with-freetype-dir=/usr/lib64/ where /usr/lib64 contains the libfreetype.so file.
My final configuration so far looks like:
./configure --with-apxs2=/usr/bin/apxs --enable-bcmath --with-curl --with-gd \
--with-jpeg-dir=/usr/lib64/ --with-png-dir=/usr/lib64/ --with-freetype-dir=/usr/lib64/ \
I found fix for development environment, because I use Mac OS and the apache php doesn't support these fonts and it's a lot of work to get it working and not mess up my system.
open vendor/zendframework/zend-captcha/src/Image.php and add return in the constructor after the parent is called like this
* @param array|\Traversable $...
It's a good idea to look at the varnishlog output. You pasted client-side varnishlog output, but the reason why fetches fail is reported in the backend-side varnishlog output.
The part where the backend request happens will have a FetchError tag, that will tell you what was going on.
Looking for fetch errors
Here's an example where I reached the backend's ...