For privacy_visibility 'followers' or 'portal', the user should be follower of the project (not the task).
Remove public access to portal task
Fixes #2372

If no project on the task (or other rule), an employee (not a portal) can access if is follower of the task.
Follower rule is not enough as a user creating a rule will subscribe to the rule but to subscribe to record, the user should have access to it in the first place.
To make sure the snake does not bit its tail, fallback to give access on task where the user is reponsible (user_id = user.id).
Fixes #139

Adapted the tests to the new behaviour (removed not relevant and added some on creation)

[FIX] Avoid access error on XML id in browse when choosing picking type for manual purchase order.  As they are ordered by sequence, just take the first you can find.

   Remove useless document ready
   Add select2 to frontend to allow public user to use tags

   Use if_dom_contains to check if we need to load js
   Fix bug where _tag_to_write_vals was called like old API but model converter was new api
   Move IsKarmaValid and Load CKE only in website_forum context

Since bank statement do not use vouchers anymore in 8.0,
it's not necessary to create the voucher anymore.

Additionally, I add an extension point to let modules adapt
the statement line.

When creating a class with the new API, we should use models.Model
instead of just Model.

closes #3713

* add latex support for exercise admonition
* latex freezes/crashes on {HEAVY WIDE-HEADED RIGHTWARDS ARROW} so
  replace them by more manual arrows
* add some preamble configuration, may not even be necessary
* generate WS setup code only in HTML output. WS doc in latex still
  isn't great as it displays all 4 languages one after the other,
  ideally they should be tagged or something, so only one language at a
  time is generated in non-HTML outputs

[FIX] website_forum: add fake tour for people waiting the tour. To remove in master. Without it, localstorage loop to search this unexisting tour after the install...

Doc pages used container() which is width-limited, works acceptably for
single-column content but WS page takes 2 columns with code, having as
much space as possible is a much better idea.

Mayhaps it should even use lg-column(2) instead of md-column(3)?

also move porting checklist/doc/thing to bottom of document, it's mostly
for seasoned or internal developers

When a failure occurs, or when exiting an assertRaises(), the environment
should not contain fields to recompute.

* opt-in toc navification
* unhide index toctree, it's now back to a list of documents
* remove text thing

closes #3685

This reverts commit b2134381.

But should use date or datetime according to the widget type

This fix is related to 69d60465

The delivery of a purchase order was not keeping the currency and cost price
from the purchase order for the reception. This was problematic for orders where
the invoice was generated from the picking (Invoicing Control: Based on incoming
shipments). The currency of the purchase order was kept while the cost was the
one in the company's currency.
It's better to keep the currency of the purchase order to make the invoice as
it's usually the one expected (and not convert everything to the currency of the
company). opw 615555