By kgad on

Since I upgraded to drupal 4.6.4 yesterday, the "previous/next page" and page number links (1,2,3,...) have stopped working, I keep on seeing the front page.

So

http://hostname/drupal/

and

http://hostname/drupal/?q=node&from=10

result both in the front page being displayed. Searching for posts still works fine and the node table in the database seems to be just fine too. I am using a postgres database though.

Anyone else is seeing this problem?

ps. At first sight, the problem doesn't seem to be related to this problem, I never get an error while reloading.

⋅ Categories: Drupal 4.6.x

Comments

pnelson’s picture

pnelson commented

I'm seeing the same problem. I upgraded 6 drupal based sites, from 4.6.3. to 4.6.4 and now they all fail in the same way, they only show the first page when "next" or a number is selected.

Sample url to the failing page:
http://hs.riverdale.k12.or.us/maverick/?q=node&from=10

rjung’s picture

rjung commented

I'm pretty sure it's the same as this bug. The ampersand argument separator was the problem, and the patch should fix it.

--R.J.
http://www.electric-escape.net/

--R.J.

pnelson’s picture

pnelson commented

Can someone help with how to apply the patch or will there be a version newer than 4.6.4 out with the fix?

Thanks...

venkat-rk’s picture

venkat-rk commented

I am not sure if a newer patched version will be released. Meanwhile, you can try this site for an interim solution:
http://www.pingvision.com/

chrislck’s picture

chrislck commented

Great! it works!! I've just replace the /include/common.inc by the new one downloaded from above and that's all. Thanks.

kgad’s picture

kgad commented

Download the check-url.patch from the above described thread and put it into your main drupal directory.

Then type 

patch -p0 < check-url.patch

That will do the trick.

klaas

donkilo’s picture

donkilo commented

Where (with what program/OS) do I type this? Thanks, Kyle.

La Red Riecken

kgad’s picture

kgad commented

Thx, that was the solution!

Klaas

hexa’s picture

hexa commented

had the same problem after aplying those security pathes for 6.4.
I changed the line in includes/common.inc
from:
$uri = htmlspecialchars($uri, ENT_QUOTES);
to
$uri = filter_xss_bad_protocol($uri, FALSE);

It works without a problem now.

I guess only aplying security patches from 6.3 to 6.4, breaks some stuff and people should be warned about it!! But we were not ;-)