×
This forum has been locked. Please submit new Feature Requests on GitHub: github.com/Jensen-Technologies/component-creator-issues/issues
(added) Filters in frontend
Dan Davis
Nieuw lid
Posts: 7
10 jaren 3 maanden geleden #357
door Dan Davis
In the interim: How to add custom filters to components
Beantwoord door Dan Davis in topic Filters in frontend
Any progress of this feature? We definitely need Filters in frontend.
Or how can we add it manually like the Filter in the administration back-end?
Look forward to hearing you replies.
In the interim: How to add custom filters to components
Gelieve Inloggen of een account aanmaken om deel te nemen aan het gesprek.
John-Paul Takats
Nieuw lid
Posts: 6
10 jaren 3 maanden geleden #371
door John-Paul Takats
Beantwoord door John-Paul Takats in topic Filters in frontend
I am looking forward to this feature too!
Gelieve Inloggen of een account aanmaken om deel te nemen aan het gesprek.
John-Paul Takats
Nieuw lid
Posts: 6
10 jaren 3 maanden geleden - 10 jaren 3 maanden geleden #373
door John-Paul Takats
Beantwoord door John-Paul Takats in topic Filters in frontend
One thing I'd like to point out well you are developing this is potential security risk i noticed of adding the frontend view. I enabled frontend list / editing for a user list table I have. I noticed that I am able to view the list view as a guest.
Example: If I have a component named helloworld with a table called userstable. If I install the component and visit this url on my site I am able to view the whole table as a guest by using a link like "www.test.com/index.php?option=com_helloworld". I am able to see this table whether or not there is a menu item corresponding to it. If I create a menu item I can set it to be "registered" view only, but even when visiting it I am able to see the table, i just get a notice saying I don't have permission, even though it still displays.
So unless there is some sort of permissions built into the frontend view I would caution people that if they use a frontend view be careful (if it has sensitive info) it will be visible to guests if they can guess the name of the component. Obviously this component creator is geared towards developers so one could put in there own permissions, and block the view... it just gets tricky sometimes when I modify the base component to much and want to reinstall.
Example: If I have a component named helloworld with a table called userstable. If I install the component and visit this url on my site I am able to view the whole table as a guest by using a link like "www.test.com/index.php?option=com_helloworld". I am able to see this table whether or not there is a menu item corresponding to it. If I create a menu item I can set it to be "registered" view only, but even when visiting it I am able to see the table, i just get a notice saying I don't have permission, even though it still displays.
So unless there is some sort of permissions built into the frontend view I would caution people that if they use a frontend view be careful (if it has sensitive info) it will be visible to guests if they can guess the name of the component. Obviously this component creator is geared towards developers so one could put in there own permissions, and block the view... it just gets tricky sometimes when I modify the base component to much and want to reinstall.
Laatst bewerkt 10 jaren 3 maanden geleden door John-Paul Takats.
Gelieve Inloggen of een account aanmaken om deel te nemen aan het gesprek.
Pedro
Nieuw lid
Posts: 12
10 jaren 3 maanden geleden #374
door Pedro
Beantwoord door Pedro in topic Filters in frontend
Hi John, I guess this is something that happens with any component out there and it's something to deal in each extension by itself
Gelieve Inloggen of een account aanmaken om deel te nemen aan het gesprek.
John-Paul Takats
Nieuw lid
Posts: 6
10 jaren 2 maanden geleden - 10 jaren 2 maanden geleden #384
door John-Paul Takats
Beantwoord door John-Paul Takats in topic Filters in frontend
Should the filters appear automatically in a frontend list view? I am not seeing them at the moment, i'll look into it
EDIT - oops noticed you said to file any bugs in the contact us, i will respond once i do a bit more testing... but it looks like the default_filter view that was added was never included anywhere to be displayed alongside other default view. So all I see is default with no filtering.
EDIT - oops noticed you said to file any bugs in the contact us, i will respond once i do a bit more testing... but it looks like the default_filter view that was added was never included anywhere to be displayed alongside other default view. So all I see is default with no filtering.
Laatst bewerkt 10 jaren 2 maanden geleden door John-Paul Takats.
Gelieve Inloggen of een account aanmaken om deel te nemen aan het gesprek.
John-Paul Takats
Nieuw lid
Posts: 6
10 jaren 2 maanden geleden #387
door John-Paul Takats
Beantwoord door John-Paul Takats in topic Filters in frontend
Andres, there was one issue in the first release that I filed a ticket for that it looks like Victor (on your team) corrected this morning. The filtering is displaying now, however there was an issue with the values - I put in another ticket for that earlier.
Thanks,
JP
Thanks,
JP
Gelieve Inloggen of een account aanmaken om deel te nemen aan het gesprek.
Tijd voor maken pagina: 0.060 seconden