Remove doesn't fully remove content

[jsumnersmith]

The API for removing blocks from a page does not fully remove the content from the page. While they are no longer displayed, content from that block is still stored in the database.

Importantly, any content that was a part of a block that was deleted can still have an impact on search results, as content in blocks are pushed into low search text.

It seems that blocks "published-ness" is controlled by the blockGroups property on the database document while the actual contents of each blocked are stored separately using the prefix/suffix annotation directly on the object itself. For instance, my blockGroups may read as follows while I have four separate blocks on a page entitled main_770957907706279738_title and main_770957907706279738_1, etc:

"blockGroups" : {
    "main" : {
        "blocks" : [
            {
                "type" : "one",
                "id" : "653641944324671888"
            }
        ]
    }
},

I understand the advantages of the separate tracking mechanism as sort order has to be maintained, etc. But search quality is affected by not actually removing the content of a block when it is "removed."

[boutell]

Tru dat.

It would be simple to remove the area. Literally just need to use the
delete keyword actually.

On Mon, Mar 9, 2015 at 2:03 PM, Joel Smith [email protected] wrote:

The API for removing blocks from a page does not fully remove the content
from the page. While they are no longer displayed, content from that block
is still stored in the database.

Importantly, any content that was a part of a block that was deleted can
still have an impact on search results, as content in blocks are pushed
into low search text.

It seems that blocks "published-ness" is controlled by the blockGroups
property on the database document while the actual contents of each blocked
are stored separately using the prefix/suffix annotation directly on the
object itself. For instance, my blockGroups may read as follows while I
have four separate blocks on a page entitled main_770957907706279738_title
and main_770957907706279738_1, etc:

"blockGroups" : {
"main" : {
"blocks" : [
{
"type" : "one",
"id" : "653641944324671888"
}
]
}
},

I understand the advantages of the separate tracking mechanism as sort
order has to be maintained, etc. But search quality is affected by not
actually removing the content of a block when it is "removed."

—
Reply to this email directly or view it on GitHub
#3.

*THOMAS BOUTELL, *DEV & OPS
P'UNK AVENUE | (215) 755-1330 | punkave.com