Support Forum

[diegos]

Hi,

I'm using 40b18 version. Don't know if this happens previously.

Using the "Save as Filter" button inside the "Filter Parameters" a user could create a Filter inside a Parent Category.

The problem is that when you go to the Filter List you could select that new created Filter, but there is no Delete button below.

And you end up with a Filter that you could not delete.

If you create a Filter in the same way but inside a Category where he is associated, you could correctly create a Filter and also the delete button appears when you go to the Filter List.

Many thanks,
Cheers,
Diego

[admin]

ok, will check this

[Petr]

Hi,

I'm using 40b18 version. Don't know if this happens previously.

Using the "Save as Filter" button inside the "Filter Parameters" a user could create a Filter inside a Parent Category.

The problem is that when you go to the Filter List you could select that new created Filter, but there is no Delete button below.

And you end up with a Filter that you could not delete.

If you create a Filter in the same way but inside a Category where he is associated, you could correctly create a Filter and also the delete button appears when you go to the Filter List.

Many thanks,
Cheers,
Diego

If I understood correctly.
You created filter and could not delete his.
But i'm checked. I have all right.
You need send anonymous data base me or admin.

[diegos]

A quick way to reproduce is this:

Start from the mysql demo database that came with 40b18.

login as root
position on task "Projects"
goto Access Control, delete the "Tech Writer" granted access to "Projects".
goto "My Project"
goto Access Control, then Grant Access to "Tech Writer" to "My Project"
logout
login as writer
change to english
position on task "Projects"
open Filter Parameters tab
click on Save as Filter
*** here you have a Filter created for "Projects", something wrong
goto Filter List
the new Filter is going to be listed there, and you could select it, but there is no Delete button

Cheers,
Diego

[admin]

This will be fixed in the next beta.

[diegos]

Excellent, many thanks.

Diego