LesGrosSacs
Forum Replies Created
-
Forum: Plugins
In reply to: [AMP] AMP Issue, CSS syntax error “style amp-custom”Thanks a lot
Forum: Plugins
In reply to: [AMP] AMP Issue, CSS syntax error “style amp-custom”@westonruter just installed the latest build and it seems like to fix it (I tried on 3 different URLs), thanks so much !
I am now launching a global validation of all my AMP pages 🙂
Can you confirm that this fix will be included in the next update ?
Thanks again so much !Forum: Plugins
In reply to: [AMP] AMP Issue, CSS syntax error “style amp-custom”I just emptied the cache of the website (I have WP Fastest Cache plugin running) but still the same error :/
Forum: Plugins
In reply to: [AMP] AMP Issue, CSS syntax error “style amp-custom”@westonruter that’s what I did 🙂 I just came back to the initial state after.
But I re-did it, as you can see now, the version alpha is installed and I still have the same issue in the validator :/Forum: Plugins
In reply to: [AMP] AMP Issue, CSS syntax error “style amp-custom”And here are some screenshots :

<br />upload pictures<br />Forum: Plugins
In reply to: [AMP] AMP Issue, CSS syntax error “style amp-custom”Hello @westonruter and sorry for the delay, I am still struggling with this issue but completely forgot to test your alpha build.
So I just did and unfortunately it doesn’t solve the issue.
I installed your package (deactivated the current version meanwhile) and I launched a new validation of a page in the search console. And I still have the CDATA error that pops and prevent me from validating the AMP page :/The issue :
<![CDATA[.mailpoet_hp_email_label{display:none}#mailpoet_form_1 .mailpoet_paragraph{line-height:20px}#mailpoet_form_1 .mailpoet_segment_label,#mailpoet_form_1 .mailpoet_text_label,#mailpoet_form_1 .mailpoet_textarea_label,#mailpoet_form_1 .mailpoet_select_label,#mailpoet_form_1 .mailpoet_radio_label,#mailpoet_form_1 .mailpoet_checkbox_label,#mailpoet_form_1 .mailpoet_list_label,#mailpoet_form_1 .mailpoet_date_label{display:block;font-weight:bold}#mailpoet_form_1 .mailpoet_text,#mailpoet_form_1 .mailpoet_textarea,#mailpoet_form_1 .mailpoet_select,#mailpoet_form_1 .mailpoet_date_month,#mailpoet_form_1 .mailpoet_date_day,#mailpoet_form_1 .mailpoet_date_year,#mailpoet_form_1 .mailpoet_date{display:block}#mailpoet_form_1 .mailpoet_text,#mailpoet_form_1 .mailpoet_textarea{width:200px}#mailpoet_form_1 .mailpoet_validate_success{font-weight:600;color:#468847}#mailpoet_form_1 .mailpoet_validate_error{color:#b94a48}#mailpoet_form_1 .mailpoet_form_loading{width:30px;text-align:center;line-height:normal}#mailpoet_form_1 .mailpoet_form_loading > span{width:5px;height:5px;background-color:#5b5b5b}:root:not(#_):not(#_):not(#_):not(#_):not(#_) .amp-wp-7d27179{text-align:justify}:root:not(#_):not(#_):not(#_):not(#_):not(#_) .amp-wp-e3120c2{font-size:36pt;font-family:moon-flower-bold}:root:not(#_):not(#_):not(#_):not(#_):not(#_) .amp-wp-7865d8c{font-family:moon-flower-bold;font-size:36pt}:root:not(#_):not(#_):not(#_):not(#_):not(#_) .amp-wp-e6a44be{display:inline-block}:root:not(#_):not(#_):not(#_):not(#_):not(#_) .amp-wp-2f58115{width:0%}:root:not(#_):not(#_):not(#_):not(#_):not(#_) .amp-wp-93b8ea5{display:none} </style>
- This reply was modified 7 years, 2 months ago by LesGrosSacs.
@suzukube can you tell me what was the issue on your side ?
I’m still struggling to find where the issue comes from 🙁Hi guys,
On my side, the issue (message : ““A conflicting version of PHP-CSS-Parser …”) is still there even with the latest update of MailPoet
Forum: Plugins
In reply to: [AMP] AMP Issue, CSS syntax error “style amp-custom”Thanks @westonruter , didn’t had the time yet to test it but will let you know as soon as I can 🙂
Forum: Plugins
In reply to: [AMP] AMP Issue, CSS syntax error “style amp-custom”All right, thanks a lot @westonruter
I’ve notify Mailpoet team, they’re also on it and should fix it in the next release.
I’ll make them aware of your comments so that they have a look at it.
Thanks again, I’ll let you know when it’s fixed.Done 🙂
After analysis, seems like the issue was coming from an incompatibility between my slider plugin (smart slider 3) and Table Press.
Thanks for your helpForum: Plugins
In reply to: [Smart Slider 3] AMP issue since last updateForum: Plugins
In reply to: [Smart Slider 3] AMP issue since last updateHello again 🙂
Seems like the issue comes from the slider (and not the cache plugin) in the end.I deactivated the cache plugin and analyzed the AMP URL again, and here are the pieces of code that are in error now for JS & CSS. Seems like its’ coming from smart slider minified files :
JS (6 JS errors in total) :
<script type=”text/javascript” src=”https://lesgrossacs.com/wp-content/plugins/smart-slider-3/nextend/media/dist/n2.min.js?1536127411″></script><script type=”text/javascript” src=”https://lesgrossacs.com/wp-content/plugins/smart-slider-3/library/media/plugins/type/simple/simple/dist/smartslider-simple-type-frontend.min.js?1536127411″></script>
</style><script type=”text/javascript”>(function(){var N=this;N.N2_=N.N2_||{r:[],d:[]},N.N2R=N.N2R||function(){N.N2_.r.push(arguments)},N.N2D=N.N2D||function(){N.N2_.d.push(arguments)}}).call(window);if(!window.n2jQuery){window.n2jQuery={ready:function(cb){console.error(‘n2jQuery will be deprecated!’);N2R([‘$’],cb)}}}window.nextend={localization:{},ready:function(cb){console.error(‘nextend.ready will be deprecated!’);N2R(‘documentReady’,function($){cb.call(window,$)})}};</script><script type=”text/javascript” src=”https://lesgrossacs.com/wp-content/plugins/smart-slider-3/nextend/media/dist/n2.min.js?1536127411″></script>
CSS :
<link rel=”stylesheet” type=”text/css” href=”https://lesgrossacs.com/wp-content/plugins/smart-slider-3/library/media/smartslider.min.css?1536127411″ media=”all” />Any idea on how I could fix that ?
Hello, indeed you’re right, when I disable the cache plugin, I still have errors but they now point to the Slider plugin for which I have issue :
Example now for the JS : <script type=”text/javascript” src=”https://lesgrossacs.com/wp-content/plugins/smart-slider-3/nextend/media/dist/n2.min.js?1536127411″></script>