Closed Bug 139887 Opened 22 years ago Closed 22 years ago

NNTP Server value not being set

Categories

(CCK Graveyard :: CCK-General, defect)

Product:
CCK Graveyard
Component:
CCK-General
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: lrg, Assigned: shrutiv)

References

Details

(Keywords: regression, Whiteboard: [adt1 rtm][cckrtm+]) 

If you set a NNTP server value in the CCK wizard, that value will not be seen in
the actual installed client, instead the user will be required to type in a
value on his own.  This problem is also present in the factory tool.
Keywords: nsbeta1+
Is this bug seen in the recent builds or was it pre-existant in the product? 
Hi, Luke:

Would you please find out if this is a regression? Please note that the settings
will go into RDF file instead of preference .js file.
Luke, can you test this on CCK 6.2.2 RTM?
It looks like this was working properly in cck 6.2.2rtm, so this should be
considered a regression
Keywords: regression
After confirmation that this is a minor bug, adding nsbeta1 instead of nsbeta1+.
Keywords: nsbeta1+ → nsbeta1
Increasing severity as per Jeff's suggestion.
Severity: major → critical
marking [adt1 rtm] per shrutiv's comments:
-----------------------------------------
Talked to Jeff regarding bugzilla 139887. It must be fixed for RTM. Need not be
marked nsbeta1+, but severity must be increased to critical.

Thanks,
Shruti
-----------------------------------------
Severity: critical → major
Whiteboard: [adt1 rtm]
136721: the core bug.
Depends on: 136721
cckrtm per triage
Whiteboard: [adt1 rtm] → [adt1 rtm][cckrtm]
cckrtm+
Whiteboard: [adt1 rtm][cckrtm] → [adt1 rtm][cckrtm+]
Status: NEW → ASSIGNED
I have noticed that this seems to be fixed in the latest factory build, but the
value is still user modifiable during the account creation process.  When was
there a patch checked in?
Marking fixed. The patch in the core bug 136721 should fix this bug.
Verified in 6/20 NCADM bld.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Marking verified.
Status: RESOLVED → VERIFIED
marking fixed1.0.1 since 136721 which appears to have fixed this was also marked
fixed1.0.1
Keywords: fixed1.0.1
blee  - can you verify this bug fix in 1.01 branch?  When verified, pls replace
fixed1.0.1 keyword with verified1.0.1.  Thanks.
Keywords: fixed1.0.1 → verified1.0.1
You need to log in before you can comment on or make changes to this bug.