Question: So for previous and next posts I used this from wordpress codex

```
<div class="navigation">
    <p>
        <?php posts_nav_link('&#8734;','Go Forward In Time','Go Back in Time'); ?>
    </p>
</div>

```

I want to change that.. in the wp-admin, I used on settings -> reading -> Blog pages show at most = 5 so I wanted to have a button to click on and load like 5 more posts, every time you click on the button and you are on the bottom of the page ... to give you an example cuz my english is not that good..

<https://instagram.com/menwithclass>

at first you see the some posts and if you scroll down, you click on a button and it loads more posts..

is that somehow possible to load the posts on the same page?

Answer: 
### **Display\_errors** should be disabled on a production website.

WP Scan accesses `wp-includes/rss-functions.php` directly, and this is it's source code, as of WordPress 4.9.7:

```
<?php
/**
 * Deprecated. Use rss.php instead.
 *
 * @package WordPress
 */
_deprecated_file( basename(__FILE__), '2.1.0', WPINC . '/rss.php' );
require_once( ABSPATH . WPINC . '/rss.php' );

```

When it is accessed directly, `_deprecated_file()` function does not exist, so it throws a fatal error.

The solution is to disable `display_errors` on a server level. If your PHP run under mod\_apache, you can do it by adding this line to your main .htaccess file:

```
php_flag display_errors off

```

If you use PHP-FPM, you will probably have override php.ini in your local public\_html folder.

### Also, WordPress is aware of that:

<https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/#why-are-there-path-disclosures-when-directly-loading-certain-files>
*Theoretically,* what I'm about to tell you is dangerous and probably shouldn't be done, if you're doing things the "proper Wordpress way".

*Practically*, this works for our production environment.

The file `rss-functions.php` is deprecated, and redirects to `rss.php`.

The file `rss.php` has been deprecated since v3.0.0, and internal comments recommend you use SimplePie instead.

So the file `rss-functions.php` can be safely deleted **as long as** you don't have an old, legacy installation, and if you have no plugins which depend on this file.

Alternatively, comment out line 8 in that file.

---

From a security standpoint, you should also definitely implement @MarkKaplun's suggestion above, as this file isn't intended to be hit directly by the browser.

---

BTW, I agree with you that divulging the full path is a security risk; we keep out WEBROOT at a custom path for that reason.