Error message: "An error occurred while duplicating the resource."

At this point, can anyone at least confirm that they are seeing that same error message? Maybe not a solution...just whether you are experiencing it? I want to see if it is a MODx thing or something with my own environment.

I was having this issue occasionally; normally clearing the cache seemed to fix it, or so I thought.

Now I have my MODX stuck in this state. Cannot create any resource. Tried clearing cache, logging out etc. with no joy.

My MODX install is boogered!

Manually deleting the content in core/cache helped rescue my MODX - should this help anyone else coming along and reading this.

And now clearching the cache manually doesn’t fix it.

Sorry, that advice above may or may not work!

I encountered the same difficulty on a new install of 2.1.3pl - and, oddly, I don’t seem to have the same problem on an upgrade of an earlier version running in the same environment (running under CentOS, Apache 2.0.63, PHP 5.2.14, mySQL 5.0.92-community, using Chrome or Firefox on Windows 7).

If I create a new resource, clear the cache, change the template, and then save it saves successfully. Then I can change the template back to the default if I want. This procedure appears to be the only way to create a new resource without getting an error while duplicating the resource.

In the end for me I have to right click on a container and select quick create document. If I try to do it in the full way, I just cannot create articles on that MODX install now.

Quote from: hostile17 at Aug 02, 2011, 04:36 AM

In the end for me I have to right click on a container and select quick create document. If I try to do it in the full way, I just cannot create articles on that MODX install now.

Yup... that’s the way I need to do it, too.

What’s happened with this system all of a sudden? Actually, I had noticed it a little bit on a site running v 2.0.8., I believe. It wasn’t nearly as bad and I thought it was just a fluke. It got really bad with these latest releases.

Probably a good time for any of the core developers of this system to chime in here, please. What to do?

Well, what to do is use one of the workarounds we’ve already identified until the bug is fixed. It’s been reported and it has a target release set for a fix. I wouldn’t worry about it, they’ll get it soon enough.

I still have the same Problem with the 2.1.2. Is the problem fixed in the 2.1.3 ?

still problem in the 2.1.3, but it's happen if my internet connection is slow