{if blank}
<td class=‘calendarBlank-big’>{day_number}</td>
{/if}

Thanks

But, I can’t get it to work. I even created a completely blank template and then pasted in the usage data that is given in the explanation of the plugin. I uploaded an mp3 file to the root level of my website and used that as my file and path info. This is what I have inserted for that information:

{exp:mp3info file=“http://cmachurch.org/EverybodyLoves.mp3” path=”/home/cmachurc/public_html/”}
version id = {version_id}
version = {version}
layer id = {layer_id}
layer = {layer}
protection = {protection}
bitrate = {bitrate}
sampling rate = {sampling_rate}
padding = {padding}
private = {private}
channel mode = {channel_mode}
copyright = {copyright}
original = {original}
filesize = {filesize}
length = {length}
{/exp:mp3info}

I installed this in a template called “test” and you can see the results that you get when you run that page at
http://cmachurch.org/index.php?/site/test/

But, be advised that it must be looping because it never seems to end loading. So, if you open this page, just close it after you see what it’s doing, else it will eat your processes.

I would have expected some results but instead get error. If anyone can give me more information as to why this is happening, I would be grateful. Thanks

If you’re unfamiliar with the benefits that PHP Markdown Extra provides, please check out http://www.michelf.com/projects/php-markdown/extra/.  To sum it up, here are the new features:

* Use Markdown inside HTML blocks
* Add id attribute to headers
* Tables
* Definition lists
* Footnotes
* Abbreviations

There shouldn’t be any issues with the plugin, since all I’ve done is overwritten the old Markdown code with the new version, and changed some of the text in the plugin information section.  Enjoy!

Download Now!

Update: 10/10/08 - Plugin now uses Markdown Extra 1.2.2. I also stripped out some extra code that was only used for WordPress compatibility. And, since the forum will not let me upload the file due to the “invalid content for its MIME type” error, you will need to download the file from the URL above.

I would like to present to your attention a new plugin called “Members”. Its purpose is similar to Yoshi Melrose’s Member Info plugin - to display info about individual members based on each member’s id number.

There are two main differences between my plugin and that of Yoshi:

1) Members plugin adopts entirely different style - it uses variable pairs for every member within exp:members tag instead of simply tag pairs for every member. This allows more control over parsing order because it is possible to wrap with exp:members tag other ExpressionEngine tags.

2) Members plugin can output the values both from fields of exp_members table and from member profile custom fields; Member Info plugin deals only with fields of exp_members table.

PARAMETERS:
 
  1) date_format - Optional. Allows you to specify how the output of
  the date variables’ should be formatted. Default value is “F %j%S, %Y”.
  About date formatting see here.
 
  2) localize - Optional. Allows you to specify if the date should be localized.
  Possible values are “yes” and “no”. Default is “no”.
 
  3) change_y - Optional. Allows you to specify what should be outputted
  in case variable’s value is “y” (this value means “yes”).
 
  4) change_n - Optional. Allows you to specify what should be outputted
  in case variable’s value is “n” (this value means “no”).
 
  VARIABLE PAIRS
 
  1) {single_member id=“9”}{/single_member} - this variable pair should be used to wrap
  single variables. No single variable outside this variable pair will be parsed by
  exp:members tag!
 
  Parameter “id” of the {single_member}{/single_member} variable pair is
  required. This parameter allows you to specify id number of the individual
  member.
 
  SINGLE VARIABLES
 
  As a single variable can be used any field name of the table exp_members. Also
  as a single variable can be used the name of any member profile custom field.
 
  The only exception is this: the value of “password” field of the table exp_members
  will not be outputted by {password} variable; empty string will be outputted instead.
 
  USAGE
 
  Say, you need to output the values of the fields “username”, “last_visit”, “notify_by_default”
  from the table exp_members and the values of member profile custom fields
  “contacts” and “preferred_language” for the members having member id 7 and 11.
  To achieve this you can use the code as this:

Changelog:

-1.0 // Initial release

Usage is similar to FeedGrab, the template:

imports a tab delimited CSV file into the weblog with id of 5, skipping the first 6 lines.

It uses column 1 as the title field, and columns 2 and 3 as the custom fields prod_description and prod_keywords.

delimiter is the character that separates the columns, encloser is the character that wraps the column.

eg, “Title”,“Description”,“Keywords” has a comma delimiter and a quote encloser.

The plugin was developed for a particular client’s requirements - let me know if there are any future development requests.

Edit: Please see the CSVGrab page to download current version

I would like to present to your attention a new plugin called “Child categories”. Its purpose - to display a list of subcategories for a given category.

