Text in the Text Element Disappeared

Hi!

I have just wrote two paragraphs of text into a template loaded from other page. After clicking something, i think it was the layout pane, the text disappeared. It is not rendering issue. After saving the text was still gone.

Thanks!

Edit, I have just lost another paragraph. Looks like RC4 is not safe for work.

Edit2: now it was gone simply by switching focus to another browser window. Redo is unable to bring it back.

I had this problem earlier in RC4 (1st or two using it) and it was when I used the duplicate text function.

I deleted both text elements and started again, not had that problem since. I did log it at the time but was unable to replicate the problem… can you replicate it?

@scotbaston, I’ll try that. This was on loaded template, so that is kind of duplication too.

Hope that helps/works for you… and that Themeco can sort this issue out promptly

Yeah, just tested on another page. Same thing. Losing stuff that I have wrote seconds before. However, it seems that only Inserted templates are affected. I will recreate the Elements from scratch until fixed. :slight_smile:

EDIT: Just lost text content on a brand new element, so it seems that this is not just about duplication.

The weird thing for me is, although I had this problem once… I have not had it since (fingers very crossed that it doesn’t happen and it also gets fixed)

1 Like

Hi @Misho,

Thanks for letting me know. I’ve spent some time experimenting and haven’t gotten this issue to occur. Something I have fixed since RC4 is an issue where the history/undo system would have an error that prevented the action from going through. I think this is the cause of some intermittent problems we’ve seen, but can’t confirm if it is related to this issue in particular. What would be really helpful is if it happens again that you check the developer console logs for errors. Often when something fails, it’s because part of a javascript error preventing the rest of the code from running. Thanks!

Hi @alexander

Pro 3.0.1. I just had the disappearing text event. This one was restorable by Undo, though. Here is what the Console says:

JQMIGRATE: Migrate is installed, version 1.4.1 jquery-migrate.min.js:2:552
unreachable code after return statement
2 cs-vendor.6466c24.js:1794
JQMIGRATE: Migrate is installed, version 1.4.1 jquery-migrate.min.js:2:552
unreachable code after return statement
cs-vendor.6466c24.js:1794
Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled. 5
This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects for further details and to join the discussion on related tools and features! pro
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. tinymce.min.js:2:9046
This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects for further details and to join the discussion on related tools and features! pro
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. tinymce.min.js:2:9046
Failed AJAX request. Switching to fallback. TypeError: "NetworkError when attempting to fetch resource." cs.6466c24.js:4480:9
Unhandled AJAX error. Expecting valid JSON from response. TypeError: "NetworkError when attempting to fetch resource." cs.6466c24.js:4479:300
Rejecting Controller promise
Object { }
cs.6466c24.js:4468:68
Unable to load presets for quote
Object { }
cs.6466c24.js:3539:140
Object { eventNs: "observer-nav", action: {…} }
cs.6466c24.js:1203:9
Object { eventNs: "observer-nav", action: {…} }
cs.6466c24.js:1203:9 

Thanks!

Thank you! Is this a site I might be able to login and check directly? A few suspicious errors in there, but I’m wondering if the text loss is a side effect of another error that halts current activity.

Sure, Credentials in the secure note.

I did have some issues with the site on update. Realized that I have to turn-off Minify CSS in SG Optimizer, which worked before.

Also, right-click in the content editor is a bit laggy. Initially it required two clicks, but now it works on one, and it takes a fraction of a second longer than in the Beta Install (other site).

I did the Plugin conflict test and it was the same.

Thanks!

Hi Misho,

I’ve spent some time playing around in the site but wasn’t able to trigger the error (Pardon my “Test Page”). Things seemed pretty normal from what I could tell. If you don’t mind, I’d like to try again tomorrow. I’ve got a few more things to check on today, but I do want to circle back to this.

No problem!

I will continue to work on my other install where this was happening much more, and without the possibility of undo. If I catch the error, I will immediately get the Console log and post back here.

Thank you!

Thanks! Sounds good.

Also, I saw this thread today: https://theme.co/apex/forum/t/text-disappears-after-new-update/64508

Hopefully with enough places to try this out I’ll be able to discern something.

1 Like

Update: I’ve finally just witnessed it firsthand on the other customer’s site. Still not sure what’s causing it, but there are no console errors so it must be something else.

1 Like

@Misho Solved! Thank you for your patience here. I was able to correct this in the second point release that was just pushed out. Here’s a quick post-mortem in case you’re curious:

  • Inspect Text element and begin typing in rich text mode
  • Start typing in the text editor
  • Stop typing, but very quickly inspect another element.
  • Text is lost

It was in the “unmount” handler of the text component. If you navigated off the editor (by inspecting something else) while it was still updating, it would send a final update but at that time it was no longer connected to the element so it sent nothing… which cleared the text. The problem is one of the timers (a debounce) was not being canceled at the right point in time.

Hopefully that makes a little bit of sense, if not oh well, it’s fixed and released!

2 Likes

@alexander

Thank you for your devotion and patience with solving all these little issues.
I understand that there must be lots of moving parts when undergoing such a huge overhaul.

Thanks again! :thumbsup:

1 Like

Thanks Misho! I appreciate the kind words. :slight_smile:

2 Likes

I was slightly worried about this one… I had it happen to me once but was unable to recreate it (Hardly surprisingly looking at the cause!)

Thank you both for sticking with this one

It was definitely bothering me in the back of my mind knowing we hadn’t confirmed the root cause before going to a release. So glad it’s behind us now! :smiley: