devot:eeDevoted to ExpressionEngine

Except the purpose and general concept everything else is different:

• Seeries module has completely different interface; it supports pagination in all relevant places of the module’s interface;
• It allows to assign to members the right to edit particular entry series (further “seeries”); members can see only those seeries they are permitted to;
• It allows do define seeries more flexibly;
• It has option allowing seeries to be updated automatically;
• It uses more efficient ‘weblog_entries_query_result’ hook.

INSTALLATION

1) copy “seeries” directory into “modules” directory on the server;

2) copy “ext.seeries_ext.php” file into “extensions” directory on the server;

3) copy “lang.seeries.php” file into “language/english” directory on the server;

4) go CP Home >  Admin >  Utilities >  Extensions Manager and enable “Seeries” extension;

5) go CP Home >  Modules find “Seeries” module in the list and click “Install”; the module will be installed;

6) then open the page of “Seeries” module and click button “Define or Edit Seeries”; Define some seeries.

7) Then again open the page of “Seeries” module and assign just defined seeries to some member or to some member group; now that member or all members of that member group has the right to custom order entries belonging to seeries. Notice: Seeries assignments made on member level override those made on member group level; but you can revoke member-level assignments for entire group while assigning Seeries to it. Also you can revoke member-level assignments for single member. In relevant places letter “m” marks that the assignment of seeries was made on member level, while letter “g” marks that assignment was made on group level.

CUSTOM ORDERING OF ENTRIES

Logged-in member after opening the page of “Seeries” module sees all seeries he has the right to reorder. To reorder some seeries he must click the link displaying seeries name. Then a list of entries belonging to seeries will be displayed.

To reorder seeries checkboxes should be checked and new count numbers should be entered in relevant text fields. To exclude entry from seeries text field should be left blank. Entries excluded from seeries are displayed at the bottom of the list.

DISPLAYING CUSTOM ORDERED ENTRIES

To display entries in the order specified by seeries one should use {exp:seeries} tag. This tag has following parameters:

1) “id”, “id_1”, “id_2”, “id_3” ... “id_48”, “id_49”, “id_50” - allows to specify one or more seeries id numbers.

2) “name”, “name_1”, “name_2”, “name_3” ... “name_48”, “name_49”, “name_50” - allows to specify one or more seeries names.

At least one out of “id”, “id_1”, “id_2”, “id_3” etc. or “name”, “name_1”, “name_2”, “name_3” etc. parameters of exp:seeries tag must be defined, since ids and names are used to uniquely identify seeries.

{exp:seeries} tag has following variables:

1) {seeries} - outputs content of the seeries specified by “id” or “name” parameter.

2) {seeries_1}, {seeries_2}, {seeries_3} ... {seeries_48}, {seeries_49}, {seeries_50} outputs content of the seeries specified by “id_1”, “id_2” ... “id_49, “id_50”, or “name”, “name_1”, “name_2”, “name_3” ... “name_48”, “name_49”, “name_50” parameters.

{exp:seeries} tag can be used to wrap {exp:weblog:entries} tag; {exp:weblog:entries} tag must have “orderby” parameter value set to “seeries”:

{exp:seeries name="eee" parse="inward"}
{exp:weblog:entries entry_id="{seeries}" orderby="seeries"}
<a href="{homepage}/template_group/template/{url_title}/">{title}</a><br>
{/exp:weblog:entries}
{/exp:seeries} 

Also {exp:seeries} tag can be used to wrap {exp:entries_list} tag of Entries List plugin:

{exp:seeries name="aaa" parse="inward"}
{exp:entries_list entry_series="{seeries}" site="1" }
<a class="menuItem" href="{weblog_url}/{url_title}/">{title}</a><br>
{/exp:entries_list}
{/exp:seeries} 

NEW PARAMETERS OF exp:weblog:entries TAG

1) seeries_limit - if you wrap with exp:seeries tag the tag exp:weblog:entries, then its “limit” parameter will work correctly only in case “paginate” parameter and {paginate}{/paginate} variable pair is used. In cases you do not use “paginate” parameter and {paginate}{/paginate} variable pair use instead of “limit” parameter use “seeries_limit” parameter.

2) seeries_entry_id_from - if you wrap with exp:seeries tag the tag exp:weblog:entries, then its “entry_id_from” parameter will not work correctly. Use instead “seeries_entry_id_from” parameter.

3) seeries_entry_id_to - if you wrap with exp:seeries tag the tag exp:weblog:entries, then its “entry_id_to” parameter will not work correctly. Use instead “seeries_entry_id_to” parameter.