The copy panel stays stuck with the blue progress indicator going.
Then if I click in the bottom of the Content panel, the Copy panel goes away. Then when I reload the content, the copy is in the content tree.
================
Things I have tried:
The App_Data/Logs/UmbracoTraceLog does not have any details.
Is there someplace else I should check??
Next thing that I would check is Chromes dev tools. Look at the JS console and see what error it's throwing. Usually, you can click on the error and see the response that the server is giving.
Copying Content results in error
Using version 7.4.3
I am getting this error when copying content.
The copy panel stays stuck with the blue progress indicator going. Then if I click in the bottom of the Content panel, the Copy panel goes away. Then when I reload the content, the copy is in the content tree.
================
Things I have tried:
The App_Data/Logs/UmbracoTraceLog does not have any details. Is there someplace else I should check??
I have bumped up the clientDendency number.
Thanks for any suggestions -- Bill
Next thing that I would check is Chromes dev tools. Look at the JS console and see what error it's throwing. Usually, you can click on the error and see the response that the server is giving.
Thanks Jason for that tip !!
The cosole is showing that it failed to load two resources:
https://www.gravatar.com/avatar/0a9b8bc496df36054ce8007d9ff7a83e.jpg?s=64&d=404
and
https://REPLACEDADDR.COM/VIRTUALDIRECTORY/umbraco/backoffice/UmbracoApi/Content/PostCopy
It seems that maybe this is a caching issue?? I tried deleting the files under /TEMP, and then touching the web.config.
But that didn't help -- so I will continue to look for and try things, but if anybody has any other suggestions, I would appreciate them.
Gravatar error is common, but this looks like the cuprit:
https://REPLACEDADDR.COM/VIRTUALDIRECTORY/umbraco/backoffice/UmbracoApi/Content/PostCopy
If you are working in VS, I would to an Edit->Find and Replace-> Find In Files for REPLACEDADDR.COM
That URL should contain the current host of the environment that you are working in, i.e., localhost:port
is working on a reply...