Problem with moving pages in sitemap
Permalink 1 user found helpful
After having upgraded from version 5.6.1.2 to 5.6.2 i'm experiencing a problem with moving pages inside the sitemap. When i try to move a page by drag and drop to another position inside a parent page, it seems to work at first, but the animated icon for the parent folder is rotating forever and the new position of the moved page doesn't get saved. The problem seems not to be browser related (it exists with the latest versions of firefox as well as internet explorer and safari for windows).
While i can still copy a page into another page, it's not possible to change the position of the page under the parent page. This is also true for flat view.
Can anybody confirm that problem?
Thank you,
Michael
While i can still copy a page into another page, it's not possible to change the position of the page under the parent page. This is also true for flat view.
Can anybody confirm that problem?
Thank you,
Michael
Same problem here, any update on this issue?
Can anyone else confirm that problem? Just to make sure before reporting it as a bug.
Problem resolved!
At least in my case, the add-on "Dashboard Maximizer" has been causing the issue. It took me some time to find out. As soon as Dashboard Maximizer was uninstalled, the problem was gone.
I have reported it to the author of Dashboard Maximizer. Since this is actually a very useful add-on, i hope a future update will evoid interfering with the drag&drop page sort functionality of concrete5.
Michael
At least in my case, the add-on "Dashboard Maximizer" has been causing the issue. It took me some time to find out. As soon as Dashboard Maximizer was uninstalled, the problem was gone.
I have reported it to the author of Dashboard Maximizer. Since this is actually a very useful add-on, i hope a future update will evoid interfering with the drag&drop page sort functionality of concrete5.
Michael
interesting!! I'm using 5.6.1.2 with dashboard maximizer installed and can do this with no problem...
This is strange!
I have tried to install and uninstall the add-on on two different installations (both 5.6.2.1, installed on two different servers) - each time with the same result. As soon as Dashboard Maximizer was installed, sorting pages by drag&drop refused to work (couldn't be saved).
The author of Dashboard Maximizer already kindly replied
http://www.concrete5.org/marketplace/addons/dashboard-maximizer/sup...
Michael
I have tried to install and uninstall the add-on on two different installations (both 5.6.2.1, installed on two different servers) - each time with the same result. As soon as Dashboard Maximizer was installed, sorting pages by drag&drop refused to work (couldn't be saved).
The author of Dashboard Maximizer already kindly replied
http://www.concrete5.org/marketplace/addons/dashboard-maximizer/sup...
Michael
The problem is now effectively resolved by an update to Dashboard Maximizer 2.0.4
The issue was due to changes in Concrete5 5.6.1 and has been kindly resolved by the author of the free Dashboard Maximizer add-on, arcanepain, by releasing an update to version 2.0.4. Thanks again for the lightning fast support and for updating the add-on within just a couple of hours! Wow!
Michael
The issue was due to changes in Concrete5 5.6.1 and has been kindly resolved by the author of the free Dashboard Maximizer add-on, arcanepain, by releasing an update to version 2.0.4. Thanks again for the lightning fast support and for updating the add-on within just a couple of hours! Wow!
Michael
Hello guys,
I have been following this posting since I am having the same issue, and unfortunately I am not using Dashboard Maximizer plug in! This now gives me some light that it might be another plug in, but the issue is not only due to Dashboard maximizer.
I will do some more testing on my site
I have been following this posting since I am having the same issue, and unfortunately I am not using Dashboard Maximizer plug in! This now gives me some light that it might be another plug in, but the issue is not only due to Dashboard maximizer.
I will do some more testing on my site
Hi,
it's very likely that other add-ons are effected by these changes too. Just to quote the author of the Dashboard Maximizer add-on:
"...It would seem that somewhere along the line - probably in the 5.6.1 release - something was re-jigged (probably for the sake of performance) in the Request library. Looks like package on_start() methods are now called before C5 has decided what/if we have a valid page for a request, meaning that alot of the page checking i'm doing in there is now redundant and, worse, is falling over altogether when tripped by a tools request (eg. what sitemap_update.php is doing in the background of that sitemap page re-order AJAX request).
Could go into more detail, but I can see exactly what's going wrong...i've rebuilt what the add-on is upto in the package's on_start() method and, once i've tightened it up a little more, i'll submit a new version to the marketplace for latest C5 versions. :)
We might have a bigger problem though as it's entirely possible that other add-ons will be tripped up this slightly change in functionality too. When I get more time i'll dig a little deeper and see if I can identify exactly what core changed caused the trouble..."
At least as regards the Dashboard Maximizer add-on, the problem has been solved.
it's very likely that other add-ons are effected by these changes too. Just to quote the author of the Dashboard Maximizer add-on:
"...It would seem that somewhere along the line - probably in the 5.6.1 release - something was re-jigged (probably for the sake of performance) in the Request library. Looks like package on_start() methods are now called before C5 has decided what/if we have a valid page for a request, meaning that alot of the page checking i'm doing in there is now redundant and, worse, is falling over altogether when tripped by a tools request (eg. what sitemap_update.php is doing in the background of that sitemap page re-order AJAX request).
Could go into more detail, but I can see exactly what's going wrong...i've rebuilt what the add-on is upto in the package's on_start() method and, once i've tightened it up a little more, i'll submit a new version to the marketplace for latest C5 versions. :)
We might have a bigger problem though as it's entirely possible that other add-ons will be tripped up this slightly change in functionality too. When I get more time i'll dig a little deeper and see if I can identify exactly what core changed caused the trouble..."
At least as regards the Dashboard Maximizer add-on, the problem has been solved.
okapi,
Thanks, I did not get to read the developers response! but it makes sense, I will uninstall and review all my packages to see which one is the culprit.
Thanks, I did not get to read the developers response! but it makes sense, I will uninstall and review all my packages to see which one is the culprit.
I'm having the same issue on a few different sites I've upgraded to 5.6.2 and I'm not using the Dashboard Max package mentioned.
I manage a bunch of sites built in concrete and they all have various different packages, thankfully I've not updated them all to 5.6.2 yet but I'm not going to go around updating then uninstalling and re-installing packages on a zillion sites to find this solution. Hopefully the core team can resolve this so I can just upgrade to a 5.6.2.2 or whatever and not sweat about it, so subscribing here for further notifications to come hopefully.
FWIW: Error in the console reports a 500 Failed to load resource
.../tools/required/dashboard/sitemap_update.php...
I manage a bunch of sites built in concrete and they all have various different packages, thankfully I've not updated them all to 5.6.2 yet but I'm not going to go around updating then uninstalling and re-installing packages on a zillion sites to find this solution. Hopefully the core team can resolve this so I can just upgrade to a 5.6.2.2 or whatever and not sweat about it, so subscribing here for further notifications to come hopefully.
FWIW: Error in the console reports a 500 Failed to load resource
.../tools/required/dashboard/sitemap_update.php...
Phew...just submitted the bug!
See here for full explanation (sorry for the essay!)
http://www.concrete5.org/index.php?cID=535792...
Explains what's going wrong, how I fixed it and how we could, potentially, remedy in the core's request library.
Sure the core guys could shed a little more light on when things were shuffled in the startup routine or the request library (i'm guessing maybe tools requests were moved to be handled before hitting page/collection stuff at some point for the sake of performance?) and whether or not my suggested array() check would do the trick to avoid certain multiple cID edge-cases causing this to happen.
See here for full explanation (sorry for the essay!)
http://www.concrete5.org/index.php?cID=535792...
Explains what's going wrong, how I fixed it and how we could, potentially, remedy in the core's request library.
Sure the core guys could shed a little more light on when things were shuffled in the startup routine or the request library (i'm guessing maybe tools requests were moved to be handled before hitting page/collection stuff at some point for the sake of performance?) and whether or not my suggested array() check would do the trick to avoid certain multiple cID edge-cases causing this to happen.
