Improved Router - Better SEF URL on front-end view

10 anos 4 meses atrás - 10 anos 4 meses atrás #126 por Mr Haha
Loading a view using item id is very bad ideal. There are SQL Injections bug there. I have tried creating a component using Joomla category and SQl Injection bug has appear.
Ultima edição: 10 anos 4 meses atrás por Mr Haha.

Por favor Acessar ou Registrar para participar da conversa.

10 anos 4 meses atrás #128 por Mr Haha
Respondido por Mr Haha no tópico Improved Router - Better SEF URL on front-end view
I have attached the component that I created using your site. Try creating a sample data and go to view single item. In here, I view my item at mydomain.com/joomla/component/documents/item/1 
If I add a ' at the end of that url, sql injection ll apear like this
hhit.com/joomla/component/documents/item/1'
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 3 SQL=SELECT title FROM bd3qu_categories WHERE id =

Esta mensagem contém arquivos anexados. Faça login ou registre-se para ter acesso.

Por favor Acessar ou Registrar para participar da conversa.

3 anos 4 meses atrás #9883 por FULLSTACK DEV
Respondido por FULLSTACK DEV no tópico Improved Router - Better SEF URL on front-end view
Hello,

Instead of using "/component-name/view-name/item-id" for the SEF output, can I make it to: "/component-name/view-name/item-name" ?

Any help would greatly be appreciated if you can point me in the right direction.

Thanks!

Elliott

Por favor Acessar ou Registrar para participar da conversa.

3 anos 4 meses atrás #9884 por Carl Fuentes
Respondido por Carl Fuentes no tópico Improved Router - Better SEF URL on front-end view
It could be archive by go to administator -> Components -> your component name -> Option (Top right corner) -> Component tab and then turn on the using modern SEF.

Por favor Acessar ou Registrar para participar da conversa.

3 anos 4 meses atrás #9886 por FULLSTACK DEV
Respondido por FULLSTACK DEV no tópico Improved Router - Better SEF URL on front-end view
I have actually tried this before and it still don't show the URL the way I envision it.

Basically, what I try to accomplish is this:

Site flow: County-->City-->Comunity

In the County page, we have list of Cities with link to City's detail page.
In the City detail page, we have list of Communities with link to Community's detail page.

I've created menu items for the County and each of the cities. No problem with the SEF there.
I have a really good SEF link for County and Cities.
However, from the City detail page, where we have the list of Communities, the link aren't looking good because I don't have menu item created for each of those communities.
If I have to create menu item for each of the Communities, it will be too many of them. We have over 1500 communities for State of Florida.

As it is now, the community URL showing as: https://TLD/name-of-city/community-template-view/community-ID

I am trying to eliminate the "community-template-view" and "community-ID" from the URL and replace it with a simple URL like: https://TLD/name-of-city/name-of-communtiy

Where can I make the edit to make it happen?

Thank you so much in advance for your help! Been scratching my heads for 2 days for this..


Elliott

Por favor Acessar ou Registrar para participar da conversa.

3 anos 4 meses atrás #9887 por FULLSTACK DEV
Respondido por FULLSTACK DEV no tópico Improved Router - Better SEF URL on front-end view
Nevermind.. I figured it out. By reading the code in router.php I was able to see that if I add the alias field then the system can call for the alias instead of the id. I've added the field and all good now.

Thanks so much!

Elliott

Por favor Acessar ou Registrar para participar da conversa.

Tempo para a criação da página:0.117 segundos
Powered by Fórum Kunena

We use cookies so that you can place orders and we can provide a better service. You can control the use of cookies at the individual browser level. If you reject cookies, you may still use our website, but your ability to use some features or areas of our website may be limited.