When I add a Link field to a content type, and the link gets filled out, the result post-save is always "Page Not Found". I've played around with all the options on the field, tried different combinations of links, titles, etc, and every time I get the same result. As soon as I edit the content and remove the value of the link fields, the problem is solved. But even a single character in a link field causes Page Not Found.

I have tried this on two separate servers, and multiple content types, old and new.

Has anyone seen this before?

Comments

azzurro’s picture

azzurro commented

I have the same problem. The front-end shows "Page Not Found" while you can still access the site as admin the admin's section.

azzurro’s picture

azzurro commented

I would also mark the bug with priority "critical", as the module is useless until the bug is fixed

maiki’s picture

maiki commented
Priority: Normal » Critical

I am also having this issue. I am not sure where to go with this, but I can do more testing if it will help a dev.

There is not other information except that the Page is Not Found.

I am using Pathauto, and I am able to edit the content by its node ID (i.e. /node/5/edit).

lacitpo’s picture

lacitpo commented

same problem. Makes the module useless

quicksketch’s picture

quicksketch
he/him
commented

Sounds like there's a conflict between pathauto, link and token module somewhere. Could someone post the version of each module they're using, along with what the declaration of the link field is, and what pattern they have setup for that node type in pathauto?

mmoreira’s picture

mmoreira commented

I have same problem. I couldn't detect before and reinstalled all drupal and modules, but when I created a post in a blog, with a link (using the Link module), I got "Page not Found".

I'm using "Link 5.x-2.0", "Token 5.x-1.8", "Pathauto 5.x-2.0-beta3" and "Content Construction Kit (CCK) 5.x-1.6-1".

The pathauto pattern for blog is just "blog", and for the posts is "blog/[title]".

The settings for the Link: No Group, NOT Required, NOT Multiple Values, Optional Title, Allow tokens, Open link in a New Window.

mmoreira’s picture

mmoreira commented

I forgot to tell: if ALLOW TOKENS is not checked, the PAGE NOT FOUND doesn't show anymore. The content appears, the link is there... everything turns to be OK...

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Fixed

This problem was fixed in the 1.9 version of token module.

content_view() not recursive safe - http://drupal.org/node/129338

In the future, please try out the latest stable (and even dev) versions of modules before reporting bugs. They may have already been fixed!

quicksketch’s picture

quicksketch
he/him
commented

mmoreira, btw thanks for the great set of info on modules. I found the problem in 5 minutes with such exhaustive configuration info.

phasmaphobic’s picture

phasmaphobic commented

Thanks for pointing me to the resolution, fellows. I'll look into it later today.

"In the future, please try out the latest stable (and even dev) versions of modules before reporting bugs. They may have already been fixed!"

I'm fairly new to drupal, but quite experienced with other CMS and general tech-supporting. I checked all the information I could that I thought would be related, but since this module only requires CCK, there was no obvious-to-me reason for me to check the tokens module (which I'm generally unfamiliar with at the moment outside of a couple of modules that I know use it). I searched a good while for different answers in whatever documentation I could find (and this very site's search features), and only posted here because I could find none.

Little quips like yours above are patronizing. Not everyone is as drupal-savvy as you, and there's no need to make anyone feel bad because of it. Thanks again for posting the solution, but in the future, please try to be more patient with those who are reporting what they think might be bugs. They may not be as familiar with the situation as you, and in the end, they're only trying to get some help, and they're also trying to help you make the module better. You should be more appreciative that your module is desired by so many people - I know if I were in your shoes I sure would, and be glad to help as many of them as I could.

quicksketch’s picture

quicksketch
he/him
commented

Apologies phasmaphobic, I didn't mean to be quipish. :)

Trying out the new unreleased versions of modules is something not many people do before posting issues. I just try to make sure it happens as little as possible to save myself some time pruning the issue queue.

The problem described here I believe only affected users who are also using token module on their site, as I experienced a similar issue when using token module. If the latest version of link module still shows this problem (with or without token module), we may have a separate issue on our hands.

phasmaphobic’s picture

phasmaphobic commented

Thanks for the reply, quicksketch. The fix works like a charm, and I'm really glad to have it. Links links everywhere!

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

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