[JavaScript Error: "Restore-to-server failed for FCL"] [JavaScript Error: "Cannot edit item in library FCL" {file: "chrome://zotero/content/xpcom/data/dataObject.js" line: 992}]
I obviously know about your other thread, but you still need to provide context when starting a new thread. This isn't just a sync error — you're getting this after trying to use Replace Online Library in the group.
Can you provide a Debug ID for a sync attempt that triggers this?
Yes, this error was due to an attempt to Replace Online Library. I noticed the error in the top right of the program next to the sync green arrow icon. I clicked on the error and it gave me a debug report.
Zotero gave me the option of submitting the debug report by clicking the associated button and it also said to start a new discussion with the Report Error Problem.
So I clicked the button to send you the debug report and I posted a new discussion here with the error problem. I'm sorry I did something in correct, I was just trying to follow the directions as they read.
I do not have the debug problem anymore. I am now going through the group and cleaning and reorganizing the collections (folders) and I will try to Replace Online Library again.
Ok, after cleaning and trying to Replace Online Library this still does not work. I have generated the Debug ID: D287964206.
This is the output:
---- [error report removed — D.S.] ----
Also note that when I originally posted to this discussion, I did so by clicking on the red exclamation mark next to the green sync arrow. That gives me the exact same output.
I can then click Next or Cancel. When I click Next then is tells me the error report has been submitted. Now it gives me a different Report ID: 1322995437. It also says to "Please post a message to the Zotero forums with this Report ID, a description of the problem and any steps necessary to reproduce it."
That appears to be a similar process, but does not generate the Debug ID.
I trust you! I did the same process twice, the same way. The first Debug ID: D287964206 and the second: D613955258. They are the exact same text in the output (I'm actually a coder myself). I don't know what get sent to you in the back-end, but the javascript errors is what I see.
They are the exact same text in the output (I'm actually a coder myself).
They're really not — I don't know why you're arguing about this. All debug reports show the same logged errors at the top that we get from the error reports (a totally different thing that you're confusing for debug reports), but that's not relevant here. For one you didn't follow the steps and logged literally two lines of debug output, and for the other you did it correctly and logged 40,000 lines. You can see the logged lines yourself before submitting.
There is a strange behavior then. This time I keep the Debug Output Window open and I am seeing the code working live. However, I didn't see a note that the debug output needed to be opened. So I had the window closed the previous two times. When I returned to step three I saw the same javascript code both times.
Now that I have the window open I am able to get all the code and submit that report. If this next ID works correctly, perhaps it would be good to add another step to open the Debug Output window between Step 1 and Step 2.
I don't know how to respond about the arguing comment. I'm just trying to provide you with what I am doing and what I am seeing.
From the Debug Output window with all the procedural steps, I have now clicked the Submit button. The new Debug ID is: D394394390.
There's no strange behavior. You don't need to have the window open. The debug code has existed for many, many years, and we get output many, many times a day — it absolutely, 100% works as documented. You're just misunderstanding how the system works and the difference between Report IDs and Debug IDs. For the first Debug ID you began logging and then submitted the output without actually performing a sync. For the second one you did the sync before submitting, so it logged the lines. That's it. There's nothing else going on here, and there's nothing else to fix or discuss. It's OK to miss a step in a system you're not familiar with. Please just stop. We will respond once we've reviewed your debug output.
Upgrade Storage
Can you provide a Debug ID for a sync attempt that triggers this?
Zotero gave me the option of submitting the debug report by clicking the associated button and it also said to start a new discussion with the Report Error Problem.
So I clicked the button to send you the debug report and I posted a new discussion here with the error problem. I'm sorry I did something in correct, I was just trying to follow the directions as they read.
I do not have the debug problem anymore. I am now going through the group and cleaning and reorganizing the collections (folders) and I will try to Replace Online Library again.
I will keep you posted momentarily.
This is the output:
----
[error report removed — D.S.]
----
Also note that when I originally posted to this discussion, I did so by clicking on the red exclamation mark next to the green sync arrow. That gives me the exact same output.
I can then click Next or Cancel. When I click Next then is tells me the error report has been submitted. Now it gives me a different Report ID: 1322995437. It also says to "Please post a message to the Zotero forums with this Report ID, a description of the problem and any steps necessary to reproduce it."
That appears to be a similar process, but does not generate the Debug ID.
Will wait to hear how this bug can be resolved.
https://www.zotero.org/support/debug_output
Debug ID: D613955258
It is the same text as what I put in the previous post that was removed.
Hope we can find a solution to this!
Now that I have the window open I am able to get all the code and submit that report. If this next ID works correctly, perhaps it would be good to add another step to open the Debug Output window between Step 1 and Step 2.
I don't know how to respond about the arguing comment. I'm just trying to provide you with what I am doing and what I am seeing.
From the Debug Output window with all the procedural steps, I have now clicked the Submit button. The new Debug ID is: D394394390.
This is fixed in the Zotero 7 beta, and it should be fixed in Zotero 6.0.27, which will be released this week.