I just began using Concrete 5 with a freshly installed version, and I'm having this exact same problem. Sometimes (not always) the spinning "wait" indicator just sits there until I give up and hit refresh. Sometimes the change has taken effect, and sometimes it hasn't.

Does anyone have any solutions for this problem?

I have seen this as well, and have not been able to pinpoint the root issue.

ChadStrat

The post from FatTony1952 indicates that this has been an ongoing problem for about a year now (I'm using 5.4.2.1). Can anyone from the design team say whether this problem is on their radar or not?

Right now it's killing our ability to use Concrete 5. The only workaround I've found is to keep clicking the update button at a very high rate (maybe 30 clicks ... as fast as I can click them). That seems to increase the probability that the change is actually accepted (when I give up clicking and refresh the page). But it's almost like a superstition at this point, and it would be helpful to know what's causing this problem. The other problem with that workaround is that it only works well for "Update" buttons. When using an "Add" button, the multiple clicks generates multiple "adds" which have to be deleted. The interesting thing is that 30 clicks of the "Add" button only generates about 0 to 5 actual entries added. Maybe that's a clue about the problem.

Thanks again for any help!!

It is due to the failure of the xhtml response for the dialogue.

Usually it occurs if you are using the wrong version of jquery, jquery-ui or have multiple jqueries loaded.

Thanks for replying. But I'm not quite sure what all of that means.

More importantly, how can I fix it? I installed a fresh C5 just a day or two ago and began having the problems right away.

@bobk
It means look at the page source and see what jquery and jquery-ui version numbers you can find (and duplicates if any).

Not saying this is the cause in your case. But it was for every instance that I've seen it. And I've seen it a lot ;)

Here's one:

jquery.js?v=f7f6ff031c585...

and here's another:

jquery.ui.js?v=f7f6ff031c585...

So what are they telling me?

Well. they are telling you they are cached. But that's not really what you are asking ;)
Click on them and see what the version number is in the top comments

Well, there were several different files, and here are the closest lines I could find to a version number in most of them:

* jQuery JavaScript Library v1.6.2

### jQuery Star Rating Plugin v3.00 - 2009-03-16 ###

* @version 1.3.3

They were all from different files, but I'm guessing that the first one is the one that matters.

That's correct for the Jquery (for 5.4.2.x)

Jquery UI should be 1.8.14.

It is also imperative that the inline JavaScript containing "CCM_IMAGE_PATH" comes before all other C5 javascript (should be near the top in the header).

Hmmm...

This is starting to get a little bit into the tall grass for a guy who wanted an "easy" web site builder!!

Given that I just installed the latest version, shouldn't everything ... just work?

@bobk

Yes it should. I know its no consolation. But I was completely unable to upgrade my production site from 5.4.1.1 to 5.4.2.x at all (so didn't bother). However the test site did install from scratch with no problems.

If you just want an easy life. I would suggest installing 5.4.1.1 until the issues with the latest release are resolved (there seems to be quite a few people having various problems).

Thanks very much for the time.

It's not so much that I want an easy life for myself. It's more important that I provide a good experience for the users of my site. :)

Thanks again for your time.

Here it is two years later and I am having exactly the same problem with version 5.2.1. I understand that version 5.6 will be coming out soon and the development team is looking for input on new features.

I say please try to get the current features working properly before you add more.

Please?

The updated core doesn't just add new features, it also resolves these types of issues. I've updated all of my sites to any version above 5.4.1 and haven't had the problems since.

I would suggest you upgrade to a newer version since this could be a bug with that version or a possible conflict with an installed package that needs an updated C5 version.

I got the version wrong. It's actually 5.5.2.1. The problem does seem better when I use Chrome. Also connection speed seems to make a difference.