Version 1.0.2 good but above version bad in the sense

  • bdy143

    (@bdy143)


    5 years, 7 months ago

    Version 1.0.2 is good that’s what I am using but one error (CSS code working good in non-amp but same not working fine in amp before “Version 1.0.2” was all fine but not others are fine, FIX IT)

    NEXT after “Version 1.0.2”

    there’s one error it’s creating 3-4 lines unnecessary spaces between “featured image and the top text of the post” which is very unattractive. FIX THIS MOST IMPORTANT.

    Others fine till now

    Waiting for fixing considering above issues in your next update I am still using the previous “Version 1.0.2” (which still contains CSS difference error for the amp and non-amp)

    Most important note for any Plugin Users

    Before updating any plugin make the backup (Updraft plus back up plugin is the best as a free tool) and restore (if plugin updated then restore only plugins, not a whole site to do faster recovery) if the problem exists.

    Or

    Use “WP rollback” wp plugin to roll back to the previous version of any updated plugin. that’s what prevents me from breaking up my site. (Using this restoring from the backup plugin is not needed)

    • This topic was modified 5 years, 7 months ago by bdy143.
    • This topic was modified 5 years, 7 months ago by bdy143.
    • This topic was modified 5 years, 7 months ago by bdy143.
    • This topic was modified 5 years, 7 months ago by bdy143.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Weston Ruter

    (@westonruter)

    5 years, 7 months ago

    @bdy143 I’m not sure I understand. Are you saying there is a CSS bug in 1.1.1?

    Have you opened a support topic with details of your issue? We need to see an AMP page on your site with the error in order to be able help.

    Thread Starter bdy143

    (@bdy143)

    5 years, 7 months ago

    This is problem I am having:

    FOR NON-AMP I USE THIS CODE:

    @media (min-width:250px) {
.cityv {
width : 49%; /*for amp set 48%, non-amp 49%*/
}
}

@media (min-width:500px) {
.cityv {
width : 24%; /*for amp set 23.5%, non-amp 24%*/
}
}

    BUT FOR AMP I USE THIS CODE

    @media (min-width:250px) {
.cityv {
width : 48%; /*for amp set 48%, non-amp 49%*/
}
}

@media (min-width:500px) {
.cityv {
width : 23.5%; /*for amp set 23.5%, non-amp 24%*/
}
}

    But previously

    Only using one code was enough:

    e.g:

    @media (min-width:250px) {
.cityv {
width : 49%;
}
}

@media (min-width:500px) {
.cityv {
width : 24%;
}
}

    ONE ANOTHER ISSUE IS THAT


    It’s creating unnecessary space between topmost image i.e featured image at the top and it’s below the text of the post. i.e. space getting created between featured image and post topmost text or anything added in topmost page of the post. Fix this most important.

    NOTE:

    I add code in amp plugin in head section from ‘html-start.php‘. I think you should suggest users add their non-amp CSS code to add here so that their website looks almost the same for the amp and non-amp.

    • This reply was modified 5 years, 7 months ago by bdy143.
    • This reply was modified 5 years, 7 months ago by bdy143.
    • This reply was modified 5 years, 7 months ago by bdy143.
    Plugin Author Weston Ruter

    (@westonruter)

    5 years, 7 months ago

    So you appear to be using Reader/Classic mode. If you want your AMP and non-AMP pages to look the same, you should instead use Transitional mode. This depends on you having a theme that is AMP-compatible (and plugins too), as can be found on https://amp-wp.org/ecosystem/themes/

    Secondly, you should not be modifying the html-start.php file in the template to add custom CSS. This will be overridden with each plugin update. In your theme’s functions.php or a custom plugin, you can do this to add custom CSS to the AMP Reader mode templates:

    add_action( 'amp_post_template_css', function() {
	?>
	/* Custom CSS goes here */
	<?php
} );

    Please make this change.

    If you update to the latest version and show the URL of the page that has the problem, we can advise. Without seeing the problem, it is difficult to help.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Version 1.0.2 good but above version bad in the sense’ is closed to new replies.

Tags