How we can deal with Error Loading Exploration
issue after discarding the changes.
#20180
-
It occur very rare. why this occur? @seanlip @Nik-09 @nikitaevg @DubeySandeep @Radesh-kumar @Anthony-Alridge PTAL |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 10 replies
-
@rahat2134 I'm not sure, you'll probably need to check the code that leads to this pop-up. The first step is probably to find a reliable way to reproduce it. |
Beta Was this translation helpful? Give feedback.
-
It is probably <div class="modal-header">
<h3>Error Loading Exploration</h3>
</div>
<div class="modal-body">
<p>
Sorry! The following changes will be lost. It appears that your
draft was overwritten by changes on another machine.
</p>
<p *ngIf="hasLostChanges">
The lost changes are displayed below. You may want to export or copy and
paste these changes before discarding them.
</p>
<oppia-changes-in-human-readable-form [lostChanges]="lostChanges">
</oppia-changes-in-human-readable-form>
</div>
<div class="modal-footer">
<button class="btn btn-secondary" (click)="cancel()">Close</button>
<button class="btn btn-primary" (click)="exportChangesAndClose()">Export Changes and Close</button>
</div> |
Beta Was this translation helpful? Give feedback.
-
-> It occurs when we discard changes, but it occur very rarely. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Let me make it clear -> updateTitleTo('New Title'); After this update, we are discarding the modifications. At times, the puppeteer operates so swiftly that it discards the changes before they can be saved. (As there is no 'Autosaving text' on mobile) This can lead to the issue. On desktop, the autosaving text is available, allowing us to wait for it to disappear and reappear. However, on mobile, we must utilize an external wait to ensure that the changes have been saved. Kindly inform me if further clarification is required. |
Beta Was this translation helpful? Give feedback.
-
@rahat2134 Could you please put this question in one of the Q&A categories and mark the relevant option as "answered" if you feel that this thread is resolved? Thanks. (Please also put future Q&A in one of those categories, not "General".) |
Beta Was this translation helpful? Give feedback.
@seanlip I have an idea. We can disable the 'discard' button until Autosave is in progress. This approach will also address the mobile view port. Let me know if you agree, and I will raise the issue and submit a PR by EOD. PTAL.
DisableDiscardButton.webm