Interface unusable with javascript disabled

subcribe

With a large features package (>10 content types, >20 views, >10 strongarm variables) even Core2Duo very slow on jquery based interface
So will be nice to make it possible work without javascript just like it was in old versions - wizard mode

subscribe

Thanks for the great module! It should make it into core for version 8.

I've got many variables, content types, panels, etc. and it is quite slow using as is. It would be nice to be able to use it without javascript in order to check many boxes quickly and then save.

Kristen

I can verify this is definitely a problem. I have a site moderately more complex than what podarok describes above, and features is virtually unusable because of the javascript-- I have to hit the 'wait for unresponsive javascript' button in firefox like 3-4 times for EACH checkbox check on my views page (I know I can up the timeout but then it just locks up completely until done).

I'm not sure what can be done to speed up the js, but running with js disabled should be option-- it always should be an option regardless of performance actually. Definitely not a feature.

Yup, agreed. Something's gotta be done about this. I have a feature with literally thousands of checkboxes and it takes me an almost an hour just to add/remove something from it due to the js loadtime. At least being able to turn off js would be a huge win here.

Agree with this, just ticking/unticking 1 box in a feature locks my computer up to a point of no return. Features in drupal 6 did not have this issue, I could add a component in less than a second on a site with roughly the same complexity!

@Rob_Feature if you have a feature with thousands of components, you may be outside the use case of a UI working well for you. You should seriously consider using the command-line tools if you can. It may be disconcerting at first, but it is *much faster*.

@Grayside commandline would be amazing. How do you add/remove items (for example, strongarm vars) from a feature using drush? I haven't seen any documentation on that (only features update or features revert)?

So, is this issue "support javascript being disabled" or "improve the UI for components that have an unreasonable amount of items"? They're two distinct things and going back and forth in one issue probably isn't the most useful.

@Rob_Feature every component of a Feature is listed in the .info file. It takes a certain amount of insight to connect the machine names to the component ids, but once you've looked at a few Feature "manifests" it starts to become really clear.

At that point, you can start playing: by adding or removing any of the features component items in the .info file, and running drush fu featurename, you will re-export all the components. Any that are removed will no longer appear.

At that point, a features-revert as you'd have to do with any update to a Feature module will push the changes live.

There are drush commands in various places for drush-only modification of features, but those haven't come together into a single recognized solution to my knowledge.

@Grayside thanks for the insight, I've tried to manually modify these and have made a mess before :) I'll have to look deeper.

@hefox: Apologies that I did take this off track with my rabbit trail. Let me refocus and reopen this:

The functionality doesn't work without Javascript. That should be the main issue here. One of the main reasons behind WHY it should work without javascript is because the .js interface is unusable with a large volume of checkboxes. Having a proper non-js fallback would help in this respect.

Please don't treat mine as an edgecase. There are others who have my issue as well (notice I'm not the one who started this issue) and, probably, in general it should work without js. I'll leave it as 'feature request' but will reopen (hows that for a compromise :).

Working on #1400298: Removing auto-detected components from a feature (UI update, removing Ajax) which should take care of this UI issue.