Forums / Setup & design / Article archive

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Article archive

Previous topic

Setup & design

Next topic

Author	Message
enigmista enigmista	Tuesday 29 July 2003 3:46:06 am How can i creare un archive for my articles for month?Example January <- when i click i see all articles published in january Febrary <- when i click i see all articles published in febrary It is possible? tnx
Pirkka Hartikainen	Tuesday 29 July 2003 2:56:23 pm It hardly seems impossible using Exponential 3 to me. :) I'm also working on a somewhat similar feature, it's a magazine archive storing few years worth of issues of a monthly print magazine. I ended up creating nodes for each year and each magazine (=month), like this: Archive node ..Volume node ....Magazine node ......Article node A content class exists for each node above. I've been thinking whether this is the best approach, since the planned GUI does not include a view for the volume node. I might end up having to remove some items from the "breadcrumb trail" navigation due to the fact. Anyway, I'm interested on any archiving solutions/best practices from the experienced eZ users. There are probably quite a few possible ways to approach this..

Author

Message

enigmista enigmista

Tuesday 29 July 2003 3:46:06 am

How can i creare un archive for my articles for month?Example

January <- when i click i see all articles published in january
Febrary <- when i click i see all articles published in febrary

It is possible? tnx

Pirkka Hartikainen

Tuesday 29 July 2003 2:56:23 pm

It hardly seems impossible using Exponential 3 to me. :)

I'm also working on a somewhat similar feature, it's a magazine archive storing few years worth of issues of a monthly print magazine.

I ended up creating nodes for each year and each magazine (=month), like this:

Archive node
..Volume node
....Magazine node
......Article node

A content class exists for each node above. I've been thinking whether this is the best approach, since the planned GUI does not include a view for the volume node. I might end up having to remove some items from the "breadcrumb trail" navigation due to the fact.

Anyway, I'm interested on any archiving solutions/best practices from the experienced eZ users. There are probably quite a few possible ways to approach this..