A topic which I would like to address today once, since it has just occupied us hard: Magento Catalog price rules and. Cart Price Rules and catalog price rules overlap partially but also have some differences and we'll get a very huge later. Both price control modes give the store owner the opportunity (special) Customers or customer groups different prices…
Today we had the import of a Magento database to a new database, the error message SQL command: — — Constraints der Tabelle 'catalog_eav_attribute’ — ALTER TABLE ‘catalog_eav_attribute’ ADD CONSTRAINT ‘FK_CATALOG_EAV_ATTRIBUTE_ID’ FOREIGN KEY ( ‘attribute_id’ ) REFERENCES ‘eav_attribute’ ( ‘attribute_id’ ) ON DELETE CASCADE ON UPDATE CASCADE ; MySQL MANDATORY: #1452 – Cannot add or update a child…
Very briefly, since the question was just: When are produced in the Magento-line translations, these core_translate stored directly in the database in the table. Here can then be adjusted (or probably (!) also deleted, to then translate the translate.csv)
We have just created a new template is placed on our multi-store, which has a great installer…a very ambitious Installer. This has all the unasked “Home” CMS pages and overwrite the entire content was lost. Unfortunately, neither the manual nor anywhere else was a reference to this “Triviality”. So our total 5 Home CMS pages lost…
It comes every now and again before, that a domain transfer, image_link a change or similar. in many places such as change in the transaction must email. This situation we had just, that the logo, which will be sent emails with the transaction was in another place and it is now over 20 had to be changed emails. Of course,…
If you want to make a database copy, order to secure and then bring in a copy shop, This can be done quickly with PHPMyAdmin. For this purpose the concerned DB and select the tab “Export” click. Now it is mostly accurate and standard, select all tables. So that nothing be changed to the default settings…
There are one or the other attribute, which can be changed not so easy on the backend, how it would perhaps like to. An example is the attribute weight / Weight. This throws out the above error message, if you try to change, whether the name (Description / Options to manage), the visibility, etc.. Therefor…
If an old database will be transferred to a new Magento System (what does not always and not without its problems), can be attempted the following way: It is created in phpMyAdmin, a DB backup of the corresponding DB. >BEFORE< it is now played in the new database, should all put the following lines to the beginning of the downloaded DB…
