Did anyone lose some Text objects in recent update?

[etcbbu]

Did anyone else lose some Text objects' content in a recent WB update that happened over the last couple or few days?

--etcbbu

[etcbbu]

I'm just simply surfing around a .WBS file, and a bunch of my basic "Text" objects on various pages around the website are in their positions and everything, but just *BLANK*. I certainly didn't delete them. What's going on?

[Pablo]

There are no known issues with text.
Maybe you have removed a font from your system?

[alan_sh]

I've seen that too. I have multiple breakpoints. If I go to another BP, I can see the text. If I go back to default, it's then there again.

If I publish when I can't see the text, then any text between <span> and </span> is not there.

But it's not something I can reproduce, so I have not yet reported it.

Here's an example of something that is OK.

<p style="font-size:16px;line-height:22px;color:#000000;"><span style="color:#000000;">Within the Pennine district, we have a fabulous scout camp - Ashworth Valley. </span></p>

And one that didn't work:

<p style="font-size:16px;line-height:22px;color:#000000;"></p>

I have Enable D2D set to zero.

Alan

[Pablo]

I need more information to be able to know what is going on.
Do you have an example project?

[alan_sh]

Pablo,

No, I don't - and you may have fixed it as your release notes in the latest version mention " Fixed: Issue with styles in <p> output format."

I'll keep an eye on this and let you know if I can reproduce it.

Alan

[alan_sh]

Pablo - this just happened to me - using the same project that you used to fix the crashing.

I changed to the page 'activities' (under 'About'). The sceen looked like this:



So, I immediately did a preview and sure enough the preview looked the same:



I immediately got a grab of the underlying html code, which can be found here https://www.dropbox.com/s/xbh2lyjaoeq4f ... e.txt?dl=1 and went into the tem/preview folder to grab all the files there. They can be found here: https://www.dropbox.com/s/1s59u6u3dhdhg ... r.zip?dl=1

Once I'd done that, I went back into WWB and clicked on the 980 break point. It looked OK. I clicked back on default and that also looked OK. This is what it should look like:


I am unsure how else I can reproduce it - it doesn't happene very time. What I will say is that WWB itself had been open with the project in it since I checked that the crash had been fixed (about 4 hours). If I close and re-open the project, this does not happen.

I have enableD2D set to 0.

ALan

[Pablo]

I think the text issues are caused by recent modifications related to memory optimization. I have disable this functionality again, so it should now work correct.
http://wysiwygwebbuilder.com/download.html (hotfix 2)

[alan_sh]

Thanks - I'll keep an eye on it but that does sound reasonable.

[etcbbu]

So, this may have totally already have been fixed, but I found a strange workaround, if anyone else was noticing any issues with these ghost Text objects with text "disappearing" recently (but like I say, the Text *objects* are still there, it's just, they're empty sometimes) .

I found a workaround:

1) I would double-click on one of the ghost Text objects, such that my insertion point flashes and it's waiting for me to input text;
2) but then click off of it;
3) then press Ctrl+Z (or perform an "undo" however you want) ;
4) the text I had there, previously, would show up, after I perform the "undo" command.

Again, I'm not trying to cause problems or discord or anything--I love WB. I just thought I'd point out this workaround I discovered, last night, in case anyone else's .WBS file seemed to have some Text objects that were ghosted out and hopefully prevent people from having to re-do large portions of--or entire--websites.

But like you're saying, this hot-fix 2 may have fixed everything since the information spilled back out whenever you do this weird "undo" trick; I think the .WBS files *should* still be containing all of the Text information, still.

I'm about to download this hot-fix 2, as displayed on the website, today, (August 25, 2019), and give it a whirl..

[Pablo]

I think it is better to download the hotfix instead of the workaround.