system.log: Warning: DOMXPath: :query() Invalid expression in /html/lib/Pelago/Emogriphier.phpBlank page issue in Admin after submitMagento PayPal order - Money taken - Not showing as an order in the backendCompletely Remove ModuleMagento system logCan't update products and attributes in Magento 1.9.2.2Magento - For “Manage Categories” Forbidden You do not have permission to access this documentWhy Magento can't load my Helper?Product price not displaying when I add to cartUnable to see the actual images in the back end

How soon after takeoff can you recline your airplane seat?

How does mmorpg store data?

Checkmate in 1 on a Tangled Board

Understanding the as-if rule, "the program was executed as written"

How many transistors are there in a logic gate?

How is it possible for tall trees to pull water to heights more than 10m?

Is there a word for the act of simultaneously pulling and twisting an object?

What prevents a US state from colonizing a smaller state?

Is leaving out prefixes like "rauf", "rüber", "rein" when describing movement considered a big mistake in spoken German?

What was the point of separating stdout and stderr?

Find the closest three-digit hex colour

How far can gerrymandering go?

Is it possible to alias a column based on the result of a select+where?

Multiple tests with effects all in same direction but only few significant

Word ending in "-ine" for rat-like

Why isn't UDP with reliability (implemented at Application layer) a substitute of TCP?

Processes in a session in an interactive shell vs in a script

Simplify the code

Basic calculations in PGF/TikZ for loop

Tricolour nonogram

Apollo Mission Operations Control Room 2 display, what do these numbers indicate?

What would you need merely the term "collection" for pitches, but not "scale"?

Why is my 401k manager recommending me to save more?

How to count the number of bytes in a file, grouping the same bytes?



system.log: Warning: DOMXPath: :query() Invalid expression in /html/lib/Pelago/Emogriphier.php


Blank page issue in Admin after submitMagento PayPal order - Money taken - Not showing as an order in the backendCompletely Remove ModuleMagento system logCan't update products and attributes in Magento 1.9.2.2Magento - For “Manage Categories” Forbidden You do not have permission to access this documentWhy Magento can't load my Helper?Product price not displaying when I add to cartUnable to see the actual images in the back end













0















I keep seeing the following lines in var/log/system.log after each transaction email is sent:




2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
expression in /html/lib/Pelago/Emogrifier.php on line 326

2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
expression in /html/lib/Pelago/Emogrifier.php on line 326

2015-10-12T00:11:12+00:00 ERR (3): Warning: Invalid argument supplied
for foreach() in /html/lib/Pelago/Emogrifier.php on line 329

2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
expression in /html/lib/Pelago/Emogrifier.php on line 326

2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
expression in /html/lib/Pelago/Emogrifier.php on line 326

2015-10-12T00:11:12+00:00 ERR (3): Warning: Invalid argument supplied
for foreach() in /html/lib/Pelago/Emogrifier.php on line 329




Someone knows what could cause this?



Thanks for your help!










