xPath error in mails #4737

lgt · 2016-05-27T10:03:34Z

I'm using magento 2.0.7 and I get the following error on order mail confirmation.Swicthing from default to production the error is still there. This seems to be related to the included css in header.
If I remove
{{inlinecss file="css/email-inline.css"}} than I do not get the error, but still need some styling!
How to suppress ?

CSS Inline Error: Warning: DOMXPath::query(): Invalid expression in .../vendor/pelago/emogrifier/Classes/Emogrifier.php on line 269

The text was updated successfully, but these errors were encountered:

designhunger · 2016-05-30T11:01:19Z

I get the same error, but not exclusive in the order confirmation, but on all magento mails (magento 2.0.6)

eug123 · 2016-05-31T16:21:17Z

Hi @lgt
What theme is applied? Have you deployed static content before switching to production?

juliansthl · 2016-06-02T20:16:01Z

We have the same issue.
Our theme is based on the blank theme. The issue even appears if we don't override the Magento_Email template files.

We have deployed static content.

eug123 · 2016-06-03T14:06:37Z

Hi,

It seems that the error happens when converting styles from email-inline.css to the inline style attribute with Emogrifier tool.

Please try to update this package changing version to 1.0.0 in composer.json ("pelago/emogrifier": "1.0.0") and running composer update.

Could you also check if the issue appears on your environment when one of the native themes is applied?

juliansthl · 2016-06-27T08:02:20Z

Hi,

sorry for my late reply.
The issue was that email-inline.less was loading less files from our theme's source and the Emogrifier tool was having problems with a few style declarations.

Thanks,
Julian

nickmarx12345678 · 2016-07-21T18:14:20Z

@eug123 I'm also having this issue, but I don't see emogrifier as a dependency in our composer.json

any other suggestios?

nickmarx12345678 · 2016-07-21T18:15:46Z

@eug123 update, it may be a sub-dependency. In our composer.lock, emogrifier as version 0.1.1

how would you recommend proceeding to get that version bumped to 1.0.0?

AntonEvers · 2016-08-11T13:24:11Z

If you let Magento minify css ul > li becomes ul>li. Emogrify turns this into xpath //ul>li instead of //ul/li so the html nodes are never matched.

This is fixed in MyIntervals/emogrifier@81947fd which is scheduled for version 1.1.0 of pelago/emogrifier. Will you upgrade to v1.1.0 when it's out?

AntonEvers · 2016-08-11T13:35:58Z

@nickmarx12345678 put this in the require-dev part of composer.json:

"pelago/emogrifier": "1.0.0 as 0.1.1",

Or if you prefer the development version:

"pelago/emogrifier": "dev-master as 0.1.1",

DevManav · 2016-08-24T12:40:24Z

Hi @lgt,
I'm also having this issue in all mail. Is there any solution for this issue? Please let me know if any one has a solution.

adamraya · 2016-08-24T14:40:06Z

I had this problem too, seems like emogrifier had trouble with a multiline comment /* code */ inside a media query in one of the .less files of our theme based on the blank theme.

oliverklee · 2016-08-24T15:01:58Z

@adamraya Could you please file a ticket at the Emogrifier issues list with the offending HTML and CSS? Then we can have a look at it. Thanks! ❤️

veloraven · 2016-08-26T15:31:34Z

@antonkril please have a look at this.

DevManav · 2016-08-31T10:29:49Z

@antonkril I had this problem in all mails same as @lgt. This error is comes when my custom created theme is applied , if i select default theme blank or luma email templates working fine. Is there any solution?

itelebar · 2016-09-05T11:44:34Z

Hi everyone, we had this issue on one site and also noticed that it is not happening when using Luma so conclusion was it must be something we have included into our theme.

I our case Font Awesome we included was root of an issue.

In file font-awesome/_animated.less there are selectors that are breaking the flow. In this case those were keyframes definitions for start and end of animation.

As we don't need this solution was simply disabling/commenting out font-awesome/_animated.less in file font-awesome/_font-awesome.less.

If you check official comment in vendor/magento/theme-frontend-blank/web/css/source/_email-base.less you will find that it is documented what kind of selectors are allowed. This might get updated in future but it is up to Emogrifier. Until all selectors are allowed we as developers should be aware of everything that is getting included and might possibly cause an error.

My advice is to use xDebug and keep an eye/breakpoint on vendor/pelago/emogrifier/Classes/Emogrifier.php (line 269) as this is place where exception is thrown. This way you can easily find out which part of CSS is causing an issue.

Hope this helps anyone!

mrkhoa99 · 2016-09-07T06:02:08Z

