跳至內容
Odoo 選單
  • 登入
  • 免費試用
  • 應用程式
    財政
    • 會計
    • 發票
    • 開支報銷
    • 試算表 (BI)
    • 文件管理
    • 電子簽名
    銷售
    • 客戶關係
    • 銷售
    • POS 銷售點管理 - 零售
    • POS 銷售點管理 - 餐廳
    • 訂閱
    • 租賃
    網站
    • 網站製作
    • 電子商務
    • 網誌
    • 討論區
    • 線上客服
    • 網上學習
    供應鏈
    • 庫存
    • 製造管理
    • 產品生命周期
    • 採購
    • 保養維護
    • 品質管理
    人力資源
    • 員工管理
    • 招聘
    • 休假
    • 工作表現評核
    • 內部推薦
    • 車隊管理
    市場推廣
    • 社交媒體推廣
    • 電郵推廣
    • 短訊營銷
    • 活動
    • 自動化推廣
    • 網上調查
    服務
    • 專案管理
    • 工時管理
    • 外勤服務管理
    • 技術支援
    • 工作規劃
    • 預約管理
    生產力
    • 聊天
    • 批核
    • 物聯網
    • VoIP
    • 知識庫
    • WhatsApp
    第三方應用程式 Odoo Studio Odoo 雲端平台
  • 行業
    零售
    • 書店
    • 服裝店
    • 家具店
    • 食品雜貨店
    • 五金店
    • 玩具店
    餐飲及款待
    • 酒吧及酒館
    • 餐廳
    • 快餐
    • 賓館
    • 飲品分銷商
    • 酒店
    房地產
    • 地產代理公司
    • 建築師事務所
    • 建造業
    • 物業管理
    • 園藝
    • 業主聯會
    顧問服務
    • 會計公司
    • Odoo 合作夥伴
    • 市場推廣公司
    • 律師事務所
    • 人才招募
    • 審計及認證
    製造管理
    • 紡織
    • 金屬
    • 家具
    • 食品
    • 啤酒廠
    • 企業禮品
    保健與健身
    • 運動俱樂部
    • 眼鏡店
    • 健身中心
    • 健康從業人員
    • 藥房
    • 髮型屋
    技術行業
    • 雜工
    • IT 硬體與支援
    • 太陽能系統
    • 鞋匠
    • 清潔服務
    • 暖通空調服務
    其他
    • 非牟利組織
    • 環境保護機構
    • 廣告板租賃
    • 攝影服務
    • 自行車租賃
    • 軟體經銷商
    瀏覽所有行業
  • 社群
    學習
    • 教學影片
    • 使用說明
    • 認證
    • 培訓
    • 網誌
    • Podcast
    增強教學效能
    • 教育計劃
    • Scale Up! 商業遊戲
    • 到訪 Odoo
    取得軟件
    • 下載
    • 版本對照表
    • 版本說明
    合作
    • GitHub
    • 討論區
    • 活動
    • 翻譯
    • 成為合作夥伴
    • 合作夥伴服務
    • 登記你的會計服務公司
    獲取服務相關資料
    • 尋找合作夥伴
    • 尋找會計服務
    • 預約顧問諮詢
    • 安裝及推行服務
    • 客戶案例
    • 支援
    • 軟件升級
    GitHub YouTube Twitter LinkedIn Instagram Facebook Spotify
    +1 (650) 691-3277
    預約示範
  • 定價
  • 技術支援

Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:

  • 客戶關係
  • e-Commerce
  • 會計
  • 庫存
  • PoS
  • 專案管理
  • MRP
All apps
只限註冊用戶才可與社群互動。
所有帖文 人 獎章
標籤 (查看所有)
odoo accounting v14 pos v15
關於此討論區
只限註冊用戶才可與社群互動。
所有帖文 人 獎章
標籤 (查看所有)
odoo accounting v14 pos v15
關於此討論區
支援

owl component: render to qweb templates via json, possible?

訂閱

此帖文有活動時,接收通知

此問題已被標幟
portalon-premise18.0
3 回覆
956 瀏覽次數
頭像
start@adjunto.fr

