<?xml version='1.0' encoding='UTF-8'?>
<rss version='2.0'>
	<channel>
		<title>cotonti.com : modules and plugs</title>
		<link>https://www.cotonti.com</link>
		<description>Neueste Themenbeiträge</description>
		<generator>Cotonti</generator>
		<language>en</language>
		<pubDate>Mon, 13 Apr 2026 16:00:19 -0000</pubDate>

		<item>
			<title>Trustmaster</title>
			<description><![CDATA[I'm sure this has been discussed before, just can't find the right topic. I don't think it is possible to merge modules and plugins in Siena at all. Probably this question is for Renaissance, but it will be obvious by that time whether such a distinction really makes sense for extension developers.]]></description>
			<pubDate>Di, 18 Jan 2011 03:56:26 -0000</pubDate>
			<link><![CDATA[https://www.cotonti.com/de/forums?m=posts&q=6127&d=0#post27985]]></link>
		</item>
		<item>
			<title>GHengeveld</title>
			<description><![CDATA[RSS and Search in their current form would be plugins since they extend upon existing functionality (namely pages). If they would be modified to be more generic (and provide an API for example), they could be classified as modules.<br />
<br />
Polls is a tricky one, but I'd classify it as a module since it provides new functionality and doesn't strictly rely on existing features (of course for forum polls it does, but that would be a plugin inside a module, actually I'd split these two into separate extensions).<br />
<br />
The way the extension is displayed (either fullscreen or as a component) is only a rough guideline and doesn't work in all cases. The main factor should be whether the extension introduces stand-alone functionality without relying on other modules.]]></description>
			<pubDate>Di, 18 Jan 2011 02:03:19 -0000</pubDate>
			<link><![CDATA[https://www.cotonti.com/de/forums?m=posts&q=6127&d=0#post27976]]></link>
		</item>
		<item>
			<title>esclkm</title>
			<description><![CDATA[koradhil. in your way how do you think it is module or plugin:<br />
a. rss<br />
b. polls<br />
c. search<br />
and why?]]></description>
			<pubDate>Mo, 17 Jan 2011 21:45:32 -0000</pubDate>
			<link><![CDATA[https://www.cotonti.com/de/forums?m=posts&q=6127&d=0#post27971]]></link>
		</item>
		<item>
			<title>Kort</title>
			<description><![CDATA[While the general idea is pretty much clear, classification entire page + php file in the root / block (not visible) is definitely not good enough.]]></description>
			<pubDate>Mo, 17 Jan 2011 17:27:41 -0000</pubDate>
			<link><![CDATA[https://www.cotonti.com/de/forums?m=posts&q=6127&d=0#post27966]]></link>
		</item>
		<item>
			<title>GHengeveld</title>
			<description><![CDATA[No. The difference is clear enough:<br />
<br />
<strong>Modules </strong>provide stand-alone and usually quite comprehensive systems that serve a very specific purpose, which often has little to do with core functionality. They normally fill the entire page. Modules would mostly be used by application developers that use Cotonti only as a framework. Hooks should be provided inside the module in order to allow plugins to extend the module. Modules are less likely to use hooks (other than standalone), since they provide new functionality rather than extending existing functionality. They should not depend on other modules or plugins.<br />
<br />
<strong>Plugins </strong>provide enhancements and additional functionality for existing features, either in core or in another plugin or module. They usually do not fill an entire page (if visible at all). Plugins would mostly be used by website owners to customize the website's behavior. They should not use the 'standalone' hook.<br />
<br />
Technically the difference between the two is limited to the fact that a module has its own .php file in the root of the site, so it's not called through plug.php like plugins. This allows for more flexibility in the naming of variables and url parameters (some are already in use by plug.php so can't be used by plugins). In the future I would like to see Modules get more technical capabilities in terms of development, in order to make the difference between the two also of technical nature. I'm thinking of object-oriented programming and a <a href="http://en.wikipedia.org/wiki/Model%E2%80%93View%E2%80%93Controller" rel="nofollow">Model-View-Controller</a> architecture (for which Trustmaster has developed quite a powerful framework, but it's still experimental).<br />
<br />
In the downloads section on the new site, modules and plugins are combined under the name 'extensions' and they reside in the same folders (extension categories), but you can filter by type if you want. When adding an extension, you have to indicate whether its a module or plugin.]]></description>
			<pubDate>Mo, 17 Jan 2011 05:57:33 -0000</pubDate>
			<link><![CDATA[https://www.cotonti.com/de/forums?m=posts&q=6127&d=0#post27960]]></link>
		</item>
		<item>
			<title>ez</title>
			<description><![CDATA[I agree,<br />
The name of the module or plugin should be clear enough  <img class="aux smiley" src="https://www.cotonti.com/./images/smilies/smile.gif" alt=":)" />]]></description>
			<pubDate>Mo, 17 Jan 2011 05:17:30 -0000</pubDate>
			<link><![CDATA[https://www.cotonti.com/de/forums?m=posts&q=6127&d=0#post27958]]></link>
		</item>
		<item>
			<title>esclkm</title>
			<description><![CDATA[version 09. Beta. In the 09 version is clearly identified modules. But between the modules and plugins difference was absolutely incomprehensible.<br />
May be we need join them?]]></description>
			<pubDate>Mo, 17 Jan 2011 04:57:47 -0000</pubDate>
			<link><![CDATA[https://www.cotonti.com/de/forums?m=posts&q=6127&d=0#post27957]]></link>
		</item>
	</channel>
</rss>