After upgrading from views 2.2 to 2.3 (Drupal 6.8, and Drupal 6.9 tested, Garland) the monthly archive block I was using has changed behaviour. Before the upgrade clicking on a link for the month of January brought me to a page with entries for that month. After the upgrade the entries are shown in the side bar with their teaser, but the page URL does not change to the new page.

All caching cleared (even turned off).
No Ajax
Garland Theme
Monthly Archive Block (enabled, but no modifications)

Side note, popular content block works the same as before the upgrade.

Comments

merlinofchaos’s picture

merlinofchaos commented

And you're 100% sure that 'use ajax' is set to 'no'?

stompersly’s picture

stompersly commented

Thank you! You were right, Ajax was to no on default and page but yes on block.

I wonder what has changed, on a fresh install with views 2.2 I just enabled Monthly Archive, now with views 2.3 I have to enable the Monthly Archive view and then edit to turn off Ajax, weird...

Thanks for your help.

stompersly’s picture

stompersly commented
Priority: Critical » Normal
Status: Active » Closed (fixed)
merlinofchaos’s picture

merlinofchaos commented
Status: Closed (fixed) » Active

Hmm. The archive view shouldn't default to ajax on, this may be a bug in itself.

marshallbu’s picture

marshallbu commented

I had this very issue as well.
With 2.2, the Archive List showed up as a block, with or without enabling the view in the view settings. I verified this on several installs.

On 2.3, I had to enable it, and not just set Ajax to NO on the block, but also had to make sure that it was set to "use default values" for that setting. Setting it to no still seems to make the links expand in the sidebar or wherever the block was located.

corbacho’s picture

corbacho commented

Thanks I found this. I had same issue here,

With Ajax set to No, it was enough for me.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

This setting is now fixed in CVS.

Status: Fixed » Closed (fixed)

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