I have a small sample app that correctly renders an owl component.  I'm trying to incorporate the component into a larger app made with qweb templates and widgets.

For the small program that works... the controller:

class MyController(http.Controller):

    @http.route('/owlg1/portal_page', type='http', auth='public', website=True)

    def render_portal_page(self):

        _logger.info ("render_portal_page(self), start...")

        html_content = request.render('owlg1.portal_page')

        _logger.info("render_portal_page : Rendered HTML content: %s", html_content)

        return html_content

...the template

<template id="portal_page" name="My Portal Page">
<t t-call="portal.frontend_layout">
        <div id="wrap">
                <div class="container">
                    <h4>My Portal</h4>
                    <owl-component name="owlg1.ChatComponent"/>
                </div>
        </div>
    </t>
</template>

and last, part of the manifest:

    'depends': ['web', 'website', 'im_livechat', 'mail'],
    'assets': {
        'web.assets_frontend': [ ... widget, owl component, owl component template ],
    },
    'data': [
        'views/portal_page.xml',
    ],


The owl component, the main widget and the owl template are all small, generic pieces. (I can post them if you wish)


In my larger app I would like to incorporate the same component into a page controlled by widgets and templates.  The template holding the owl component is not immediately on the page when the user goes there.  The user has to click on a few links to drill down to the template with the owl component is.  The source code is like this:

The widget that renders various part of the page, and the method in question:

