简体   繁体   English

Magento中的/ app / code / core / Mage / Catalog / Model / Resource文件夹?

[英]/app/code/core/Mage/Catalog/Model/Resource folders in Magento?

I'm trying to fix some problems with a Magento site, but I'm running into lots of problems . 我正在尝试修复Magento网站的一些问题,但是我遇到了很多问题。 . .

I've located a folder in Magento with the path: 我在Magento中找到了以下路径的文件夹:

"/app/code/core/Mage/Catalog/Model/Resource" “ / app / code / core / Mage / Catalog / Model / Resource”

In the default install of Magento it has a file structure like so: 在Magento的默认安装中,它具有如下文件结构:

 - category
 - collection
 - eav
 - helper
 - layer
 - product
 - more php files

However the dump of the current site I've received didn't have any of those folders or files except the "Eav" folder, the site was throwing errors so I added the other folders in (which seemed to fix it) unfortunately I think this may have caused other problems. 但是,我收到的当前站点的转储中除了“ Eav”文件夹外没有任何其他文件夹或文件,该站点抛出错误,因此很遗憾,我在其中添加了其他文件夹(似乎可以解决该问题)这可能引起了其他问题。

My question is, are all of those folders absolutely necessary for Magento to work? 我的问题是,所有这些文件夹对于Magento来说都是绝对必要的吗? Or are there situations in which you might remove all of those folder/files except the "Eav" folder? 或者在某些情况下,您可能会删除“ Eav”文件夹以外的所有这些文件夹/文件?

There was a general ORM rework which occurred in CE1.6. CE1.6中进行了一般的ORM返工。 Along with the introduction of DB-specific helpers and the completion of the Varien DDL components, the resource models were generally moved to a standard location for all modules. 随着特定于数据库的帮助器的引入以及Varien DDL组件的完成,通常将资源模型移至所有模块的标准位置。 In the case of Mage_Catalog the resource models were moved from Mage/Catalog/Resource/Eav/Mysql4/ to Mage/Catalog/Model/Resource/ and the resource model class group was changed from catalog_resource_eav_mysql4 to catalog_resource . 在Mage_Catalog的情况下,资源模型从Mage / Catalog / Resource / Eav / Mysql4 /移至Mage / Catalog / Model / Resource / ,资源模型类组从catalog_resource_eav_mysql4更改为catalog_resource

As noted in comments above, it is best to compare apples to apples, meaning to verify the version number in the Mage class and comparing the core files to a known-good copy. 如上面的注释所述,最好将一个苹果与另一个苹果进行比较,这意味着要验证Mage类中的版本号,并将核心文件与一个已知良好的副本进行比较。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 如何覆盖magento核心模型(直接在app / code / core / Mage / Core / Model目录下的模型类文件) - How to override magento core model (model class file direct under app/code/core/Mage/Core/Model directory) 当预期使用Mage_Catalog_Model_Resource_Eav_Mysql4_Product_Collection时,使用Mage_Catalog_Model_Resource_Product_Collection对象的Magento 1.9.0.1 - Magento 1.9.0.1 using Mage_Catalog_Model_Resource_Product_Collection object when Mage_Catalog_Model_Resource_Eav_Mysql4_Product_Collection is expected Magento-从Mage_Catalog_Model_Resource_Product_Collection对象访问值 - Magento - Accessing values from an Mage_Catalog_Model_Resource_Product_Collection object 找不到Mage_Core_Model_App'magento XAMPP - Mage_Core_Model_App' not found magento XAMPP Magento upsell_products引发错误“必须是Mage_Catalog_Model_Resource_Eav_Mysql4_Product_Collection的实例” - Magento upsell_products raises error “must be an instance of Mage_Catalog_Model_Resource_Eav_Mysql4_Product_Collection” 使用Mage_Catalog_Model_Resource_Product_Collection进行分页 - paging with Mage_Catalog_Model_Resource_Product_Collection Magento法师:: helper('目录/类别') - Magento Mage::helper('catalog/category') Magento - 致命错误:在816行的app / code / core / Mage / Eav / Model / Entity / Abstract.php中的非对象上调用成员函数getBackend() - Magento - Fatal error: Call to a member function getBackend() on a non-object in app/code/core/Mage/Eav/Model/Entity/Abstract.php on line 816 致命错误:找不到使用'Zend库'的类'Zend_Pdf_Color_RGB'app / code / core / Mage / Sales / Model / Order / Pdf / Shipment.php magento - Fatal error: Class 'Zend_Pdf_Color_RGB' not found app/code/core/Mage/Sales/Model/Order/Pdf/Shipment.php magento using zend library Magento - Mage注册表项“_resource_helper / core”已经存在 - Magento - Mage registry key “_resource_helper/core” already exists
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM