Response pages not always presented to users

[sturek]

My response pages work when users attempt to browse to a blocked category but when the blocked item is buried within the page users just get a blank screen until the connection times out.

Any ideas or suggestions would be greatly appreciated!

Thanks!

[BPry]

@sturek,

That sounds like expected behavior to me, but we don't actually do a ton of category blocking so someone may be able to point out how you are able to get this to function as you like. 

[gwesson · Accepted solution]

@BPry is right, there is no way to change this behavior because of the way the web works, especially with javascript and dynamic content.

Sometimes, if only an element is blocked (say, a CSS file) the rest of the page can load fine but it may look weird. An embedded ad could also be blocked without issue in many cases.

But often, if the object being blocked is a key element of the page there's no way to "inform" the rest of the page that it needs to display a block page. 

If your users were to attempt to get just that object you would likely see the block page correctly. Since there's no way for the page elements that already have been delivered to be un-delivered, so to speak, those elements waiting on the blocked one simply time out.

-Greg

[sturek]

Thank you to both responders!

This is what my thought was too but I wanted to throw this out there to see if anyone had found a way around this.