Opened 10 years ago
Closed 9 years ago
#32094 closed defect (bug) (fixed)
Unable to drag widgets down page past certain length.
Reported by: | tw2113 | Owned by: | azaozz |
---|---|---|---|
Milestone: | 4.2.3 | Priority: | normal |
Severity: | normal | Version: | 4.2 |
Component: | Widgets | Keywords: | has-patch needs-testing fixed-major |
Focuses: | javascript, administration | Cc: |
Description
Confirmed in 4.2 by myself and at least a couple other people. When you have enough available widgets to make the page pretty long, it becomes impossible to drag an active widget down past a certain point in the page. It'll behave like an invisible floor that you can move the widget along horizontally, but not any further down.
Attachments (1)
Change History (34)
#2
@
10 years ago
Updated a site to 4.2
Couldn't reproduce, I lengthened the page to 10792px in height via lots of expanded Inactive Widgets
Did not see any invisible floor, dragging stops at footer as expected.
#3
@
10 years ago
Client confirmed bug on IE 9 on Windows 7.
And I can confirm bug on Chrome 42.0.2311.135 (64-bit) using Max OS X.
Looks like it stops once you hit the "Inactive Widgets" area.
#4
@
10 years ago
It happens to me with WP 4.2.1 in Firefox 37.0.2, Chrome 42.0.2311.135 m (64-bit), and IE 11. For me, it stops well before Inactive Widgets.
#5
@
10 years ago
I'm experiencing the same issue on 4.2.2. The floor doesn't seem to be related to where the Inactive Widgets area starts. I've noticed that if you make your browser wider, the floor moves further down the page.
#6
@
10 years ago
- Keywords has-patch needs-testing added
- Milestone changed from Awaiting Review to 4.1.3
Reproduced, 32094.patch fixes it here. Also fixes the "disappearing" widget when dragging over a closed sidebar, and "unsticks" the admin menu when all widget containers and sidebars are folded (so the main page becomes shorter than the menu).
#7
@
10 years ago
- Owner set to azaozz
- Resolution set to fixed
- Status changed from new to closed
In 32480:
#8
@
10 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Reopen for 4.2. Still needs some more testing.
This ticket was mentioned in Slack in #core by netweb. View the logs.
10 years ago
#12
@
10 years ago
I have a large amount of widgets on admin page and am experiencing this problem. I manually made the patches but I don't see a change. I've searched and searched to see what I'm doing wrong. It appears to me that load-styles.php and load-scripts.php arent picking up the edited files. Can someone point me in the right direction so I can help test this patch? I don't think I've applied the patch correctly or I'm missing a step.
#13
@
10 years ago
@doo_it, I wager your admin is still using the compiled/minimized copies of the js/css files, that the patch from @azaozz didn't apply anything to.
You should be able to get the non-minimized versions by setting SCRIPT_DEBUG to true in your wp-config. just define it the same way you do with WP_DEBUG
#14
@
10 years ago
Thank you @tw2113 that did the trick. I was hunting around for something like that and was coming up short. I had found CONCATENATE_SCRIPTS but that wasn't working. I've done some testing and so far the patch is working for me. Our content team here uses the widget admin page almost daily so if any more bugs show up I'll report back. We have around 180 sidebars available on the widget admin page.
#15
in reply to:
↑ description
@
10 years ago
Replying to tw2113:
Confirmed in 4.2 by myself and at least a couple other people. When you have enough available widgets to make the page pretty long, it becomes impossible to drag an active widget down past a certain point in the page. It'll behave like an invisible floor that you can move the widget along horizontally, but not any further down.
Yes I also tested it. And its issue after WP 4.2.1
#18
@
10 years ago
@azaozz,
The same issue occurs with widgets in the Dashboard screen if there are too many notifications on top.
See screencast for further clarification: https://dl.dropboxusercontent.com/u/21559010/Screencast_dashboard_widgets_drag_bug.mp4
I fixed it by changing the sortable initialization in dashboard.js from this:
$( '.meta-box-sortables' ).sortable( 'option', 'containment', 'document' );
To this:
$( '.meta-box-sortables' ).sortable( 'option', 'containment', '.wrap' );
#20
@
10 years ago
This has been a huge problem for me on several sites, with different themes, plugins, etc. The only common property is WP 4.2.XX. And yes, have tried a whole lot... see https://wordpress.org/support/topic/cant-drag-widgets-to-inactive?replies=27#post-6962077
#21
@
10 years ago
Just to note that I am experiencing this same issue... i posted about it in the How to and Troubleshooting support forum 3 days ago... With no responses to that post I have been going around and around since then, trying to discover what is going on... The senior admin for my hosting service has been helping, it seeming it might be a server issue... None of my google searches ever turned up this ticket...
Tonight I got this message from the head tech:
I was finally able to reproduced your issue on my end doing some different testing at different resolutions and so was another senior admin that I had doing testing throughout the day. The issue does not appear when you’re running a high resolution such as 2560 x 1440 that all of our systems run.
The issue you are having is actually a Wordpress related bug that was reported 4 weeks ago and has not been fully resolved yet. You can view the bug tracker that Wordpress referred me to regarding the issue by visiting this Core Trac URL; https://core.trac.wordpress.org/ticket/32094
That brought me here. If there is testing I can do to help let me know... I have a test installation I set up to try and figure this out, no thought at all that it might be a WP bug...
Kind regards...
#22
@
10 years ago
Adding that this occurs for me in four browsers, Chrome, Firefox, Safari and Opera...
And also that the zooming out workaround mentioned in the thread @OctoTooT links to above actually works for me... This seems to maybe have some relationship with how the issue also does not apparently occur on high resolution monitors...?
#23
@
10 years ago
Another "fix" is to minimize active widgets by moving cursor near the top right part on the active widget area and "clicking" the minus sign.
Problem is definitely occurs on multiple browsers - have same issue with Firefox and Chrome.
#24
follow-up:
↓ 25
@
10 years ago
- Keywords fixed-major removed
- Severity changed from normal to major
Same issue. Can't drag any widget past a certain point on the screen. The patch code above didn't do anything. Issue persists. When is a workable patch planned to be released?
Zooming out does work for me as well, btw.
#25
in reply to:
↑ 24
;
follow-up:
↓ 29
@
10 years ago
- Focuses javascript added
- Severity changed from major to normal
Replying to igotkat:
Same issue. Can't drag any widget past a certain point on the screen. The patch code above didn't do anything. Issue persists. When is a workable patch planned to be released?
Make sure you have SCRIPT_DEBUG set to true, else the patches above will do nothing. Patches above need to be applied to trunk (not to 4.2.2, the current stable) as well.
This is not a major severity issue. Relowering.
#26
@
10 years ago
Confirmed in multiple browsers after reports from WordPress.com VIP users. Would love to have a patch for this as soon as is practical.
#28
@
10 years ago
Still have same issue on multiple sites using different plugins (one site doesn't even have any - just for grins), different themes, etc.
This has affected all my WP sites with version 4.2.xx
The best work-around I have found until this gets resolved is to minimize the Available Widgets section by moving your cursor near the upper right side and clicking the small up arrow. Then you should have the Inactive Widgets section appear much higher on your monitor and you can drag your sidebar widgets with no problems.
#29
in reply to:
↑ 25
@
10 years ago
Replying to chriscct7:
Replying to igotkat:
Same issue. Can't drag any widget past a certain point on the screen. The patch code above didn't do anything. Issue persists. When is a workable patch planned to be released?
Make sure you have SCRIPT_DEBUG set to true, else the patches above will do nothing. Patches above need to be applied to trunk (not to 4.2.2, the current stable) as well.
This is not a major severity issue. Relowering.
May not be a severity issue, but it sure is a pain in the meantime.
#31
@
9 years ago
I'm not a coder and I'm not sure how to apply this patch to my website. Can someone explain the process to me or point me to a tutorial. I've been having this issue as well.
Confirmed using Mac OS X Version 44.0.2378.0 canary (64-bit)