Archives views doesn't work. In fact I have a list of Year that link to content for that Years. But some Years are not linked and I have a message : "The page you requested could not be found." Does anyone have an idea ?

Comments

webbykat’s picture

webbykat commented
Priority: Critical » Normal

Hi there,

I'm downgrading the priority since support requests are never major or critical.

I'd like to help, but I'm not sure what's causing the problem yet. Could you provide the information below?

  • Do you have content for the unlinked years in your system? e.g. If the year is 2009, do you have posts/pages from 2009?
  • Have you made any modifications to the view? If so, which?
  • Do you have both a block display (e.g. a months block in your sidebar) and a page display (e.g. a long page of posts for that month) generated by the view, or only one of these?

If you don't mind providing a link, it would be helpful in this case, but if you'd rather not, you don't need to.

Thanks,
Kat

jarmo’s picture

jarmo commented

Hi,
the year is 2009 and I have posts/pages from 2009.
I change my view : I have the cck date of my content type as argument
I have the both (block and a page display by year)

Precision :
I used node import module to import a part of my content maybe it causes trouble on my archive view ?

thanks

kars-t’s picture

kars-t commented
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed".

If there is new information, please re-open the issue.

--
This issue was edited with the help of Issue Helper

Automatically closed -- issue fixed for 2 weeks with no activity.