edit views

[jrlenz]

how can we actually edit views to apply match-clients {} ? purpose being GeoIP; facileManager seems to be well-suited to it otherwise. Quick and easy setup.

[WillyXJ]

Wow, what an oversight! This will be fixed in 1.0-rc2, but to get you going, run the following on your MySQL database:

INSERT IGNORE INTO fm_dns_functions (
def_function ,
def_option ,
def_type ,
def_multiple_values ,
def_view_support
)
VALUES
('options', 'match-clients', '( address_match_element )', 'yes', 'yes'),
('options', 'match-destinations', '( address_match_element )', 'yes', 'yes'),
('options', 'match-recursive-only', '( yes | no )', 'no', 'yes');

Once done, you can click on your view which will bring up the options page. Click the + and select 'match-clients' from the drop-down list and fill in your address_match_element.

I'll leave this issue open until rc2 is released and resolves this issue.

[jrlenz]

Yeah I looked into the code and hacked it already, but thanks for the reply :)

----- Original Message -----
From: "WillyXJ" notifications@github.com
To: "WillyXJ/facileManager" facileManager@noreply.github.com
Cc: "jrlenz" jrlenz@jrlenz.com
Sent: Saturday, September 14, 2013 10:28:30 PM
Subject: Re: [facileManager] edit views (#16)

Wow, what an oversight! This will be fixed in 1.0-rc2, but to get you going, run the following on your MySQL database:

INSERT IGNORE INTO fm_dns_functions (
def_function ,
def_option ,
def_type ,
def_multiple_values ,
def_view_support
)
VALUES
('options', 'match-clients', '( address_match_element )', 'yes', 'yes'),
('options', 'match-destinations', '( address_match_element )', 'yes', 'yes'),
('options', 'match-recursive-only', '( yes | no )', 'no', 'yes');

Once done, you can click on your view which will bring up the options page. Click the + and select 'match-clients' from the drop-down list and fill in your address_match_element.

I'll leave this issue open until rc2 is released and resolves this issue.

—
Reply to this email directly or view it on GitHub .

[WillyXJ]

This has been fixed in 1.0-rc2.