Garbage content and "rendering for the first time" message on blank pages

RESOLVED FIXED

Status

developer.mozilla.org
Editing
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: lorchard, Assigned: lorchard)

Tracking

Details

(Whiteboard: c=wiki u=user s=2012-07-18 p=1, URL)

(Assignee)

Description

6 years ago
Some pages are blank, migrated as-is from MindTouch.

However, when viewed on Kuma, these pages have garbage content like:
    T�K�j�+��kz���ݜ�����\y�4w޶�����{�[���w-4

And when a logged in user hits shift-refresh to trigger a re-render, this message appears:
    "This document is being rendered for the first time by the system."

But, the "first time" message never goes away, because it's triggered by blank content in the rendered_html database field. The thing is, though, the content is *really* blank, so this message is erroneous.
(Assignee)

Updated

6 years ago
Blocks: 770383, 756263
No longer depends on: 756263
(Assignee)

Comment 2

6 years ago
https://github.com/mozilla/kuma/pull/390
Assignee: nobody → lorchard
Whiteboard: c=wiki u=user s=2012-07-18 p=1

Comment 3

6 years ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/9b8539834ea2f52e802d2351afb58b2099283437
fix bug 773362 - Garbage content and "rendering for the first time" message on blank pages

* Don't make a request to kumascript for blank content

* Don't display rendering warnings when there's blank content

* When there's blank content, display a message to that effect in the
  content area in document template

https://github.com/mozilla/kuma/commit/c4002b661b0b987e15e37b61f0d32bee1b9f48a4
Merge pull request #390 from lmorchard/blank-garbage-773362

fix bug 773362 - Garbage content and "rendering for the first time" message on blank pages

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Version: Kuma → unspecified
Component: Docs Platform → Editing
Product: Mozilla Developer Network → Mozilla Developer Network
You need to log in before you can comment on or make changes to this bug.