jannisg / statamic-pagereorder Goto Github PK

Hi, I have added this to my Statamic Themes plugin resources hope you don't mind, its all on GitHub now so feel free to edit things and add to it as you want.

With Statamic v1.10.3, the child of a sub-page unable to re-order / generates error.

I get the following error...

Here's a quick video showing the error.

Below, I have a picture of the page layout, and the one with a green box, I can re-order. The level with a red box, I am unable to re-order.

NOTE: I am using the latest version of the add-on, v.0.3.

When reordering child pages of another child page, extra folders are being created.

Before reorder:

After page reorder through the control panel:

When reordering entries in the dashboard the child pages for entries that have then reopen if they were closed. It would be nice to respect the display state of the entries and keep them closed if they were originally closed.

Unless I'm doing something wrong it doesn't seem to work in v1.5b8 but from the looks of things you're probably aware of that.

Sorry, this is not an issue, just an idea.

Currently if we need to change the position number of entries (when not ordered by date) we have to (1) open the entry, (2) change the position field and (3) save and fix the numbering conflicts since now we have number duplicity. Quite puzzling and annoying for the user. It would be 100 times better and smarter to have a drag and drop mode to quickly change the ordering of entries. In my projects, ordering entries are always more important than ordering pages. That because the webdesigner is supposed to create the layout, which includes the page ordering. 90% of clients are never like: "Oh, I think I want to put the About Us page first". Usually they don't even think about page ordering. But the entries are inserted by the client, so he should be able to quickly reorder them as he pleases. For example, reorder the slides in the home page, or a restaurant manager reorder dishes in the food menu page.

Running Statamic 1.5RC1. Installation has no effect on the Pages area of the CP. Tested in Chrome 27.0, Safari 5, Firefox 20.0. This is all on a local MAMP server.

Screenshot of my install, in /_add-ons/:

Let me know if I've done it incorrectly, thanks!

Hi.

It would be awesome to be able to reorder subpages.

My client wants to reorder pages, but the only possibility is to alter the slug.
Which is not very usability friendly.

Wouldn't this be easy possible trough grabbing the foldername number of the subpage and alter this number trough the reorder plugin?

Thank you

I'm trying to use the add-on with Statamic 1.7.3, but it's throwing a javascript error and won't save. Any idea what might be causing this?

Thanks!

Tried build 0.3.0 on Statamic 1.10.3 with Chrome 40.0. Statamic installed in a subfolder.

After accounting for the subfolder problem in issue #9 reordering childpages worked fine, but I got an error if I tried reordering the top level folders. The error was cast at line 150 in hooks.pageredordering.php.

I managed to fix it by changing line 91 from:

        if ( isset($page->url) && $page->url == $url ) {

To:

        if ( isset($page->url) && substr(Config::getSiteRoot(),0,-1).$page->url == $url ) {

The substr is there to remove an extra /. There is probably a nicer way of doing this, but should give you an idea.

Love the add-on! :)

Tried build 0.3.0 on Statamic 1.10.3 with Chrome 40.0.

After dragging and dropping a page in the control panel I get the error:

There was an error saving your page order. Please try again.

In the console I get the error:

POST http://localhost/TRIGGER/pagereorder/reordersubpages 404 (Not Found)

The correct path when i have it installed in a subfolder should be:

http://localhost/subfolder/TRIGGER/pagereorder/reordersubpages

Need som extra magic on line 111 in jquery.page-reorder.coffee that account for the site root I presume :)

Is it possible to limit the number of leading zeroes based on the number of pages/entries in the current context? In other words, having only a single leading zero (01-) rather than several (0001-) when there are under 100 pages. (And so on.)

It's an aesthetic issue, to be sure. But then, that's why we got in this racket in the first place :)