Non-responsive when adding new fields to the views_data_export

Created on 14 April 2015, over 9 years ago
Updated 6 December 2024, 13 days ago

I have 23 fields in my export view right now. I'm trying to add a few more but its non-responsive. When I click to add fields, i can choose the fields I want to add, then I click "Apply this display". The screen comes back and the button is then changed to "Add and configure fields". So far so good. Then when i click "Add and configure fields" the little drupal wheel comes up for about 1 second and then the wheel disappears and the screen never changes to go to the configure screen. I click it another dozen times or so thinking maybe the server just isn't responding quick enough. Nothing happens. I ran a test to add this same field on the regular view that the views_data_export is attached to - the screen view - and the field adds fine. Obviously adding fields of the views_data_export view has worked before because I already have 23 fields and have done this before. This problem just started today.

Any ideas? We are on Version 7.x-3.0-beta8.

πŸ› Bug report
Status

Closed: won't fix

Component

User interface

Created by

πŸ‡ΊπŸ‡ΈUnited States stsharp

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • πŸ‡¬πŸ‡§United Kingdom steven jones

    Sorry for the lack of attention to your issue, please accept my apologies.

    Drupal 7 is going to be end-of-life'd by the community in approximately 1 month. β†’

    As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on πŸ“Œ Close down Drupal 7 issues Active .

    If you feel like this issue has been closed by mistake, please do comment about re-opening it.
    If you feel like the ticket is still relevant for the 8.x-1.x version of the module, then please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.

    Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated.
    The Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :)

Production build 0.71.5 2024