2.4.4-RC - SquidGuard issue - Blacklist
-
In my case the Target Rules field is filled out. The problem is with the Target Rules List. I tested the variable $ upt_val, which should contain the value of the rule, but it comes empty. In summary, the rules seem to be read from the file, but there is some problem filling in the variables passed to or in make_grid_controls. I'm having some difficulty because php is not the "my native language".
-
I found and fixed the problem:
in the /usr/local/pkg/squidguard.inc file
on line 558
change: if (!empty ($val) && is_array ($val)) {
to: if (!empty ($val)) { -
@Carlos-Renato-Monteiro
Sounds good. I will test it here Renato. -
Save a backup of the file before editing it.
As a bonus, I changed the grid to show the rule name before the description, because I think it's better:
Line 799: $tbl .= "<td $color> [$name] $description </ td>";
if you use Target Categories for off-time (overtime), remove rows 580, 581, and 582.
-
This post is deleted! -
@carlos-renato-monteiro it didn't work. Maybe because you are using 2.4.3 with the old php version. We got different behaviors.
i am also investigating from here.Fabricio.
-
If you want to post the file (changed), I'll help you check other things.
-
This post is deleted! -
Estou com o mesmo problema, atualizei, funcionou tudo direitinho, porém quando vou em GroupACL na parte das Target Rules não aparecem as listas, e quando coloco na mão a regra simplesmente não é salva, e sempre fica no campo como "!all". Ou seja! não consigo usar as Groups ACL do SquidGuard.
Alguém ai com o mesmo problema?
-
@skala - Sim, é um BUG que aconteceu depois da mudança de versão do php.
Já está postado lá no Forum em Português - Este aqui é só Inglês. -
Por isso não atualizei ainda o Pfsense. Só corrigi o bug do SquidGuard novo no 2.4.3.
-
some update of this?
because is impossible to use squidGuard in 2.4.4 16 days ago!!! -
Fixed in squidGuard pkg v 1.16.18 which is up now for 2.4.4-RELEASE and will show up with the next snapshots for 2.4.5-DEV
-
It was released version 1.16.18 that corrects this problem, it worked out right here for me pfsense 2.4.4, Thanks to all
