<?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 - feature</title>
 <link>http://www.m2osw.com/taxonomy/term/318/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>CSS3 media queries</title>
 <link>http://www.m2osw.com/css3-media-queries</link>
 <description>&lt;p&gt;&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; is improving with the introduction of CSS3.&lt;/p&gt;
&lt;p&gt;Contrary to the previous version, CSS3 supports selections that are very advanced, offering capabilities close to what you could write in JavaScript.&lt;/p&gt;
&lt;p&gt;Today I wanted to talk about the Media Queries because that can be used to very much optimize the list of links used to load your CSS data.&lt;/p&gt;
&lt;p&gt;In &lt;abbr class=&quot;mo-glossary mo-glossary-abbr&quot;  title=&quot;Hyper Text Markup Language&quot; lang=&quot;en&quot;&gt;HTML&lt;/abbr&gt;, you can use a &amp;lt;link ...&amp;gt; to add a CSS file to your page.&lt;/p&gt;
&lt;pre class=&quot;rteindent1&quot;&gt;
&amp;lt;link rel=&amp;quot;stylesheet&amp;quot; type=&amp;quot;text/css&amp;quot; href=&amp;quot;style.css&amp;quot; /&amp;gt;&lt;/pre&gt;
&lt;p&gt;In this case, the file style.css will always be loaded, whatever the media being used.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/css3-media-queries&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/css3-media-queries#comments</comments>
 <pubDate>Sun, 15 Jan 2012 05:26:21 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">676 at http://www.m2osw.com</guid>
</item>
<item>
 <title>Snap! Websites Upgrade: Advanced Filters</title>
 <link>http://www.m2osw.com/snap-upgrade-advanced-filters</link>
 <description>&lt;div class=&quot;product-info product display&quot;&gt;&lt;span class=&quot;uc-price-product uc-price-display uc-price&quot;&gt;$1.50&lt;/span&gt;&lt;/div&gt;&lt;div class=&quot;product-body&quot;&gt;&lt;h2&gt;
	Upgrade your website: Snap! Inline Tag Filters&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Snap!&lt;/strong&gt; has a filtering system dynamically transforming inline tags in your pages with live content from your website. By default we include the foot note tag filter in your website.&lt;/p&gt;

&lt;/div&gt;&lt;div class=&quot;product-info product sell&quot;&gt;&lt;span class=&quot;uc-price-product uc-price-sell uc-price&quot;&gt;$1.50&lt;/span&gt;&lt;/div&gt;&lt;div class=&quot;add-to-cart&quot;&gt;&lt;form action=&quot;/taxonomy/term/318/all/feed&quot;  accept-charset=&quot;UTF-8&quot; method=&quot;post&quot; id=&quot;uc-product-add-to-cart-form-668&quot;&gt;
&lt;div&gt;&lt;input type=&quot;hidden&quot; name=&quot;qty&quot; id=&quot;edit-qty&quot; value=&quot;1&quot;  /&gt;
&lt;input type=&quot;submit&quot; name=&quot;op&quot; id=&quot;edit-submit-668&quot; value=&quot;Add to cart&quot;  class=&quot;form-submit node-add-to-cart&quot; /&gt;
&lt;input type=&quot;hidden&quot; name=&quot;form_build_id&quot; id=&quot;form-70d5b7644d3330a8aac735a24b18c977&quot; value=&quot;form-70d5b7644d3330a8aac735a24b18c977&quot;  /&gt;
&lt;input type=&quot;hidden&quot; name=&quot;form_id&quot; id=&quot;edit-uc-product-add-to-cart-form-668&quot; value=&quot;uc_product_add_to_cart_form_668&quot;  /&gt;

&lt;/div&gt;&lt;/form&gt;
&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/snap-upgrade-advanced-filters&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/snap-upgrade-advanced-filters#comments</comments>
 <pubDate>Sun, 04 Sep 2011 23:43:54 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">668 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 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>Protected Node Password Fork Feature</title>
 <link>http://www.m2osw.com/doc-protected-node-fork</link>
 <description>&lt;h2&gt;Password Fork&lt;/h2&gt;
&lt;p&gt;The new module allows for a password fork.&lt;/p&gt;
&lt;p&gt;This means you can send your users to one specific page, and tell them about a password to use on that one page. Depending on the password, they will be sent to one of several nodes.&lt;/p&gt;
&lt;p&gt;This works in a very similar way as the other password form, except that there is no specific destination, and the users need to know any one of the passwords.&lt;/p&gt;
&lt;p&gt;The feature uses a specific URL defined as follow:&lt;/p&gt;
&lt;p&gt;/protected-nodes?protected_pages=&amp;lt;nid1&amp;gt;,&amp;lt;nid2&amp;gt;,...&amp;amp;back=&amp;lt;url&amp;gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;protected_pages=&amp;lt;nid1&amp;gt;,&amp;lt;nid2&amp;gt;,...&lt;/li&gt;
&lt;/ul&gt;
&lt;p class=&quot;rteindent1&quot;&gt;This

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/doc-protected-node-fork&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/doc-protected-node-fork#comments</comments>
 <pubDate>Thu, 28 Apr 2011 04:21:32 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">653 at http://www.m2osw.com</guid>
</item>
<item>
 <title>Protected Node Global Settings</title>
 <link>http://www.m2osw.com/doc-protected-node-settings</link>
 <description>&lt;p&gt;The protected node module has global settings found under:&lt;/p&gt;
&lt;p class=&quot;rteindent1&quot;&gt;&lt;span style=&quot;color: rgb(128, 0, 0);&quot;&gt;Administer &amp;raquo; Site configuration &amp;raquo; Protected node&lt;/span&gt;&lt;/p&gt;
&lt;h2&gt;Protected node Statistics&lt;/h2&gt;
&lt;p&gt;The page starts with statistics to let you know how pages are protected on your website. All the counts include published and unpublished content.&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Total nodes &amp;mdash; the total number of nodes on your website&lt;/li&gt;
    &lt;li&gt;Unprotected nodes &amp;mdash; number of nodes that do not have a password&lt;/li&gt;
    &lt;li&gt;Protected nodes &amp;mdash; number of nodes that are current protected by a password
    &lt;ul&gt;
        &lt;li&gt;Showing title &amp;mdash; number of nodes showing their title&lt;/li&gt;
 ...&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt;

&lt;p&gt;&lt;a href=&quot;http://www.m2osw.com/doc-protected-node-settings&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.m2osw.com/doc-protected-node-settings#comments</comments>
 <category domain="http://www.m2osw.com/taxonomy/term/607">Protect</category>
 <pubDate>Thu, 28 Apr 2011 00:49:24 +0000</pubDate>
 <dc:creator>Alexis Wilke</dc:creator>
 <guid isPermaLink="false">650 at http://www.m2osw.com</guid>
</item>
</channel>
</rss>


