Topic: Changing IMP conf.php boolean

[kingttx]

Folks,

Please forgive me if this has been covered elsewhere. Please point me to the location if it has been answered and thank you for your time.

When at work behind a rather large bank of proxies, accessing the Horde webmail page is a bit of a pain with $conf['auth']['checkip'] = true in /home/httpd/html/horde/config/conf.php. While 'true', IMP will log me off repeatedly after about 30 seconds to a couple of minutes. This was answered in the Horde mailing list, changing the boolean to false corrects the behavior for me.

Of course, changing this directly in the file means it returns to the initial config upon updates|restarts|whatever. Unfortunately, I'm a plebe with SME and I have no blinkin' idea where to change this in the SME database. What is the process?

Thanks!

[kingttx]

I may have figured this one out. After reading a bit, it occurred to me that I may need to work in the templates and see if that worked instead of going through the db system. I'm hoping this is the answer.

Code: [Select]

cd /etc/e-smith/templates/home/httpd/html/horde/config/conf.php
vim 125AuthenticationChange '$conf['auth']['checkip'] = ' to 'false' and save the file.

Code: [Select]

expand-template /home/httpd/html/horde/config/conf.php
So far, the pertinent item in /home/httpd/html/horde/config/conf.php has the boolean 'false'. After running 'signal-event post-upgrade; signal-event reboot', the boolean remained 'false' so this should fix my problem getting signed out constantly when accessing IMP/DIMP webmail from behind a proxy.

[mercyh]

You are close.

Read here and come back if you have questions:

http://wiki.contribs.org/SME_Server:Documentation:Developers_Manual:Section2#Local_site_overrides:_templates-custom_and_templates-user-custom

Basically you need reverse the change you made, copy that template(and associated directory structure) into the templates-custom directory and make your changes in the the templates-custom file that you created. Then run your expand-template command (or "signal-event post-upgrade" and "signal-event reboot") and you will have a modification that will live through an update.

[kingttx]

Would it be OK if I wrote something up for possible inclusion in the Admin guide to cover this? It would not be in as much depth as the developer guide section on templates and would point someone to that guide for more information. However, I kept looking all through the how-tos and admin guides for this info where I would expect it to be found, and this info is not there.

[mercyh]

I think it would fine to include something in documentation. I would think it should go in the how-tos. It is hardly a FAQ as I have never seen the question asked before.

Understanding the templating system and how to make changes to the conf files that are not part of the DB is part of an advanced knowledge of SME server. Once you understand the concept it does not just apply to conf.php but to all the configuration files.

With your how-to are you thinking of explaining the templating system in a manner that is easier to understand? or explain how to change the particular setting that you are working with?

[kingttx]

Easier to understand and target admins that want to make changes to text config files but don't know where to start. The section in the developer's guide is great for deeper understanding and for those creating a new package for SME. However, for admins like me that want to make some changes to a config file, there is no quick reference to it. I can use my particular change as an example but I'd want to write it generally enough so an admin can apply it to other config files as well.

[mercyh]

I think that might belong in the FAQ, maybe a new category called "Advanced Configuration using the Template System". (or something like that.)

Here is the information for helping with documentation.

http://wiki.contribs.org/Help:Contents

I am sure that some of the other doc team members will have some input and be glad to help if you get stuck.

[kingttx]

That will work. I'll get started this week and hopefully have something to give to the doc team soon.

Thanks for your help!

[mercyh]

read through the information on working in mediawiki. You can then start your new page and you will find that there are users that are watching for new entries. They will step in and help if they feel like the new input needs clarification or change.

As soon as you get access, you are part of the doc team yourself

Thanks for your willingness to help improve the project.