Gary Buckmaster wrote:
Thanks for jumping on this, and thanks for such a great package. I'm available for testing any new fixes you have, so feel free to ping me when you're ready.

Hi,

I think I have fixed the gui update problem. I have not yet updated the fix to main pfsense repository. In the mean time you can test this by:

0. Remove all existing packages.
1. change the xmlrpcbaseurl in /etc/inc/globals.inc to agni.linuxense.com
2. remove /tmp/config.cache
3. remove all entries inside <havp> in /conf/config.xml
4. Update the Available Packages by clicking System -> Packages
5. Install HAVP package.

I hope I have not made any new bugs with this fix :)

let me know how it goes.

raj


  Also, a question about the blacklist/whitelist
feature. This appears to work properly in the GUI, although HAVP doesn't seem to pick up the entries. I'm perfectly willing to assume that I'm goofing up by putting the full domain name of the site including the prefix and the scheme. Since I haven't been able to find anything in the extremely thin HAVP documentation, your insight into this feature would be appreciated. Maybe putting an example or two in the WebGUI instructions for the page might be in order?
-Gary

Rajkumar S wrote:

Gary Buckmaster wrote:

When editing the HAVP configurations, the settings aren't saved in the WebGUI. When you view havp.config you see that the settings are actually being appended to the configuration file, rather than replacing the currently blank settings. Even after removing the empty settings, the WebGUI doesn't track the current configuration. Although the values aren't tracked in the WebGUI, they are apparently maintained somewhere because manually editing the HAVP configuration file, and then re-editing it via the WebGUI produces two sets of configurations.



Thanks for your bug report. I thought I had nailed this bug before I submitted the package. What is happening is that with each save, pkg_edit.php creates new <config> entries inside the <havp> tree inside config.xml instead of editing the 0th entry. The argument id=0 should have fixed this. I am digging into this now.

raj

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to