Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#1 2009-05-14 21:52:08

RalphFFM
Member
Registered: 2008-10-05
Posts: 40

md_expirations

Hello,

i’m searching for the plugin code of md_expirations.
(http://textpattern.org/plugins/776/expiration-of-the-articles)
Compressed or uncompressed.
The download link doesn’t work no more. And i’ve no success with google.

Would someone be so kind to show or email the code? (Or the visible
part of the plugin via the administration > plugin > edit)

Many thx in advance! Regards, Ralph

Offline

#2 2009-05-14 22:50:56

maniqui
Member
From: Buenos Aires, Argentina
Registered: 2004-10-10
Posts: 3,070
Website

Re: md_expirations

Since TXP 4.0.7, articles can have an expiration date.

Would that work for you?


La música ideas portará y siempre continuará

TXP Builders – finely-crafted code, design and txp

Offline

#3 2009-05-15 06:35:47

RalphFFM
Member
Registered: 2008-10-05
Posts: 40

Re: md_expirations

My idea behind is to bring the articles in better order. Md_expirations promised
to switch the status of an article to hidden as soon as expired. (So i’ve understand.)

That will help me to group (separate) hidden articles from live articles.
(In the article list on the admin side)

Or is there another plugin that can separate live-and-not-expired articles
from live-and-expired articles?

Thx. in advance.
-Ralph

Last edited by RalphFFM (2009-05-15 06:39:06)

Offline

#4 2009-05-15 07:52:37

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 9,090
Website GitHub Mastodon Twitter

Re: md_expirations

By using the built in feature, expired articles return a 410 once their time is up.


Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.

Offline

#5 2009-05-15 12:16:08

RalphFFM
Member
Registered: 2008-10-05
Posts: 40

Re: md_expirations

Oh, i think there is a mistake, misunderstanding. I would like to increase the overview
over the article list in the admin area. In the backend at content > articles list.
(There i can “only” sort with 1 criterion..)

Thx.,
-Ralph

Offline

#6 2009-05-15 14:52:44

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 976
Website

Re: md_expirations

RalphFFM

Basically you want a plug-in that will

1) changes an article’s status
2) when triggered by a given event — in this case on a certain (expiration) date
3) in order to organize expired articles in the back end — ie tag them (w/ hidden) for sorting?

Last edited by maverick (2009-05-15 14:53:09)

Offline

#7 2009-05-15 15:07:24

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 976
Website

Re: md_expirations

An exercise in thinking aloud (for better or ill) . . . .

1) Might it be useful if an “expired” status was added to draft/hidden/static/pending/live, and if the built in expired automatically changed the status . . . . and how much of a coding change would be involved . . .

2) Might a plugin that changes statuses be useful on an event such as a date be useful in general (for example – pending to live on such and such a date). . . . would it be different or more useful than simply setting a future publish date . . . how might it be used with zem_event and smd_calendar . . .

Offline

#8 2009-05-15 18:19:08

RalphFFM
Member
Registered: 2008-10-05
Posts: 40

Re: md_expirations

Hello,

in the meantime the author of md_expirations (Martin) has send me his Plugin.

maverick schrieb:

1) Might it be useful if an “expired” status was added to draft/hidden/static/pending/live, and if the built in expired automatically changed the status . . . . and how much of a coding change would be involved . . .

I guess that would be tricky, because the information “expired” will be exist 2x.
What would be if someone changes the expired-time (later), but the status says
still “expired”?.. :-(

2) Might a plugin that changes statuses be useful on an event such as a date be useful in general (for example – pending to live on such and such a date). . . . would it be different or more useful than simply setting a future publish date . . . how might it be used with zem_event and smd_calendar . . .

Imho an interesting question. Generally i think there have to be very strong
arguments to make changes that increase the (internal) complexity of TXP. At the
moment, i can’t say if a change-status-trigger would be strong enoth that it is worth
it, or not.(?) In the most of all (my) cases the default possibilities are very very good..
i think.

Offline

Board footer

Powered by FluxBB