Viewing 4 replies - 1 through 4 (of 4 total)
  • I’m not 100% convinced that these “missing files” are being called by WordPress core at all. Can you replicate the problem on a fresh install with no plugins or additional themes installed?

    Thread Starter KerriM

    (@kerrim)

    esmi, I think you may be right… I don’t have an opportunity to thoroughly test right now (have to update the test environment first), but I now suspect that this is caused by the Advanced Custom Fields plugin (in my case), as I see other related issues in the support forums.

    This has only been an issue with one site so far, though I’ve use ACF in all Worpdress sites I’ve created within the past year or so… the only real distinction I can see between this site and the others is that this is a multisite installation (which each site on a subdirectory of the main domain) — though I don’t see how that would be a related issue…

    It’s possible that the plugin contains a pretty esoteric bug that’s only triggered in certain multisite situations. As the co-maintainer of a plugin, I know we can have problems with multisite testing as we cannot really replicate a large, working, multisite install. Your best bet would be to post in the plugin’s forum with as much detailed info as possible. Perhaps the plugin’s developer will be able to spot the problem and issue a fix.

    Thread Starter KerriM

    (@kerrim)

    That I did — well, I contributed my details to a report that was already started. He hasn’t been able to reproduce it yet. It’s an outstanding plugin, so my mentioning it in no way should detract anyone from using it. It is the most essential plugin in my arsenal!

    Thanks, esmi. I’ll repost if I find a resolution, for anyone else who comes upon this thread.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WP calling TINYMCE language files that don't exist’ is closed to new replies.