-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-ordering fields does not work #1055
Comments
After a bit of digging, i've found:
|
Is that an officially supported CWP extension? or one defined in your custom code base? |
@emteknetnz I've tried it on a fresh CWP install. It does not appear to be affected. So i guess the offending code is in our code base, or an extension we've got. feel free to close this. i think it warrants more investigation on our end |
Based on the above I'll close this issue. We can re-open it if a problem is found with a supported extension. |
We're getting more angry CMS admins not being able to edit user forms. From what I can tell this is a duplicate of #773 |
Hi @torleif, are your replication steps still the same of creating a page with 10 or so fields on a production system? You've mentioned using the CWP recipe, if that's the case I'm not sure how related to #773 it would be. For me, running the following can be done in under 7 seconds on a small CWP stack:
|
@brynwhyman yes the steps were the same, a modest 10 or so fields. though a key step was re-ordering one or more of the fields |
Sorry forgot to mention that, I also tried replacing the 'Save the page' step with 'Re-order a field' and saw the same result of completing within ~7 seconds. |
Steps to reproduce:
Our production system times out when someone reorders an item (by drag and dropping it in the CMS)
While on dev mode, I've got this response time:
this is on a modest page with about 10 or so form fields. I've taken a xdebug profile of a reorder, so i might be able to give some more insight into why it's failing
The text was updated successfully, but these errors were encountered: