Automattic / Automattic/jetpack
Jetpack Infinite Scroll and AMP for WP plugin: %%footer%% text displayed
- Dominant language
- PHP
- Stars
- 1.8k
- Forks
- 898
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 774
Description
Without [Accelerated Mobile Pages for WP plugin](https://it.wordpress.org/plugins/accelerated-mobile-pages/), regardless of the setting I select in Jetpack infinite scroll, `%%footer%%` text does not appear at the bottom of my site.
#### Steps to reproduce the issue
1. Install and activate Jetpack plugin.
2. Install and activate [Accelerated Mobile Pages for WP plugin](https://it.wordpress.org/plugins/accelerated-mobile-pages/) and configure settings
3. Go to Jetpack settings > Writing > Theme enhancements > Infinite Scroll and select either "Load more posts in page with a button" or "Load more posts as the reader scrolls down".
4. Visit the front page of your site, scroll down to the bottom and `%%footer%%` text will be displayed
#### What I expected
%%footer%% text should not appear at the bottom of the site regardless of the option selected under Infinite Scroll.
#### What happened instead
In Jetpack settings > Writing > Theme enhancements > Infinite Scroll, only when setting **“Load more posts using the default theme behavior”,** `%%footer%%` text will be removed / will not appear at the bottom of the site.
**Screenshots**
- In the browser inspector, `%%footer%%` shows:
`

- when Infinite Scroll is set to either **"Load more posts in page with a button"** or **"Load more posts as the reader scrolls down"**, %%footer%% is displayed at the bottom of the site:

- when Infinite Scroll is set to **“Load more posts using the default theme behavior”,** %%footer%% text is removed / not displayed:

Reference: 3553352-zen
Contributor guide
Research direction
Start by reproducing the issue with Jetpack and the Accelerated Mobile Pages for WP plugin, then compare the two Infinite Scroll settings on the site's front page. Inspect the rendered AMP markup shown in the report, especially the amp-next-page footer, and confirm that %%footer%% is absent for both non-default behaviors when done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100