Uncategorized Creations

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.

Hi, thank for your feedback. All ideas are welcomed for further releases ??

Thank you for the feedback. we’ll integrate that in further releases.

Hi, at this time, no, we don’t have plans to support Wikis.

Hi. We have a branch with all prepared SQL done and we’re testing it. We’ll release it ASAP.

Bug fixed in version 1.4.

Hi, we added support for scheduled pages in version 1.4.

Hi, by “homepage”, you mean the site’s homepage?

Hi, thank you for using our plugin.

I believe you mean by “hiding comments” to disallow them (?).

The first you can do is to use the apm_tree_row_actions hook to add this action. For that you’ll have to create an addon. See the Other Notes tab.

I am going to check with Mathieu (our lead dev) for the bulk action request.

Regards.

You’re welcome. We hope that it will help for your projects.

Thank you for your feedback.

Inactive thread. Closing.

Thank you for this feedback. We’ll add prepare statements in our next release and let you know in this thread.

Grrr… That’s a perfect example ?? I didn’t see that you were talking of that thread ??

That’s clearly a bug we can’t reproduce.

Could you tell us which version of WordPress you’re using and what are the plugins installed to begin?

A good thing too is to have a look to the browser console to see if any errors might lurk in there.

It’s not about saying it’s not important. It’s just more efficient for everybody. One problem/people = one thread. This is why we request it (or sometimes the support moderators request it). It helps plugin authors and plugin users to keep track. It’s like avoiding duplicates in a bug tracking system. Again, it doesn’t presume that the bug will be more or less important (at least for us).