Conversation
761bc8a to
f4be405
Compare
OCA Transbot updated translations from Transifex
f4be405 to
a46c1a0
Compare
|
@hurrinico |
lasley
left a comment
There was a problem hiding this comment.
Oops actually looks like there's a few warnings
|
Hint the warnings are due to us using |
|
@hurrinico please fix what @lasley says and I'll merge. |
|
@lasley @pedrobaeza @hurrinico changing to would prevent page What do you suggest? cc @antespi |
|
Hmmmm I see the problem. Odoo SA's A controller with an explicit route is my preferred. Interface or not, it is pretty commonly accepted practice to isolate everything by namespacing & breaking the good practice is not worth the 6-7 lines of code we'll save. That's my opinion. Anyone else have thoughts? |
|
I agree with @lasley |
|
add setup here hurrinico#1 |
…up-jne [ADD] setup.py
|
@lasley I don't know how to implement what you suggest. Hints? |
|
@eLBati - I'll actually submit a PR in the next few days. I was just looking, and it seems I had a branch doing exactly this in v9 + updating the privacy policy in accordance with some advice I have received from legal counsel. |
yajo
left a comment
There was a problem hiding this comment.
I feel adding custom controllers is an overkill.
This addon just adds 3 pages, and it uses the tool Odoo uses for pages. It lets submodules to know the URL for that page and make sure it exists; these pages are expected to be changed by the user. Seems legit IMHO; custom controllers and so on would be more code to maintain for basically no benefit.
|
@lasley This is working perfectly and is holding other PRs; mind if we merge as it is? You can update the texts later, and we can defer the controller conversation to future v11... |
|
@yajo - merging as is will break the 10.0 Runbot build going forward. Is that something we're OK with? |
|
Hmm no, definitely. It seems it breaks due to 3 warnings: Hard to fix if we don't do custom controllers... OK, well if you can have it for today it would be great, we are at #ocacodesprint merging like crazy goats! 🐐 |
yajo
left a comment
There was a problem hiding this comment.
As said, we need to fix bots, which will probably include adding the controller.
|
What is the state of this? |
|
You see, current design raises warnings, which kills runbot. @lasley suggested to add custom controllers and that's what we're waiting for. |
|
OK, thanks for the heads-up. Let's see if @hurrinico can work on this. |
|
Hi @pedrobaeza as i said few days ago, this mod is quite hard and at the moment i'm quite busy, so can be difficult to me redefine all the module |
|
I've actually already done this, just need to add tests. Will submit a PR today |
|
@lasley did you checked your code for making the PR? |
|
hurrinico#3 - TBD whether tests pass |
* Move legal pages to explicit /legal routes
[10.0] [IMP] website_legal: Move to explicit route
| type='http', | ||
| website=True, | ||
| ) | ||
| def show(self, page='legal'): |
There was a problem hiding this comment.
SEO-wise, if you have a /legal and a /legal/legal page that are the same, you get penalized.
I think you should better not add a default page and require it (404 error otherwise), or make it redirect to /legal/legal if not page.
Remember to add **kwargs so that we can add ?debug=assets and so on.
Also, this controller's name should be legal instead of show IMHO.
There was a problem hiding this comment.
/legal is the default route here. I guess technically /legal/legal would work too, but I'm pretty sure I rigged everything up as /legal
There was a problem hiding this comment.
Oh I see, you're recommending explicitly denying (still early here, need coffee).
What about /legal/overview or something? I don't like the one duplicated
| response = self.url_open('/legal') | ||
| self.assertEqual( | ||
| response.getcode(), | ||
| 200, |
There was a problem hiding this comment.
This will change with my above comment.
| name="Legal advice Link"> | ||
| <xpath expr="//footer//div/span[@t-field='res_company.name']" position="after"> | ||
| <span>- <a href="/page/legal">Legal advice</a></span> | ||
| <span>- <a href="/legal">Legal Advice</a></span> |
There was a problem hiding this comment.
/legal/advice maybe? Better than /legal/legal, right?
| name="Privacy policy Link"> | ||
| <xpath expr="//footer//div/span[@t-field='res_company.name']" position="after"> | ||
| <span>- <a href="/page/privacy">Privacy policy</a></span> | ||
| <span>- <a href="/legal/privacy">Privacy Policy</a></span> |
There was a problem hiding this comment.
It turns out that it is better for SEO having a explicit name than a short one (unless the explicit one is too long). What if we take the chance to rename this one to /legal/privacy-policy?
| name="Terms of use Link"> | ||
| <xpath expr="//footer//div/span[@t-field='res_company.name']" position="after"> | ||
| <span>- <a href="/page/terms">Terms of use</a></span> | ||
| <span>- <a href="/legal/terms">Terms of use</a></span> |
There was a problem hiding this comment.
This one could be /legal/usage-terms too.
There was a problem hiding this comment.
I went with terms-of-use so that it more closely matches the link text
|
@yajo as @hurrinico said #310 (comment) he cannot finish this PR so please make a PR to his branch to go ahead |
|
Superseding with #353 in order to save a bunch of side merges/PRs |
No description provided.