Anything like api.decoreateCooked() for topics displayed via Page Publishing?

[craigconstantine]

Is there anything analogous to api.decorateCooked() for Page Publishing display of a topic?

I have some j/s in a theme component which is called by using api.decoreateCooked(). Works great. But when I view the topic via Page Publishing, the j/s doesn’t get called. So I’m assuming that api. method doesn’t apply.

Here’s a topic that shows it in action. Everything you see below the “Upcoming Events” H1 is not actually in the topic. That content is added into the DOM dynamically.

https://forum.podcaster.community/t/podcaster-community-calendar/123

Here’s that same topic using Page Publishing. The stuff in the yellow box (local CSS rule styles the div explicitly) is what is literally in the topic. When it’s “cooked” the j/s replaces the DIV (see below) with other DOM elements…

https://forum.podcaster.community/pub/calendar

So you can see what’s going on, here’s the actual DIV in the topic. The j/s in the theme component spots DIVs like this one and modifies the DOM.

<div data-custom="umbconn" data-umbconn="/vcalendar">

A list of calendar events appears here if viewed on the Podcaster Community forum at https://forum.podcaster.community/t/podcaster-community-calendar/123

</div>

[craigconstantine]

oh, crud, Page Publishing - #76 by pfaffman

[Canapin (Coin-coin le Canapin)]

Hi Craig

You may be interested in this alternative:

Page Publishing

An alternative to Page Publishing - another method is to use CSS to remove the unwanted elements on a regular Topic Post, while preserving all of the functionality (i.e. Javascripts in installed Theme Components, and CSS styling, etc.) Tags in the composer can be used to selectively apply formatting to a specific Topic Post. For example, on my site I achieve this by pasting the following CSS into my theme’s CSS in the Common tab: /********************** REMOVE THINGS FROM LAYOUT USING TAGS **…

Be aware of this though:

@hellekin

One obvious drawback to using CSS for “removing” content, is that it’s not actually removed, just hidden. Therefore you’re loading data that your client won’t be using.

[craigconstantine]

I’m using j/s to insert things into the DOM. I’m asking if it’s possible to fire some j/s from a component, on Page Publishing pages…

[Canapin (Coin-coin le Canapin)]

I understood that and I’m aware that published pages don’t load theme components; that’s why I proposed an alternative that, of course, may not fit everyone for various reasons.

(my sentence was badly worded though, I’ll change it)