### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [February 13, 2024, 8:10pm UTC](https://meta.discourse.org/t/adplugin-not-compatible-with-changes-to-model/295251/1 "2024-02-13T20:10:16Z")
I might be seeing things, but this component is expecting a model with a topic object contained:
>
However, when I log this model out, there is no longer a topic attribute?:
Is there a reason the topic attribute was removed? I was actually using it too for an extension to the adplugin ☹
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [February 14, 2024, 11:45am UTC](https://meta.discourse.org/t/adplugin-not-compatible-with-changes-to-model/295251/3 "2024-02-14T11:45:43Z")
Hi Robert - I don’t think this was intentional. Were you able to find out what `@model` is referring to? Would be good to work out whether it was a core or plugin change.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [February 14, 2024, 11:56am UTC](https://meta.discourse.org/t/adplugin-not-compatible-with-changes-to-model/295251/4 "2024-02-14T11:56:40Z")
Is it not taking the Post model passed down by the `post-bottom` connector?
```plaintext
{{post-bottom-ad model=this}}
```
That said, I performed a search for `post-bottom` on the discourse repo and it comes up blank … I’ll dig a bit more
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [February 14, 2024, 12:44pm UTC](https://meta.discourse.org/t/adplugin-not-compatible-with-changes-to-model/295251/5 "2024-02-14T12:44:36Z")
This seems very old code:
>
Which contains the topic object, so things change _below_ this 😅
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [February 14, 2024, 1:43pm UTC](https://meta.discourse.org/t/adplugin-not-compatible-with-changes-to-model/295251/6 "2024-02-14T13:43:08Z")
Ok I see what happened here - thanks for the heads-up @merefield
>
>
> Changes in 0948d6b19e34320f95226cc43fbce976b71ceb31 caused the post-bottom-ad co…mponent to start receiving the widget-ised 'transformedPost' instead of the original \`post\` model. In most cases this difference didn't matter, but it did cause noticable issues with \`@model.category\` and \`@model.topic\`.
>
> This commit also deletes the unused \`post-bottom/discourse-adplugin.hbs\` connector. In the past, the adplugin itself was defining the post-bottom outlet. But now, we use RenderGlimmer to load the \`post-bottom-ad\` directly.
Two things:
1. During some refactoring a few months ago, we inadvertantly started passing the ‘transformedPost’ instead of ‘post’ into post-bottom-ad
2. During the same refactoring, we left an old `post-bottom/discourse-adplugin.hbs` file lying around. It didn’t actually do anything, but it made this issue waaay more tricky to figure out 😅
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [February 14, 2024, 2:22pm UTC](https://meta.discourse.org/t/adplugin-not-compatible-with-changes-to-model/295251/7 "2024-02-14T14:22:09Z")
> [@david](#):
>
> tricky to figure out
Is the perfect description 🙂
The post stream UI architecture is quite a beast!
Thanks very much for looking into this!!
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [February 19, 2024, 8:00am UTC](https://meta.discourse.org/t/adplugin-not-compatible-with-changes-to-model/295251/8 "2024-02-19T08:00:35Z")
This topic was automatically closed after 4 days. New replies are no longer allowed.