I'm not sure if this belongs to feature request or to a bug report, and I also think this straddles the Code component and the User Interface.

We have a Drupal site that is for relators. And it has a custom node type for property, which as you can imagine has lots of different pieces, like prices, information on owners, legal numbers, maps, image attachments, video tours, PDF brochures etc... lots of fields, at this moment we have 86 fields in content type property.

When we want to move a field from disable to a region while managing a display
(E.G.: http://ourdevsite.com/admin/structure/types/manage/property/display/print)
We drag the element or use the select box for region to select the region we want on the field row we want to move. This process starts an Ajax process, that takes on the order of 1 or 2 minutes to complete. During which we can do nothing else to the layout. Loading the page it self is slow but reasonable 25 seconds.

I think the purpose of using ajax is to make things faster not slower. Worse we have NO way of turning off the ajax for this site, short of digging around in the code, which looks pretty scarry.

Ok, so we know we're pushing the envelope with a lot of fields, but I really think there should be some way to *not* use ajax for the form, particularly when it's costing 2 to 4 times as much wait time!!

Any chance anyone else has experience this slow down, or any chance we can get some kind of way to turn off the ajax? We're thinking about updating DS to the 7.x-1.5 later today, since we just saw it was out.

Comments

swentel’s picture

swentel commented

Well, the ajax stuff is done 'thanks' to Field UI. IIRC, you can toggle the 'Show row heights', the javascript is going to be turned of and you can actually select the region and weight through select dropdowns.

Question, do yo have field templates enabled as well ? If not, than this is just purely field ui (try not using a ds layout and normally moving a field from hidden to display should take long as well. If you're using field templates, than I can imagine why it's slow since we are adding a lot of form elements on the screen. This is going to be solved in a new branch (it's called restructure at this point and has more or less working code, but is not all ready for production). So yeah, we're working on that a little bit. Other than that, I can only say myself, that in some occasions, doing an ajax call isn't the most performant option, but that's how Drupal chose to do it.

swentel’s picture

swentel commented
Version: 7.x-1.4 » 7.x-2.x-dev
Status: Active » Fixed

This has been completely reworked inthe 7.x-2.x branch, so less form fields coming from Display suite are loaded. The ajax is still triggered as this is Field UI itself, but it should be better now at least.

Note: won't backported to 7.x-1.x though (and is almost impossible anyway).

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

gboggs’s picture

gboggs commented

Compared to the Content Type UI with no display suite, the AJAX call for moving a fields is still incredibly slow.

Other than disabling javascript when building DS modes, are there any work arounds for this? Merely clicking show row weights does not help.

gboggs’s picture

gboggs commented
Issue summary: View changes

missing punctuation