We have developed URL patterns to easily adjust the extension’s logic to the specific category or set of pages. We use them in many extensions, such as AMP, Popup Login, Cookie Consent, and others to enable or disable some functionality only on specific pages.<\/p>\n\n\n\n
Please note that this documentation applies to Magento 2 Base extension v2.9.0 and later.<\/p>\n\n\n\n
Important information:<\/p>\n\n\n\n
Only the URL path is taken into account when checking the pattern. For example, the following URL Note for developers:<\/p>\n\n\n\n You can use Regular Expressions instead of the provided URL patterns by adding the <\/p>\n<\/div><\/div>\n\n\n\n Use the following special characters in URL patterns:<\/p>\n\n\n\n If your patterns don’t start with Example 1.<\/strong><\/p>\n\n\n\n The However, it does not match the following URLs: <\/p>\n\n\n\n Example 2.<\/strong><\/p>\n\n\n\n The https:\/\/example.com\/category\/product.html?v=1#reviews<\/code> will be truncated to \/category\/product.html<\/code>.<\/p>\n<\/div><\/div>\n\n\n\nregex::<\/code> prefix to the pattern. For example, regex::#\\\/category\\\/.*?#<\/code> or regex::~[\/]category[\/]?~<\/code>.<\/p>\n\n\n\nURL Pattern Specification<\/h2>\n\n\n\n
*<\/code> – matches 0 or more of the preceding characters (equivalent to the .*<\/code> regular expression)<\/li>+<\/code> – matches 1 or more of the preceding characters (equivalent to the .+<\/code> regular expression)<\/li>\\<\/code> – makes the character non-special, for example, \\+<\/code> will be considered as +<\/code>.<\/li><\/ul>\n\n\n\n\/<\/code>, *<\/code>, or +<\/code><\/em> characters, a slash (\/<\/code>) will be automatically added to the beginning to reduce the number of mistakes. Therefore, \/category\/*<\/code> and category\/*<\/code> patterns are considered the same. <\/p>\n\n\n\nURL Pattern Examples<\/h2>\n\n\n\n
\/category\/*<\/code> pattern matches the following URLs:<\/p>\n\n\n\n\/category\/<\/code>)<\/li><\/ul>\n\n\n\n\/category\/+<\/code> pattern matches the following URL:<\/p>\n\n\n\n