share|improve this question




























    0















    I keep seeing the following lines in var/log/system.log after each transaction email is sent:




    2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
    expression in /html/lib/Pelago/Emogrifier.php on line 326

    2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
    expression in /html/lib/Pelago/Emogrifier.php on line 326

    2015-10-12T00:11:12+00:00 ERR (3): Warning: Invalid argument supplied
    for foreach() in /html/lib/Pelago/Emogrifier.php on line 329

    2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
    expression in /html/lib/Pelago/Emogrifier.php on line 326

    2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
    expression in /html/lib/Pelago/Emogrifier.php on line 326

    2015-10-12T00:11:12+00:00 ERR (3): Warning: Invalid argument supplied
    for foreach() in /html/lib/Pelago/Emogrifier.php on line 329




    Someone knows what could cause this?



    Thanks for your help!










    share|improve this question


























      0












      0








      0








      I keep seeing the following lines in var/log/system.log after each transaction email is sent:




      2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
      expression in /html/lib/Pelago/Emogrifier.php on line 326

      2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
      expression in /html/lib/Pelago/Emogrifier.php on line 326

      2015-10-12T00:11:12+00:00 ERR (3): Warning: Invalid argument supplied
      for foreach() in /html/lib/Pelago/Emogrifier.php on line 329

      2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
      expression in /html/lib/Pelago/Emogrifier.php on line 326

      2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
      expression in /html/lib/Pelago/Emogrifier.php on line 326

      2015-10-12T00:11:12+00:00 ERR (3): Warning: Invalid argument supplied
      for foreach() in /html/lib/Pelago/Emogrifier.php on line 329




      Someone knows what could cause this?



      Thanks for your help!










      share|improve this question
















      I keep seeing the following lines in var/log/system.log after each transaction email is sent:




      2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
      expression in /html/lib/Pelago/Emogrifier.php on line 326

      2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
      expression in /html/lib/Pelago/Emogrifier.php on line 326

      2015-10-12T00:11:12+00:00 ERR (3): Warning: Invalid argument supplied
      for foreach() in /html/lib/Pelago/Emogrifier.php on line 329

      2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
      expression in /html/lib/Pelago/Emogrifier.php on line 326

      2015-10-12T00:11:12+00:00 ERR (3): Warning: DOMXPath::query(): Invalid
      expression in /html/lib/Pelago/Emogrifier.php on line 326

      2015-10-12T00:11:12+00:00 ERR (3): Warning: Invalid argument supplied
      for foreach() in /html/lib/Pelago/Emogrifier.php on line 329




      Someone knows what could cause this?



      Thanks for your help!







      magento-1.9 transactional-mail order-email






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Oct 12 '15 at 0:21









      Adarsh Khatri

      6,7601 gold badge17 silver badges44 bronze badges




      6,7601 gold badge17 silver badges44 bronze badges










      asked Oct 12 '15 at 0:20









      LenaLena

      43 bronze badges




      43 bronze badges




















          1 Answer
          1






          active

          oldest

          votes


















          0















          As the comment in the class definition states - This class provides
          functions for converting CSS styles into inline style attributes in
          your HTML code.




          Looking at the calls of emogrify() method we discover that it is called by _applyInlineCss() method which is in turn called by getPreparedTemplateText() method defined in Mage_Core_Model_Email_Template_Abstract.



          The issue occurs when an invalid expression is passed to $xpath->query() also making $nodesMatchingCssSelectors invalid thus triggering the second error.



          In my case, I had this issue in the new-account.phtml template that was using inlinecss file="email-inline.css" and in which at some point I had something like:



          @-webkit-keyframes fa-spin 
          0%
          -webkit-transform: rotate(0deg);
          transform: rotate(0deg);

          100%
          -webkit-transform: rotate(359deg);
          transform: rotate(359deg);




          The issue was occurring when Emogriphier library tried translate 100% into path: $nodesMatchingCssSelectors = $xpath->query(100%). Because 100% is not a valid selector the error is triggered.



          /**
          * Right now, we support all CSS 1 selectors and most CSS2/3 selectors.
          *
          * @see http://plasmasturm.org/log/444/
          *
          * @param string $paramCssSelector
          *
          * @return string
          */
          private function translateCssToXpath($paramCssSelector) {


          A little bit late but hope this helps. :)






          share|improve this answer



























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "479"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f86072%2fsystem-log-warning-domxpath-query-invalid-expression-in-html-lib-pelago-e%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0















            As the comment in the class definition states - This class provides
            functions for converting CSS styles into inline style attributes in
            your HTML code.




            Looking at the calls of emogrify() method we discover that it is called by _applyInlineCss() method which is in turn called by getPreparedTemplateText() method defined in Mage_Core_Model_Email_Template_Abstract.



            The issue occurs when an invalid expression is passed to $xpath->query() also making $nodesMatchingCssSelectors invalid thus triggering the second error.



            In my case, I had this issue in the new-account.phtml template that was using inlinecss file="email-inline.css" and in which at some point I had something like:



            @-webkit-keyframes fa-spin 
            0%
            -webkit-transform: rotate(0deg);
            transform: rotate(0deg);

            100%
            -webkit-transform: rotate(359deg);
            transform: rotate(359deg);




            The issue was occurring when Emogriphier library tried translate 100% into path: $nodesMatchingCssSelectors = $xpath->query(100%). Because 100% is not a valid selector the error is triggered.



            /**
            * Right now, we support all CSS 1 selectors and most CSS2/3 selectors.
            *
            * @see http://plasmasturm.org/log/444/
            *
            * @param string $paramCssSelector
            *
            * @return string
            */
            private function translateCssToXpath($paramCssSelector) {


            A little bit late but hope this helps. :)






            share|improve this answer





























              0















              As the comment in the class definition states - This class provides
              functions for converting CSS styles into inline style attributes in
              your HTML code.




              Looking at the calls of emogrify() method we discover that it is called by _applyInlineCss() method which is in turn called by getPreparedTemplateText() method defined in Mage_Core_Model_Email_Template_Abstract.



              The issue occurs when an invalid expression is passed to $xpath->query() also making $nodesMatchingCssSelectors invalid thus triggering the second error.



              In my case, I had this issue in the new-account.phtml template that was using inlinecss file="email-inline.css" and in which at some point I had something like:



              @-webkit-keyframes fa-spin 
              0%
              -webkit-transform: rotate(0deg);
              transform: rotate(0deg);

              100%
              -webkit-transform: rotate(359deg);
              transform: rotate(359deg);




              The issue was occurring when Emogriphier library tried translate 100% into path: $nodesMatchingCssSelectors = $xpath->query(100%). Because 100% is not a valid selector the error is triggered.



              /**
              * Right now, we support all CSS 1 selectors and most CSS2/3 selectors.
              *
              * @see http://plasmasturm.org/log/444/
              *
              * @param string $paramCssSelector
              *
              * @return string
              */
              private function translateCssToXpath($paramCssSelector) {


              A little bit late but hope this helps. :)






              share|improve this answer



























                0












                0








                0








                As the comment in the class definition states - This class provides
                functions for converting CSS styles into inline style attributes in
                your HTML code.




                Looking at the calls of emogrify() method we discover that it is called by _applyInlineCss() method which is in turn called by getPreparedTemplateText() method defined in Mage_Core_Model_Email_Template_Abstract.



                The issue occurs when an invalid expression is passed to $xpath->query() also making $nodesMatchingCssSelectors invalid thus triggering the second error.



                In my case, I had this issue in the new-account.phtml template that was using inlinecss file="email-inline.css" and in which at some point I had something like:



                @-webkit-keyframes fa-spin 
                0%
                -webkit-transform: rotate(0deg);
                transform: rotate(0deg);

                100%
                -webkit-transform: rotate(359deg);
                transform: rotate(359deg);




                The issue was occurring when Emogriphier library tried translate 100% into path: $nodesMatchingCssSelectors = $xpath->query(100%). Because 100% is not a valid selector the error is triggered.



                /**
                * Right now, we support all CSS 1 selectors and most CSS2/3 selectors.
                *
                * @see http://plasmasturm.org/log/444/
                *
                * @param string $paramCssSelector
                *
                * @return string
                */
                private function translateCssToXpath($paramCssSelector) {


                A little bit late but hope this helps. :)






                share|improve this answer
















                As the comment in the class definition states - This class provides
                functions for converting CSS styles into inline style attributes in
                your HTML code.




                Looking at the calls of emogrify() method we discover that it is called by _applyInlineCss() method which is in turn called by getPreparedTemplateText() method defined in Mage_Core_Model_Email_Template_Abstract.



                The issue occurs when an invalid expression is passed to $xpath->query() also making $nodesMatchingCssSelectors invalid thus triggering the second error.



                In my case, I had this issue in the new-account.phtml template that was using inlinecss file="email-inline.css" and in which at some point I had something like:



                @-webkit-keyframes fa-spin 
                0%
                -webkit-transform: rotate(0deg);
                transform: rotate(0deg);

                100%
                -webkit-transform: rotate(359deg);
                transform: rotate(359deg);




                The issue was occurring when Emogriphier library tried translate 100% into path: $nodesMatchingCssSelectors = $xpath->query(100%). Because 100% is not a valid selector the error is triggered.



                /**
                * Right now, we support all CSS 1 selectors and most CSS2/3 selectors.
                *
                * @see http://plasmasturm.org/log/444/
                *
                * @param string $paramCssSelector
                *
                * @return string
                */
                private function translateCssToXpath($paramCssSelector) {


                A little bit late but hope this helps. :)







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Jan 5 '17 at 12:37

























                answered Jan 5 '17 at 9:49









                RaduRadu

                16013 bronze badges




                16013 bronze badges



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Magento Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f86072%2fsystem-log-warning-domxpath-query-invalid-expression-in-html-lib-pelago-e%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Category:9 (number) SubcategoriesMedia in category "9 (number)"Navigation menuUpload mediaGND ID: 4485639-8Library of Congress authority ID: sh85091979ReasonatorScholiaStatistics

                    Circuit construction for execution of conditional statements using least significant bitHow are two different registers being used as “control”?How exactly is the stated composite state of the two registers being produced using the $R_zz$ controlled rotations?Efficiently performing controlled rotations in HHLWould this quantum algorithm implementation work?How to prepare a superposed states of odd integers from $1$ to $sqrtN$?Why is this implementation of the order finding algorithm not working?Circuit construction for Hamiltonian simulationHow can I invert the least significant bit of a certain term of a superposed state?Implementing an oracleImplementing a controlled sum operation

                    Magento 2 “No Payment Methods” in Admin New OrderHow to integrate Paypal Express Checkout with the Magento APIMagento 1.5 - Sales > Order > edit order and shipping methods disappearAuto Invoice Check/Money Order Payment methodAdd more simple payment methods?Shipping methods not showingWhat should I do to change payment methods if changing the configuration has no effects?1.9 - No Payment Methods showing upMy Payment Methods not Showing for downloadable/virtual product when checkout?Magento2 API to access internal payment methodHow to call an existing payment methods in the registration form?