<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.m2osw.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Made to Order Software Corporation - module</title>
 <link>http://www.m2osw.com/taxonomy/term/273/all</link>
 <description></description>
 <language>en</language>
<item>
 <title>Protected Node Rules Support</title>
 <link>http://www.m2osw.com/doc-protected-node-rules</link>
 <description>&lt;p&gt;The following features are available only when installing the Rules extension of protected nodes. This extension requires the thrid party Rules extension for Drupal.&lt;/p&gt;
&lt;h2&gt;
	Protected Node Rules Conditions&lt;/h2&gt;
&lt;p&gt;When handling a Node, it is possible to check whether the node is currently protected or locked.&lt;/p&gt;
&lt;h3&gt;
	Protected Nodes&lt;/h3&gt;
&lt;p&gt;A node is said protected when the node was protected by a password using the Protected node module.&lt;/p&gt;
&lt;p&gt;Whether the user can view that node is irrevelant in this case. Only the fact that the node requires a password to be viewed is what this condition checks.&lt;/p&gt;
&lt;h3&gt;
	Locked Nodes&lt;/h3&gt;
&lt;p&gt;A ...&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/doc-protected-node-rules&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/doc-protected-node-rules#comments</comments>
 <category domain="http://www.m2osw.com/taxonomy/term/607">Protect</category>
 <pubDate>Thu, 22 Mar 2012 00:26:28 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">680 at http://www.m2osw.com</guid>
</item>
<item>
 <title>MO Auto add terms for Drupal</title>
 <link>http://www.m2osw.com/mo_auto_add_terms</link>
 <description>&lt;p&gt;&lt;a href=&quot;/mo_auto_add_terms&quot; title=&quot;Read more about the MO Auto add term Drupal 6.x module.&quot;&gt;&lt;img align=&quot;left&quot; alt=&quot;MO Auto-Add Terms Logo&quot; border=&quot;0&quot; height=&quot;120&quot; src=&quot;/sites/default/files/images/mo-autoaddterms_0.jpg&quot; style=&quot;padding-right: 10px; padding-bottom: 10px;&quot; title=&quot;MO Auto add terms, a Drupal 6.x module.&quot; width=&quot;120&quot; /&gt;&lt;/a&gt; &lt;em&gt;MO&amp;nbsp;Auto add terms&lt;/em&gt; is a PHP&amp;nbsp;&lt;a class=&quot;mo-glossary mo-glossary-a1&quot;  title=&quot;A Drupal module is an extension to the Drupal CMS. It is written in PHP and uses the Drupal hook system to implement functionality not otherwise offered by Drupal Core. For example, the Views module extends the Drupal CMS offering lists of nodes, users and other elements available in Drupal. Made to Order Software developed modules for Drupal 6.x and these are available on its website.&quot; href=&quot;http://www.m2osw.com/drupal&quot;&gt;module for Drupal&lt;/a&gt; 6.x.&lt;/p&gt;
&lt;p&gt;It is particularly useful for maintaining small and large taxonomies with a small or large number of nodes. Especially taxonomies used as site indexes or glossaries.&lt;/p&gt;
&lt;p&gt;This module automatically handles the addition (and optionally removal) of taxonomy terms to a node. It does it at the time the node is saved and when the background process runs (i.e.&amp;nbsp;&lt;abbr class=&quot;mo-glossary mo-glossary-abbr&quot;  title=&quot;Command Run ON&quot; lang=&quot;en&quot;&gt;CRON&lt;/abbr&gt;.)&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/mo_auto_add_terms&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/mo_auto_add_terms#comments</comments>
 <pubDate>Sun, 05 Feb 2012 05:03:32 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">677 at http://www.m2osw.com</guid>
</item>
<item>
 <title>Insert Node Parameter: target (6-1.4) [no content]</title>
 <link>http://www.m2osw.com/doc-insert-node-parameter-target</link>
 <description>&lt;p&gt;Add a window target in a link. For example&lt;/p&gt;
&lt;pre&gt;
   &lt;span&gt;[&lt;/span&gt;node:123 target=_blank; link]
&lt;/pre&gt;
&lt;p&gt;This option only applies to links and defines the target attribute of those links, as created with:&lt;/p&gt;
&lt;p&gt;&lt;span class=&quot;insert-node insert-node1 insert-nid440&quot;&gt;&lt;span class=&quot;insert-node-link&quot;&gt;&lt;a href=&quot;/doc-insert-node-parameter-title&quot;&gt;Insert Node Parameter: title (6-1.1)&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;,&lt;/p&gt;
&lt;p&gt;&lt;span class=&quot;insert-node insert-node2 insert-nid447&quot;&gt;&lt;span class=&quot;insert-node-link&quot;&gt;&lt;a href=&quot;/doc-insert-node-parameter-link&quot;&gt;Insert Node Parameter: link (5-1.0)&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;, or&lt;/p&gt;
&lt;p&gt;&lt;span class=&quot;insert-node insert-node3 insert-nid446&quot;&gt;&lt;span class=&quot;insert-node-link&quot;&gt;&lt;a href=&quot;/doc-insert-node-parameter-more&quot;&gt;Insert Node Parameter: more (6-1.1)&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;.&lt;/p&gt;
&lt;p&gt;Using the target option by itself resets the Insert Node module to the default behavior (i.e. no target attribute):&lt;/p&gt;
&lt;pre&gt;
   &lt;span&gt;[&lt;/span&gt;node:123 target=_blank; link target more]
