Se rendre au contenu
Odoo Menu
  • Se connecter
  • Essai gratuit
  • Applications
    Finance
    • Comptabilité
    • Facturation
    • Notes de frais
    • Feuilles de calcul (BI)
    • Documents
    • Signature
    Ventes
    • CRM
    • Ventes
    • PdV Boutique
    • PdV Restaurant
    • Abonnements
    • Location
    Sites web
    • Site Web
    • eCommerce
    • Blog
    • Forum
    • Live Chat
    • eLearning
    Chaîne d'approvisionnement
    • Inventaire
    • Fabrication
    • PLM
    • Achats
    • Maintenance
    • Qualité
    Ressources Humaines
    • Employés
    • Recrutement
    • Congés
    • Évaluations
    • Recommandations
    • Parc automobile
    Marketing
    • Marketing Social
    • E-mail Marketing
    • SMS Marketing
    • Événements
    • Marketing Automation
    • Sondages
    Services
    • Projet
    • Feuilles de temps
    • Services sur Site
    • Assistance
    • Planification
    • Rendez-vous
    Productivité
    • Discussion
    • Validations
    • Internet des Objets
    • VoIP
    • Connaissances
    • WhatsApp
    Applications tierces Odoo Studio Plateforme Cloud d'Odoo
  • Industries
    Commerce de détail
    • Librairie
    • Magasin de vêtements
    • Magasin de meubles
    • Épicerie
    • Quincaillerie
    • Magasin de jouets
    Food & Hospitality
    • Bar et Pub
    • Restaurant
    • Fast-food
    • Maison d’hôtes
    • Distributeur de boissons
    • Hôtel
    Immobilier
    • Agence immobilière
    • Cabinet d'architecture
    • Construction
    • Gestion immobilière
    • Jardinage
    • Association de copropriétaires
    Consultance
    • Cabinet d'expertise comptable
    • Partenaire Odoo
    • Agence Marketing
    • Cabinet d'avocats
    • Aquisition de talents
    • Audit & Certification
    Fabrication
    • Textile
    • Métal
    • Meubles
    • Alimentation
    • Brewery
    • Cadeaux d'entreprise
    Santé & Fitness
    • Club de sports
    • Opticien
    • Salle de fitness
    • Praticiens bien-être
    • Pharmacie
    • Salon de coiffure
    Trades
    • Bricoleur
    • Matériel informatique et support
    • Systèmes photovoltaïques
    • Cordonnier
    • Services de nettoyage
    • Services CVC
    Autres
    • Organisation à but non lucratif
    • Agence environnementale
    • Location de panneaux d'affichage
    • Photographie
    • Leasing de vélos
    • Revendeur de logiciel
    Browse all Industries
  • Communauté
    Apprenez
    • Tutoriels
    • Documentation
    • Certifications
    • Formation
    • Blog
    • Podcast
    Renforcer l'éducation
    • Programme éducatif
    • Business Game Scale-Up!
    • Rendez-nous visite
    Obtenir le logiciel
    • Téléchargement
    • Comparez les éditions
    • Versions
    Collaborer
    • Github
    • Forum
    • Événements
    • Traductions
    • Devenez partenaire
    • Services for Partners
    • Enregistrer votre cabinet comptable
    Nos Services
    • Trouver un partenaire
    • Trouver un comptable
    • Rencontrer un conseiller
    • Services de mise en œuvre
    • Références clients
    • Assistance
    • Mises à niveau
    Github Youtube Twitter Linkedin Instagram Facebook Spotify
    +1 (650) 691-3277
    Obtenir une démonstration
  • Tarification
  • Aide

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

  • CRM
  • e-Commerce
  • Comptabilité
  • Inventaire
  • PoS
  • Projet
  • MRP
All apps
Vous devez être inscrit pour interagir avec la communauté.
Toutes les publications Personnes Badges
Étiquettes (Voir toutl)
odoo accounting v14 pos v15
À propos de ce forum
Vous devez être inscrit pour interagir avec la communauté.
Toutes les publications Personnes Badges
Étiquettes (Voir toutl)
odoo accounting v14 pos v15
À propos de ce forum
Aide

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

S'inscrire

Recevez une notification lorsqu'il y a de l'activité sur ce poste

Cette question a été signalée
portalon-premise18.0
3 Réponses
1002 Vues
Avatar
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
Avatar
Ignorer
Avatar
Samad Alimadadi
Meilleure réponse

.

0
Avatar
Ignorer
Avatar
start@adjunto.fr
Auteur Meilleure réponse

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
Avatar
Ignorer
Avatar
Cybrosys Techno Solutions Pvt.Ltd
Meilleure réponse

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
Avatar
Ignorer
start@adjunto.fr
Auteur

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.

Vous appréciez la discussion ? Ne vous contentez pas de lire, rejoignez-nous !

Créez un compte dès aujourd'hui pour profiter de fonctionnalités exclusives et échanger avec notre formidable communauté !

S'inscrire
Publications associées Réponses Vues Activité
Adding Front-end/Website Theme to Odoo 18 Not Working
theme website on-premise 18.0
Avatar
1
janv. 25
3423
Trying to replace default “Invoices & Bills” breadcrumb in Odoo portal
portal
Avatar
Avatar
1
nov. 25
368
How To Hide Action Report By Picking Type Code ?
18.0
Avatar
Avatar
Avatar
3
nov. 25
592
Dynamically update cart icon after adding products from a reorder popup in Custom Odoo portal
portal
Avatar
Avatar
1
nov. 25
297
How do I set up budget management / planning Résolu
18.0
Avatar
Avatar
2
août 25
1089
Communauté
  • Tutoriels
  • Documentation
  • Forum
Open Source
  • Téléchargement
  • Github
  • Runbot
  • Traductions
Services
  • Hébergement Odoo.sh
  • Assistance
  • Migration
  • Développements personnalisés
  • Éducation
  • Trouver un comptable
  • Trouver un partenaire
  • Devenez partenaire
À propos
  • Notre société
  • Actifs de la marque
  • Contactez-nous
  • Emplois
  • Événements
  • Podcast
  • Blog
  • Clients
  • Informations légales • Confidentialité
  • Sécurité.
الْعَرَبيّة 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 est une suite d'applications open source couvrant tous les besoins de votre entreprise : CRM, eCommerce, Comptabilité, Inventaire, Point de Vente, Gestion de Projet, etc.

Le positionnement unique d'Odoo est d'être à la fois très facile à utiliser et totalement intégré.

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