This website uses cookies to personalise ads and to analyse traffic ok
web design

Page scroll to id for WordPress

Page scroll to id is a fully featured WordPress plugin for creating links that scroll the page smoothly to any id within the document. The plugin replaces browser’s “jumping” behavior with a smooth scrolling animation, when links with href value containing # are clicked.
It provides all the basic tools and advanced functionality for single-page websites, in-page navigation, back-to-top links etc. with features like: adjustable scrolling animation duration and easing, link and target highlighting via ready-to-use CSS classes, vertical and/or horizontal scrolling, scrolling from/to different pages etc.

Get started

The plugin works by “connecting” links with href/URL in the form of #my-id or http://my-site.com/page/#my-id to sections/elements within the document with an equivalent id attribute value (e.g. <div id="my-id">...</div>). Clicking such links will scroll the page smoothly to their target id position.

Get started by creating or setting-up your links. The plugin is enabled by default on WordPress Menu links (created in Appearance → Menus), so you can start adding custom links and set their URL to the id/target you want to scroll to (e.g. #my-id, /page/#my-id, http://my-site.com/page/#my-id etc.).
You can use id values that already exist in your theme or you can create your own id targets using plugin’s “Insert Page scroll to id target” button in wp post visual editor or the [ps2id] shortcode (e.g. [ps2id id='my-id'/]).

To create links within your content, use plugin’s “Insert/edit Page scroll to id link” button and/or shortcode (e.g. [ps2id url='#my-id']link text[/ps2id]) in wp post visual/text editor.
To enable the plugin on existing links, add the ps2id class or the m_PageScroll2id rel attribute to them, making sure the link’s href/URL value contains a hash (#) with the id of the section you want to scroll-to. In addition, you can simply add your links CSS selector (e.g. .menu-item a, a[href*=#]:not([href=#]) etc.) in “Selector(s)” field in plugin settings.

To highlight your links (or targets), use the classes provided by the plugin in your theme’s stylesheet or custom CSS. The default highlight class is mPS2id-highlight but you can set your own in the “Classes & highlight options”. For example, to style the highlighted link (the link whose target element is considered to be within the viewport), you could add in your CSS:
a.mPS2id-highlight{ background: #ff0; } or .menu-item a.mPS2id-highlight{ background: #ff0; } for highlighting custom menus links only.

If you have a fixed-positioned/sticky menu which overlaps your target’s content when page scrolling is completed, insert your menu CSS selector or a fixed pixel value in the “Offset” field. For example, inserting #navigation-menu will offset the scroll-to position according to the height/width/position of the element with id navigation-menu. In the same manner, setting the “Offset” value to 100 will offset page scrolling by 100 pixels.

Plugin settings

Selector(s)

Use the Selector(s) field when you need to instruct the plugin to handle specific links. The value(s) should be anchor tags (a, i.e. links) in the form of strings that represent ways of choosing elements in the DOM (i.e. CSS selectors).
Each selector is separated by comma, so multiple selectors can be defined as: selector1, selector2, selector3 etc.

The default selector value is a[rel='m_PageScroll2id'], meaning the plugin handles by default all anchor elements (a) with m_PageScroll2id rel attribute value.
Other selector examples could be: a[href*='#'] (links that contain # in their href/URL attribute), a[href='#my-id'] (links with href attribute value: #my-id), a.className (links with class: className).

To enable the plugin on any link that has a hash (#) in its URL, insert a[href*=#]:not([href=#]) as a single selector.

Other default selectors which the plugin is applied automatically include the class ps2id (actual selectors: .ps2id > a[href*='#'] and a.ps2id[href*='#']). This means that any link with a hash in its URL/href (e.g. #my-id) which has the class or is contained (direct children) within an element with the class ps2id will be handled by the plugin automatically.

The option “Enable on WordPress Menu links” (enabled by default) enables the plugin automatically on custom links created in WordPress Menus.

Scroll duration

Scroll animation duration (i.e. scrolling speed) in milliseconds (1000 milliseconds equal 1 second). Lower values equal faster scrolling.

“Auto-adjust scrolling duration” option (enabled by default) lets the plugin fine-tune scrolling duration/speed according to target and page scroll position. This normalizes the animation duration in order to avoid short-distance scrolling taking too long (e.g. a page scroll of just 100 pixels will last shorter than the value specified in “Scroll duration”).

Scroll type/easing

Scroll animation easing type (i.e. the way the animation progresses at different points within its duration).
You can set different easing types according to page scrolling state: one that is applied when the page is idle (no scrolling currently running) and another that applies while page is scrolling (when a link is clicked while the page is animated/scrolling).

Scroll duration and easing demo

Scroll behavior

Always scroll smoothly when reaching the end of the page/document option adjusts scroll-to position so it does not exceed document length. For example, when scrolling to a target element that is at the bottom of the page, the scrolling animation stops smoothly at bottom of the page instead of “breaking” at an earlier point.
Enable Stop page scrolling on mouse-wheel or touch-swipe option if you want to stop page scrolling when the user tries to scroll the page manually (e.g. via mouse-wheel or touch-swipe).
Enabling Verify target position and readjust scrolling (if necessary), after scrolling animation is complete option, will auto-correct scrolling if the target’s position was changed while the page was scrolling. This event will fire one time only after scrolling animation is complete. This option is useful when document’s length changes according to scroll (for example when a menu becomes sticky after scrolling down the page and its previous state space gets zero).

Page layout

Set page scrolling direction (i.e. restrict scrolling) to top-bottom (vertical) or left-right (horizontal) accordingly. For both vertical and horizontal scrolling select auto.
This option does not transform your theme’s templates layout (i.e. it won’t change your theme/page design from vertical to horizontal).

Offset

Offset scroll-to position by x amount of pixels or by selector. The offset value can a be a positive or negative number (indicating pixels), or a matching set of elements in your html (selector). For example, setting the value to 50 will stop page scrolling 50 pixels before reaching the target.
If you need to offset scrolling according to the height (or width) of some element (e.g. according to a responsive/sticky navigation menu), insert the element’s selector in the Offset field. For example, if you have a top fixed/sticky menu with id navigation-menu, set the offset value to #navigation-menu in order to stop page scrolling below it and avoid the menu overlapping your content.

To set different vertical and horizontal offsets (e.g. when Layout is set to auto), add comma separated values in Offset field, e.g. 100,50 (vertical offset 100 pixels, horizontal offset 50 pixels).

The plugin offers selector expressions in order to define more advanced offset values. Examples:

  • :fixed expression – Offset by element with id “some-id” and CSS position fixed: #some-id:fixed
    Assuming vertical layout, the value above will offset scrolling according to the height of #some-id element (i.e. the element that has id some-id), but only when this element CSS position is fixed (i.e. element is sticky). This is useful when for example you have a navigation menu that is sticky/fixed only above a specific viewport size (e.g. only on desktop).
  • :height() expression – Offset by element with class “some-class” and height equal to 100 pixels: .some-class:height(100)
    The value above will offset scrolling according to the height (on vertical layout) of .some-class element (i.e. the element that has class some-class), but only when this element height is exactly 100 pixels.
  • :width() expression – Offset by element with id “some-id” and width greater than 800 pixels: #some-id:width(>800)
    The value above will offset scrolling according to the height of #some-id element, but only when this element width is greater than 800 pixels. This is useful when having responsive navigation menus. For instance, you might have a responsive top sticky menu that switches to a “hamburger” menu when viewport is 800 pixels wide or less. Assuming the menu is as wide as the page/viewport, you’d only want to apply its height as offset when its width is greater than 800 pixels (i.e. when it’s not “hamburger” menu). Adding: #your-menu-id:width(>800) as the offset value will do exactly that.
  • Multiple expressions – Offset by element with id “some-id”, CSS position fixed and height between 50 and 100 pixels: #some-id:fixed:height(>50):height(<100)
    The value above will offset scrolling according to the height of #some-id element, but only when this element CSS position is fixed and its height is anywhere between 51 and 99 pixels.

Highlight selector(s)

The matching set of elements (i.e. selectors) handled by the plugin, that will be eligible for highlighting. The value(s) should be anchor tags (a, i.e. links).

The plugin highlights by default all the links it handles. Using this field, you can specify which links should be highlighted and exclude the rest.
For example, assuming you have various links that scroll the page (e.g. menu links, back-to-top etc.) and you want only the menu links to get highlighted, you could insert:
.menu-item a[href*='#']

Classes & highlight options

The plugin adds special classes to the links and the target elements it handles when the following happen:

  • When a link is clicked, it gets the mPS2id-clicked class.
    You can change this class name to your own and you can use it in your CSS to style the clicked link. For instance:
    .mPS2id-clicked{ background: #ff0; }
  • When a link’s target element is within the viewport (i.e. visible on the screen), the link gets the mPS2id-highlight class and the target element gets the mPS2id-target class.
    You can change these class names to your own and you can use them in your CSS to style the highlighted link and target. For instance:
    .mPS2id-target{ background: #ff0; }
    a.mPS2id-highlight{ background: #ff0; }

In addition, the plugin will add the above highlight classes with the -first and -last suffix (e.g. mPS2id-highlight-first, mPS2id-highlight-last) in order to differentiate multiple highlighted elements. This is useful when you need to style only the first or last of the highlighted links or targets in your CSS.
For example, if multiple links are highlighted at the same time, instead of using .mPS2id-highlight in your stylesheet, you could do:
a.mPS2id-highlight-first{ background: #ff0; }

An alternative way of restricting highlight to a single link/target and prevent multiple elements from being highlighted at the same time, is to enable Allow only one highlighted element at a time.

There are times when you need to keep at least one element (e.g. a menu link) always highlighted. Enable Keep the current element highlighted until the next one comes into view option if you need such functionality/behavior and your template/page is laid out in a way that at certain scrolling points there are no target sections visible on the screen (no links highlighted).

Enable Highlight by next target option when your target elements have zero height/width to improve highlighting behavior. This option is useful when you add id targets in your content via plugin’s buttons or the [ps2id id='some-id'/] shortcode, as it extends the scrolling range at which an element stays highlighted.

Disable plugin below

Set the viewport/screen-size in pixels, below which the plugin will be disabled. The value can be width or width,height.
For example, insert 1024 to disable plugin’s functionality when the viewport/window width is 1024 pixels or less. Insert 1024,600 to disable plugin when viewport width is 1024 pixels or less and viewport height is 600 pixels or less.
Please note that the values entered will match CSS media queries.

Leaving the field value empty or 0 (default) disables the option.

Administration

Check Display widgets id attribute in order to show the id attribute of each widget in Appearance → Widgets. This is a convenient way of finding existing id values in order to use them as links targets.
You can also create your own id targets in widgets via the “Page scroll to id target” widget.

Enable insert link/target buttons in post visual editor activates plugin’s buttons in WordPress visual editor toolbar. You can use these buttons to insert links and id targets in your content.

Advanced options

If another plugin or a theme script handles page scrolling and conflicts with “Page scroll to id”, try enabling Prevent other scripts from handling plugin’s links option. This option attempts to remove (on-the-fly) javascript click events by other scripts from the links. Please note that this might not work on some themes or plugins, as it depends on the way those scripts are attaching the link events.

Enable Normalize anchor-point targets to normalize/reset the CSS properties (height, line-height, border etc.) of anchor-point targets.

wp-config options

define('PS2ID_MINIFIED_JS', false);
Use the PS2ID_MINIFIED_JS constant (permanent global variable) in wp-config.php to select which script files will be loaded on the front-end by the plugin. Adding the above in wp-config.php instructs the plugin to load the non-minified/development version of its scripts.

Divi WordPress Theme Monarch Social Sharing Plugin

Plugin shortcodes

Plugin’s [ps2id] shortcode can be inserted directly in WordPress post editor (as with any WordPress shortcode) in order to create links and id targets in your content.

[ps2id url='#some-id']link text[/ps2id]

Attributes

  • url (required) – Link URL
    Examples:
    [ps2id url='#some-id']link text[/ps2id]
    [ps2id url='http://some-site.com/page/#some-id']link text[/ps2id]
    [ps2id url='/page/#some-id']link text[/ps2id]
    
  • offset (optional) – Link-specific offset (bypasses the general offset value in plugin settings)
    Examples:
    Offset scrolling by 100 pixels
    [ps2id url='#some-id' offset='100']link text[/ps2id]
    
    Offset scrolling by the height (or width for horizontal layout) of the element with id navigation-menu
    [ps2id url='#some-id' offset='#navigation-menu']link text[/ps2id]
    
    Offset vertical scrolling by 100 pixels and horizontal scrolling by 50 pixels
    [ps2id url='#some-id' offset='{"y":"100","x":"50"}']link text[/ps2id]
    
  • class (optional) – Link custom class(es)
    You can give the link one or more custom classes (separate multiple classes with space).
    Examples:
    [ps2id url='#some-id' class='class-a']link text[/ps2id]
    [ps2id url='#some-id' class='class-a class-b']link text[/ps2id]
    

    You can change the scroll duration/speed of the link (bypass the general scroll duration value in plugin settings) by adding a special class in the form of ps2id-speed-VALUE (i.e. ps2id-speed-600) with VALUE indicating the scroll duration in milliseconds (lower duration equals faster scrolling).
    Examples:

    [ps2id url='#some-id' class='ps2id-speed-400']link text[/ps2id]
    [ps2id url='#some-id' class='ps2id-speed-1300 class-a class-b']link text[/ps2id]
    

Target id shortcode

There are 2 target shortcodes:

1. Anchor-point target

[ps2id id='some-id'/]

2. Wrapper target

[ps2id_wrap id='some-id']
your content...
[/ps2id_wrap]

You can use the wrapper target ([ps2id_wrap]) when you need to wrap content in a target id (same as adding an id attribute to some content). Doing this gives you better control over the highlighting of associated links.
In addition, wrapper target allows you to include other shortcodes within its content, e.g.

[ps2id_wrap id='some-id']
content... [ps2id url='#another-id']link text[/ps2id] 
more content...
[ps2id id='another-id'/]
content... 
[/ps2id_wrap]

Attributes

  • id (required) – Target id
    Examples:
    [ps2id id='some-id'/]
    [ps2id_wrap id='some-id'] your content... [/ps2id_wrap]
    
  • target (optional) – The element that’ll be considered as the actual target for highlighting
    This can be useful when you need better highlighting for target elements that have zero dimensions.
    Examples:
    The associated link will scroll to #some-id element but will be highlighted as if its target is the next adjacent div (the div immediately following #some-id element)
    [ps2id id='some-id' target='#some-id + div'/]
    
    The associated link will scroll to #some-id element but will be highlighted according to #another-id element
    [ps2id id='some-id' target='#another-id'/]
    

Previous versions

Development version: https://downloads.wordpress.org/plugin/page-scroll-to-id.zip

Pages: 1 2


390 Comments

Post a comment

Comments pages: 1 3 4 5

  1. Aaron Youngren
    Posted on February 14, 2019 at 22:38 Permalink

    I’ve been using this awesome plugin for a year now. That said, it seems like with the latest upgrade to WordPress, the scrolling seems broken. Scrolling from the menu is really clunky, and not smooth at all. I’m sure I’m just missing something. Do you have any idea why that might be happening?

    Reply
    • Aaron Youngren
      Posted on February 14, 2019 at 22:38 Permalink

      Sorry, example is here: https://greatcommissiondesign.us/nlbfcnewton

      Try clicking a menu link.

      Reply
    • malihu
      Posted on February 14, 2019 at 23:08 Permalink

      Hello,

      This is not about some upgrade. You have another plugin (mobile menu) which handles your links and prevents “Page scroll to id” from doing its thing. Don’t know if you installed (or updated) this plugin recently, but this is causing the issue.

      The script that does this is (function starts on line 162):

      ...plugins/mobile-menu/includes/js/mobmenu.js

      Try this:

      Go to “Page scroll to id” settings and enable/check “Prevent other scripts from handling plugin’s links” option.

      Save changes and test your page.

      Let me know if it works.

      Reply
  2. Thierry
    Posted on February 4, 2019 at 19:34 Permalink

    Hi and first of all, Thanks a lot for this plugin. It s doing a great job!

    Nevertheless I experience an issue on my website with the last link/target of the wordpress menu.

    All the five other targets are working perfectly and leads the visitor according to his click.

    The 6th anchor nevertheless brings back (a bit) below to the top of the page. I have checked the coding (the 6 of them are the same), and the settings and I dont understand why it’s not working with only one of them (the 6th of the menu list, called “blog”). I wonder if there is a limit of use per page or per menu.

    In case of doubt, you can have a look to my home page.

    I look forward to reading your advice. Many thanks in advance for your help.

    Thierry

    Reply
    • malihu
      Posted on February 14, 2019 at 23:12 Permalink

      Hello,

      Sorry for the late reply but it seems I somehow missed your comment.

      I checked your page and the “Blog” link points to a different page/URL, so it’s not handled by the plugin. I don’t know if you changed it, fixed it or need more help(?)

      Reply
  3. Stephan
    Posted on January 25, 2019 at 15:49 Permalink

    I love this plug-in, but since we upgraded to the WP Gutenberg edition the link/target button’s do not appear in the editor. Will there be an update that fixes that or will I need to use shortcode?

    Reply
    • malihu
      Posted on January 26, 2019 at 02:56 Permalink

      Hello,

      Right now, the best way to use the plugin with Gutenberg is with plugin’s shortcodes.
      “Page scroll to id” shortcodes do exactly the same thing as the toolbar buttons on the classic/old editor.

      With Gutenberg, you can create links and targets with shortcodes via Gutenberg’s shortcode block (under Widgets).

      Using the shortcodes gives you more control because you can use all the options for individual links and targets (offset, class and target attributes), the same way you did with plugin’s toolbar buttons on the old editor.

      This said, you can simplify your workflow by changing plugin’s “Selector(s)” option to:

      a[href*=#]:not([href=#])

      This way you no longer need to create links with the ps2id shortcode, as any link you create in Gutenberg or classic editor will be handled by “Page scroll to id” (as long as it points to an in-page target of course).

      In addition, Gutenberg provides the option to add an id to its heading blocks (under common blocks). Insert a heading block, click “Advanced” in block settings and insert the target value (i.e. id) you want in “HTML Anchor” field. You can then use this id in your link’s url.

      So if you use targets mainly on headings, you can also avoid using plugin’s ps2id target shortcode.

      FYI:
      I’m planning on adding a target block for Gutenberg and an inline link element in the future. I’ll need to do extensive testing for this and also consider what other updates Gutenberg will get, as they might add such blocks by default.

      I’m not rushing this because Gutenberg is fairly new and will probably get new similar blocks in the near future. I also prefer to let Gutenberg work for a while and have a stable API before using it.

      Sorry for the long reply!
      Hope this helps 🙂

      Reply
  4. Perica Bukic
    Posted on January 21, 2019 at 19:55 Permalink

    Hello,

    Thanks for the great plugin, is it possible to hide [ps2id id=’some-id’ target=”/] codes from visual editor? And replace it with anchor icon or something similar.

    Cheers

    Reply
    • malihu
      Posted on January 21, 2019 at 22:15 Permalink

      At the moment there’s no such feature. The main reason is that ps2id can be used as an anchor-point target ([ps2id id='some-id'/] ) and/or wrapper target ([ps2id_wrap id='some-id']your content...[/ps2id_wrap] ). Using icons for both can be a little tricky.

      Reply
      • Perica Bukic
        Posted on January 22, 2019 at 01:14 Permalink

        Alright, one more quick question, what’s the actual difference between using ps2id for setting anchors when compared to doing it with this: <li><a href="#anchor">Anchor</a></li>

        Reply
        • Perica Bukic
          Posted on January 22, 2019 at 01:17 Permalink

          Sorry, I meant with this:
          <h2 id="link">RandomLink</h2>

          Reply
          • malihu
            Posted on January 23, 2019 at 19:30 Permalink

            There’s no difference.

            Both work exactly the same. It’s just that the plugin provides ways (e.g. via shortcode) to add page anchors/targets without having to write HTML.

            Basically, you can add a target id anyway you want (with HTML, via shortcode etc.). In addition, most page builder plugins provide ways to add an id to their block elements, which does exactly the same thing.

            The only additional benefit when using the ps2id shortcode, is that it offers the target attribute, which you can use like this:

            [ps2id id='some-id' target='#another-id'/]

  5. LAtelier
    Posted on January 18, 2019 at 22:36 Permalink

    Hi there! Your plugin is pretty awesome, thank you! I am suing it with a super simple theme called Blankslate and with WP Bakery Page Builder. There isn’t any other plugin installed.

    One problem I have is with Microsoft Edge and on mobile: when the plugin is activated, the anchor links created with WPBakery Page Builder on the same page are not working. So for example if I have a Get Started button at the top which is supposed to scroll to the bottom of the page, it works on Chrome and Firefox but not on Edge and not on mobile. When I disable your plugin, the link works and “jumps” to the bottom section on both mobile and Edge. So that means the conflict is between your plugin and Page Builder probably. Can you try on your end and let me know if you are encountering the same issue?

    Let me know! Thank you for your time!

    Reply
    • malihu
      Posted on January 20, 2019 at 19:27 Permalink

      Hello,

      I haven’t encountered this problem with WPBakery Page Builder.

      The issue you describe might happen for any number of reasons. I can’t really know where the “Get Started” button links to and how exactly it works.

      Is it possible to post your page/site url so I can check what happens?

      If not, you can try changing plugin’s selector (“Selector(s)” option in plugin settings) so it doesn’t handle this particular link. For example, changing the “Selector(s)” option to:

      .menu-item a

      instructs “Page scroll to id” to handle only the links in your menu(s).

      You could also try enabling the “Prevent other scripts from handling plugin’s links” option and see if it fixes the issue.

      In general, “Page scroll to id” is browser agnostic. If it works in one browser, it should work on every browser but sometimes other scripts might also handle the links which might cause an issue. I’d need to see your page in order to see what exactly happens and help.

      Also, check this guide as it might help:
      http://manos.malihu.gr/using-page-scroll-to-id-with-wpbakery-page-builder/

      Reply

Comments pages: 1 3 4 5

Post a comment

Your e-mail is never published nor shared. Required fields are marked *

You may use these HTML tags and attributes:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
You can write or copy/paste code directly in your comment using the <code> tag:
<code>code here...</code>
You may also use the data-lang attribute to determine the code language like so:
<code data-lang-html>, <code data-lang-css>, <code data-lang-js> and <code data-lang-php>

css.php