Hello,

I just installed the newest recommended release to my website. I had updated to a version that was in development on Friday (I think it was 7.x-1.4??) and things weren't perfect, but it seemed to be working ok for the most part - I could at least get the comparison table. When I installed recommended 7.x-1.5 today I noticed that when I click "Compare Selected" I get the following error:

The requested page "The requested page "/compare/type/blog/31/29/27" could not be found." could not be found.

Nodes 31, 29 and 27 are what I'm trying to compare.

I've checked the settings and nothing looks out of place, I also didn't alter any settings after the update. I've cleared the cache, re-installed the module and tried clearing and re-comparing nodes. Can't seem to get it to work.

Anyone else having problems?

CommentFileSizeAuthor
#7 img-nodecompare-notworkingasexpected.png141.36 KBkelo335

Comments

Dalay’s picture

Hm, I have everything works fine (try demo 7.x-1.5). I do not know than to help you.

Maybe your fields have no values?

FinderFees’s picture

I tried this out on my Acquia Development Desktop which originally had 7.x-1.4 (I verified this time) and worked correctly. When I updated it to 7.x-1.5 it also broke. I understand it's really hard to diagnose without a better error other than "page not found". Perhaps someone will have more information if they are experiencing the same thing.

Dalay’s picture

Status: Active » Closed (cannot reproduce)
Dalay’s picture

Status: Closed (cannot reproduce) » Closed (fixed)

I have identified the bug. This occurred if the limit for compared items has not been set. Fixed in release 7.x-1.6.

Dalay’s picture

Issue summary: View changes

Edited

khakistocracy’s picture

Issue summary: View changes

This seems to be a problem I've just developed. This module was working perfectly to begin with, and through development of the site with no real changes to the structure it seems to have stopped working and just reports a page not found error when comparing. I began with 7.x.1.6, and have tried uninstalling and reinstalling with 7.x.1.6 and the dev version - still just get page not found now.

I've got a real lack of information to pass on really, but is there anything obvious that might be causing this? Or anything I could check? Or any info I could give you that might be useful. This was a perfect little module until something went wrong!

khakistocracy’s picture

Version: 7.x-1.5 » 7.x-1.6
Status: Closed (fixed) » Active
kelo335’s picture

StatusFileSize
new141.36 KB

I get this error message too, using Drupal7 and module 7.x-1.6. I have a limit of 2 set on the compare.
Page not found
The requested page "/drupal/compare/type" could not be found.

For me, I wonder if the problem stems from the instruction "Set the region to display the block which to display a deferred items to compare." How do I do that?

In my install, I don't see the queue like https://www.drupal.org/files/project-images/node-compare-display-block.png. It shows in the body that they've been added to compare, but not in nav like in the demo.

andreas1stdru’s picture

Dear All,
Unfortunately I don't get the "node compare" going and it sounds as if I have a very much similar issue then the developers above.
The node compare seems to work from all its configuration parameters, even on the web-site it is possible to "ADD" and "REMOVE" nodes. Once I click the "Comparison table" the error:
"For comparison requires at least two items" and "required page /compare/type not found" .

I'm using Drupal 7.34, installed the released version of "node compare"–7.x-1.6, came to the problem above, uninstalled the module, installed the development version " node_compare-7.x-1.x-dev", tried many other things … no solution still the same issue.

Is anybody able to give me a hint on what I'm doing wrong here?

Many thanks in advance!!!!
Andreas

criz’s picture

It seems as the linked url compare/type doesn't work without arguments. The block works for me.

Dalay’s picture

Status: Active » Closed (fixed)

The above problems have been fixed in a last dev-releases.