Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
7 Jun 2009 at 20:58 UTC
Updated:
28 May 2010 at 21:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
dawehnerWouldn't it be better to place the button in the live preview form? See the attachment
Comment #2
ccrackerjack commentedI'd like to see this feature too which I think should be there from the beginning. Right now I have to wait for 5 to 10 secs for each field I edited (up to few mins when I'm at office with slower Internet connection) and its annoying and crazy time consuming.
Comment #3
tm01xx commentedYes, me too. We should have a choice whether we want to live preview or not. For me, most of the time I dont need it really.
Thanks,
Comment #4
dawehnerHere is the patch
Comment #5
figover commentedGood work, This is working for me.
But when i import this patch, an error is coming on command line
"
(Stripping trailing CRs from patch.)
patching file includes/admin.inc
patch unexpectedly ends in middle of line
Hunk #2 succeeded at 502 with fuzz 1.
"
Why this error is coming?
If i am doing something wrong, please guide me.
Comment #6
dawehnerThe problem is that views has patched the full admin.inc file to unix line endings. I will rerole the patch for 2.x
Comment #7
merlinofchaos commentedI can still apply the patch either way just by running it through a quick conversion, so sticking this back into the review queue.
Comment #8
merlinofchaos commentedDisabling live preview should actually happen elsewhere. This disables live preview after the AJAX call has already been made. That seems very silly. It also means you can't live preview on request, so I would consider this actively harmful.
What you really want is to disable *automatic* live preview. That should be a general setting on the tools >> settings tab.
Comment #9
fabio84I'd like this feature, too. I think live preview may be the cause of server slowdown I experienced sometimes.
I think you should be able to see the generated SQL code, without executing it. So you can check what query it's going to execute, check what may slow it down, and optimize it before it can bring down the server.
Comment #10
dawehnerEarl suggest to disable the preview request.
I let enabled the display of the request, but denied the querying and the rendering of the preview.
I like your idea to just disable the query/rendering but still display the query itself. Any other ideas?
Comment #11
dawehnerAnother try :)
This time there is no ajax request fired
Comment #12
stborchertDecide which one to use:
* Nearly all uppercase?
* First word uppercase?
Apart from that: looks really good (and nearly RTBC).
Powered by Dreditor.
Comment #13
dawehnerNext version
I used: * First word uppercase?
Comment #14
dawehnerHuch another try. I was in the wrong directory / uploaded the wrong file
Comment #15
stborchertRTBC from me.
Comment #16
merlinofchaos commentedCommitted to 6.x-2.x and 6.x-3.x
I admit I didn't try, as I assume this will not directly apply to 7.x-3.x =)
Comment #17
webel commentedSubscribe, very interested in this feature.
Comment #18
dawehnerPorted and fixed existing issues with the non-static form id.