Unpublished Site Wall - Revision history

Luke: /* Source location */

2022-11-15T10:49:49Z

Source location

← Older revision		Revision as of 10:49, 15 November 2022
Line 25:		Line 25:
	= Source location =		= Source location =

	The block wall is part of the Pages module and specifically exists in the HtmlService.cs file. As of the time of writing [https://github.com/socialstack-core/modules/blob/master/Api/Pages/HtmlService.cs#L1441 the code block is located here].		The block wall is part of the Pages module and specifically exists in the HtmlService.cs file. As of the time of writing [https://github.com/socialstack-core/modules/blob/master/Api/Pages/HtmlService.cs#L1441 the code block is located here]. In the event that the code has moved, try a ctrl+f for "GenerateBlockPage" in HtmlService.cs instead.

Luke at 10:48, 15 November 2022

2022-11-15T10:48:40Z

← Older revision		Revision as of 10:48, 15 November 2022
Line 22:		Line 22:

	</syntaxhighlight>		</syntaxhighlight>

			= Source location =

			The block wall is part of the Pages module and specifically exists in the HtmlService.cs file. As of the time of writing [https://github.com/socialstack-core/modules/blob/master/Api/Pages/HtmlService.cs#L1441 the code block is located here].

Luke: /* What it blocks */

2022-11-15T10:47:38Z

What it blocks

← Older revision		Revision as of 10:47, 15 November 2022
Line 6:		Line 6:

	* The block wall will only block the UI of the website, not the API. I.e. you can still login via posting a username and password to the /v1/user/login endpoint.		* The block wall will only block the UI of the website, not the API. I.e. you can still login via posting a username and password to the /v1/user/login endpoint.
	* It does not block logged in users.		* It does not block logged in administrator users.

	= Configuring the block wall =		= Configuring the block wall =

Luke at 10:46, 15 November 2022

2022-11-15T10:46:18Z

← Older revision		Revision as of 10:46, 15 November 2022
Line 1:		Line 1:
	SocialStack has a built in block wall which indicates that a site is not published yet. This is not a security feature and instead has the primary goal of ensuring that a search engine like Google does not flag the live version of the site as a phishing site. That can happen as it sees two identical sites on different domains and the stage site gets classified as the true original because it existed before the live one did. It can also be used to hide a live website before it is fully ready.		SocialStack has a built in block wall which indicates that a site is not published yet. This is not a security feature and instead has the primary goal of ensuring that a search engine like Google does not flag the live version of the site as a phishing site. That can happen as it sees two identical sites on different domains and the stage site gets classified as the true original because it existed before the live one did. It can also be used to hide a live website before it is fully ready.

			[[File:Socialstack-block-wall.png]]

	= What it blocks =		= What it blocks =

Luke: Created page with "SocialStack has a built in block wall which indicates that a site is not published yet. This is not a security feature and instead has the primary goal of ensuring that a sear..."

2022-11-15T10:45:32Z

Created page with "SocialStack has a built in block wall which indicates that a site is not published yet. This is not a security feature and instead has the primary goal of ensuring that a sear..."

New page

SocialStack has a built in block wall which indicates that a site is not published yet. This is not a security feature and instead has the primary goal of ensuring that a search engine like Google does not flag the live version of the site as a phishing site. That can happen as it sees two identical sites on different domains and the stage site gets classified as the true original because it existed before the live one did. It can also be used to hide a live website before it is fully ready.

= What it blocks =

* The block wall will only block the UI of the website, not the API. I.e. you can still login via posting a username and password to the /v1/user/login endpoint.
* It does not block logged in users.

= Configuring the block wall =

Login as an administrator and go to the configuration section of the administration panel (/en-admin/configuration/). From there, look for the configuration for HtmlService and in there is two configuration options for the block wall: a password to use and a date string (ISO 8601) indicating when the block wall should expire automatically.

The active until date is optional. If it is not specified, the block wall will be present so long as a password is configured.

<syntaxhighlight lang="json">

{
"BlockWallPassword": "hello",
"BlockWallActiveUntil": "2022-01-01T00:00:00.000Z"
}

</syntaxhighlight>