[eluser]Fabdrol[/eluser]
Hi Wade,
That's kinda a mess... but, anyway. I didn't read the entire file, way to much messy code. I'll be honest, tie-ing thát into CI is going to be a very, very hard and long-lasting job, mainly because it's a mixture of data (the sessions and the data from the database), of functionality and even of view-code, namely the font-size setting (I'm not sure what's that doing there). Anyway, I don't really see a time-efficient way of plugging this into CI, and also using the code.
You talked about 'having to update in three places', could you tell me more about your current systems architecture? Is menu linked to some kind of CMS, how are they interlinked? What kind of app are you building/revising? If all the code is as messy as the code in that file, I truly believe you'd be spending less time by rewriting the entire HUGE app, which will then probably be much less HUGE, then when you try to integrate systems in the way you describe... If you do so, you should expect a lot of writing glue code, rewriting and deleting et cetera.
If all you need from logincode.php is the repdata array, I'd write a small model or library to fetch that same data. Right now you fetch this array using a session and a query, in CI you can easily do the same:
Code:
<?php if(!defined('BASEPATH')) exit('Direct script access denied');
class Repdata extends CI_Model {
private $data = false;
public function __construct() {
parent::__construct();
$sess = $_SESSION['agent_id'];
// assuming that it's set in some other file, since CI uses its own sessions
$this->db->where('aid', $sess);
$sql = $this->db->get('table_name');
if($sql->num_rows() > 0) {
$this->data = $sql->result_array();
}
}
public function get_data() {
return $this->data;
}
}
