Made to Order Software Corporation - protection

Protected Node per Node Type Settings

Alexis Wilke — Mon, 06 Jun 2011 21:08:51 +0000

Node Type extension

The Protected Node module adds a field set to the Node Type form that you edit under:

Administer » Content management » Content types

These additions are explained in detail below.

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.

Protected mode for nodes of this type

This option let you choose how this node type handles the Protected Node capability.

Never protected

This means this node type is

Protected Node Password Form

Alexis Wilke — Thu, 28 Apr 2011 03:54:56 +0000

Protected Node Password Form

Once a node is protected, users who cannot bypass the password are sent to the password form (see image on the side.)

The password form is very simple. It includes one field for users to enter the node password and an OK button.

When the browser of the user sent us a referrer, then the Protected node module adds a Cancel link back to that referrer. Using the global settings, you can force a Cancel link to always be there. When no referrer is available, the Cancel link will send your users to your home page.

The title, information, description and title over the

Protected Node Global Settings

Alexis Wilke — Thu, 28 Apr 2011 00:49:24 +0000

The protected node module has global settings found under:

Administer » Site configuration » Protected node

Protected node Statistics

The page starts with statistics to let you know how pages are protected on your website. All the counts include published and unpublished content.

Total nodes — the total number of nodes on your website
Unprotected nodes — number of nodes that do not have a password
Protected nodes — number of nodes that are current protected by a password
- Showing title — number of nodes showing their title

Protected Node Permissions

Alexis Wilke — Thu, 28 Apr 2011 00:18:20 +0000

The Protected Node module adds permissions to define who has the right to make use of the password feature.

access protected content

This is the basic access permission for users. Users who are given this permission can access a protected node as usual, except that they need to enter the password to handle the node.

This is true whether they want to view, edit, delete the node.

bypass password protection

Users with the bypass permission can access all nodes that are protected without having to enter the passwords. This is very handy for website administrators and

Protected Node (The Drupal module —)

Alexis Wilke — Wed, 27 Apr 2011 23:39:02 +0000

The Protected Node module is used on websites where some pages need to be password protected. This is different from asking someone to create an account and often seen as much more user friendly, although in terms of protection it is quite similar.

If you've seen photo websites where you can go to an album but have to enter a password to see the photos, that's one example how this module can be used.

The module adds a field set in the node form to let authors enter a password.

The module has many options that are rather tricky to use so this documentation tries to explain what you can do

To Do List Global Settings

Alexis Wilke — Mon, 24 May 2010 01:22:22 +0000

Global Settings

Global settings are found under Administer » Site configuration » To do list (admin/settings/to_do).

Only To Do List administrators can edit the Global Settings.

MO Anti-pounding for Drupal

Alexis Wilke — Mon, 22 Feb 2010 11:58:39 +0000

$195.00

MO Anti-pounding helps you prevent heavy hammering of your websites from robots and individuals by catching and banning them before the Drupal database is accessed. Use this module to prevent a large amount of your resources from being eaten up by malicious users.

$195.00

Insert Node Known Issues

Alexis Wilke — Sun, 31 Jan 2010 10:47:34 +0000

The following are problems that have not been resolved and will probably not be.

Tag not transformed

At times, you enter the tag as in [node:123 cck=title] and it is not converted by the filter.

There are 3 common reasons for this to append:

You did not select the filter in your Input formats;
You did not select the format that uses the filter in that node; or
There is a syntax error in the tag.

The 3^rd one is certainly the most likely explanation once you made sure that the filter was effectively selected for that node. In many cases, it will be the missing semi-colon

Protect

Alexis Wilke — Mon, 30 Nov 2009 12:02:38 +0000

Tag Info

Tag Number:

Tag Type:

Define

Tag Flash Version:

Tag Structure:

struct swf_protect {
	swf_tag			f_tag;		/* 24, 58 or 64  */
	if(version >= 5) {
		if(tag == ProtectDebug2) {
			unsigned short	f_reserved;1
		}
		/* the password is optional when tag == Protect */
		string		f_md5_password;
	}
};

1. f_reserved must be set to zero.

DefineSound

Alexis Wilke — Sun, 29 Nov 2009 23:57:55 +0000

Tag Info

Tag Number:

Tag Type:

Define

Tag Flash Version:

Tag Structure:

struct swf_definesound {
	swf_tag			f_tag;		/* 14 */
	unsigned short		f_sound_id;
	unsigned		f_sound_format : 4;
	unsigned		f_sound_rate : 2;
	unsigned		f_sound_is_16bits : 1;
	unsigned		f_sound_is_stereo : 1;
	unsigned long		f_sound_samples_count;
	unsigned char		f_sound_data[<variable size>];
};

A DefineSound tag declares a set of samples of a sound effect or a music.

The sound samples can be compressed or not, stereo or not and 8 or 16 bits. The different modes are not all available in version 2, although the same tag is used in newer versions with additional capabilities.

The f_sound_is_16bits is always set to 1 (16bits samples) if the samples are compressed (neither Raw nor Uncompressed).