No Index meta tags for thin content.

Just add an EventListener that sets allowSpidersToIndexThisPage to false.

You can add the robots meta tag manually to the head section of any page/template too, works just fine

Other meta tags don't work so well however so don't start adding meta descriptions that way...

WCF has an API for meta tags, which can be used programatically via EventListeners. I'd recommend using the existing API instead of fiddling with templates (which can lead to troubles when templates get updated).

Quote from Sherrie

Can it be achieved through the custom template listener mod?

No. TemplateListeners and EventListeners are two different things. The former are used to insert template scripting into templates, the latter are the implementation of the Observer-Pattern in program code.

Im interested in this myself, is there a list of Woltlab events available and/or a guide to TemplateListeners/EventListeners?

Many thanks,

For template listeners, there is no such list. And frankly, there is no need for one. The normal way is to visually identify a location where you want to do stuff, then to open the corresponding template and then to watch for an event.

If you had a list of events you#dd still need to open the template in order to identify where exactly the event is located. So it wouldn't really do you any good.

For event listeners, there used to be a list for WCF 1.x, but there isn't anymore for WCF 2.x. But again, the usefulness of such is list is questionable. EventListeners implement the observer-pattern, if you want to know how that workd read a book about design pattern, I recommend the Gang of Four book. If you know OOP and PHP and know what the Observer-Pattern is, then there isn't much you#d need to know anymore. So basically, this isn't WCF specific stuff, but rather basic programming knowledge. The only WCf specific stuff you need to learn is how to set en EventListener via the EventListener-PIPm e.g. what to write into the eventListener.xml, and that's covered in the old WCF 1.x docs (hasn't changed) or can easily be determined by opening an arbitrary eventListener.xml from an existing plugin or WBB itself.

Since events are inherited to derived classes, an exhaustive list of events would go in the thaosends, if not tens of thousands. It wouldn't be that much helpful at all.

Thank you, great help... Im a hobby programmer at best, I am currently learning. I am going to try a few TemplateListeners soon as I have 100's of template edits.

Where would be a good place to start reading about them, what basic files are needed and basic santax etc?

Template listeners inject template script into templates. So the normal template script that you see in templates are used in template listeners as well.

For a template listener, you'd need to use the template listener PIP, which is an XML-based PIP. So you'll want to create an templateListener.xml and add that to the install instructions in your package.xml.