65

Symptom: I changed Base Urls and now my website is inaccessible or I moved everything to a new server, didn't change the base_url and my website is inaccessible. How to change or restore base_url settings with phpMyAdmin Instructions are for a simple "one store" website where the "default store view" is set to inherit its setup from the "default config". ...


31

You should try using the image resize command to pre-generate all necessary resizes. php bin/magento catalog:image:resize This command gets all the images sizes that have been defined in the theme XML and pregenerates the images in their correct folders. You can also check the command documentation for more information http://devdocs.magento.com/guides/v2....


17

Method 1: Import Images from the Local Server On the Magento server, upload the image files to the pub/media/import folder. This is the default folder for importing product images. [magento installation folder]/pub/media/import You can use a different folder on the Magento server, as long as the path to the folder is specified during the ...


15

In Magento2, there is also a way to do this directly via Magento using below commands rather than having to go through SQL which i find a bit quicker. Within Magento’s root directory run below commands: Set Unsecure URL bin/magento setup:store-config:set --base-url="http://www.magento2.com/" Set Secure URL bin/magento setup:store-config:set --base-url-...


15

Here are some Delta migration General understanding Data Migration Tool migrates data created only by Magento's own modules (eg. Orders, Customers Profile) and is not responsible for the code or extensions made by third-party developers. If these extensions created data in the frontend database and the merchant wants to have this data in Magento 2, then ...


14

There is a quick reference: Basically, we need to change the connection config in app/etc/env.php, the url config in core_config_data and set the permission your source files. --After importing the backup database, we need to change web/unsecure/base_url and web/secure/base_url paths in core_config_data table. We can check: SELECT * FROM core_config_data ...


12

I had this exact same error when creating a custom module. Not sure if this will solve it for your case, but maybe it will help to illuminate what's going on. In my custom layout xml, I had a uiComponent that was not yet defined. File: MyCompany/MyModule/view/adminhtml/layout/mycompany_mymodule_index_index.xml <uiComponent name="my_custom_form" />...


11

Not sure if this is too late to add, but when I had this It appeared to be caused by some entity ids that needed to be set to 0. This script worked for me: SET FOREIGN_KEY_CHECKS=0; UPDATE `store` SET store_id = 0 WHERE code='admin'; UPDATE `store_group` SET group_id = 0 WHERE name='Default'; UPDATE `store_website` SET website_id = 0 WHERE code='admin'; ...


11

Data Migration from Magento 1 to Magento 2 is a bit technical if you are a newbie or a new Magento learner. You can start the migration process by installing the Magento 2 Data Migration Tool via composer. To install this tool, make sure that the version of Magento 2 and Data Migration Tool matches exactly. For example, if you are using Magento v2.1.2, you ...


10

I think the resources is relating to the actual database connection. M1 in the past had something like this: <resources> <backup_setup> <setup> <module>Mage_Backup</module> </setup> <connection> <use>core_setup</use> ...


10

Please try below changes in config.xml file at location magento/data-migration-tool/etc/opensource-to-commerce/1.9.3.3. I have faced same issue and below changes fixed my issue. <bulk_size>100</bulk_size> <direct_document_copy>1</direct_document_copy>


9

404 issues are quite common when migrating Magento installations between servers. As per this post on SO please see the following answer Magento Admin 404 You need to go your server directly and do this via SSH/ FTP You have to delete the following file: app/etc/use_cache.ser If you get an error after that like: Notice: Undefined index: 0 in /srv/www/...


8

Before trying anything, clear the cache. That might not help, but do it anyway. The error is cause by this: $this->_frontend = Mage::getModel($this->getFrontendModel()) ->setAttribute($this); this means Mage::getModel($this->getFrontendModel()) returns null (or false). This can be caused by an attribute that has the field ...


8

Magento 2 uses the same folder structure for product images. Assuming your CSV contains the product image attribute, you can simply copy /media/catalog/ to /pub/media/catalog/


7

