Download the PHP package zero1/layout-xml-plus without Composer

On this page you can find all versions of the php package zero1/layout-xml-plus. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of zero1/layout-xml-plus

Informations about the package layout-xml-plus

Zero1_LayoutXmlPlus

This module is aimed at reducing the need to override templates for blocks. For example, changing a single class for a button shouldn't require you to override the template. However for significant dom structure changes we would still recommend overriding the template.

Installation

Actions

The functionality has been split into "actions" different actions that can be taken on the output of a blocks html before it is passed to a user.

Common Parameters

AttributeValueReplace

id: attribute_value_replace Replace a value within an attributes value, a good example would be replacing a class with another class.

example catalog_category_view.xml

AttributeValueSet

id: attribute_value_set

Completely override the value of an attribute

example catalog_category_view.xml

AttributeValueAppend

id: attribute_value_append

Add an item to an attributes list of values (e.g add a class)

example catalog_product_view.xml

example catalog_product_view.xml

AttributeValueRemove

id: attribute_value_remove Remove a value from an attributes list of values

example catalog_product_view.xml

AttributeRemove

id: attribute_remove

Completely remove an attribute

example catalog_product_view.xml

ChildHtml

id: child_html

Insert a childs html into a specific part of the output. This requires you to add the child block in layout xml.

Valid targets

example default.xml

Remove

id: remove

Remove an element from the dom.

example default.xml

XPath Cheat Sheet

Other Recommendations

When it comes to stopping blocks outputting content, using layout xml can often remove the requirement to change the template. N.B when referencing a block you must use it's name and not it's alias Example dont do

do

CLI Commands

Module Status

Disabling the module is a quick way to debug if layout-xml is responsible for a change you are seeing.

Logging

Enabling logging will cause the module to log out all changes to output, as well as fails to change output (i.e when the xpath doesn't match anything in the content)

When enabled logging will output all blocks that have any layout-xml-plus directives into var/layout-xml-plus/logging/* Each block will be stored as:

Collection / Evaluation

The module also includes as way to find template overides that can be replaced with layout xml directives.

  1. Magento setup ``bash php bin/magento deploy:mode:set developer \ && php bin/magento cache:enable \ && php bin/magento cache:flush bash php bin/magento dev:layout-xml-plus:collect --with-theme --clear bash php bin/magento dev:layout-xml-plus:collect --without-theme --clear \ && php bin/magento cache:flush bash find ./app/design/frontend/ -type f -name '*.phtml' -exec rm "{}" \; bash php bin/magento dev:layout-xml-plus:collect --without-theme --clear \ && php bin/magento cache:flush

    1 exception(s): Exception #0 (Magento\Framework\Exception\ValidatorException): Invalid template file: 'Magento_Cms::static-blocks/pagetop.phtml' in module: '' block's name: 'pagetop'

    git checkout app/design/frontend/VENDOR/THEME/Magento_Cms/templates/static-blocks/pagetop.phtml bash php bin/magento dev:layout-xml-plus:collect --disable bash git checkout app/design/frontend bash php bin/magento dev:layout-xml-plus:analyse

var xpathExists = (xpath) => !!document.evaluate(xpath, document, null, XPathResult.FIRST_ORDERED_NODE_TYPE, null).singleNodeValue;

pathExists('//header/div//div[@class="flex gap-4 items-center"]/div[@class="relative hidden lg:inline-block mr-4"][1]/a')


Before moving this into your layout file be sure to prepend the XPath value with '/root'

## Roadmap
- [x] make module disable-able
- [x] make log flag setable/env'able
- [x] record blocks and output, with/without theme
- [ ] generate analysis report.
- [ ] make play nice with hyva when prod mode (ccs classes)
- [ ] unit tests
- [ ] coding standards
- [ ] initial release

**Potentials**
- [ ] profiler with autowarning when block takes excessive time?

SDS testing

https://www-sdslondon-co-uk-21843.54.mdoq.dev/
https://www-sdslondon-co-uk-21843.54.mdoq.dev/british-made-bronze-door-knobs.html
https://www-sdslondon-co-uk-21843.54.mdoq.dev/bronze-beehive-morticerim-door-knob-50-mm.html

enable with theme
php bin/magento deploy:mode:set developer \
    && php bin/magento cache:enable \
    && php bin/magento cache:flush \
    && git checkout app/design/frontend \
    && php bin/magento dev:layout-xml-plus:collect --with-theme --clear

enabled without theme
php bin/magento deploy:mode:set developer \
    && php bin/magento cache:enable \
    && php bin/magento cache:flush \
    && php bin/magento dev:layout-xml-plus:collect --without-theme --clear  \
    && find ./app/design/frontend/ -type f -name '*.phtml' -exec rm "{}" \; \
    && git checkout app/design/frontend/z1/sds_hyva/Magento_Cms/templates/static-blocks/pagetop.phtml \
    && git checkout app/design/frontend/z1/sds_hyva/Magento_Theme/templates/html/header/menu/C-desktop.phtml \
    && git checkout app/design/frontend/z1/sds_hyva/Magento_Theme/templates/html/header/menu/C-desktop-item.phtml \
    && git checkout app/design/frontend/z1/sds_hyva/Magento_Cms/templates/static-blocks/usps.phtml \
    && git checkout app/design/frontend/z1/sds_hyva/Magento_Theme/templates/html/tradewidget.phtml \
    && git checkout app/design/frontend/z1/sds_hyva/Klaviyo_Reclaim/templates/product/viewed_hyva.phtml \
    && git checkout app/design/frontend/z1/sds_hyva/Hyva_Checkout/templates/section/custom-summary-header.phtml

disable
php bin/magento deploy:mode:set developer \
    && php bin/magento cache:enable \
    && php bin/magento cache:flush \
    && git checkout app/design/frontend \
    && php bin/magento dev:layout-xml-plus:collect --disable

Analyze
php bin/magento dev:layout-xml-plus:analyse

All versions of layout-xml-plus with dependencies

PHP Build Version
Package Version
Requires magento/framework Version ^100.1|^101.0|^102.0|^103.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package zero1/layout-xml-plus contains the following files

Loading the files please wait ....