Hi all,
This issue also occurs because the email style will import some less files. And then, we add some unsupported selectors to these files. Read more: http://magento.stackexchange.com/a/132691/33057

DevManav · 2016-09-13T06:04:19Z

Hi all,
I solved this problem in my site by below step:-
step-1:- copy email less and css file from blank theme under below path
app/design/frontend/Your_vendor/Your_theme_neme/web/css
app/design/frontend/Your_vendor/Your_theme_neme/web/css/source
step-2:- After that run command setup:static-content:deploy Your_language.

step-3:- Clear below directory
var/cache
var/generation
var/view_preprocessed
That's it Now check your email error is resolved and if you want to change your email design ,your email css is located in
app/design/frontend/Your_vendor/Your_theme_neme/web/css/email-inline.css

Bartlomiejsz · 2016-10-19T08:21:43Z

@veloraven @antonkril are there any updates? Do you know when pelago/emogrifier will be up to date with latest release?

magento-engcom-team · 2018-04-14T08:29:08Z

Hi,
Looks like the issue has been fixed by updating to Emogrifier 2.0.0.
Thanks to everyone for collaboration!

nikidexa · 2018-04-19T10:20:32Z

Hi, I have the same problem, so it looks like been fixed by udpdating Emogrifier 2.0.0
How can I update this file? sorry fro this question, but I'm learning now to use magento 2
thanks

Puru2016 · 2018-05-16T05:30:12Z

I am facing same issue in Magento ver 2.2.3,

My composer ver is:-
vendor\magento\magento2-base\composer.json => "pelago/emogrifier": "1.2.0"

Please suggest the solution for this

oliverklee · 2018-05-16T07:49:46Z

@Puru2016 Does an upgrade to emogrifier ^2.0.0 solve the problem for you?

Puru2016 · 2018-05-19T05:36:43Z

I have changed "pelago/emogrifier": "1.2.0" to "pelago/emogrifier": "2.0.0", and update the composer and then recompile the store , still same issue.

mattkrupnik · 2018-05-21T08:16:01Z

Magento 2.2.3
Just add this to the composer require "pelago/emogrifier": "2.0.0 as 1.2.0" then run composer update pelago/emogifier and it solved problem.

nikidexa · 2018-05-21T08:43:03Z

Magento 2.2.3
Just add this to the composer require "pelago/emogrifier": "2.0.0 as 1.2.0" then run composer update pelago/emogifier and it solved problem.

Im still using Magento 2.2.2... is it the same?

mattkrupnik · 2018-05-21T10:14:08Z

@nikidexa I think that it will be working on 2.2.2 but I did not test.

nikidexa · 2018-05-21T14:57:43Z

Yes, I can confirm that now is working good for me too....
so the solution is:
-add this line to composer.json : "pelago/emogrifier": "2.0.0 as 1.2.0"
-run -> composer update pelago/emogifier

thanks to everyone

rafaelaco · 2018-05-22T17:20:47Z

It worked for me: https://magento.stackexchange.com/a/132691

Puru2016 · 2018-05-26T06:39:57Z

Still issue is there as I am not able to update the "pelago/emogrifier" due to below error:-

Problem 1
- magento/magento2-base 2.2.3 requires pelago/emogrifier 1.2.0 -> satisfiable by pelago/emogrifier[V1.2.0] but these conflict with your requirements or minimum-stability.
- magento/magento2-base 2.2.3 requires pelago/emogrifier 1.2.0 -> satisfiable by pelago/emogrifier[V1.2.0] but these conflict with your requirements or minimum-stability.
- magento/magento2-base 2.2.3 requires pelago/emogrifier 1.2.0 -> satisfiable by pelago/emogrifier[V1.2.0] but these conflict with your requirements or minimum-stability.
- Installation request for magento/magento2-base (locked at 2.2.3) -> satisfiable by magento/magento2-base[2.2.3].

I have tried with below "pelago/emogrifier" version:-
"pelago/emogrifier": "1.0.0 as 0.1.1"
"pelago/emogrifier": "2.0.0 as 1.2.0",
"pelago/emogrifier": "1.0.0 as 0.1.1",
"pelago/emogrifier": "dev-master as 0.1.1",

in vendor\magento\magento2-base\composer.json
Please suggest the solution if I am doing wrong in the above process.

My exact error is as below in email template:-
CSS inlining error: DOMXPath::query(): Invalid expression in selector >> 50% << in /var/www/html/magento2/vendor/pelago/emogrifier/Classes/Emogrifier.php on line 370"

crtl · 2018-06-20T08:58:58Z

