Blueprints

Blueprints is designed to bring a visual representation of Structure templates to the Publish Page, and easily show the user what fields are available in each template

The idea came from my experiences in having to add a descriptions such as "This field is only available in pages/one-column" to a custom field. It is clunky and confusing to many clients. Blueprints also lets you modify which templates are even available in the Structure publish tab. For each Channel on your site you can select the templates that are available to the user. I hated telling clients "ignore these other 20 templates, just use these 4". Inevitably, someone would screw it up, and use a template they were not supposed to, then call me wondering why their content wasn't showing up. With Blueprints, this shouldn't happen anymore. 

Blueprints uses the built in Publish Layout functionality in EE 2.0. It requires that you create a new Member Group for each template/Publish Layout. You need to create a Member Group, and assign the 4 permissions listed below. Once you have done this, customize your Publish Layout and save it, then in the Blueprints settings you can assign that Publish Layout to 1 or more templates. I would recommend naming your Member Groups something along the lines of "Layout: One Column", or anything else to easily distinguish it from real Member Groups.

If you have a small project, or don't want to go through the hassle to create multiple Publish Layouts, don't worry, you can still use Blueprints. The first option in the settings screen lets you turn off the Publish Layout "Hi-jacking" that happens. With this turned off, you will still be able assign preview thumbnail images to a template, and restrict which templates are available in the Structure template list.

To purchase Blueprints, please go to Devot:ee

Current URL

This was a combination of Tom Kiss' last_segment extension, and Mark Bowen's fetch_current_uri plugin. I needed {current_url} available as early as possible in the parse order.

Now includes {all_segments}, which returns /segment-1/segment-2/segment-3/.../ and {parent_segment}, which will return the current page's parent segment/url_title

Custom System Messages

This extension lets you define any 2 templates within your template groups to be used as the error page. You have access to all the usual variables from the Specialty Templates, plus a new one, referrer. So on top of any EE template tag you want to use in the error page, you have title, meta_refresh, heading, content, link, and referrer. link can also be changed to render without the JavaScript history.go() method if you desire. There are 3 options which I called Accessibility in the extension settings.

There is a known conflict with the Flash Messenger extension, which also extends the core Output class, and overrides Custom System Messages. To fix this, you can change Flash Messenger to extend this extension, instead of the core. In Flash Messenger change MyOutput extends Output  to MyOutput extends System_Messages_Output.

WYMEditor for ExpressionEngine 2.0

If you are looking for THE WYMEditor, please visit wymeditor.org. This is just an implementation of WYMEditor for ExpressionEngine.

WYMEditor 2.0 for ExpressionEngine is aimed at bringing a simple, and intuitive editor to the control panel, and offer seamless integration with the default File Browser, and native Pages module, and 3rd party Structure module to provide a better content entry work flow. You can see these two features in action in the video below.

New in version 2.1:

• No longer need the Allow EE Code plugin, and my Page URL plugin to create links to pages based on ID. A new extension is now included, and if enabled, all links to pages in the Pages or Structure modules will be created as global variables, for example: {page_url:23}. 23 is the ID of the page you are linking too. Since these are global variables, you can use these variables anywhere in your site.
• Revised UI. I moved the Containers and Classes drop downs into the main toolbar to provide a wider editing area on narrow screens, or when used in a Matrix cell.
• Matrix support! When it appears within a Matrix cell, the UI is even more minimal.
• No more per field settings. All settings are now global. (The only setting is the path to the custom CSS file)
• A lot of functions have been added to utilize the session cache, so less queries are performed when multiple WYMEditor fields are on the same Publish page.

Images are inserted into the editor area with the full absolute path to the image so it is visible while editing your content, however, on save, the path is replaced with the correct {filedir_N} value, so it is completely portable.

Please submit all support/bugs to Get Satisfaction

Requirements: PHP 5.2, ExpressionEngine 2.0.2 (for Pages/Structure support)

Default and Corporate theme

Fruit theme

Redeemer

Redeemer is an ExpressionEngine module for managing coupon codes. You can create them from the control panel, and even let users create their own codes based on an action they perform. On Twitter I mentioned I was building this and I got a couple of responses along the lines of "why don't you just use EE's built in Weblog to create coupons?" I could have done this, and thought about it, but you can only create a basic coupon code system with EE's built in features. You won't be able to easily, if at all, manage the number of times a coupon can be redeemed before it is invalid, limit by the user's IP address, or member ID. You also won't be able to generate new codes in the templates, and creating randomized codes would still require an extension or plug-in.

You can use the template tags with Ajax calls to validate a code without a page refresh, but if you use the URL Redirect feature will not work if you're calling the exp:redeemer:validate method in an Ajax call for obvious reasons.

This is my first full featured module for EE. It is LG Addon Updater and should be MSM compatible as well. The exp:redeemer:generate method has not been used in a production environment. I added this after the original module was complete for a client project, so don't hold it against me if it isn't fully fleshed out.

Here is a demo with an Ajax request to validate a code, and another using the URL redirections.

For further information please go to the forum post over at ExpressionEngine.com

{exp:redeemer:validate} {/exp:redeemer:validate}

{exp:redeemer:validate name="offer_code"}
    You entered: {entered_code}
    {if valid} 
        Do whatever you want! 
    {/if}
    {if invalid} 
        Show the default {invalid_message}, and do something else 
    {/if}
{/exp:redeemer:validate}

{exp:redeemer:redeem}

{exp:redeemer:generate}{/exp:redeemer:generate}

{exp:redeemer:generate start_date="2009-12-09" end_date="2009-12-10"}
    Your code is: {code}
{/exp:redeemer:generate}

Restricted Content

This is a simple plugin to hide content from users unless they belong to a defined user group.

Page URL

This is a ridiculously simple plugin to return the full path to a page created in Structure, or the native Pages module.

Week Range

Print out a single week of a calendar, or get Month, Day, or Year values from a week range with a given date.

Anonymous Member

Create a completely anonymous member to take advantage of some modules or features that require a user to login. This was originally written to allow users to create favorites with Solspace's Favorites module, which requires a user to be logged in.

Get/Post Parameters

Print GET and POST parameters in your templates.

In Segments

See if a word exists in any segment, or is an exact segment match.

Documentation

This is a simple module that will let you add documentation specific to your site into the Control Panel. The accompanying extension will let you define the server path to your documentation folder, and will always expect an index.php file within that directory. Use this module and add it as a tab to your Control Panel so other users can easily refer to the documentation you write. You must enable the accompanying Extension first, set the path to your documentation, then enable the Module.

Entry Permissions

Entry Permissions allows Administrative users to assign editing privileges on a per entry basis to other member groups. Other member groups can optionally be allowed to add new entries to to assigned weblogs as well. Entry Permissions will also hide any entry in the Edit tab that is not editable by the current user, so there is no confusion with your content editors as to what entries they can or can't edit.