Yeah, i'll be taking the best out of every hint!
The big problem is that the user has a lot of freedom. If he just
wants to search for "barber" he can and urls will be /barber/
/... Every parameter is optional, they're just bound to an
order, if they're all present... So i don't have a "special" ca
On 10-08-11 15:50, samuele.mattiuzzo wrote:
I was considering the option/country/italy/city/milan/job/engineer/,
it wasn't that bat, but i'm risking very long urls if 4-5 parameters
are set...
If /italy/milan/barber is the normal url, by all means use that.
The other scenarios can then get a l
Well, i don't understand it plenty, since i never spoke with them
directly. Btw, our "seo consultants" said that /london/designer/ is
SEO-OK while ?city=london&job=designer is SEO-BAD. I really don't
think there's much difference between the two, but i cannot discuss
too much with them :)
On Aug 1
On Wed, Aug 10, 2011 at 2:50 PM, samuele.mattiuzzo wrote:
> my boss told me to use get requests instead of post, so i could
> explicit the parameters, but SEO experts said "NO WAY!". i don't like
> get method either, but the reason is different :P
>
I dont understand SEO reason, can you explain.
Yeah, it was just a shorthand to let you understand my problem, it
wasn't my actual url definition :)
I was considering the option /country/italy/city/milan/job/engineer/,
it wasn't that bat, but i'm risking very long urls if 4-5 parameters
are set...
On Aug 10, 12:18 pm, Reinout van Rees wrot
On 10-08-11 11:20, samuele.mattiuzzo wrote:
url(//, search_view),
url(//, search_view),
url(///, search_view)
as you can see, case 1 and case 2 are a trouble: country and city are
both strings, how's the url supposed to know if a link pointed to one
url or another? Should i use named views in t
i wanted to keep urls as clean as possible, but i was studying
something like mysite.com/country.italy/city.milan/job.king/
i do not like it so much, but it's the cleanest thing i can think
of...
On Aug 10, 11:47 am, Subhranath Chunder wrote:
> If you are planning for reverse URL in your templat
If you are planning for reverse URL in your templates, then named URL
pattern is the thing for you.
https://docs.djangoproject.com/en/dev/topics/http/urls/#naming-url-patterns
Else to simply, you might also consider changing the url patterns to
something like:
/country//
/city//
If you have the op
Hi all, i'm developing a search-engine-like application using django
1.3 and apache-solr as "database"
I'm now stuck with urls handling. Basically, i need to compose urls
with the parameters used to query solr. Fair enough, but i faced a
problem.
Basically, you can filter your results by choosing
9 matches
Mail list logo