In addition to Raphael: I Debugged this code with altering the exception constructor for debug purposes (either by xdebug or old dumps). Alter the construct of the exception for now (the file is \lib\internal\Magento\Framework\Exception\NoSuchEntityException.php) $trace = debug_backtrace(); var_dump($trace[1]['class'] . '::' . $trace[1]['function'] . '('.$...


7

Second error are generate because of above all three field withing cms_page are not a default field, All of three field are generated using custom module. So You have to remove custom module field using below way using map.xml file, <source> <field_rules> <ignore> <field>cms_page....


6

Check any whitespace or new line character on core_config_data table entries for base_url fields (web/unsecure/base_url, web/secure/base_url, web/unsecure/base_url, web/secure/base_url). I encountered this once and that's how I've resolved it. Also another error that you may get because of this mistake is Warning: Header may not contain more than a ...


6

You can't really upgrade from 1.9 to 2.0. What you can do is migrate the installation from 1.9 to 2.0 You can find every detail you need in the official documentation here: http://devdocs.magento.com/guides/v2.0/migration/bk-migration-guide.html Here's a workflow diagram that will give you a good idea of what to do:


6

Download "Regenerate Url rewrites" extension from here : https://github.com/olegkoval/magento2-regenerate_url_rewrites Follow the below steps MANUAL INSTALLATION Extract files from an archive Create a app/code/OlegKoval/RegenerateUrlRewrites folder in magento root directory, and copy the extracted files from Step1 folder and upload it to directory app/...


5

install php7 install and enable opcache (make opcache.enable = On, opcache.max_accelerated_files = 65535) disable xdebug (comment zend_extension). php -i|grep xdebug should not found xdebug settings run bin/magento setup:static-content:deploy run bin/magento setup:di:compile enable production mode in apache/nginx run bin/magento cache:flush (and verify ...


5

Default Magento 2 Migration tool. Guide Link : http://devdocs.magento.com/guides/v2.0/migration/bk-migration-guide.html Install tool for a migration : https://github.com/magento/data-migration-tool/ OR UberTheme migration tool. This is easier way to migrate Magento 1.9.X to Magento 2.X.X Guide Link : https://www.ubertheme.com/magento-news/magento-2-...


4

I also had to deal with this kind of issue once. Possible ways of migrating the attributes and attribute-sets to a fresh (!!) installation: Copying tables to the new database As the OP already already mentioned, copying the eav_* and catalog_eav_attribute is a possible option. Creating setup scripts to execute on the new installation This is the best-...


4

Do you know which parts of the database are hacked? If the attributes are fine, maybe you could just run export and import them via SQL. Your products could be copied using the Magento Dataflow Profiles and so are the customers. Of course, all of this depends on which parts of the database are hacked and the amount of attributes, products and customers that ...


4

It is resolved by this query : SET FOREIGN_KEY_CHECKS=0; UPDATE `store` SET store_id = 0 WHERE code='admin'; UPDATE `store_group` SET group_id = 0 WHERE name='Default'; UPDATE `store_website` SET website_id = 0 WHERE code='admin'; UPDATE `customer_group` SET customer_group_id = 0 WHERE customer_group_code='NOT LOGGED IN'; SET FOREIGN_KEY_CHECKS=1;


4

In order to run bin/magento migrate:delta step you first need to run the bin/magento migrate:data step because it is in this step where the Data Migration Tool creates triggers in the source database. Those triggers will be used to pull only the changes made in Magento 1 since the last time you migrated data. For more information have a look to the ...


4

All media files (images for products, categories, the WYSIWYG editor, and so on) should be copied manually from your Magento 1 install media folder to your Magento 2 install pub/media folder. However, do not copy the .htaccess files located in the Magento 1 media folder. Magento 2 has its own .htaccess that should be preserved. Reference: http://devdocs....


4

The Ratings Step does not transfer any data but assign 'is_active' = 1 for records in 'rating' table which are related in 'rating_store' table. So you can skip this step from execution and do it manually in your Magento 2 DB after migration. Comment following code: vendor/magento/data-migration-tool/etc/source-to-destination/1.x.x.x/config.xml <step ...


4

I got such an error after migration and one of the attributes had a custom frontend_input. I see in your stack trace that the problem is with the created_by field. Maybe you should set the frontend_input for that field to text or something similar.


4

I have to fetch the same issue so Please, a check-In Database View is created or not If a View is not there so create view after indexing and flush... may your issue resolve... Happy Coding...


4

Please add the code your map.xml file hope work this code <destination> <field_rules> <ignore> <field>quote.shipping_delivery_date</field> </ignore> </field_rules> </destination>


Only top voted, non community-wiki answers of a minimum length are eligible