Closed (outdated)
Project:
Masquerade
Version:
7.x-1.0-rc7
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Apr 2015 at 14:00 UTC
Updated:
17 Apr 2026 at 11:19 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
joshi.rohit100Comment #2
tinker commentedPatch #1 fixes the redirect URL but does not use the same language as on the maintenance page as there is no longer 'online' and 'offline' options. There is also a problem with the %config-perm not being translated.
Comment #3
tinker commentedComment #4
tinker commentedComment #5
hansfn commentedPlease commit.
Comment #6
izmeez commentedThis issue #2475897: alert message shows a wrong link for maintenance page overlaps with #2559407: Error message contains link to 404 and both have patches that are RTBC.
Each patch applies to current 1.x-dev.
The patch in this issue includes several lines of code while the patch in #2559407: Error message contains link to 404 changes only one line.
Which approach is better?
Comment #7
izmeez commentedAdding related issue.
Comment #8
tinker commented@izmeez,
My patch in this thread does more that just change the URL. It also:
- Fixes terminology from 'online', which is no longer used, and instead uses the exact label that is used next to the checkbox 'Put site into maintenance mode'
- Removes santization on URL which used @site-maintenance to use !site-maintenance. This fixed issues with URL not working when used on site that was installed in sub-directory.
- Finally it uses drupal standards for code and splits the t() array variables onto separate lines for better readability.
So suprise-surprise I vote for my patch.
Comment #9
izmeez commented@tinker comment #8 is just what's needed. Thanks.
Comment #10
izmeez commentedIn fact when I reviewed this issue I thought it was continuation of work started in the other thread and even the name of the first patch seemed to confirm that.
+1 for patch in #3
Comment #11
ressaThanks everyone for working on this. In an attempt to help the maintainers, I am going through some of the Drupal 7 issues, and closing them, since Drupal 7 is EOL.
Maintainers should grant credit for the great work to the relevant users, even if the patch did not get committed: https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquett....
Since Drupal 7 is EOL, we can probably close this issue, but feel free to re-open if this is still a problem in Drupal 11, so we can get it fixed. Thanks!