Johansensen
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Problems with Visual Editor in WP 3.1Thanks for the FCKEditor suggestion, this works for me too. Hardly a real solution, but it’ll hold the users over until I can implement a functional alternative in Drupal and deploy that instead.
Bye WordPress. I would say it’s been fun, but honestly it really hasn’t…
Forum: Fixing WordPress
In reply to: Problems with Visual Editor in WP 3.1Oh right, I see. Mine is definitely enabled, glad it worked for you though!
Forum: Fixing WordPress
In reply to: Problems with Visual Editor in WP 3.1Wait, enabled what?
Forum: Fixing WordPress
In reply to: TinyMCE broken after upgrade, suggested fixes not workingI’m back… turns out that wasn’t the solution after all. Sigh…
I’ve now tried all troubleshooting steps that have been suggested so far, all I know is that the editor starts working again if no theme content whatsoever is present.
Forum: Fixing WordPress
In reply to: TinyMCE broken after upgrade, suggested fixes not workingSo it turns out that having themes installed *was* breaking the php memory limit. Increasing the limit from 16 to 32 solved the problem. This doesn’t make me any less unimpressed with WP (in fact it makes me more so), but my problem is solved and the user will be happy, which right now is what matters.
Thanks for your help.
Forum: Fixing WordPress
In reply to: Problems with Visual Editor in WP 3.1And a breakthrough: increasing the php memory limit from 16MB to 32MB makes things suddenly work again. Why anything in this software needs that much RAM is beyond me, but nonetheless it now works. Thanks everyone.
Forum: Fixing WordPress
In reply to: Problems with Visual Editor in WP 3.1(also, I have manually replaced all of the code files myself as well)
Forum: Fixing WordPress
In reply to: Problems with Visual Editor in WP 3.1Just adding my voice to the crowd: same issues as above, and I’ve worked out it’s connected to having themes installed, the editor works fine if *all* themes (including the default one) are deleted. However, even reinstalling the default theme causes the issue to reoccur.
I’ve also tried disabling script concatenation, which did nothing.
I’m running a Mac, and I’ve tested this on Chrome, FF3.6 and 4, and Safari. So far only safari works with this configuration (possibly the only time anyone has ever used that phrase).
So yeah, having *any* theme installed breaks it. Does anyone else find this?
Forum: Fixing WordPress
In reply to: TinyMCE broken after upgrade, suggested fixes not workingAs above, I have already tried the first two suggestions. The concatenate_scripts mode idea also sadly does not help. Thanks for the suggestions.
Forum: Fixing WordPress
In reply to: TinyMCE broken after upgrade, suggested fixes not workingMy hosting provider is a very large VM farm run by my organisation, and the server itself is administered by me, so I doubt there are any material restrictions being placed on it.
Either way, I would be very surprised if something like a theme (which is essentially a whole bunch of css, right?) managed to break the php memory limit or something. Then again, wordpress has surprised me a lot in the last couple of weeks, so perhaps I shouldn’t speak too soon…
Forum: Fixing WordPress
In reply to: TinyMCE broken after upgrade, suggested fixes not workingSome progress, but not really that much:
I have discovered that actually *removing* all installed themes (as opposed to disabling) makes TinyMCE suddenly work again. However, this is not very comforting seeing as having any theme at all present, even a freshly-downloaded version of twentyten 1.1, causes TinyMCE to go back to resolutely not working. Sadly for this user theming is a non-optional thing, so I’m going to need to find the root cause of this issue and work around it somehow.
I have also tried manually copying wp-admin and wp-includes from a download of the 3.1 tarball, in case the auto upgrade didn’t do it right, but to no avail.
Any thoughts for what I can try? Even vague suggestions would be great at this point.
Forum: Fixing WordPress
In reply to: Visual Editor Broken in 3.1For what it’s worth, I had the same issue and found that I had to do the dir-rename trick on the themes dir to get any joy out of TinyMCE. Thanks indeed for posting this fix, was rather disconcerting to discover that even disabled plugin code can still break things.
Forum: Fixing WordPress
In reply to: TinyMCE broken after upgrade, suggested fixes not workingAs stated above, yes I have.
Forum: Fixing WordPress
In reply to: Cannot Update Pages in WYSIWYG mode since upgrade!I have a user with the same issue, rolled out 3.1 into production without confirming it actually worked, and discovered the rich-text/html editor was broken. I’ve tried all the steps suggested in the fixes thread, including disabling all plugins and falling back to the default theme. I also tried installing the TinyMCE advanced plugin on the offchance that it would override whatever is not working here, but no dice.
You know what would be nice? Not changing the database schema every point release. This wouldn’t be an issue if I could just revert the changes my user made… </whinge>