const PortalDashboardWidget = publicWidget.Widget.extend({
    selector...
    events... (but nothing related to the button in the own component)
    ... methods...

_setupSubjectDetail: async function(in_userSubjectId) {
    const userSubjectResult = await rpc(
     urlBase + '/dashboard/usersubject/chatbutton',   
                    { userSubject_id: in_userSubjectId }
      );
    $('#chat-block').html(chatButtonResult.html);

});

publicWidget.registry.PortalDashboardWidget = PortalDashboardWidget;
export default PortalDashboardWidget;
The controller:

@http.route(WebsiteController._routes['base'] + '/dashboard/usersubject/chatbutton', type='json', auth='user')

def getChatButton(self, userSubject_id=None, **_kw):
    ... get the chat id from the db, livechat_channel_session.id  (this part works)
    html_content = request.env['ir.ui.view']._render_template(
      "myapp.chat-button-content", { 'chat_session_id': livechat_channel_session.id
    })
    html_content = str(html_content)
    return {'html': html_content}

... and finally part of the manifest:

   'depends': ['base_setup',
        'base',
        'web',
        'portal',
        'project',
        'mail',
        'website',
        'im_livechat',
    ],
    'installable': True,
    'application': True,
    'data': [
        'security/ir.model.access.csv',
...templates... except the owl-component template
        'data/website_data.xml',
...
    ],
'assets': {
    'web.assets_frontend': [
        'myapp/static/src/js/chat/chat_service.js', #owl service, component, template     
'myapp/static/src/js/chat/chat_component.js',
        'myapp/static/src/xml/chat/chat_template.xml',
        ... scss, images, widget javascript
    ],
},


chat-block is a template that is not immediately rendered when the user goes to the page.  The user has to click to "drill-down" to the template where the chat button is.

The above code works well for all of my other templates and widgets, but in this case, when the teamplate is rendered by the controller, <owl-component>... is in the rendered html, and it is inserted into the web page and sits there, inert.


If I move the owl component to a higher level template, one rendered as shown in my sample code, with a controller using type='http',  and "render(...)", it works.  So I believe the component itself is ok. 


I belive I have to alter the widget javascript and the python controller, but have no idea how.  I've modified both files in various ways but have not succeeded.  One idea I had was to make the controller method type='http' so get the rendering correct, and then somehow change it's http response into a json response to work with the widget.  Mostly I either get <owl-component> in my rendered html, and it does not activate, or I get empty json.


Any help/examples would be greatly appreciated.  If you could provide the "import... " lines in your answer that would help.  Thanks!






0
頭像
捨棄
頭像
Samad Alimadadi
最佳答案

.

0
頭像
捨棄
頭像
start@adjunto.fr
作者 最佳答案

Hello CTS, definitely better... but not quite working.

I'm getting this error message:


OwlError: Missing template: "adjuntohub.ChatContentTemplate" (for component "ChatComponent")


Which I find strange, because when I put <owl-component> on the main page it finds the template.  So I'm pretty sure the manifest is ok


here is the component:

/** @odoo-module **/

import { useService } from "@web/core/utils/hooks";

import { Component } from "@odoo/owl";  

import { registry } from "@web/core/registry";


export class ChatComponent extends Component {


    static template = 'adjuntohub.ChatContentTemplate';

    static props = {

        sessionId: { type: String, optional: true },  // chat session id as string

    };


    setup() {

        console.info("ChatComponent(), setup(), start...");

        this.mail_store_service = useService("adjuntohub.ChatService");

        this.chat_id = parseInt(this.props.sessionId);

        console.info("ChatComponent(), setup(), chat_id is %d.  End.", this.chat_id);

    }


    async onClickChat(ev) {

        ev.preventDefault();

        if (!this.props.sessionId) {

            console.warn("ChatComponent.onClickChat(): sessionId not provided as prop, hard coding to 20 (subject 1336-sv) for testing");

            this.props.sessionId = "20";

        }

        const chat_id = parseInt(this.props.sessionId);

        console.info("ChatComponent.onClickChat(chat_id=%d) start...", chat_id);  // chat_id -> channel_id


        if (chat_id) {

            console.info("  chat_id present, try to open the chat");

            await this.mail_store_service.open_specific_chat(chat_id);

        } else {

            console.warn("chat_id not present");

        }

        console.info("ChatComponent.onClickChat(chat_id=%d) end", chat_id);


    }

}


registry.category("public_components").add("adjuntohub.ChatComponent", ChatComponent);



Here is the component template:


<?xml version="1.0" encoding="UTF-8"?>

<templates xml:space="preserve" >


    <t t-name="adjuntohub.ChatContentTemplate" >  <!-- owl="1" didn't change anything -->

        <p> OWL component adjunto_hub.ChatContent</p>

        <button t-on-click="onClickChat"

            id="chat-button"

            t-att-data-chat-id="chat_id"

            class="btn btn-primary">

            Open Chat

        </button>

        <p>chat_session_id=<t t-esc="chat_session_id"/> </p>

    </t>

</templates>



Here is the crucial part I didn't have in my widget, mounting the component:

// Dynamically mount the OWL component
// Find the <owl-component> element inside the inserted HTML
const owlEl = $chatBlock[0].querySelector('owl-component');
if (owlEl) {
  const cc = registry.category("public_components").get("adjuntohub.ChatComponent");
    mount(cc, { target: owlEl }); 
}

So the controller renders the html and the javascript correctly places it.  And then this code tries to mount it.

What I don't see is any sign of the component being initialized.  I did see that when I had the component on my main page (the page rendered with http).  But I removed the component from that page. 

Things I've tried:
adding owl="1" attribute to the template
using components instead of public_components
I tried a few variations of mountComponent but still got the same error.

And, I don't know if this makes a difference, but I couldn't find this._rpc(...) so I used just rpc(...)

Any ideas?  Maybe look at cc, see if is has a template?
Thank for your help, much obliged.







0
頭像
捨棄
頭像
Cybrosys Techno Solutions Pvt.Ltd
最佳答案

Hi,


You need to:


    Return the template HTML via JSON as you do.

    After inserting the HTML, manually mount the OWL component using @web/owl utilities.

Step 1: Import necessary OWL modules in your widget JS


/** chat_widget.js **/

import { registry } from "@web/core/registry";

import { Component } from "@odoo/owl";

import { mount } from "@odoo/owl";

import { publicWidget } from "web.public.widget";


Step 2: Update your widget _setupSubjectDetail method


_setupSubjectDetail: async function(in_userSubjectId) {

    // Fetch the template HTML via RPC

    const chatButtonResult = await this._rpc({

        route: "/dashboard/usersubject/chatbutton",

        params: { userSubject_id: in_userSubjectId },

    });


    // Insert HTML into the DOM

    const $chatBlock = $('#chat-block');

    $chatBlock.html(chatButtonResult.html);


    // Dynamically mount the OWL component

    // Find the <owl-component> element inside the inserted HTML

    const owlEl = $chatBlock[0].querySelector('owl-component');


    if (owlEl) {

        const ChatComponent = registry.category("components").get("myapp.ChatComponent");

        mount(ChatComponent, { target: owlEl });

    }

}


Step 3: Ensure your OWL component is registered


/** chat_component.js **/

import { Component } from "@odoo/owl";

import { registry } from "@web/core/registry";


export class ChatComponent extends Component {

    static template = "myapp.ChatComponentTemplate";

}


registry.category("components").add("myapp.ChatComponent", ChatComponent);


* ChatComponentTemplate is your OWL template ID in XML (chat_template.xml).

* Ensure the template is loaded via assets (web.assets_frontend).


Step 4: Controller remains type='json'


No need to change the Python controller. Your current setup works:


@http.route('/dashboard/usersubject/chatbutton', type='json', auth='user')

def getChatButton(self, userSubject_id=None, **_kw):

    # Prepare the template HTML

    html_content = request.env['ir.ui.view']._render_template(

        "myapp.chat-button-content",

        {'chat_session_id': livechat_channel_session.id}

    )

    return {'html': str(html_content)}


- OWL does not auto-initialize components inserted via AJAX/JSON.

- After inserting the HTML, you must mount the OWL component manually.

- Use registry to fetch the component and mount from @odoo/owl.

- Keep controller type='json' for AJAX loading — no need to convert to http.


Hope it helps

0
頭像
捨棄
start@adjunto.fr
作者

Yes, I got closer, thanks! But it's still not working. I put the details in another reply, yesterday. I didn't see the comment button.

喜歡這則討論?不要只閱讀,加入發表意見吧!

今天就建立帳戶,享受獨家功能,與我們精彩的社群互動!

註冊
相關帖文 回覆 瀏覽次數 活動
Adding Front-end/Website Theme to Odoo 18 Not Working
theme website on-premise 18.0
頭像
1
1月 25
3394
Trying to replace default “Invoices & Bills” breadcrumb in Odoo portal
portal
頭像
頭像
1
11月 25
357
How To Hide Action Report By Picking Type Code ?
18.0
頭像
頭像
頭像
3
11月 25
566
Dynamically update cart icon after adding products from a reorder popup in Custom Odoo portal
portal
頭像
頭像
1
11月 25
286
How do I set up budget management / planning 已解決
18.0
頭像
頭像
2
8月 25
1083
社群
  • 教學影片
  • 使用說明
  • 討論區
開源
  • 下載
  • GitHub
  • Runbot 測試環境
  • 翻譯
服務
  • odoo.sh 網頁寄存
  • 支援
  • 升級
  • 自訂功能開發
  • 教育及培訓
  • 尋找會計服務
  • 尋找合作夥伴
  • 成為合作夥伴
關於我們
  • 關於 Odoo 公司
  • 品牌資產
  • 聯絡我們
  • 招聘
  • 活動
  • Podcast
  • 網誌
  • 客戶
  • 法律 • 私隱政策
  • 安全性
الْعَرَبيّة Català 简体中文 繁體中文 (台灣) Čeština Dansk Nederlands English Suomi Français Deutsch हिंदी Bahasa Indonesia Italiano 日本語 한국어 (KR) Lietuvių kalba Język polski Português (BR) română русский язык Slovenský jazyk slovenščina Español (América Latina) Español ภาษาไทย Türkçe українська Tiếng Việt

Odoo 是一套開放源碼的商業管理系統,涵蓋你公司全部的營運需要,包括客戶關係管理(CRM)、電子商務、會計、庫存管理、POS(銷售點管理)、專案管理等應用程式。

Odoo 的獨特價值是非常簡單易用,同時將不同應用程式完美整合。

Website made with

Odoo Experience on YouTube

1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.

Live support on Youtube
Watch now