8000 BackUpBuddy compatibility · Issue #37 · lukasjuhas/lj-maintenance-mode · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

BackUpBuddy compatibility #37

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.

Sign up for GitHub

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

Jump to bottom
Open
lukasjuhas opened this issue Jul 17, 2017 · 1 comment · May be fixed by #50
Open

BackUpBuddy compatibility #37

lukasjuhas opened this issue Jul 17, 2017 · 1 comment · May be fixed by #50

Comments

@lukasjuhas
Copy link
Owner

From Gordon and his support chat:

In regards to getting everything to work in maintenance mode, you'll need to find out what is preventing WordPress from connecting back to itself while in maintenance mode. WordPress will need to be able to connect back to /wp-cron.php and /wp-admin/admin-ajax.php. A lot of maintenance/coming soon/etc. plugins do not account for the fact that WordPress needs to connect back to itself. And unfortunately, I'm not involved with any of those types of plugins, so I'm not aware of any that are written well and account for the fact that WordPress needs to connect back to itself. You may want to contact the developers of the plugin/application you are using for maintenance mode to see if there is an option within their plugin/application to allow WordPress to connect back to itself. Perhaps through the whitelisting of an IP Address, Hostname, etc.
@john-lang-86 john-lang-86 linked a pull request Jan 8, 2022 that will close this issue
Open
@john-lang-86
Copy link
john-lang-86 commented Jan 8, 2022 •
edited
Loading

Hi Lukas,

Additional checks before the wp_die() call would fundamentally allow specific scenarios/conditions to by-pass the maintenance mode page being actioned.

The six most useful scenarios/conditions seem to be:

  1. An "Allowed IP List" check that uses $_SERVER[REMOTE_ADDR].
  2. An "Allowed URI List (Strict Match)" check that uses $_SERVER[REQUEST_URI].
  3. An "Allowed URI List" check that uses $_SERVER[REQUEST_URI].
  4. An "Allowed Query String List" check that uses $_SERVER[QUERY_STRING].
  5. An "Allowed Referer List" check that uses $_SERVER[HTTP_REFERER].
  6. An "Allowed User Agent List" check that uses $_SERVER[HTTP_USER_AGENT].

lj-maintenance-mode 6 Allow settings (2022-01-07)

Working solution available in forked Milestone.
All feedback is welcomed.

@john-lang-86 john-lang-86 mentioned this issue Jan 9, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Maintenance Mode 2.5.2 - Enhancements & Fixes 37, 43, 44 and 47 john-lang-86/lj-maintenance-mode
2 participants
@lukasjuhas @john-lang-86
0