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:32 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
0000954	ClearOS	app-base - Base System	public	2013-01-29 15:15	2013-02-28 14:21
Reporter	user2
Assigned To
Priority	normal	Severity	feature	Reproducibility	N/A
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version
Target Version	6.4.0 Beta 2	Fixed in Version
Summary	0000954: Clean up get_search_results in File class
Description	The get_search_results() needs to handle how much memory is allowed by the PHP engine (memory_limit in php.ini). As a result, the max bytes parameters in get_contents and get_contents_as_array is no longer required (and was only used by the "Log Viewer" app).
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes
(0000657) user2 2013-01-29 15:17	Source Code Changelog --------------------------------------------------- - Changed get_search_results to detect max memory limit [fixed tracker 0000954] File Changes --------------------------------------------------- Details: http://code.clearfoundation.com/svn/revision.php?repname=ClearOS&rev=5547 [^] U webconfig/apps/base/trunk/deploy/upgrade U webconfig/apps/base/trunk/language/en_US/base_lang.php U webconfig/apps/base/trunk/libraries/File.php A webconfig/apps/base/trunk/libraries/File_Too_Large_Exception.php

Notes

Issue History
Date Modified	Username	Field	Change
2013-01-29 15:15	user2	New Issue
2013-01-29 15:15	user2	Issue generated from: 0000645
2013-01-29 15:15	user2	Status	new => confirmed
2013-01-29 15:17	user2	Checkin
2013-01-29 15:17	user2	Note Added: 0000657
2013-01-29 15:17	user2	Status	confirmed => resolved
2013-01-29 15:17	user2	Resolution	open => fixed
2013-02-28 14:21	user2	Status	resolved => closed

Issue History