Ive recently updated from Magento 2.1.11 to 2.2.4 and got this exception.
Installed version of pelago/emogrifier is v2.0.0.

Exception is:
[2018-06-20 08:29:16] main.ERROR: DOMXPath::query(): Invalid expression in selector >> 100% << in /path/to/magento/vendor/pelago/emogrifier/Classes/Emogrifier.php on line 372 {"exception":"[object] (InvalidArgumentException(code: 1509279985): DOMXPath::query(): Invalid expression in selector >> 100% << in /path/to/magento/vendor/pelago/emogrifier/Classes/Emogrifier.php on line 372 at /path/to/magento/vendor/pelago/emogrifier/Classes/Emogrifier.php:1785)"} []

rszczepaniec · 2018-06-25T08:22:57Z

Same situation here. Magento 2.2.4, pelago/emogrifier in version 2.0.0.
Issue is still valid.

chammedinger · 2018-07-17T14:00:02Z

Again having the same issue on Magento 2.2.5.
I had it fixed with the composer line "pelago/emogrifier": "2.0.0 as 1.2.0" on Magento 2.2.3
but sadly on 2.2.5 this fix does not work anymore.

chammedinger · 2018-07-17T16:52:49Z

found a solution for Magento 2.2.5:

created the files
/web/css/email.less and
/web/css/email-inline.less
in my custom theme and added the content from
/vendor/magento/theme-frontend-blank/web/css/email.less and
/vendor/magento/theme-frontend-blank/web/css/email-inline.css respectively
but each with the line "@import 'source/_theme.less';" commented out (or removed)

tehtea · 2018-07-20T14:12:58Z

@chammedinger your fixed worked, thank you! If you don't mind sharing, what is your thought process towards fixing the bug?

jorgb90 · 2018-11-02T13:54:52Z

@tehtea Probably your _theme.less file is causing the css problem for the transactional emails, so by including the email-inline.less and email.less into your theme you are overwriting it and by commenting @import _theme.less you fix the error by excluding it :)

pratikhmehta · 2019-01-09T05:31:11Z

composer.json >> require-dev >> "pelago/emogrifier": "dev-master as 0.1.1"
Then composer update.

pablobae · 2019-02-05T18:51:28Z

Still present on 2.2.7 and the fix doesn't work
composer.json >> require-dev >> "pelago/emogrifier": "dev-master as 0.1.1" Then composer update.

chammedinger · 2019-02-05T18:56:52Z

@pablobae

thats correct. but my fix above for 2.2.5 still works on 2.2.7

pablobae · 2019-02-05T19:26:40Z

@pablobae

thats correct. but my fix above for 2.2.5 still works on 2.2.7

hmm I've done that too, but it doesn't work.. not on my M2 instance. I will try tomorrow this:

https://magento.stackexchange.com/questions/116952/order-mail-confirmation-generates-domxpathquery-error/132691#132691

I think, in my case, the issue comes from others files. The error appears in the newsletter confirmation mail. I've tried even remove all lines with import sentences on email.less, email-fonts.less and email-inline.css. With that the static file generated has no content (for example https://www.DOMAIN.com/pub/static/version1549392940/frontend/grand/theme/es_ES/css/email-fonts.css )
`/**

See COPYING.txt for license details.
*/`

But the issue happens yet...

sumeetmobiwebtech · 2019-04-03T10:57:11Z

Warning: DOMXPath::query(): Invalid expression in /var/www/html/xxx/xxx/vendor/magento/framework/Config/Dom.php on line 277

Getting this error when send email to customer programatically.
I tried this -
"pelago/emogrifier": "dev-master as 0.1.1"
"pelago/emogrifier": "2.0.0 as 1.2.0"
pelago/emogrifier is v2.0.0

But nothing work
please anyone here, i need help

I am using magento 2.3 version

Ravindrasinh · 2019-12-17T12:29:25Z

CSS inlining error: DOMXPath::query(): Invalid expression in selector >> @-webkit-keyframes bounceIn << in /var/www/html/vendor/pelago/emogrifier/src/Emogrifier.php on line 530

Getting this error Load Email template and check preview.

And currently my Pelago version ""pelago/emogrifier": "^2.0.0","

But nothing work
Please anyone here,i need help.

I am using magento 2.3.2 version.

Ravindrasinh · 2019-12-17T13:19:42Z

CSS inlining error: DOMXPath::query(): Invalid expression in selector >> @-webkit-keyframes bounceIn << in /var/www/html/vendor/pelago/emogrifier/src/Emogrifier.php on line 530

Getting this error Load Email template and check preview.

And currently my Pelago version ""pelago/emogrifier": "^2.0.0","

