Title: js errors (visual editor, tinymce)
Last modified: August 22, 2016

---

# js errors (visual editor, tinymce)

 *  [marcilla](https://wordpress.org/support/users/marcilla/)
 * (@marcilla)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/js-errors-visual-editor-tinymce/)
 * Hello,
    I’m running a fresh install of WP 4.0.1 on Server 2003 x64 R2, IIS6, 
   FastCGI, MySQL 5.5, PHP 5.3.8, (Yes I know, all dated) default theme, no plugins.
 * I was experiencing problems with getting the visual editor to work on an existing
   WP install that had been upgraded from a lower version, so I tested out setting
   up a new install from a fresh download. Unfortunately, this instance of WP also
   happens to be exhibiting the same behavior.
 * Trying to troubleshoot this has been quite a task. I took a look in the console
   on the browser’s developer tools and here’s what I’m seeing:
 *     ```
       7post-new.php:22 Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
       post-new.php:25 GET http://mydomain/wp-includes/js/?ver=2.15.0 net::ERR_TOO_MANY_REDIRECTS
       post-new.php:27 GET http://mydomain/wp-includes/js/?ver=0.9.8 net::ERR_TOO_MANY_REDIRECTS
       post-new.php:1916 GET http://mydomain/wp-includes/js/?c=1&ver=4104-20140822 net::ERR_TOO_MANY_REDIRECTS
       post-new.php:24 GET http://mydomain/wp-includes/js/?ver=4.0.1 net::ERR_TOO_MANY_REDIRECTS
       post-new.php:26 GET http://mydomain/wp-includes/js/?ver=4.0.1 net::ERR_TOO_MANY_REDIRECTS
       post-new.php:256 Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
       ```
   
 * Even just loading up the dashboard fires up a js error:
 *     ```
       6index.php:22 Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
       index.php:24 GET http://mydomain/wp-includes/js/?ver=4.0.1 net::ERR_TOO_MANY_REDIRECTS
       index.php:293 Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
       ```
   
 * Any thoughts on how to troubleshoot this? The threads I did look at in search
   didn’t seem to match my situation.
 * Any help appreciated. Thanks in advance

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Moderator [t-p](https://wordpress.org/support/users/t-p/)
 * (@t-p)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/js-errors-visual-editor-tinymce/#post-5565639)
 * Might you have an .htaccess issue? A redirect that is improperly configured?
 *  Thread Starter [marcilla](https://wordpress.org/support/users/marcilla/)
 * (@marcilla)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/js-errors-visual-editor-tinymce/#post-5565643)
 * Here’s the current htaccess. Should something be adjusted?
 *     ```
       RewriteEngine On
       RewriteBase /
       RewriteRule ^index\.php$ - [L]
   
       # add a trailing slash to /wp-admin
       RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
   
       RewriteCond %{REQUEST_FILENAME} -f [OR]
       RewriteCond %{REQUEST_FILENAME} -d
       RewriteRule ^ - [L]
       RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
       RewriteRule ^(.*\.php)$ $1 [L]
       RewriteRule . index.php [L]
       ```
   
 *  Moderator [t-p](https://wordpress.org/support/users/t-p/)
 * (@t-p)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/js-errors-visual-editor-tinymce/#post-5565645)
 * I am familiar with that rule, may be someone lse chimes in and take a look at
   it.
 *  Thread Starter [marcilla](https://wordpress.org/support/users/marcilla/)
 * (@marcilla)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/js-errors-visual-editor-tinymce/#post-5565766)
 * Just as a followup, the errors I linked were from Chrome’s Java console. As for
   the Firefox console, the only error that seems to be firing is:
 * `ReferenceError: tinymce is not defined`
 * I did some comparisons to my other WP and noticed the requests looked different.
   In the actual source code on the php, the src references of the lines firing 
   the errors appear to be looking for this:
 * `../wp-includes/js/tinymce/wp-tinymce.php?ver..`
    or `../wp-includes/js/mediaelement/
   mediaelementplayer.min.css?ver..` (among others)
 * While monitoring console of the problem site, the requests seem to be pointing
   to this instead (as shown in the errors of the intial post):
 * `../wp-includes/js/?ver..`
 * Is this a Rewrite issue or something? A bit stumped here…
 *  Moderator [t-p](https://wordpress.org/support/users/t-p/)
 * (@t-p)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/js-errors-visual-editor-tinymce/#post-5565767)
 * try a few basic troubleshooting steps:
    – Flushing any caching plugins you might
   be running, as well as server and/or browser caches. – deactivating ALL plugins
   temporarily to see if this resolves the problem (plugin functions can interfere).
   If this works, re-activate them individually (one-by-one) to find the problematic
   plugin(s). When you can’t get into your admin dashboard, try deactivating via
   [FTP or SFTP ](http://codex.wordpress.org/FTP_Clients)or whatever file management
   application your host provides (also read [http://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F](http://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F)).
   Also remember to deactivate any plugins in the mu-plugins folder (If you have
   such folder). The easiest way is to rename that folder to mu-plugins-old. – If
   that does not resolve the issue, try switching to the unedited default Twenty
   Fourteen Theme for a moment using the WP dashboard to rule out any theme-specific
   issue (theme functions can interfere like plugins). When you don’t have access
   to your admin area, use [FTP or SFTP ](http://codex.wordpress.org/FTP_Clients)
   or whatever file management application your host provides. Navigate to /wp-content/
   themes/ and switch to the default theme by renaming your current theme’s folder
   by adding “-old” to the end of the folder name via [FTP or SFTP ](http://codex.wordpress.org/FTP_Clients)
   or whatever file management application your host provides. Alternately, you 
   can remove other themes except the default theme. That will force your site to
   use it. – If that does not resolve the issue, try [resetting the plugins folder](http://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F)
   via [FTP or SFTP ](http://codex.wordpress.org/FTP_Clients)or whatever file management
   application your host provides. Sometimes, an apparently inactive plugin can 
   still cause problems (because the hooks remain unless plugins completely removed
   or some plugins stick around in cached files. So by renaming the folder, you 
   break them and force them inactive). – If all the above steps do not resolve 
   the issue, then try **MANUALLY** re-uploading all files and folders EXCEPT the
   wp-config.php file and the /wp-content/ directory from a fresh download of WordPress.
   Make sure that you delete the old copies of files & folder before uploading the
   new ones. Read the [Manual Update ](http://codex.wordpress.org/Updating_WordPress#Manual_Update)
   directions first! – running the upgrade manually via wp-admin/upgrade.php – **
   If you haven’t already done, always backup everything (including your database)
   before doing any actions, just in case something really goes wrong.**
 *  Thread Starter [marcilla](https://wordpress.org/support/users/marcilla/)
 * (@marcilla)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/js-errors-visual-editor-tinymce/#post-5565768)
 * I would try those things, but this is from a completely vanilla install of 4.01
   from a fresh download, and these errors were present right out of the gates once
   setup was complete.
 * I did try those things on the original site (which was from an upgrade), but 
   to no avail. That’s why I tried to replicate the error from a fresh install to
   see if it was a different issue, since a fresh install would rule out all the
   plugin and theme problems.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘js errors (visual editor, tinymce)’ is closed to new replies.

## Tags

 * [javascript](https://wordpress.org/support/topic-tag/javascript/)
 * [tinymce](https://wordpress.org/support/topic-tag/tinymce/)
 * [visual editor](https://wordpress.org/support/topic-tag/visual-editor/)

 * In: [Installing WordPress](https://wordpress.org/support/forum/installation/)
 * 6 replies
 * 2 participants
 * Last reply from: [marcilla](https://wordpress.org/support/users/marcilla/)
 * Last activity: [11 years, 6 months ago](https://wordpress.org/support/topic/js-errors-visual-editor-tinymce/#post-5565768)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
