| Age | Commit message (Collapse) | Author |
|---|
|
Commit e11f23b701cd061ee2090e506e7ff71cc2ed8c33 split the website
customize_template_get into web_editor and website ones. This split
was not perfect and commit 20861b482a0f84c2946cc14a05648b87b95bdac4
tried to make it work... but did not made it totally and added an
indirect dependency to website module in web_editor...
As the final result is wrong and inconsistent and that the previous
9.0 implementation was already ugly, this was not possible to make
a consistent full-stable fix.
This commit tries to make a fix as stable as possible (the main method
name did not change, the arguments did not change, their purpose is
the same, ...) which makes the code work and be less ugly. However,
the function returns are now slightly different (and JS depends on it).
It returns only valid view information (not header stuff which is not
related to anything and the inherit_id value is now a combination of
the inherit view id and name). Also, a new private method has been
created.
Also, the method contained code which was deprecated since saas-6 but
was never removed (and never broke anything "by chance").
In master these methods will be refactored to make more sense.
|
|
Commit 48a1eaf79273fbf40b4b0a55ed28d27382477450 adapt the welcome
message on website so that it fits the page height. But this does
only worked for large screens as the height was forced to main
height... which is smaller than the default welcome message height
on small screen. The fix only had to use min-height instead of height.
|
|
Studio altered (probably by error) the default value.
We reset the old default value, and by security, add the params in the call
|
|
Following commit 3cbc7ebc4c3e0edb25d1a91dcbf4df163ef6d29e, the bug for customize menu
could have been ignored but as it is an easy fix :
The customize menu is filled after a rpc which is performed on
mousedown on the menu toggle. But in the case the user clicked on the
customize menu before the mousedown handler was attached... nothing
occured. It is possible since the customize menu is rendered but its
JS widget is only attached to it once everything is ready.
Now, the menu is filled on first mousedown or if the menu is already
opened when the JS widget is attached.
|
|
In edit menu, search with de demo data /shop, was the 12th results, but limit 9.
We only move the problem to later, but when the user start with the website apps,
it avoid to be lost on first menu creation.
|
|
|
|
For the sake of simplicity, the method adapter `call_kw_multi` does not look up
for `ids` in keyword arguments, instead it expects it in positional arguments.
|
|
|
|
|
|
The code for page creation from menu edition dialog was there but
invisible to the user because of a wrong qweb template inheritance.
Indeed, the edit menu dialog relies on an extension of the link dialog
template. But this one is extended in-place in another location and
that extension is not considered when the second extension is made
because a t-extend always use the base template. The only solution to
achieve the same result is to copy the edit menu dialog qweb extension
in Javascript.
Note: the feature was still available from the link dialog in page
edition though because this was not concerned by the wrong qweb
extension.
However, adding a page by this way would create multiple pages because
one was created each time a page name was entered (and not only on
save !). So typing "test", then changing its mind and typing "hello",
then rechanging to "test", then hitting the save button created the
"test, "test-1", "test-2" and "hello" pages.
This fix takes advantage of an already present parameter which can
determine if a new page should be created or not. However, a code
refactoring should be done in master for these classes.
|
|
* Mobile preview dialog
* Add page dialog (allow to click anywhere to close the modal)
* Change label for "auto resize" and "resize" options to "auto size"
and "fixed size" and add a checkmark to the currently active one
* Overlay border / Options dialog content
* Hide the odoo navbar after a delay when the editor starts
|
|
|
|
* Adapt DOM selectors
* Refactore dialog XMLs to have odoo styling
* New editor options (background-position, ...)
* Various improvements
|
|
|
|
class oe_no_empty or oe_not_editable
|
|
|
|
for html field) and website
|
|
|
|
Use .css convert into absolute url
|
|
Firefox doesn't allow to access sheets cssRules
In such a case, we just pass, these css rules will simply
not be available for the edition of some inputs.
Probably, when a real use case needing these external css rules
will come, we will probably need to fetch these style sheets
another way.
opw-642752
|
|
Apparently in some unclear situations, using delete on the dataset blows
up (issue appears in both Safari and phantomjs) failing the test.
Only try the deletion if the item is actually present in the dataset,
and wrap it in a try/except to handle it blowing up
|
|
This reverts commit e18a3a43e44da86a92acbe77501838ec6deb87db.
website.error is used in the Javascript file it was removed from,
in website.js, line 350.
Another solution to not load this template when not needed has
to be found
opw-640822
|
|
|
|
To avoid loading unneccesary templates on every page.
|
|
|
|
when closing a modal, the class 'modal-open' was removed from the
'body' tag and all the existing modals became not scrollable.
The class 'modal-open' must be kept in the 'body' tag if there is
still a visible modal in the dom.
Inspired from commit: dee000be14fd55f7d287eee8569f769505f339ac
opw:633801
|
|
|
|
a previous click, need to get the parent node to trigger the history
|
|
modal after add a question in website_forum
|
|
The module system needs to know the dependencies of a given module
before executing the function. This is why the dependencies were
defined once in an array, and then were described one more times in the
call to require.
But a trick can simplify this: the boot function can parse the string
representation of the module and extract the calls to require from it.
It is more work for the processor, but it leads to simpler module
definitions.
|
|
|
|
button for forum; raise if click on a button before click inside the editor
|
|
with the website builder
|
|
|
|
|
|
that.
|
|
field to keep image in center
|
|
opw-626209
|
|
media is changed
|
|
insert images and option resize apply width in percent
|
|
available in image edition bar)
|
|
last and first char
|
|
This module allow to make versioning and A/B testing of the website.
|
|
button from the modal, all its right sibling buttons are dis-appeared.; delete content of the range is wrong
|
|
and need to push the new parser in website.editor.fontIcons javascript object)
|
|
the top editor bar
|
|
|
|
the pictograms or videos as cover of blog.
|
|
|
|
unable to do the opposite. Can't select text from right side to left. Fix re-range.
|
