8.1.0 Express Object - Custom Display Order - Re-Order Entries 404ing
Permalink
I would like to use the Custom Display Order for my Express Object. Everything looks normal but when I click Re-Order Entries under Object Details the page will give me a Page Not Found. Everything else working as intended.
Using 8.1.0. Any suggestions?
Using 8.1.0. Any suggestions?
http://localhost:8888/index.php/dashboard/system/express/entities/order_entries/93daf31a-eca4-11e6-9196-3d3e80c55e85
Probably a bug. It should let you do a custom reorder, not show a page not found message.
I am also having this issue, and it might be related to another issue I'm having :https://www.concrete5.org/developers/bugs/8-1-0/bug-express-select-o...
We should probably band together and put this in a (my?) bug report to try to get this stuff fixed, as I am not finding the cause just yet.
We should probably band together and put this in a (my?) bug report to try to get this stuff fixed, as I am not finding the cause just yet.
I didn't find a solution. I ended up putting the data objects on the page in individual blocks and reordered them that way. Not ideal, but at least I can reorder.
Not sure how to band together on this. I usually just say I'm having a problem, then hope it gets shook out next update.
Not sure how to band together on this. I usually just say I'm having a problem, then hope it gets shook out next update.
From what I've been told by those in the dev team/community, the first step for reporting a bug is reporting it in the bug tracker on the concrete5.org website.
Short form, the link is here :https://www.concrete5.org/developers/bugs/8-1-0/...
To find this on the site, along the top, go to the pull-down menu "Community", then "Bug Tracker", takes you to the same page.
We can file bugs for different versions, but let's just do it for 8.1.0 for now.
So, I've also been advised that, in a sense, "banding together" is effective. What I recommend you do is create the bug report, link it here, and then I'll put my info in as confirmation that I'm seeing it, and this _should_ increase the traction we get on getting this fixed. Once it's recognised as affecting multiple people, it will be taken more seriously. It's more in an attempt to try to get people to make the issues reproducible.
Make sense? :)
Me, I'd rather see this fixed in v8.2.0, so let's see what we can do to make that happen.
Short form, the link is here :https://www.concrete5.org/developers/bugs/8-1-0/...
To find this on the site, along the top, go to the pull-down menu "Community", then "Bug Tracker", takes you to the same page.
We can file bugs for different versions, but let's just do it for 8.1.0 for now.
So, I've also been advised that, in a sense, "banding together" is effective. What I recommend you do is create the bug report, link it here, and then I'll put my info in as confirmation that I'm seeing it, and this _should_ increase the traction we get on getting this fixed. Once it's recognised as affecting multiple people, it will be taken more seriously. It's more in an attempt to try to get people to make the issues reproducible.
Make sense? :)
Me, I'd rather see this fixed in v8.2.0, so let's see what we can do to make that happen.
Is this a bug or should we expect this to work?