&lt;/pre&gt;
&lt;p&gt;The title link will have target=&amp;quot;_blank&amp;quot; and the more link will not.&lt;/p&gt;
&lt;p&gt;Note that this data is

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/doc-insert-node-parameter-target&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/doc-insert-node-parameter-target#comments</comments>
 <pubDate>Wed, 22 Jun 2011 11:19:41 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">665 at http://www.m2osw.com</guid>
</item>
<item>
 <title>Simplemenu Settings</title>
 <link>http://www.m2osw.com/doc-simplemenu-settings</link>
 <description>&lt;h2&gt;Menu Settings&lt;/h2&gt;
&lt;h3&gt;Menu&lt;/h3&gt;
&lt;p&gt;Select the menu to be displayed as the &lt;em&gt;Simplemenu&lt;/em&gt;. By default, we display the Navigation Menu which makes the most sense for administrator (as the &lt;em&gt;Simplemenu&lt;/em&gt; was primarily created for administrators wanting to quickly go to all administration pages.)&lt;/p&gt;
&lt;h3&gt;Theme&lt;/h3&gt;
&lt;p&gt;Select a theme to display your &lt;em&gt;Simplemenu&lt;/em&gt; items and dropdowns. The default is called &lt;strong&gt;original&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;The themes reside in the module sub-folder named themes. Each theme is defined in a specific directory named after the theme. That name is what appears in the dropdown in the settings.&lt;/p&gt;
&lt;p&gt;It is possible to add new themes as

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/doc-simplemenu-settings&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/doc-simplemenu-settings#comments</comments>
 <category domain="http://www.m2osw.com/taxonomy/term/581">End</category>
 <pubDate>Sat, 11 Jun 2011 21:10:18 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">664 at http://www.m2osw.com</guid>
