Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update maintenance page for multistore setup #3393

Closed
sreichel opened this issue Dec 3, 2018 · 4 comments · Fixed by #8247
Closed

Update maintenance page for multistore setup #3393

sreichel opened this issue Dec 3, 2018 · 4 comments · Fixed by #8247
Assignees
Labels
Progress: done Technical Updates to the code or processes that alter the technical content of the doc
Projects

Comments

@sreichel
Copy link

sreichel commented Dec 3, 2018

Topic clarification/correction request

Topic Link

Description

Guide/suggestion for multistore maintenance pages.

A problem i faced was to have different layout and localized content. As speculated here (same for Magento2) it not possible out of the box, but it is.

The error processor accepts an parameter to change the error page template.

        if (isset($_GET['skin'])) {
            $this->_setSkin($_GET['skin']);
        }

This can be passed via rewrite rule in .htaccess and needs no further changes. IMHO this should be documentated for multistore setups.

Possible solutions

Add documentation for $_GET['skin'] parameter

  • check if .maintenance.flag exists
  • check host (or whatever you want - ENV variables maybe)
  • set parameter

.htaccess:

RewriteCond %{DOCUMENT_ROOT}/var/.maintenance.flag -f
RewriteCond %{HTTP_HOST} ^sub.example.com$
RewriteCond %{QUERY_STRING} !(^|&)skin=sub(&|$) [NC]
RewriteRule ^ %{REQUEST_URI}?skin=sub [L]

copy files:

  • pub/errors/default/503.phtml to pub/errors/sub/503.phtml
  • pub/errors/default/css/styles.css to pub/errors/sub/css/styles.css
  • make your edits there

(directory name has to match url parameter)

Additional information

nginx setting should be added too.

@dshevtsov dshevtsov added Help Wanted Help wanted for issue/PR Technical Updates to the code or processes that alter the technical content of the doc groomed labels Dec 4, 2018
@lorikrell lorikrell added Technical Updates to the code or processes that alter the technical content of the doc and removed Technical Updates to the code or processes that alter the technical content of the doc labels Dec 4, 2018
@meker12 meker12 added this to To do in Install and Configuration Documentation via automation Feb 26, 2019
@meker12
Copy link
Contributor

meker12 commented Feb 26, 2019

We are re-organizing our unresolved GH issues into smaller, more focused projects, and have moved this to the the Installation and Configuration Documentation project.

@Ketika
Copy link

Ketika commented Apr 30, 2019

Hi @meker12 How can I assign this issue to me?

@jeff-matthews
Copy link
Contributor

@Ketika, only someone with write access to this repo can assign issues. I've assigned this to you.

@magento-engcom-team magento-engcom-team added this to Ready for Grooming in Backlog Jun 27, 2019
@m2-community-project m2-community-project bot moved this from Ready for Grooming to Dev In Progress in Backlog Jun 27, 2019
@dshevtsov dshevtsov removed the Groomed label Aug 19, 2020
@m2-community-project m2-community-project bot moved this from Dev In Progress to Ready for Grooming in Backlog Sep 3, 2020
@meker12 meker12 moved this from Ready for Grooming to Ready for Development in Backlog Sep 10, 2020
@dineshvb
Copy link
Contributor

@magento I am working on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Progress: done Technical Updates to the code or processes that alter the technical content of the doc
Projects
Backlog
  
Done
Development

Successfully merging a pull request may close this issue.

9 participants