localized-landing-pages: Localized landing pages created code and config

[gauravaxl]

Summary

Metadata

Question	Answer
Did you use a meaningful pull request title?	yes
Did you apply meaningful labels to the pull request?	yes/no
Did you perform a self review first?	yes
Documentation reflects changes?	yes/no
CHANGELOG reflects changes?	yes/no
Unit/Functional tests reflect changes?	yes/no
Did you perform browser testing?	yes
Risk level	Medium
Relevant links	JIRA issue, bug reports, security alerts, etc.

Testing Instructions

1. Login to the site as an Editor/Administrator.
2. Go to Content -> Add Content -> Localized Landing Pages, and create a localized landing page.
3. You can choose the language of your content. In the case of an administrator, and in the case of an editor, your default language will be selected by default.
4. You can add content in different blocks on the node.
5. You can add localized headers, localized footer links, and localized footer global links from the admin/structure/menu page.

[RCheesley]

@nick-vanpraet how do we go about reviewing this in the QA environment please?

[nick-vanpraet]

This PR was labeled with qa-4, so the URL is http://mauticorg.qa4.sites.dropsolid-sites.com/. Whoever needs to test it, needs the basic auth user and password which is available on platform. Someone with access can securely pass that along to the tester, or give them an account on platform? I don't know what the contracts say regarding extra platform accounts, etc.

Normally each new commit to this PR should trigger a build of the environment linked to that URL. It may take a few minutes for that to complete after the mirroring is done.

Resetting the environment database after testing is done, etc is a manual step someone with enough rights can execute on platform by, for example, downsyncing the database and files from production.

[RCheesley]

@gauravaxl could you provide some test instructions in the description please? We need to know where to view the page/s and what needs reviewing etc. Thanks!

[RCheesley]

I've fixed the issue of not being able to log in - the sites are deployed without SSL and we didn't have that set as a valid callback URL. So you should be able to log in now in the QA environment @ekkeguembel @gauravaxl