at HTMLInputElement.dispatch (load-scripts.php?c=1&load=jquery-core,jquery-migrate,utils,plupload&ver=4.7.4:3)
at HTMLInputElement.r.handle (load-scripts.php?c=1&load=jquery-core,jquery-migrate,utils,plupload&ver=4.7.4:3)
4-7 Days Ago 39616 Twenty Seventeen: Issue with Header Video Bundled Theme 4.7.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2017-01-17T19:59:04Z 2017-04-24T07:11:14Z "via https://wordpress.org/support/topic/issue-with-the-header-video/#post-8665585
Upgrade of the theme and the WP (4.7.1) messed up the header video.
Now there’s a big black bar at the top and bottom (wasn’t there in the previous version(s)).
I've checked on a variety of browsers (all updated to the newest versions):
4-7 Days Ago 40146 Starter content can be silently published with other themes Customize 4.7 normal normal Future Release defect (bug) new reporter-feedback 2017-03-13T18:07:33Z 2017-04-24T05:37:16Z "To replicate on a fresh install, open the Customizer with Twenty Seventeen active, preview a different theme, then ""Save & Activate"" the new theme. All of the Twenty Seventeen starter content will be published along with the new theme.
The potentially confusing part of this behavior is that starter content might or might not have been in the preview, depending on the new theme.
For example, in Twenty Eleven, some of the Twenty Seventeen starter widgets are visible in the preview, but the menu items aren't.
I'm not quite sure what the preferred behavior would be in this scenario, assuming it's not the current behavior. The attached patch would have `WP_Customize_Manager::unsanitized_post_values()` skip any changeset values flagged as starter content when the current theme doesn't support it, but that might not be desirable." dlh
4-7 Days Ago 39594 Multisite Upgrade Network - cURL Attempting Port 443 on HTTP Networks and Sites 4.7.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2017-01-15T19:31:31Z 2017-04-23T14:38:10Z "The ""Upgrade Network"" utility fails to perform it's tasks correctly in `4.7.1`. cURL is connecting to each subsite through HTTP, however, the port it's attempting to use is 443 and not 80.
All sites in this network are HTTP, so everything should be done through port 80.
'''Here's how I discovered this:'''
Update from `4.7` -> `4.7.1` through the admin interface.
Immediately there after, Upgrade Network.
Warning! Problem updating http://domain.com. Your server may not be able to connect to sites running on it. Error message: cURL error 7: Failed to connect to domain.com port 443: Connection refused
I'm aware of connections refused on port 443. (Firewall rules) The problem is: It shouldn't even be attempting to connect to port 443. All the sites in the network are HTTP.
I've tested the ""Upgrade Network"" utility on `4.7` using another copy of the SAME exact network on the SAME exact server. It upgrades all the sites just fine.
4-7 Days Ago 40467 "Hardcoding Template and Stylesheet paths inside the wp-config.php leads to ""constant already defined in default-constants.php""" Themes normal normal Awaiting Review defect (bug) new reporter-feedback 2017-04-16T14:56:12Z 2017-04-23T13:46:23Z "I've tried to hardcode the Template and Stylesheet directory inside the wp-config with:
You are posting comments too quickly. Slow down.