</item>
<item>
 <title>Simplemenu Upgrade Path</title>
 <link>http://www.m2osw.com/doc-simplemenu-upgrade-path</link>
 <description>&lt;h2&gt;Version 7.x&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Version 7.x-1.x-dev&lt;/strong&gt; is a starting point... It is not complete, although it shows you a functional Management menu as a dropdown. More to come as time allows... See issue [#791664] for more info.&lt;/p&gt;
&lt;h2&gt;Version 6.x&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Version 6.x-1.13&lt;/strong&gt; fixes the vertical menu problem which had to do with &lt;abbr class=&quot;mo-glossary mo-glossary-abbr&quot;  title=&quot;Cascading Style Sheet&quot; lang=&quot;en&quot;&gt;CSS&lt;/abbr&gt; caching getting lost.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Version 6.x-1.10 to 6.x-1.12&lt;/strong&gt; fixes the non-called theme() function versus the other sub-modules that have callbacks through the theme() calls. However, we really need to have callbacks instead. Added horizontal and vertical themes. Attempts to fix to the vertical menu problem

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/doc-simplemenu-upgrade-path&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/doc-simplemenu-upgrade-path#comments</comments>
 <pubDate>Sat, 11 Jun 2011 20:23:51 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">663 at http://www.m2osw.com</guid>
</item>
<item>
 <title>Protected Node per Node Type Settings</title>
 <link>http://www.m2osw.com/doc-protected-node-node-type</link>
 <description>&lt;h2&gt;Node Type extension&lt;/h2&gt;
&lt;p&gt;The Protected Node module adds a field set to the Node Type form that you edit under:&lt;/p&gt;
&lt;p class=&quot;rtecenter&quot;&gt;&lt;span style=&quot;color: rgb(128, 0, 0);&quot;&gt;Administer &amp;raquo; Content management &amp;raquo; Content types&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;These additions are explained in detail below.&lt;/p&gt;
&lt;p&gt;The main reason for adding this feature is to avoid seeing the field set on all the node edit forms. With this feature you can hide the form on all the node types that you will never protect with a password.&lt;/p&gt;
&lt;h2&gt;Protected mode for nodes of this type&lt;/h2&gt;
&lt;p&gt;This option let you choose how this node type handles the Protected Node capability.&lt;/p&gt;
&lt;h3&gt;Never protected&lt;/h3&gt;
&lt;p&gt;This means this node type is

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/doc-protected-node-node-type&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/doc-protected-node-node-type#comments</comments>
 <category domain="http://www.m2osw.com/taxonomy/term/607">Protect</category>
 <pubDate>Mon, 06 Jun 2011 21:08:51 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">661 at http://www.m2osw.com</guid>
</item>
<item>
 <title>MobileKey Known Issues</title>
 <link>http://www.m2osw.com/doc-mobile-key-known-issues</link>
 <description>&lt;h2&gt;Cached Pages&lt;/h2&gt;
&lt;p&gt;The Boost module can be used to cache pages on your website. Unfortunately, if a page is cached, it is served without accessing Drupal. This means, the redirection offered by the MobileKey doesn&#039;t take effect on pages cached by Boost or similar modules.&lt;/p&gt;
&lt;p&gt;Also if you have a form of proxy cache (a cache before Apache2,) then the redirection will probably be prevented by that cache early on.&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/doc-mobile-key-known-issues#comments</comments>
 <pubDate>Mon, 16 May 2011 20:07:42 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">659 at http://www.m2osw.com</guid>
</item>
<item>
 <title>MobileKey global settings</title>
 <link>http://www.m2osw.com/doc-mobile-key-settings</link>
 <description>&lt;p&gt;The MobileKey module comes with the following settings. These settings are found here:&lt;/p&gt;
&lt;p class=&quot;rteindent1&quot;&gt;&lt;span style=&quot;color: rgb(153, 51, 0);&quot;&gt;Administer &amp;raquo; Site configuration &amp;raquo; MobileKey&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;Front Page Redirect&lt;/h2&gt;
&lt;p&gt;Since you generally give one URL to your users, your home page (called Front Page in Drupal), it can be practical to send Mobile phone users to a special URL so when they access your site they see a better adapted front page than the usual.&lt;/p&gt;
&lt;p&gt;The settings accept a local path (i.e. &lt;span style=&quot;color: rgb(0, 0, 255);&quot;&gt;mobile&lt;/span&gt;) or a full path (i.e. &lt;a href=&quot;http://mobile.snapwebsites.info/&quot;&gt;http://mobile.snapwebsites.info/&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;Note that this gives you a way to use the ThemeKey capability to change the theme of all

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/doc-mobile-key-settings&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/doc-mobile-key-settings#comments</comments>
 <pubDate>Mon, 16 May 2011 19:13:43 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">658 at http://www.m2osw.com</guid>
</item>
<item>
 <title>MobileKey addition to ThemeKey</title>
 <link>http://www.m2osw.com/doc-mobile-key-themekey</link>
 <description>&lt;p&gt;The main idea of MobileKey is to give you the capability to switch your website theme to a mobile specific theme when the user access your site from one&#039;s mobile phone. A mobile theme will make it easier to access your website on a mobile device.&lt;/p&gt;
&lt;p&gt;For go to the ThemeKey settings page:&lt;/p&gt;
&lt;p class=&quot;rteindent1&quot;&gt;&lt;span style=&quot;color: rgb(153, 51, 0);&quot;&gt;Administer &amp;raquo; Site configuration &amp;raquo; ThemeKey&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The MobileKey adds one selection to the list of attributes to match. The new selection is called:&lt;/p&gt;
&lt;pre class=&quot;rteindent1&quot;&gt;
mobile:device
&lt;/pre&gt;
&lt;p&gt;This works everywhere on your website (it is a global option, not specific to any kind of pages.) The system checks different parameters to

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/doc-mobile-key-themekey&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/doc-mobile-key-themekey#comments</comments>
 <pubDate>Mon, 16 May 2011 18:59:11 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">657 at http://www.m2osw.com</guid>
</item>
<item>
 <title>MobileKey Installation</title>
 <link>http://www.m2osw.com/doc-mobile-key-installation</link>
 <description>&lt;p&gt;Get the tarball or the zip file of the module from Drupal.org (&lt;a href=&quot;http://drupal.org/project/mobilekey&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot; title=&quot;MobileKey on Drupal.org&quot;&gt;MobileKey on Drupal&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;Go to one of you module folders and extract the file you downloaded.&lt;/p&gt;
&lt;p&gt;The default installation folder is sites/all/modules, if you have a multi-site installation and want the module for just a few sites, go to sites/&amp;lt;sitename&amp;gt;/modules instead (create the modules folder if it doesn&#039;t exist yet.) It is recommended that you do not install under the top modules folder as this one is reserved for Drupal Core modules.&lt;/p&gt;
&lt;p&gt;At that point, go to your Drupal website and go to &lt;span style=&quot;color: rgb(128, 0, 0);&quot;&gt;Administer &amp;raquo; Site building &amp;raquo; ...&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/doc-mobile-key-installation&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/doc-mobile-key-installation#comments</comments>
 <pubDate>Mon, 16 May 2011 18:12:40 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">656 at http://www.m2osw.com</guid>
</item>
</channel>
</rss>


