Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#22904 closed defect (bug) (invalid)

Admin scripting broken for IDN domains

Reported by: knutsp Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.5
Component: Administration Keywords:
Focuses: Cc:


  1. Install WordPress 3.5 (release or RC4) on an IDN domain, like kolsåsbakken.no (xn--kolssbakken-08a.no)
  2. Log in to dashboard, using Firefox, Chrome or any
  3. Use 2012 theme and no active plugins
  4. Hover an inactive menu item

Expected: Submenu flyout

Observed: No submenu appears (but shows below when clicked)

  1. Visit edit.php or users.php (maybe create an extra post or user)
  2. Click the table header or footer checkbox

Expected: All items checked

Observed: No items checked

Then install 3.5-RC3 from the archive and do the same tests. It should work, it least it then works here.

This is a new site, I'm talking about, not yet released to the public. It has been following the complete cycle from 3.5-beta1. We have another (non IDN) site at the same web host, with no problems using 3.5.

I'm really sorry I missed this bug between RC3 and RC4. We were mostly concerned with the new media stuff and other things new.

Other observations:

  1. No scripting errors in Firefox errors panel in this setup
  2. If I activate some plugins using a heavy scripting dependent settings page, the page is completely broken.
  3. When activated, Jetpack throws a lot of scripting errors in the admin, saying jQuery is not defined (visible in FF error panel).

Change History (4)

#1 @knutsp
6 years ago

  • Cc knut@… added

I see a lot of issues with javascript in the admin being broken due to the "Bulletproof Security" plugin.

I admit this plugin has been installed and activated at one time in the site affected, and now deleted, but the created .htaccess file has been deleted and then recreated by WordPress. Inspecting it reveals no traces of anything but WordPress' own rules for "pretty permalinks". And even without any .htaccess, and using the default permalink structure, the problem is still there as described.

#2 follow-up: @dd32
6 years ago

I admit this plugin has been installed and activated at one time in the site affected, and now deleted

Thats most likely the issue. Check for a .htaccess file in wp-admin/.htaccess

#3 in reply to: ↑ 2 @knutsp
6 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Replying to dd32:

Check for a .htaccess file in wp-admin/.htaccess

WTF. I didn't know there could be one left over in a subdir (blush). I learn. Thank you, dd32. I still wonder why 3.4.2 and 3.5-RC3 worked and works perfectly with that offending file in place. The .htacces of the root dir was deleted long before RC3 came out, and nothing changed. And now there's no errors from Jetpack, either. Anyway, that plugin is mean. Sorry for the disturbance.

3.5 is awesome! Congratulations to all contributing developers!

#4 @SergeyBiryukov
6 years ago

  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.