PARAMETERS:

  1) parent - Optional. Use it to specify parent category id number.
  You can stack parent categories using pipe character e.g. parent=“3|16|28”.
  2) sibling - Optional. Use it to specify child category id number
  (plugin will find parent category and other child categories).
  Either “parent” or “sibling” parameter MUST BE defined.
  3) weblog - Optional. Use it to specify weblog name. Pipeline character and “not” are supported.
  4) site - Optional. Use it to specify site id number.
  5) child_categories_sort_by - Optional. Use it to specify sort order
  of child categories. This parameter accepts three values: “name” (child
  categories will be sorted by name), “id” (child categories will be sorted
  by id number), and “custom” (child categories will be sorted using custom order
  as defined in control panel). Default value is “name”.
  6) child_categories_sort_direction - Optional. This parameter accepts two values: “asc” and “desc”. Default value is “asc”.
  7) show_empty - Optional. Allows you to specify if child categories having no
  entries should be displayed or not. This parameter accepts two values: “yes” and “no”.
  Default value is “no”.
  8) entries_sort_by - Optional. Allows you to specify sort order of entries.
  This parameter accepts two values: “title” and “date”. Default value is “date”.
  9) entries_sort_direction - Optional. Allows you to specify sort direction
  of entries. This parameter accepts two values: “asc” and “desc”.
  Default value is “desc”.
  10) entries_limit - Optional. Allows you to specify how many entries posted into
  child category should be displayed. This parameter accepts as its value an integer
  or “none”. Default value is “10”. Value “none” means that all entries will be
  displayed.
  11) date_format - Optional. Allows you to specify PHP date format string
  (Not ExpressionEngine’s date format string!). Default value is “Y-m-d”.

VARIABLE PAIRS:
 
  1) {parent_category_start}{parent_category_end} - Allows you to specify portion of
  code which will be iterated as many times as there are parent categories.
  Single variables available for use inside this variable pair:

  2) {child_category_start}{child_category_end} - Allows you to specify portion of
  code which will be iterated as many times as there are child categories.
  Single variables available for use inside this variable pair:

  3) {entries_start}{entries_end} - Use it to specify portion of
  code which will be iterated as many times as there are entries posted into child
  category. Single variables available for use inside this variable pair:

4) {entries_wrapper_top_start}{entries_wrapper_top_end} - Use it to specify top part of the code with which you want to wrap output of {entries_start}{entries_end} variable pair.
5) {entries_wrapper_bottom_start}{entries_wrapper_bottom_end} - Use it to specify bottom part of the code with which you want to wrap output of {entries_start}{entries_end} variable pair.
The tag {exp:child_categories} MUST contain at least one variable pair out of
{parent_category_start}{parent_category_end}, {child_category_start}{child_category_end} and {entries_start}{entries_end} variable pairs and each single variable MUST BE inside relevant variable pair.

SINGLE VARIABLES:
 
1) {parent_category_id}
2) {parent_category_name}
3) {parent_category_url_title}
4) {parent_category_description}
5) {parent_category_image}
6) {child_category_id}
7) {child_category_name}
8) {child_category_url_title}
9) {child_category_description}
10) {child_category_image}
11) {child_category_order_num} - outputs number used for custom ordering of
  categories.
12) {entries_total} - outputs total number of entries posted into child category.
13) {weblog_name} - outputs full weblog name.
14) {weblog_short_name} - outputs short weblog name.
15) {weblog_url}
16) {title}
17) {url_title}
18) {entry_date}
19) {count}

  EXAMPLE OF USAGE:
 

Here’s another one for anyone that might be interested. This allows you to re-create a drop-down menu in a form if you have a custom field of type drop-down.

Instructions are fairly simple :

Version 1.0.1 - Added initial_value_value and initial_value_option parameters

If you leave the initial_value_option=”“ parameter blank then nothing will be output and you will just get your options without an initial one.

Version 1.0

Hope it helps.

Best wishes,

Mark

Disclaimer
I’m pretty sure this should just work as advertised but please don’t sue me if anything goes wrong

I’m using the Twitter Timeline plug-in and wonder if it’s possible to force it to auto-link URLs? I’ve tried wrapping the ’{text}’ variable with the ‘Auto-link’ plug-in but no luck. I guess becuase I’m trying to execute one plug-in inside another (sounds like a bad idea!).

Could the Twitter Timeline plug-in be extended to include the option to have EE parse the text variable with it’s typography class?

Here’s an example: I was writing a comment on my blog, and typed in the following Textile snippet:

Here’s what the official Textile page returns:

This is what ExpressionEngine returns, however:

A few things seem to be going on here:

# Block-level elements such as blockquote, h1, h2, etc. are ignored by the Textile plugin if they appear on the first line of the textarea.
# Links aren’t processed if any non-URL characters are appended to the <code>“link”:URL</code> string.

There is, I believe, some wacky processing with lists (both ordered and unordered) as well, but I don’t have a test case handy. I’ve just experienced a lot of output inconsistencies with the plugin, and thought I’d raise the issue.

If anyone has any insight, it’d be much appreciated.

Just another very very quick one here. This plugin was written to help out in this thread here so that you can have a way on your single entry pages of checking if a user has already purchased an item using the Simple Commerce Module. May have uses so thought I would post it up here in the plugins forum for all to see.

Usage :

Best wishes,

Mark