iqmatrix

I have the same issue:

/home3/studymat/public_html/products/wp-content/plugins/nextgen-gallery/photocrati_nextgen/modules/nextgen_basic_gallery/templates/thumbnails/index.php is not a valid MVC template

Lowlight,

Even with the latest WordPress, the error seems to have re-surfaced. I went back to re-edit a post that has already been published, pressed SAVE and the Visual Editor vanished, and I can’t seem to get it back.

All my REVISIONS have also disappeared from that post and can no longer be accessed.

I am running WordPress 2.7.1

Initially when I upgraded from 2.7 the problem vanished, however it has now become another frustrating aspect of using WordPress ??

I sincerely hope that a solution can be found.

The latest WordPress update seems to have fixed the bug.

Shimshon9,

Personally, I also haven’t been able to resolve the issue. Through trial and error I found out the HeadSpace2 was causing the problems. When I deactivate this plugin everything works fine. However, for some reason after I deleted the JS directory and then re-populated it again, the editor buttons are no longer displaying any images. The buttons are there, however the icons representing these buttons are blank. I therefore must scroll over each button to determine what it represents.

I really don’t know what else to say. I am hoping that WordPress will bring out a new version which will hopefully fix these issues.

natarem,

When you say delete your entire wp-includes/js/ directory. Then repopulate it. Do you actually mean delete everything within the js folder first, and then upload a fresh copy of these js folder files? I don’t know too much about these technical things, and I just want to make sure that it doesn’t break anything within WordPress. My js folder seems to contain all the same files. So I am not sure if this will work.

I appreciate you spending the time to help others resolve this issue.

On another note, I utilize a plugin called “Instant Upgrade” to install new versions of WordPress. I am curious to know if this plugin could be the cause of this error. Is anyone experiencing this error while having manually upgrading WordPress? It would be interesting to find out.

That’s very strange. Everyone seems to have a different method for fixing the same issue. Personally, everything I have tried hasn’t worked for so far. Although when I disable the Visual Editor the HTML Editor functions correctly, yet enabling it causes the same errors once again.

Lem4,

I have exactly the same issue. The Visual Editor appears on some posts for a slip second, then disappears. At the same time, other posts are not effected at all. This is the same no matter what browser I use or computer. These issues only started occuring when I upgraded to WP 2.7.

I wonder how many others are experiencing exactly this problem?

Thanks for the suggestion azaozz. Unfortunately I don’t find any errors. Until I can figure something else out; all I can hope for is that the next update of WordPress can resolve this issue. Thanks for helping out.

I am also getting a similar error on some of my posts in WP 2.7:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 5 bytes) in /home/studymat/public_html/iqmatrix/blog/wp-content/plugins/headspace2/modules/page/tags/auto_suggest.php on line 69

I’ll play around with the memory setting to see if that works.

Nothing has worked for me either after trying all the above suggestions.

Personally, the Visual Editor works when I create a new Post. However, after the post is saved a few times it is prone to playing up and I can no longer access it. However, when I create a new post and paste the old html code (from the Post where the Visual editor didn’t work) into it, then it will work fine again – and I may not have further troubles, unless of course it is saved one too many times. It’s incredibly inconsistent.

On other Blog Posts, when I return to edit them, the Visual Editor just doesn’t work at all from the very beginning.

I am getting the same result on the latest Internet Explorer, Firefox, Google Chrome, and Prism.

Personally I don’t use the Kimli Flash plugin. Therefore, at least for me, this is not the cause.

There must be a global cause for this issue arising from the upgrade to WP 2.7. If we are all using different plugins and browsers then there has to be something more to this. Unless there are several plugins causing the same error.

Can all members who are having problems with the Visual Editor clearly list the symptoms here.

– Does it happen all the time?
– Does it happen when you save a post several times?
– Does anything else disappear when the Visual Editor plays up? For instance the revision posts disappear for me.
– Does it happen for specific posts and not for others?
– Can you paste the HTML from the Post where the Visual Editor isn’t working, and into another new Post? Does this resolve the issue?
– Anything else you have discovered or any other symptoms that you would like to share about this problem.

May be in this way we can gather an overall perspective of the extent of the problem.

Yes, the interface is composed of shades of gray.

Today I discovered that I don’t actually have to save a post in order to get this error. For some unknown reason, when I go back to edit some posts the Visual editor is not accessible and I can only view the HTML.

I have taken a screen capture of the Visual Editor. Click HERE to View.

As you can see the Visual Editor is selected, however it does not display any visuals, just html. When the HTML button is clicked than I am unable to even access the HTML unless the page is refreshed. My Post revisions have also vanished for some unknown reasons.

Does the WordPress development team acknowledge this error? Can a forum moderator confirm or provide any further insight into this?

I don’t use the “All in One SEO Pack” and I still get this error. Instead I use “HeadSpace2” which does the same thing.

The error doesn’t happen all the time when I save a post or page. However, when it does occur, I have no choice but to create a new page or post and copy the HTML over.

I don’t think that it’s an error originating from a plugin. It must have something to do with WP 2.7 version.