Module: Seeries
Development and Programming
Hi Laisvunas,
I installed this module to see if it’s something that I can use. Even though it looks like it’s working fine, I have some questions and remarks:
- I am using the following code:
{exp:seeries name="test" parse="inward"}
{exp:weblog:entries weblog="software" entry_id="{seeries}" orderby="seeries"}
<a href="http://{url_title_path=">{title}</a>
{/exp:weblog:entries}
{/exp:seeries}At the top of the page, it always shows the following PHP notice:
Notice: Undefined index: paginate in /home/domain/public_html/ee/system/extensions/ext.seeries_ext.php on line 232- On some of the CP pages, it shows a weird character encoding. For example:
CP Home › Modules › Seeries › Order Seeriesand
CP Home › Modules › Seeries › Define SeeriesWhen defining seeries, what does the “Order By” option do exactly? I mean, when I enable the “Add new entries automaticaly?” option, I already select where I want new entries to be added, so they are already sorted that way?
Two other PHP notices I’ve seen after enabling the “Add new entries automaticaly” option:
Notice: Undefined variable: LOC in /home/domain/public_html/ee/system/modules/seeries/mod.seeries.php on line 465
Notice: Trying to get property of non-object in /home/domain/public_html/ee/system/modules/seeries/mod.seeries.php on line 465- Minor typo: “automaticaly” should be “automatically” 😊
Looking forward to your reply, this is a very promising module!
Hi Gleon,
Your remarks (1), (2), (4) and (5) concerned bugs. I fixed them, so grab the version 1.4.1 and check if now everything works as expected.
Concerning your remak (3):
Using “Order By” option you specify how entries in the seeries should be ordered initially, i.e. before any reordering can happen. “Add new entries automaticaly?” setting has no relation to initial ordering of seeries; it starts functioning when seeries is created and initially ordered.
Perfect, thanks! I haven’t been able to reproduce the bugs, so this version looks very stable now!
Regarding the “Order By” option, I guess it confused me because it’s still an option that you can change when you choose to edit a previously created seeries…but it will no longer function by then because it’s only used when you initially created the seeries?
If so, it may be better to not show a dropdown box for the “Order By” and “Sort” options when you edit a seeries, but rather show a message such as “This seeries was initially ordered by date and sorted descendingly” instead?
Thanks again Laisvunas, I’m going to play with it some more in the next couple of days 😊
PS the categories column is a very nice feature, something I was missing in the REEOrder module (when you have hundreds of entries it’s nice to see the categories they belong to).
Hi Gleon,
If so, it may be better to not show a dropdown box for the “Order By” and “Sort” options when you edit a seeries, but rather show a message such as “This seeries was initially ordered by date and sorted descendingly” instead?
Excellent suggestion. Grab the version 1.5. In it after defining seeries there will be no more selectboxes “Order By” and “Sort” displayed. Instead you will see messages, such as
This seeries has been initially ordered by title.
and
This seeries has been initially sorted descendingly.
Thanks for the quick replies and version updates Laisvunas! Downloaded and installed v1.5, works perfectly it seems 😊
Hi,
I released version 1.8 of Seeries module.
In this release:
1) fixed bug - group level assignments not being transferred to members transferred from the group not having access to Publish form to group having such access;
2) added possibility to revoke member-level assignments for single member;
3) in relevent places seeries assigned on member level are marked by letter “m” while seeries assigned on group level are marked by the letter “g”.
Hi,
I released version 1.9 of Seeries module.
In this release a bug was fixed - order of seeries not being preserved after updating assigned seeries list at member level.
I just installed a fresh copy of v1.9 on an MSM site. Not sure if that’s related though, but when I enter a status with a space – or use “not” which requires a space after, I get an error:
Statuses contain invalid characters!
One more thing, the site also has thousands of entries and every time I click the link to a Seeries it takes a really long time to load. Maybe there should be way to set a limit so that it only looks for the most recent x amount or past x number of days.
Hi smartpill,
I just installed a fresh copy of v1.9 on an MSM site. Not sure if that’s related though, but when I enter a status with a space – or use “not” which requires a space after, I get an error:Statuses contain invalid characters!
This is a bug. I fixed it in version 1.9.1, so grab it from the first post in this thread.
One more thing, the site also has thousands of entries and every time I click the link to a Seeries it takes a really long time to load. Maybe there should be way to set a limit so that it only looks for the most recent x amount or past x number of days.
I will think about it when releasing a new version.
Hi,
I released version 1.9.2 of Seeries module.
In this version a bug was fixed - just created seeries not being displayed in the form allowing to assign seeries on member level.
Hi,
I released version 2.1 of Seeries module.
In this release:
1) A new option in seeries definition was added - “Clean seeries automatically”. If “yes” selected, then seeries will be automatically cleaned from entries which no longer satisfy seeries definition.
2) the code was optimized in order to process long seeries more quickly.
Doesn’t quite work.
When I try to create a group I get:
[Wed Dec 23 12:29:46 2009] [error] [client ***] PHP Fatal error: Call to undefined function filter_var() in /var/www/vhosts/***/httpdocs/system/modules/seeries/mcp.seeries.p
hp on line 1806, referer: http://www.***.com/system/index.php?S=44ead99c534d3d355583bdc3d646efe789f14d03&C=modules&M=Seeries&P=seeries_prefsI very much like the idea though 😊
Hi Milan,
filter_var() function was added to PHP 5.2; it seems that Your PHP version is a littele bit older.
D’oh! 😊
Thanks!
PS I’m using Redhat Enterprise linux on Rackspace with default repositories. This equates to PHP 5.1.6.
RHEL is a very common distribution for “serious” servers and for sake of stability.. so lots of people will keep the default repositories, so won’t have PHP 5.2