Closed
Bug 155468
Opened 23 years ago
Closed 23 years ago
Installation of c11n build crash due to incorrect attributes for Viewpoint
Categories
(CCK Graveyard :: CCK-Wizard, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jimmyu, Assigned: shrutiv)
Details
(Whiteboard: [cckrtm+])
Attachments
(1 file, 1 obsolete file)
|
7.78 KB,
patch
|
Details | Diff | Splinter Review |
Creating a c11n build with selected Viewpoint component during installation it
doesn't display as a selectable component when doing custom install. Also it
crash "Error occur during installation - Viewpoint Media Player: -204
NO_INSTALL_SCRIPT"
The c11n build config.ini for Viewpoint should be as follow ~
[Component Viewpoint]
Attributes=SELECTED|UNCOMPRESS|LAUNCHAPP
Currently, it is as follow ~
Attributes=SELECTED|INVISIBLE
Summary: Installation of c11n build crash due to in correct attributes for Viewpoint → Installation of c11n build crash due to incorrect attributes for Viewpoint
| Assignee | ||
Comment 1•23 years ago
|
||
Patch includes the following changes:
- Updated code to include newly introduced attributes like SUPERSEDE, VISIBLE,
etc.
- Empty attributes are now replaced with 'VISIBLE' attribute in installer,
accordingly updated cecko code.
- Included some code cleaning: Removed the age old unreadable code (multiple
conditions in if else) and replaced it with better/easier code. This may help
all cecko developers to easily fix similar bugs (introduced everytime attribute
changes are made in browser) and also reduces a code cleaning bug in my list
:-)
| Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [cckrtm+] → [cckrtm+] need r=
Comment 2•23 years ago
|
||
I asked for a few comments, then r=smeredith.
| Assignee | ||
Comment 3•23 years ago
|
||
Attachment #91174 -
Attachment is obsolete: true
| Assignee | ||
Comment 4•23 years ago
|
||
Resolving fixed.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Whiteboard: [cckrtm+] need r= → [cckrtm+]
VErified with CCK 2002-07-16-11-1.0
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•