It is unclear from the documentation how this is most efficiently achieved, and I would value any guidance that this community can offer about the best way to approach doing this.
If you can shed any light on the best way forward using these (or some other) methods I would be most grateful.
A dedicated software development team will be able to provide you with an end-product that is custom to your requirements. A dedicated team will be able to take on the challenges that you have and deliver quality products by mlsdev.com. They’ll be able to troubleshoot bugs and ensure your products run smoothly. Having a dedicated software development team also makes the project more affordable in the long run. This way, you’ll get more value out of your investment.
Added here in case it is useful for others:
In the absence of any better suggestions what I did was:
template_post_parsehook to grab the rendered HTML for the page
This works. Whether a better solution exists within EE core methods will (I guess) remain a mystery.
I talked with the team and
template_post_parse definitely seems to be the way to go. Add-ons are called earlier in the parsing process, so using
ee->output methods with your add-on won’t work.
template_post_parse you should be able to use
append_output or other output methods. However, I would also saying that the way you’re doing this isn’t wrong either.
Thanks Andy for the further clarification: I’ll just leave it doing what it is doing then.
In passing, while we are here, worth noting that the documentation for the
append_output method appears in the documentation for the Output Class which is one of the “tersely” documented Classes in the docs … and so it is not made clear what element the method is ‘appending’ stuff to … one of the several places where just a couple more sentences in the docs would make them much more useful…