Implementing some code |
[eluser]manilodisan[/eluser]
I'm trying to implement what seems to be a very good class but I'm having big troubles. The code is supposed to help me cache the pages better and have some sort of a better control over the headers and stuff. The problem is that I have to use the code right after an ob_start() which should sit after the opening php tag and call the class right before the closing php tag. This would have been very simple on a regular php file but, as you can surely imagine, it's a little complicated with our controllers and views. Here's a sample usage of the code: Code: <?php Also, here's a link to the original package (it's on phpclasses.org you will need some sort of credentials), PLUS the original support page for this class with more details. I would really appreciate your help. Thank you.
[eluser]Michael Wales[/eluser]
Just curious why you don't use CI's caching? Caching is a pretty simple concept and one library isn't going to produce significant benefits over another.
[eluser]manilodisan[/eluser]
Well...I needed something more advanced with a little more options (Etag, Pragma etc.) and this seems to be the one. I'm just testing new water, might or might not give better results.
[eluser]Michael Wales[/eluser]
Open up the Caching library, basically copy-paste that into a new library of your own, make your code changes to use your new Caching library (you will see where the native library makes it's appropriate function calls).
[eluser]manilodisan[/eluser]
Well it's not that simple. I tried it with Output.php and Loader.php but it seems to fail at some point. On line 68 in Output.php (in CI's library folder) there's set_output() which seems to set the final output to be sent. Code: function set_output($output) I tried working with that but I get errors of all types...
[eluser]Michael Wales[/eluser]
Experiment around line 172: Code: // Is compression requested? This is where CI is starting it's compression, which involves header changes - probably a good place for your to start modifying yours as well.
[eluser]Michael Wales[/eluser]
I have no idea why I thought Caching was an independent library... didn't have the code sitting in front of me. When you mentioned digging through Output and Loader I was like "wtf... I better look at what I am talking about"
[eluser]manilodisan[/eluser]
Yes...Caching is not separate on CI and far from what I would like. I tried this for the function that you recommended but no response besides a blank page and even on error_reporting(E_ALL);. Code: function _display($output = '')
[eluser]Michael Wales[/eluser]
I'll have to come back to this one a bit later on when I can look through Conteg's documentation. Sorry I couldn't help you out quicker - this issue is going to be a bit more involved than I initially thought. Hopefully someone else can come through and point you in the right direction.
[eluser]manilodisan[/eluser]
Yep...I was hoping for someone from the team to look at this. I think I got it to stop the errors but fear that somewhere in the CI's engyne they get rewritten. My cache still expires in 1981 and that's not what I was hoping...I'm curious where do the headers get set. |
Welcome Guest, Not a member yet? Register Sign In |