But nothing work
Please anyone here,i need help.

I am using magento 2.3.2 version.

JJBalso · 2020-01-08T23:16:16Z

@Ravindrasinh

I believe that error is only shown in develop/default mode. Try to set the mode to production:

php bin/magento deploy:mode:set production

sujith-cs · 2021-01-25T10:00:38Z

CSS inlining error: DOMXPath::query(): Invalid expression in selector >> @-webkit-keyframes bounceIn << in /var/www/html/vendor/pelago/emogrifier/src/Emogrifier.php on line 530
Getting this error Load Email template and check preview.

And currently my Pelago version ""pelago/emogrifier": "^2.0.0","

But nothing work
Please anyone here,i need help.

I am using magento 2.3.2 version.

hello @Ravindrasinh have you got any soulution? @JJBalso Im getting the issue in production mode also

MomotenkoNatalia added the Progress: needs update label May 31, 2016

MomotenkoNatalia assigned buskamuza Jul 22, 2016

MomotenkoNatalia removed the Progress: needs update label Jul 22, 2016

buskamuza removed their assignment Aug 18, 2016

vkorotun added the Component: Cms label Aug 22, 2016

veloraven added bug report TECH labels Aug 26, 2016

veloraven assigned antonkril Aug 26, 2016

veloraven added Area: Frontend 2.0.x labels Oct 13, 2016

veloraven mentioned this issue Oct 13, 2016

Outdated pelago/emogrifier package #6946

Closed

sidolov added the good first issue label Apr 6, 2018

magento-engcom-team closed this as completed Apr 14, 2018

magento-engcom-team removed the good first issue label Apr 14, 2018

malikt mentioned this issue Apr 26, 2018

Issue with updating pelago/emogrifier to v2.0.0 #14859

Closed

xPath error in mails #4737

xPath error in mails #4737

Comments

lgt commented May 27, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

designhunger commented May 30, 2016

Uh oh!

eug123 commented May 31, 2016

Uh oh!

juliansthl commented Jun 2, 2016

Uh oh!

eug123 commented Jun 3, 2016

Uh oh!

juliansthl commented Jun 27, 2016

Uh oh!

nickmarx12345678 commented Jul 21, 2016

Uh oh!

nickmarx12345678 commented Jul 21, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

AntonEvers commented Aug 11, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

AntonEvers commented Aug 11, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

DevManav commented Aug 24, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

adamraya commented Aug 24, 2016

Uh oh!

oliverklee commented Aug 24, 2016

Uh oh!

veloraven commented Aug 26, 2016

Uh oh!

DevManav commented Aug 31, 2016

Uh oh!

itelebar commented Sep 5, 2016

Uh oh!

mrkhoa99 commented Sep 7, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

DevManav commented Sep 13, 2016 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Bartlomiejsz commented Oct 19, 2016

Uh oh!

magento-engcom-team commented Apr 14, 2018

Uh oh!

nikidexa commented Apr 19, 2018

Uh oh!

Puru2016 commented May 16, 2018

Uh oh!

oliverklee commented May 16, 2018

Uh oh!

Puru2016 commented May 19, 2018

Uh oh!

mattkrupnik commented May 21, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nikidexa commented May 21, 2018

Uh oh!

mattkrupnik commented May 21, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nikidexa commented May 21, 2018

Uh oh!

rafaelaco commented May 22, 2018

Uh oh!

Puru2016 commented May 26, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

crtl commented Jun 20, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rszczepaniec commented Jun 25, 2018

Uh oh!

chammedinger commented Jul 17, 2018

Uh oh!

chammedinger commented Jul 17, 2018

lgt commented May 27, 2016 •

edited

Loading

nickmarx12345678 commented Jul 21, 2016 •

edited

Loading

AntonEvers commented Aug 11, 2016 •

edited

Loading

AntonEvers commented Aug 11, 2016 •

edited

Loading

DevManav commented Aug 24, 2016 •

edited

Loading

mrkhoa99 commented Sep 7, 2016 •

edited

Loading

DevManav commented Sep 13, 2016 •

edited

Loading

mattkrupnik commented May 21, 2018 •

edited

Loading

mattkrupnik commented May 21, 2018 •

edited

Loading

Puru2016 commented May 26, 2018 •

edited

Loading

crtl commented Jun 20, 2018 •

edited

Loading

jorgb90 commented Nov 2, 2018 •

edited

Loading

pablobae commented Feb 5, 2019 •

edited

Loading

chammedinger commented Feb 5, 2019 •

edited

Loading

sumeetmobiwebtech commented Apr 3, 2019 •

edited

Loading