Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Two article for the same thing: end date and future release?
I’m stuck on a case, maybe someone will have an idea on how to go about it.
I’m building a website with product (the product is describe in an article) that have a launch (release) date. What I’m trying to do, is to have a “future releases” pile of products, that will automatically become “released products” once we reach the launch date.
The trick is, I’m trying to have two different description (or even better, partially different) for the same product. Basically for future products something like “this product will rock your socks once it’s release, it’s planned for Christmas but Murphy can happen”, and for released one something like “this product has this, and that, and oh also this”.
This need for two descriptions tells me I can’t use one article (because I also need the excerpt for… an excerpt :)
I could use two articles, one with a published date set in the future, and one with some kind of plugin to handle the “end date” (I wonder what plugin would do that nicely); but then I hit a permalink issue. They can’t have the same URL, and the visitors will need some consistancy at this level.
I’m sure I’m missing an elegant way of doing that… does anyone has an idea?
Offline
Re: Two article for the same thing: end date and future release?
I have a very similar problem with managing the neme.org site. At the moment all calls and info are posted in their own categories/sections, once the call expires I manually move it to the archives. I can spot the expired posts in the site’s sitemap and the glx_countdown plugin.
I cannot offer you a solution here Jeremie, but think that the best way to deal with these kind of posts is an automated way which moves the post to a section/category. I kind of hinted for help re this kind of funtionality a number of times in the past but there were no responses.
I understand that my problem is slightly different to yours and it might even change the url of the article for those who use ‘section’ in their url scheme but upart from the zem_event plugin which is too specific in what it does, there is nothing out there which comes close to either your or my dilemma.
Last edited by colak (2007-09-13 13:09:57)
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Two article for the same thing: end date and future release?
Could do the trick:
- rss_suparchive-plugin’s timeframe “future” could do the “future releases”-list and
<txp:article />released products. - rss_auto_excerpt could automatically create other excerpt from the article-body, and also jump over it when reading the full, single article. So it would be hidden, as even it is in the body.
Cheers!
Last edited by Gocom (2007-09-13 13:39:38)
Offline
Re: Two article for the same thing: end date and future release?
@Colak,
The thing is, I already have use for any other capabilities. Each “product” has a section (and a real one… its own URL prefix, its own stylesheet, its own page), category (again a real one, that can be called cross-site and merged with other articles from others sections of the same category), etc.
The TXP structure (sections, categories, etc.) is — for once! — perfect for this project. It’s just that small functionality I’m asking about here I’m stuck unto.
And on top of that, the content will be handled and generated by non-geeks, so I need to keep its management neat and clean.
I thought about an event plugin, but I’m guessing they are too specific yes.
I also thought about using a custom field to hold the “pre-release status” additional data or text, but it would mean a lot of core code and database hacking (a lot as in: complex to update and manage in the future) to have a custom field large enough (both as an sql container and as a textarea on the backend)…
Last edited by Jeremie (2007-09-13 13:46:29)
Offline
Re: Two article for the same thing: end date and future release?
Gocom wrote:
rss_auto_excerpt could automatically create other excerpt from the article-body, and also jump over it when reading the full, single article. So it would be hidden, as even it is in the body.
You mean, I store the pre-release text in the excerpt field and display it as content when I’m in a pre-release context; and then when I’m in the released context, I skip the real excerpt and generate another excerpt with the plugin?
MMhhh… nice idea…
I’ll have to check to article’s body structure and content to see if that’s possible.
Last edited by Jeremie (2007-09-13 13:47:25)
Offline
Offline
Re: Two article for the same thing: end date and future release?
Another option is to use a custom field to store the story id of the post launch article. Then have it compare today with the referenced article and use its info instead of the current (pre launch) article.
If you can get away with modding the excerpt plugin, that would probably be less work and keep each product bundled in 1 article.
Offline
Re: Two article for the same thing: end date and future release?
That would be a little user unfriendly yup.
I’m still investigating playing with another way of generating an excerpt, and use the TXP built-in excerpt as alternate body or something.
Offline