Great! Hope they can fix the bug on their end.

Both are essentially HTML pages of your website, but there are some assumptions around both which is the difference you see here. Posts are meant to be time based content that you push out to readers – like a journal log. Pages are forever live content. There are differences in URL, but that can be tweaked in Settings > Permalinks in WordPress admin panel.

This is why default sorting for posts is chronological – most recent on the top.

Comments are by default not enabled on pages, but you can enable them if you require.

Whether post or page has a sidebar or not, is totally dependent on how the WordPress theme you are using, has chosen to show them. Some themes would let us choose layouts as well, so you can have sidebar no pages as well.

Seems like $current_options is an empty string rather than an array, which causes an issue when code tries to lookup an entry inside of it.

You can try to save settings in your theme, where you control the banner title for category or something & that should fix it. Otherwise, to fix it in code, I would need to see the whole file but it would be something like:

if isset( $current_options['banner_title_one_category'] ) {
    $h1 = $current_options['banner_title_one_category'];
}
if isset( $current_options['banner_title_two_category'] ) {
    $h2 = $current_options['banner_title_two_category'];
}
if isset( $current_options['banner_description_category'] ) {
    $bd = $current_options['banner_description_category'];
}

I have reproduced this on my install as well. This is definitely a bug with pagination block.

I found two such issues reported: https://core.trac.wordpress.org/ticket/51662 and https://core.trac.wordpress.org/ticket/52419

WordPress automatically redirects urls without trailing slash to trailing slash ones, so you would be fine without doing anything, if you are ok with accepting final URLs with trailing slash included.

If not, then you would have to change it in every place where it still includes the trailing slash. I think in this instance, the pagination plugin you are using doesn’t account for your configured permalink to not include the trailing slash. It should have a filter with which you can change the URL for pages. Else you can file an issue with the plugin author.

Are there other instances which still includes the trailing slash?

Yes, functions.php would work. Also, you would need to pull out properties from $post object like $post->post_title to make up your data before you send it.

Available properties on post object:

object(stdClass)
      public 'ID' => int
      public 'post_author' => string
      public 'post_date' => string
      public 'post_date_gmt' => string
      public 'post_content' => string
      public 'post_title' => string
      public 'post_excerpt' => string
      public 'post_status' => string
      public 'comment_status' => string
      public 'ping_status' => string
      public 'post_password' => string
      public 'post_name' => string
      public 'to_ping' => string
      public 'pinged' => string
      public 'post_modified' => string
      public 'post_modified_gmt' => string
      public 'post_content_filtered' => string
      public 'post_parent' => int
      public 'guid' => string
      public 'menu_order' => int
      public 'post_type' => string
      public 'post_mime_type' => string
      public 'comment_count' => string
      public 'filter' => string

Do mind that any syntax error in that file and your site would stop loading, so make sure you are able to change it again when you save it i.e. changing that file other than the WP file editor.

• This reply was modified 1 year, 1 month ago by Ashish Kumar (Ashfame).

Technically, a URL with / and without it are considered two different URLs, which is why should stick with one version of URL to avoid duplicate content issues.

WordPress likes to have the trailing slash and there is no harm in it. Its not productive to change links everywhere in code just to not have the trailing slash since it has no impact on SEO.