{"action":"closed","issue":{"url":"https://api.github.com/repos/bcit-ci/CodeIgniter/issues/3694","labels_url":"https://api.github.com/repos/bcit-ci/CodeIgniter/issues/3694/labels{/name}","comments_url":"https://api.github.com/repos/bcit-ci/CodeIgniter/issues/3694/comments","events_url":"https://api.github.com/repos/bcit-ci/CodeIgniter/issues/3694/events","html_url":"https://github.com/bcit-ci/CodeIgniter/issues/3694","id":63723544,"number":3694,"title":"Cannot override Core Libraries with packages?","user":{"login":"lonnieezell","id":51931,"avatar_url":"https://avatars.githubusercontent.com/u/51931?v=3","gravatar_id":"","url":"https://api.github.com/users/lonnieezell","html_url":"https://github.com/lonnieezell","followers_url":"https://api.github.com/users/lonnieezell/followers","following_url":"https://api.github.com/users/lonnieezell/following{/other_user}","gists_url":"https://api.github.com/users/lonnieezell/gists{/gist_id}","starred_url":"https://api.github.com/users/lonnieezell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lonnieezell/subscriptions","organizations_url":"https://api.github.com/users/lonnieezell/orgs","repos_url":"https://api.github.com/users/lonnieezell/repos","events_url":"https://api.github.com/users/lonnieezell/events{/privacy}","received_events_url":"https://api.github.com/users/lonnieezell/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-03-23T13:31:21Z","updated_at":"2015-03-25T11:41:18Z","closed_at":"2015-03-25T11:41:18Z","body":"Overriding core libraries doesn't seem to work any longer. There's a check in `Loader::_ci_load_library()` that checks if the library exists in `BASEPATH/libraries` and, if so, runs `_ci_load_stock_library()`. This method never checks across package folders for classes overriding these core libraries. \r\n\r\n@narfbg Is this intentional? Did I just miss it in the docs? Seems like packages should have the ability to override this, yes? \r\n\r\nThis came up as a comment on my Profiler bar replacement and I found it when digging through why it wasn't working. Because the profiler bar, being a small package, was placed in the third_party folder and wasn't loading like it used to."}}