Title: Feature Request
Last modified: August 22, 2016

---

# Feature Request

 *  Resolved [patrick_here](https://wordpress.org/support/users/patrick_here/)
 * (@patrick_here)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/feature-request-270/)
 * First: Very good plugin!
 * **Feature Request:** Like another user said nine months ago, the first thing 
   one notices is “Trash Everywhere”. This almost defeats the purpose of the plugin
   which is to manage large quantities of pages. Sometimes there can be a need to
   keep Pages which have been put into the trash for a few weeks or so. During that
   time if all those trashed pages are showing up in the interface it really renders
   the plugin almost unusable. I find that I often have to disable the plugin entirely
   because of this. So I recommend that you make it possible in some way for the
   user to see pages without trashed ones. In the default editor there is a link
   to see only the Trashed pages. The other links (published/private) do not show
   the trashed pages. This is correct.
 * [https://wordpress.org/plugins/advanced-page-manager/](https://wordpress.org/plugins/advanced-page-manager/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Thread Starter [patrick_here](https://wordpress.org/support/users/patrick_here/)
 * (@patrick_here)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/feature-request-270/#post-5632976)
 * Another problem: I just discovered that Advanced Page Manager seems to store 
   its own hierarchy …independent of the WordPress Hierarchy. This seems incorrect
   to me – WordPress already provides for a built-in page hierarchy system by giving
   the user a way to specify a parent page. If your plugin is going to setup a separate
   independent hierarchy I think it should give the user the option of using the
   built-in hierarchy also. This way if -for example- the user is using the plugin
   on a pre-existing site that already has many pages arranged in a parent-child
   hierarchy, they will not have to go back through to every page and duplicate 
   the hierarchy for “Advanced Page Manager” (one mistake and the two systems are
   differing with each other). This is a big problem, as I see it.
 *  [Uncategorized Creations](https://wordpress.org/support/users/uncategorized-creations/)
 * (@uncategorized-creations)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/feature-request-270/#post-5633238)
 * Hi,
 * Thank you for your feedback.
 * As mentioned several times before, trashing in a page tree can be a serious problem
   as the trashed page has to retain its relations whatever tree manipulation is
   done later. This is why we didn’t implement it.
 * Regarding the separate tree management, you’re partially wrong. APM **DO** use
   the built-in WordPress hierarchy. We preserve the user content at all cost. And
   this is why your pages remain without problem if you uninstall the plugin and
   also how we grab pre-existing page relations. However, the built-in hierrarchy
   is pretty badly done for fast display. This is why we maintain a second hierarchy
   fully synchronized to speed up the display.
 * Regards.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Feature Request’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/advanced-page-manager_709cd7.svg)
 * [Advanced Page Manager](https://wordpress.org/plugins/advanced-page-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/advanced-page-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/advanced-page-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/advanced-page-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/advanced-page-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/advanced-page-manager/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Uncategorized Creations](https://wordpress.org/support/users/uncategorized-creations/)
 * Last activity: [11 years, 2 months ago](https://wordpress.org/support/topic/feature-request-270/#post-5633238)
 * Status: resolved