mehthesheep

Hi Ahmed, is the fix going to be in your coming release?

Thank you Ahmed, I was amazed that no one has brought this up yet ?? Anyways, thanks for being responsive on this and your impact of continuing developing and refining the plugin is impact of millions (the very least). Highly appreciate it! I hope the coming update will happen very soon, look forward to it.

You’re right that AMP doesn’t allow, I’m not sure how exactly the team solved it but they did it. From the result, I can see they create unique class for each inline style.

The open issue was discussed here: https://github.com/Automattic/amp-wp/issues/395 , and
They mentioned the merge of fix here: https://github.com/Automattic/amp-wp/pull/470

If you look at the changelog here https://www.ads-software.com/plugins/amp/changelog/ , they mentioned “Fix: support for inline styles (props coreymckrill)” since version 0.4

Hope this helps ??

Hey Chad, if you’re on the latest version of Transporter, you shouldn’t need to use Jetpack’s infinite scroll. This plugin is sufficient.

Quick question to Tom – I’ve just found out that actually all the new loading pages ain’t tracked in the GA (i checked via real time GA).

The real-time GA was reflecting fine during first page loading. But subsequent pages does not have any effect. I also noticed my GA does not has any real improvement on pageviews too.

Could this be something we overlooked? Anything I can help with?

It really works! Thanks Tom, you saved the day again!

Jack raised some great add-ons I’m looking at too, look forward to them in another thread!

Those are great help, Tom.

Thanks!

I’ve found the problem child. It’s the advanced image lazy load plugin. Can’t work in harmony : https://www.ads-software.com/plugins/advanced-lazy-load/

Tom, I found this javascript error when scroll to the bottom of post.

https://www.evernote.com/shard/s120/sh/8fb8a6ec-77eb-4e14-a57e-6108e2e29029/503be7c905c7a370a56422f6e5af5811

Thanks Tom, I’ve put in the code to functions.php and updated the plugin but can’t notice any difference.

Is there something to do with cache? I’ve cleared all the cache though. The home page still presented in few pages and article not loading after one another in single post.

Thanks Tom!

Here’s the config.

function mytheme_infinite_scroll_init() {
	add_theme_support( 'infinite-scroll', array(
	'container' => 'content',
	'footer' => false,
	'type'           => 'scroll',
    'footer_widgets' => false,
    'wrapper'        => true,
    'posts_per_page' => false,
	) );
}
add_action( 'init', 'mytheme_infinite_scroll_init' );

function mytheme_infinite_scroll_render() {
	get_template_part( 'loop' );
}

function mytheme_infinite_transporter_init() {
	add_theme_support( 'infinite-transporter', array(
	    'type'            => 'scroll', // scroll | click
	    'requested_type'  => 'scroll', // store the original type for use when logic overrides it
	    'footer_widgets'  => false, // true | false | sidebar_id | array of sidebar_ids -- last two are checked with is_active_sidebar
	    'container'       => 'content', // container html id
	    'wrapper'         => true, // true | false | html class
	    'footer'          => false, // boolean to enable or disable the infinite footer | string to provide an html id to derive footer width from
	    'google_analytics'=> true, // boolean if using google analytics, set to true
	    'post_order'    => false, // boolean. false to display newest post after initial post. True to display next reverse chronological post after current post.
	    'footer_callback' => false, // function to be called to render the IS footer, in place of the default
	    'posts_per_page'  => false, // int | false to set based on IS type
	    'click_handle'    => true, // boolean to enable or disable rendering the click handler div. If type is click and this is false, page must include its own trigger with the HTML ID 'infinite-handle'.
	) );
}
add_action( 'init', 'mytheme_infinite_transporter_init' );