Magento 中仍然使用数据库布局更新吗？

发布于 2024-10-11 09:33:44 字数 1077 浏览 3 评论 0原文

在 Magento 布局系统的深处，有以下代码用于将包布局 xml 文件转换为创建块所需的特定 XML，从而创建页面

public function merge($handle)
{
    $packageUpdatesStatus = $this->fetchPackageLayoutUpdates($handle);
    if (Mage::app()->isInstalled()) {
        $this->fetchDbLayoutUpdates($handle);
    }
}

第二种方法 fetchDbLayoutUpdates 尝试加载使用 SQL 查询从数据库进行额外的 XML 更新，如下所示

SELECT `update`.`xml` FROM `core_layout_update` AS `update`
INNER JOIN `core_layout_link` AS `link` 
    ON link.layout_update_id=update.layout_update_id 
WHERE (link.store_id IN (0, '1')) 
    AND (link.area='frontend') 
    AND (link.package='default') 
    AND (link.theme='default') 
    AND (update.handle = 'default') 
ORDER BY `update`.`sort_order` ASC'

在默认安装中，core_layout_update 和 core_layout_link 表都是空的。

所以，我一直认为这是我使用 Magento 之前的遗留功能。是否在任何地方使用此功能

有谁知道
Magento核心代码库
任何众所周知/著名的扩展
你！< /p>

我可以理解为什么该功能被保留下来（遗留问题以及其他问题），但我很好奇它是否已被正式放弃，或者是否只是大大未得到充分利用。

原文

Deep in the Magento Layout system, there's the following code that's used to turn your package layout xml files into the specific XML needed to create your Blocks, and therefore create your pages

public function merge($handle)
{
    $packageUpdatesStatus = $this->fetchPackageLayoutUpdates($handle);
    if (Mage::app()->isInstalled()) {
        $this->fetchDbLayoutUpdates($handle);
    }
}

The second method there fetchDbLayoutUpdates tries to load additional XML Updates from the database with SQL queries something like this

SELECT `update`.`xml` FROM `core_layout_update` AS `update`
INNER JOIN `core_layout_link` AS `link` 
    ON link.layout_update_id=update.layout_update_id 
WHERE (link.store_id IN (0, '1')) 
    AND (link.area='frontend') 
    AND (link.package='default') 
    AND (link.theme='default') 
    AND (update.handle = 'default') 
ORDER BY `update`.`sort_order` ASC'

Both the core_layout_update and core_layout_link tables are empty in a default installation.

So, I've always assumed this is a legacy feature that predates my time with Magento. Does anyone know if this feature is used anywhere by

The Magento Core Codebase
Any well known/prominent Extensions
You!

I can see why the feature's been left in place (legacy concerns and what not), but I'm curious if it's something that's been officially-ish abandoned, or if it's just vastly under utilized.

分享到QQ

分享到微博