SYSTEM WARNING: 'file_get_contents(https://www.clearos.com/?rendertype=json&get=header): failed to open stream: Connection refused' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

Anonymous | Login

2024-12-22 05:41 MST

Project: All Projects ClearCenter ClearOS

Main | My View | View Issues | Change Log | Roadmap | Repositories

View Issue Details [ Jump to Notes ]				[ Issue History ] [ Print ]
ID	Project	Category	View Status	Date Submitted	Last Update
0001055	ClearOS	app-network-report - Network Report	public	2013-03-26 10:13	2013-04-01 10:15
Reporter	user2
Assigned To
Priority	normal	Severity	tweak	Reproducibility	always
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version
Target Version	6.4.0	Fixed in Version
Summary	0001055: Check database initialization before running data insert
Description	The anaconda/installer environment is skipping over the database initialization for some anaconda-reason. No matter, an initialization check should be done before every data insert -- that's more robust.
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes
(0000776) user2 2013-03-26 19:11	Source Code Changelog --------------------------------------------------- Added another layer of initialization [fixed tracker 0001055] File Changes --------------------------------------------------- Details: http://code.clearfoundation.com/svn/revision.php?repname=ClearOS&rev=5837 [^] U webconfig/apps/network_report/trunk/deploy/info.php U webconfig/apps/network_report/trunk/deploy/install U webconfig/apps/network_report/trunk/libraries/Network_Report.php U webconfig/apps/network_report/trunk/packaging/app-network-report.spec

Notes

Issue History
Date Modified	Username	Field	Change
2013-03-26 10:13	user2	New Issue
2013-03-26 10:13	user2	Status	new => confirmed
2013-03-26 10:14	user2	Issue cloned: 0001056
2013-03-26 10:14	user2	Issue cloned: 0001057
2013-03-26 19:07	user2	Issue cloned: 0001063
2013-03-26 19:11	user2	Checkin
2013-03-26 19:11	user2	Note Added: 0000776
2013-03-26 19:11	user2	Status	confirmed => resolved
2013-03-26 19:11	user2	Resolution	open => fixed
2013-04-01 10:15	user2	Status	resolved => closed

Issue History