summaryrefslogtreecommitdiff
path: root/addons/website/static/src/xml/website.pageProperties.xml
AgeCommit message (Collapse)Author
2017-10-12[IMP] website: warn user about key change when editing special file namerde
The idea is to warn user if he created a special file (website.page with supported extension) and he wants to change the file's name, which will at the end also change the key). If this special file has been t-called elsewhere, they t-call wont work anymore This is why warning user is needed. Note that this is different than the already existing page_search_dependencies that is just checking if the URL is present in menus, templates, blog or pages. This is about checking if the key is present somewhere. (we assume that if the key is present, it is surely about a t-call. Technically, the flow is: 1. Get supported extension 2. Get key dependencies 3. Check if user modify name 4. If name changed and it is/was a supported extension (special file) and it has dependencies (surely t-call) then warn user these call wont work anymore -- search_page_dependencies is also improved by returning links to be clickable (on delete dialog eg) and splitting template/page results. it also refactor dependencies warning that was creating HTML in javascript into using XML template
2017-09-25[IMP] website: pageManagement - improvements according to first feedbacksrde
- labelling and screen redesign (update labels, hide labels, hide fields, ...) - make UI more mobile friendly (icon biggest, color using less variables,...) - Page & Redirection menu are for visible only in debug mode - Add meta noindex for website.page not shown in sitemap - Add mechanism to be able to edit in backend a broken view (Needed for - Internal Error 500, css, js file, ...) - website pagemanager dedicated to website_publisher only
2017-09-15[ADD] website: add new page managementrde
website.page = old ir.ui.view with page=True website.redirect is a new mechanism to replace in the futur the ir.attachment mechanism of redirect. From now, we don't have a specific /page controller to serve 'page'. We use a new model website.page which is rendered if none route matches the url and that the field 'url' on website.page matches the request.httprequest.path. The order to serve a path is: - Routes defines in controllers (/shop, /blog, ...) - ir.attachment with name matching the path - website.page with url matching the path - website.redirect with url_from matching the path - 404 To improve: - allow regexp in website.redirect model - allow to edit the view_arch from the page.management via redirect backend (needed when traceback in the page, or when modifying a js/css/less/...)