Closed
Bug 345970
Opened 19 years ago
Closed 18 years ago
Avoid using the string 'the web'
Categories
(Bugzilla :: User Interface, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.2
People
(Reporter: timeless, Assigned: timeless)
References
()
Details
(Keywords: ue)
Attachments
(1 file, 5 obsolete files)
18.55 KB,
patch
|
LpSolit
:
review+
|
Details | Diff | Splinter Review |
The Web is probably a proper noun and refers to some strange view of The Internet (also a proper noun).
Bugzilla is software with an html interface for use in web browsers, however it doesn't have to run on The Web, it can instead run on an intranet (not a proper noun). When it runs on an intranet it is generally *not* accessible "from The Web".
The following are OK since they reference things generically:
web server -- a server that can serve web content
web browser -- browser that can render web content
web site -- a place that has web content
The following aren't OK:
the web
web accessible -- this is equivalent to "accessible from the web"
Here are the instances I found (landfill's bugzilla tree doesn't update, so there could be some stale bits):
206 <para>The most-likely cause is that the <quote>cookiepath</quote> parameter
207 is not set correctly in the Bugzilla configuration. You can change this (if
/docs/xml/troubleshooting.xml
208 you're a Bugzilla administrator) from the editparams.cgi page via the web.
209 </para>
176 <section id="security-webserver-access">
177 <title>Disabling Remote Access to Bugzilla Configuration Files</title>
178
179 <para>There are many files that are placed in the Bugzilla directory
/docs/xml/security.xml
180 area that should not be accessable from the web. Because of the way
181 Bugzilla is currently layed out, the list of what should and should not
182 be accessible is rather complicated. A new installation method is
183 currently in the works which should solve this by allowing files that
184 shouldn't be accessible from the web to be placed in a directory outside
185 the webroot. See
/docs/xml/installation.xml, line 199 -- <para>Once all the files are in a web accessible directory, make that
/checksetup.pl, line 1070 -- # duplicates.xul and must be loadable over the web
/template/en/default/global/user-error.html.tmpl, line 426 -- We recommend that you store your attachment elsewhere on the web,
In a lot of cases "using a web browser" is probably a valid substitution. This bug is obviously not important, but we should probably try to enforce this rule (eventually adding 'the web' and maybe 'web accessible' to the spelling error list).
Comment 1•19 years ago
|
||
I think that sometimes it's fine, even if it's not exactly correct. For example, this sentence seems OK:
> you're a Bugzilla administrator) from the editparams.cgi page via the web
At the worst, we can replace it with "web interface." In fact, that might even be on the next line.
Severity: normal → trivial
OS: Windows XP → All
Hardware: PC → All
Comment 2•19 years ago
|
||
I am seeing use of both 'webserver' and 'web server'. Does anyone have a preference?
Comment 3•19 years ago
|
||
Attachment #231367 -
Flags: review?(timeless)
Comment 4•19 years ago
|
||
Comment on attachment 231367 [details] [diff] [review]
Inital changes for use of 'the web'
Messed up my search. Trying again.
Attachment #231367 -
Attachment is obsolete: true
Attachment #231367 -
Flags: review?(timeless)
Comment 5•19 years ago
|
||
Attachment #231369 -
Flags: review?(timeless)
Comment on attachment 231369 [details] [diff] [review]
This should cover all files. Also normalized use of 'web server' instead of 'webserver'
+# duplicates.xul and must be accessible on the web server
- i'd use "from" instead of "on" - this occurs a couple of times.
don't use tabs.
you'll need to post a new patch so that someone can commit this.
Attachment #231369 -
Flags: review?(timeless) → review+
![]() |
||
Updated•19 years ago
|
Assignee: ui → jhulten
Target Milestone: --- → Bugzilla 3.0
![]() |
||
Comment 7•19 years ago
|
||
Jeffrey: request approval when you have updated your patch per timeless' comments.
Status: NEW → ASSIGNED
Comment 8•19 years ago
|
||
Attachment #231369 -
Attachment is obsolete: true
Attachment #231381 -
Flags: review?(timeless)
Comment 9•19 years ago
|
||
*** Bug 345971 has been marked as a duplicate of this bug. ***
Comment 10•19 years ago
|
||
Attachment #231381 -
Attachment is obsolete: true
Attachment #231382 -
Flags: review?(timeless)
Attachment #231381 -
Flags: review?(timeless)
Assignee | ||
Comment 11•19 years ago
|
||
Comment on attachment 231382 [details] [diff] [review]
Made consistent use of 'from the web server' instead of 'on the web server'
> the web servers document directories. See
I think this should be we server's :)
Attachment #231382 -
Flags: review?(timeless) → review+
Updated•19 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Flags: approval?
Resolution: --- → FIXED
![]() |
||
Comment 12•19 years ago
|
||
The patch hasn't been comitted yet. Reopening!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•19 years ago
|
Flags: approval? → approval+
Updated•19 years ago
|
Status: REOPENED → ASSIGNED
![]() |
||
Comment 13•19 years ago
|
||
The patch doesn't apply cleanly:
Hunk #1 FAILED at 149.
1 out of 1 hunk FAILED -- saving rejects to file Bugzilla/Install/Filesystem.pm.rej
Hunk #2 FAILED at 75.
1 out of 3 hunks FAILED -- saving rejects to file docs/xml/troubleshooting.xml.rej
Could you make sure your patch isn't conflicting with some recent checkin?
![]() |
||
Comment 14•19 years ago
|
||
This bug has been approved 3 months ago but the patch has never been committed and is bitrotten as mentioned in comment 13. Update the patch, ask someone for review, and then request approval again when you get this review.
Flags: approval+
Assignee | ||
Comment 16•18 years ago
|
||
Assignee: jhulten → timeless
Attachment #231382 -
Attachment is obsolete: true
Attachment #273310 -
Flags: review?(LpSolit)
![]() |
||
Comment 17•18 years ago
|
||
Comment on attachment 273310 [details] [diff] [review]
updated
>Index: docs/xml/security.xml
>+ be accessible is rather complicated. A new installation method is
>+ currently in the works which should solve this by allowing files that
>+ shouldn't be accessible on the web server to be placed in a directory outside
>+ the web servers document directories. See
>+ <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=44659">bug 44659</ulink>
>+ for more information.
This bug has been resolved as WONTFIX! So this comment doesn't make sense.
>Index: template/en/default/global/messages.html.tmpl
> decreased security. If you experience problems running [% terms.Bugzilla %]
> scripts, log in as [% constants.ROOT_USER FILTER html %] and re-run this script, become a
> member of the group, or remove the value of the "webservergroup" parameter.
>+ Note that any warnings about "uninitialized values" that you may see
>+ below are caused by this.
Huh??? Max, is that true?
Attachment #273310 -
Flags: review?(LpSolit) → review-
Assignee | ||
Comment 18•18 years ago
|
||
Attachment #273310 -
Attachment is obsolete: true
Attachment #273342 -
Flags: review?(LpSolit)
![]() |
||
Comment 19•18 years ago
|
||
Comment on attachment 273342 [details] [diff] [review]
without bad merges
Looks good. r=LpSolit
Attachment #273342 -
Flags: review?(LpSolit) → review+
![]() |
||
Updated•18 years ago
|
Flags: approval+
Target Milestone: --- → Bugzilla 3.2
Assignee | ||
Comment 20•18 years ago
|
||
Comment on attachment 273342 [details] [diff] [review]
without bad merges
mozilla/webtools/bugzilla/testserver.pl 1.17
mozilla/webtools/bugzilla/Bugzilla/Attachment.pm 1.48
mozilla/webtools/bugzilla/Bugzilla/CGI.pm 1.33
mozilla/webtools/bugzilla/Bugzilla/Constants.pm 1.73
mozilla/webtools/bugzilla/Bugzilla/Install/Filesystem.pm 1.21
mozilla/webtools/bugzilla/Bugzilla/Install/Localconfig.pm 1.9
mozilla/webtools/bugzilla/docs/xml/installation.xml 1.139
mozilla/webtools/bugzilla/docs/xml/security.xml 1.17
mozilla/webtools/bugzilla/docs/xml/troubleshooting.xml 1.13
mozilla/webtools/bugzilla/template/en/default/global/messages.html.tmpl 1.59
mozilla/webtools/bugzilla/template/en/default/global/user-error.html.tmpl 1.222
Status: ASSIGNED → RESOLVED
Closed: 19 years ago → 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•