Routes introspection fixes:
* convert <int:x_id> to <model():x>
* remove **kw, specify explicit enable_editor parameter
Suckless:
* remove useless `/blog/tag/` route
* add pagination support in tags
* add pagination support when no category or tag (`/blog/`)
* remove handling of impossible case of category *and* tag
* make exclusive cases more exclusive, avoid repeatedly checking the
same condition over and over
bzr revid: xmo@openerp.com-20131108142149-v2z2m6kwgf97o7b0
* most controllers turn out to be complete cork and thus can't be
reversed
* fixup a pair of simple controllers
TODO:
* fixup more controllers
* how can labels/page names be produced?
* grouping/categories of links?
At a high level, workings are pretty simple:
* iterate on all rules (every url pattern produces a werkzeug rule)
* check if the url can make sense as a link: GET, http, no auth or
public auth, coming from the CMS (no web client links) and all
converters can generate values for themselves (e.g. a url with an
`int` converter can't be generated as there is no finite set of
integers, let alone one small enough to make sense to show to users)
* check if the controller function bound to the URL can use the URLs
we can generate (no **kwargs as that means arbitrary get|post
parameter, no query param without a default value (a query param is
a parameter which does not come from a URL/rule converter))
* use rule converter(s) to generate a matrix of values, and build urls
from these
bzr revid: xmo@openerp.com-20131108132615-2n7t1vj8hz9v9eis
context was not passed while setting request.website
forced to refactor a bit in order to make true model methods but stopped
because it will be duplicated work when migrating to the new api
bzr revid: fme@openerp.com-20131107151400-9dmtgz7xs34qmbmq
Depending on the way the search view is setup, a single item
(e.g. "Search foo for bar") can follow a list of a bunch of
completions. In that case, it is hard to notice that it's not just one
more item of said list.
Add a marker on the first of every completion list in order to catch
1-item lists (or lists without titles/categories) and prepend a small
border every time, so that single-element completions following
lists-with-titles can be noticed.
bzr revid: xmo@openerp.com-20131107112858-1xyvcesize0doblz
hide it and replace it with a button telling the user what we're
currently doing (uploading the image).
Leave the possibility of discarding the whole thing and going away
though.
bzr revid: xmo@openerp.com-20131106152412-eb283vghb18aafyr
On runbot the base url dispatches into a unknown void of no db being
selected and the CMS thus 404s. For human beings there are additional
links to special subdomains setting the right db in the right place
(or maybe the right dbfilter, whatever) but that doesn't work right
for the crawler test suite.
Instead go through /web/ with a forced db selection, this *should* set
the db correctly in the user's session even if he's anonymous and thus
allows us to browse said db.
No idea if this fevered idea is actually going to work.
bzr revid: xmo@openerp.com-20131106115547-0ozlex09svkecrhb
Fabien Pinckaers
ddm
Christophe Matthieu
Xavier Morel
Fabien Meghazi
Stephane Wirtel
niv-openerp