Helen Hou-Sandi

It’s been tested and we’ve updated the compatibility to the latest, which is now 4.9.4.

Hi! This plugin is still being maintained and we just did a new release yesterday. That said, it does not handle altering hierarchy, only the order of pages.

I’ve reproduced the issue, which seems to be related to any hidden columns, and opened an issue to track the technical fix over on GitHub: https://github.com/10up/simple-page-ordering/issues/11

Posts (and other non-hierarchical content types) are typically ordered chronologically and therefore do not have drag-and-drop ordering enabled. There are some workarounds available in the FAQ: https://www.ads-software.com/plugins/simple-page-ordering/#faq

Hi there! Sorry to hear this isn’t working for you. I don’t know for sure but I suspect WP Engine’s setup might not route requests to all filetypes through the rewrite rule that allows WordPress to handle them. So in this case their server sees a request for .txt file, tries to find the actual file, and doesn’t fall through to WordPress when it doesn’t find it. Could you perhaps ask them and see if that’s the case?

Hi all – sorry for neglecting this for so long. I’ll add this to my list of things to take a look at in the next couple of days. Glad to hear people find good use for it!

Strings in PHP (grossly simplified, things that aren’t numbers or special boolean words like true or false) need to be in quotes. That one of your examples works is very likely a coincidence.

There will be another plugin for making your own schemes very soon ??

Linked for information; am not expressing any opinion on what could or should be written where: https://www.slideshare.net/govloop/word-press-as-anopen-source-projectwp-as-an-open-source-project-nacin (in particular, slides 16 and 17).

If we leave the admin as it is and leave changing the scheme up to the user, we are in essence saying that they are equally good. If that is the case, then why are we changing it at all? That is a bad experience. If we have to instruct the user to change a scheme to the latest and greatest, that is a failed experience.

Sorry, I haven’t been able to take a look at forum messages for a while – had a baby and thus it’s toward the bottom of the priority pile. I know what the problem is, and the fix I would like to do is more substantial. It has nothing to do with wpdb::prepare().

Meant to add that I could be wrong that that would help, but an overall thought ??

Pagination means it has to do total found rows to calculate. If you don’t need pagination, you can set no_found_rows to true and it won’t do that anymore. Whenever I do a one-off WP_Query instance that doesn’t need pagination I set that arg for better performance.

You’d need to do this via AJAX, otherwise you will indeed get the whole page reload you experienced. I’ve been thinking about changes I’d need to make it work well when used that way, but I don’t see that sort of behavior being a part of the core plugin itself at any point, as it’s not something I’d want to generalize.

DB syncing across environments is often asking for trouble ?? Anyway, thanks for the consideration!