1. Remove the mass mailing install checkbox from marketing and sales settings
2. Show the mass mailing settings only when the module is installed
3. Remove the marketing campaign install checkbox from marketing settings
4. Move the marketing_crm module into marketing_campaign
5. Merge the *.po files from marketing_crm with marketing_campaign
a many2many field can open a pop up dialog with different views, such
as form view and list view. when the user click on the create button,
it should hide the list view and display the form view. apparently,
this behavior was hardcoded in the pop up dialog, and broken at some
point between v8 and master.
A proper fix would be to abstract the
view manager behavior as a mixin and use it for the selectcreatepopup
widget, for the one2many view manager and for the viewmanager. But this
will take too much time for now, so a quick fix will do it. (however a
task has been created)
has also been added, because the action open_website_url linked to the publish
button is not defined on res.users model (but on its inherited partner).
It now has the method that is routed on its partner.
employees. Website publishers now see all employees + a publish button, like
for other website documents. Other people see the same published employees
as before.
The URL link for employees is not a specific url for each employee but the
about us page.
Also cleaned grade form view and its inheritance.
Now the website displays partners related to all grades (website publisher) or
only published grades (other people). A publish button has been added in the
website for grades, to have the same behavior as for other website documents.
Also added basic controllers on the partner model, allowing to see the public
page of a published partner (or all partners if website manager). The template
was already existing, but the controller was missing. It has been added.
[FIX] website_customer: fix the inheritance of view as the website group has been
removed in the parent view. Also added a breadcrumb fix.
website_hr_recruitment, website_sale: add published mixin on blog / event /
track / job / product objects and update their website url and form view
according to the publish mixin/button refactoring.
and website_url fields. This will allow to remove custom code in every website
addons that redefine those two fields and the URL getter method.
The published button in backend has also been cleaned. It is now a link button
that redirects to the website_url. It does not change the publish status
anymore. Indeed it makes sense publish and unpublish website documents
directly in the website, while checking that everything is correct, instead
of doing it in the backend.
Next commits will update the Odoo addons to use this mixin and the new button
in the form view.
- removed unnecessary More menu entry to see the meetings from applicants
- small wording / display fixes on applicant form view
- applicant graph view tuning
- job form view inheritance cleaning
- labelling
- check_holidays does not raise anymore, the constraint is responsible of doing it
- cleaning of holidays status form view
- number of remaining days on an employee is now in technical feature, leave
summary exist to have statistics
The motivation behind that change is that the hash index in postgres is not
compatible with streaming replication. The new index is defined on md5(src),
which provides good performance without size limitation on src.
The limit on the list of answers and questions posted by
a given forum user is purposely limited to reduce the
performance penalty for displaying them all.
(see 78fa861936)
However seeing the full list is useful for forum moderators
(e.g. when tracking down abuse), and there are only a few
such users with high karma, so enabling it for them is
negligible performance-wise.
Fixes#3955
* remove ZeroClipboard, pain to test locally and deployment didn't work
right due to needing absolute path to the swf always
* remove the clipboard alteration on the fly, behaves oddly and can be
confusing
* add an explicit button to expand and collapse the setup content
* fixup some styling
The first line having the globalisation code is the globalized amount,
then the next line having this same globalisation code
is the last line of the globalisation (the last children).
The first line must no be included in the bank statement,
but the last line must (as this is a real children line)
This is a regression of commit: cbc52f80eb
Official doc concerning globalization code:
The value which is mentioned (1 to 9), specifies the hierarchy level of the
globalisation of which this record is the first.
The same code will be repeated at the end of the globalisation
courtesy of mva. This adds the weekday function to date objects in
pyeval. This will be useful for adding better filters (such as this
week) in the searchview.
Martin