I don't know what's going on, but after things were working, randomly, all the sudden (maybe after I deleted and rebuilt aliases?) when I click to edit a node, it takes me to "page not found"! I can see that the url is pointing to where it *should* go (the aliased url), but I still get page not found! This is also happening to views - the urls are converted and look like they should, but only the non-aliased name works.

For example:
1. www.mydomain.com/users/username shows the user's profile
2. click Edit, returns "Page Not Found"
3. Edit tries to go to page "www.mydomain.com/users/username/edit
4. the page that actually works is "www.mydomain.com/user/1/edit"

This happens on all nodes, not just user profiles! It also happens to views!

Please Help! I'm in panic mode!

Comments

tevih’s picture

I've cleared cache, removed and uninstalled and reinstalled the module, and this still happens! I also have Sub-path URL Aliasing.

Please help! What's going on??

tevih’s picture

please can someone help??

greggles’s picture

I'm not sure, I've never seen this problem before.

I suggest disabling modules one by one until the problem goes away.

nmarkelz’s picture

Title: "Edit" node leading to "Page not found"! » Having the same problem: "Edit" node leading to "Page not found"!

I'm not a web developer to say the least, so I have no idea how to fix this new problem. Anytime I try to edit a page, hitting submit goes to "Page not found". Please help!!

JoshuaJones’s picture

Title: Having the same problem: "Edit" node leading to "Page not found"! » The issue was Sub-path URL Aliasing for me

After preforming a recent update for path_redirect, everything went to hell. I combed through all the modules I had and activated each - one by one. Once I activated Sub-path URL Aliasing, I was unable to edit nodes and users.

Try disabling Sub-path URL Aliasing and see if that resolves your problem. (When I try to edit the About page, Sub-path points me to /about/edit which leads to a page not found. Disabling sub-page will take you to the actual node edit page. /node/3/edit for example.)

greggles’s picture

Title: The issue was Sub-path URL Aliasing for me » Edit page for node leads to "Page not found"

I've used subpath url aliasing module with no problem, so maybe it's just some versions of it or some configurations.

Regardless, thanks for figuring that out.

greggles’s picture

Status: Active » Fixed

Marking this fixed since it is fixed for Joshua, but if other folks are still having problems please try his solution and if it doesn't work re-open the issue.

lcasassa’s picture

Version: 6.x-1.1 » 6.x-1.2
Component: Code » User interface
Status: Fixed » Active

I steel have the problem and I don't have Sub-path URL Aliasing and path_redirect module installed...

dave reid’s picture

Version: 6.x-1.2 » 6.x-1.1
Component: User interface » Code
Status: Active » Fixed

@lcasassa: Can you open a new issue since its not related to the symptoms above? Please be sure to include in your new issue as many details about the problem as you can provide.

Status: Fixed » Closed (fixed)

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

Patricia_W’s picture

I also started having this problem and I disabled pathauto which was the closest I could find to sub-path aliasing ... still not working.
Does anyone have any ideas? ... I still get the problem when I use the node URL but the pages are definitely there since I can see them before editing. I also tried to rebuild the menus (suggested somewhere) but that did not help.

Patricia_W’s picture

In my case, removing the FCKeditor module allows me to edit the page. I'll try to reinstall it and see if it works properly.

ktsour’s picture

For me the problem was a field. Actually it was the Font Awesome icon picker widget. When I tried to edit the field, it would give me a "Page not found". When I changed the field's widget from "Font Awesome icon picker" to simple "text", everything worked.
I don't know was broke the widget, but it was the widget causing the 404 pages.