I’m legitimately freaking out. I am trying to render a .gjs component, but that doesn’t show up. I tried rendering in template tags <h1>Hi</h1>, but even that won’t show up. What is going on? import { apiInitializer } from "discourse/lib/api"; export default apiInitializer((api) => { api.renderI…

I am incredibly blind. The file was in api_initializers, not api-initializers :facepalm:.

Great… now my component isn’t rendering… Does anyone have any ideas? My api-initializers file: import { apiInitializer } from "discourse/lib/api"; import CategoryHeader from "../components/category-header"; export default apiInitializer((api) => { api.renderInOutlet("above-category-heading", …

[imagen] Nate Dhaliwal: Everything looks technically correct, so why doesn’t it render :thinking:..? How do you conclude that it looks correct, did you follow basic steps? Check eslint errors and warnings and resolve them Check console errors and warnings and resolve them

[imagen] Manuel Kostka: Check console errors and warnings and resolve them Didn’t see any so I skipped the first one. Turns out :facepalm: [A dark-themed interface displays a list of code linting tools—ESLint, Stylelint, Prettier, and Ember template lint—each marked with a red 'x' indicati…

@manuel So I’ve fixed everything (except for some vague Prettier errors: <a class="lightbox" href="https://d11a6trkgmumsb.cloudfront.net/original/4X/b/5/8/b58d4578f8ab4d820fcd8543a48612a5eb9460c0.png" data-download-href="/uploads/short-url/pU55RX6dHUOGGqxPIm5glpUAoIU.png?dl=1" title="A terminal window displays the output of running the command, followed by warnings about code style issues in several files and an error indicating the process completed with an exit code of 1. (Captioned by AI)">[A terminal window displays the output of running the command, followed by warnings about code style issues in several files and an error indicating the process completed with an exit code of 1. (Captioned by AI)] ) but not…

I’m not sure what your current code is after your fixes, but seeing the warning you’re getting, the .category-title-header div should at least be rendering in the DOM. I recommend inspecting the page in your browser. Also, try tossing in a bunch of console.log to see where the application reaches t…

[imagen] Nate Dhaliwal: Any ideas? If you can, the easiest way to get feedback on this would be to share your repo. The files you shared above are not stand-alone and require a settings file as well.

Yes, sorry for not including that earlier. That would be: https://github.com/NateDhaliwal/discourse-category-headers/tree/fix-compatibility-issues-new-new (The fix-compatibility-issues-new-new branch.) [imagen] Alteras: I recommend inspecting the page in your browser. Also, try tossing in a b…

@Alteras It’s actually there, but not showing for some reason. Adding display: block !important made it appear, but the styling is now quite different :slightly_frowning_face: EDIT: Got the CSS fixed, and the headers are now displaying. Thanks so much @merefield @Alteras @manuel !

Seems to work fine now :+1: I still get some undefined errors in the console. You should use optional chaining with the ?. operator when looking up nested structures. For example: this.args.category.description?.replace

¿api.renderInOutlet no se está renderizando?

Desarrollador

NateDhaliwal (Nate Dhaliwal) 27 Junio, 2025 07:24 2

Soy increíblemente ciego. El archivo estaba en api_initializers, no en api-initializers .

Tema		Respuestas	Vistas
Cannot put the template in the desired outlet Development	13	293	13 Noviembre 2024
Templating of my "component" broke. How do I fix it? Development	15	108	16 Abril 2026
Overriding .gjs files - not possible? Development	2	616	10 Octubre 2023
Showing different content for mobile view in a .gjs file Development mobile , ember	5	115	18 Julio 2025
Render a post above the discovery-list-container-top Outlet Development	8	111	24 Febrero 2026

¿api.renderInOutlet no se está renderizando?

Temas relacionados