By sebbo92 on
Hi all,
I'm having a horrible problem where when editing a page, after clicking "save" it brings up a page (the theme still shows, but no menus) that says "Page not found". This get's annoying after a while...
I'm not sure what changed as it was all working fine and funnily enough, still works on some pages sometimes. But generally it gives me that error. I really need to finish this website and I can't edit anything, so it's a really big problem.
Please help if you can.
Comments
Hi, Did you install any
Hi,
Did you install any module afterwards which this problem started, which url it is getting redirected ?
Acquia certified Developer, Back end and Front specialist
Need help? Please use my contact form
There isn't a problem with
There isn't a problem with the modules. I uninstalled CCK and Views and re-installed, and tried saving at all three points of that process and it didn't work.
It seems like, per my error report, I'm getting a 404 error (page not found) on the 403 (forbidden) error page. In other words, some security settings on my server are stopping that code from being saved, but the 403 error page isn't there so it ends up giving me a 404 error.
I'm going to call the host today to find out if they can help me.
Turned out to be a problem
Turned out to be a problem with a sort of server firewall called mod_security. It's purpose is to stop hackers from inserting mysql_query type commands into your website. So, I solved this problem by creating the page with the titles, all settings but with a blank body. Then going into your database where your Drupal is installed and opening the table node_revisions, find the row for the page you just created, and editing the body column. It's either that or call your host and ask them to remove the rule from mod_security, but that puts you at risk.
So there you go. Solved.
Page Not Found error given for some existing nodes
I have this 'Page Not Found' error with seemingly random nodes, if you try to view or edit them, you get the page not found page. The content is in the database, and views can find them just fine, but when you click on the node title in the view, some content works (displays the node page) and some give the not found error...
Most nodes work just fine, only a handful are having this problem so I don't see how it could be a server firewall.
This is a 6.24 site on a godaddy VPS (centos)server, I don't think I have full access to the logs, the one I can see shows nothing. I've cleared all caches... I'm stumped!
Random 'page not found' problem sort of fixed
I never fails, once I post my problem on drupal.org, I figure out the problem, weird. Anyway, turns out my nodes that were getting the Page Not Found error had a uid value of 4 - and there is no user 4 on the site. Not sure why they were 4, the people creating the nodes were users 2 and 3. So once I changed the uid in the node table to be '2', that fixed my 'page not found' issue.
So if I ever figure out why those were saved with the wrong uid, I'll let you know.
Just changed the text
I just spent 3 hours trying to understand why I was getting page not found. In the end I narrowed it down to one sentence in my content. I change the wording that one sentence and the page saved. Ultra strange.
double dash was the culprit
I had a similar error where a node I had previously saved fine was now giving a "page not found" error on save. After some trial and error, I found the problem was caused by double dash at the beginning of a line. I.e. "--" at the start of a new line in the html in node content. I just add a space before the double dash or reword without the double dash and the node saved fine.
Go figure!
Saving one particular node results in 403 error
Not sure if I'm experiencing the same thing - I moved my dozen drupal sites to a new host. Immediately, the image module used in most of my sites started complaining, but that was remedied by setting memory_limit to 128M (http://classicjets.org/phpinfo.php).
Now I have one node (duplicated at http://classicjets.org/content/eleven2-test) that results in a 403 error when attempting to save. In order to update the page, I now have to open phpmyadmin and edit the node_revision table. That'll work for a while but I suspect it will become old after a while.
There are quite a few variables, but all signs point to a php setting at my new host:
It's just this one page on one Drupal site at a reputable host, and it's not a mod_security issue. Any thoughts?
I am currently trying to
I am currently trying to upgrade from Drupal 7.43 to 8.1. I have my site partially working, with many bugs. I am currently plaqued with the error reported above. It happens on EVERY "save", NONE of my contents have -- in them. Any ideas? I am self-hosting on Windows 10 Pro, using Apache webserver. It all works fine on D7.43.
regards,
DJ
Did you find solution?
Hello,
Does anyone has found a solution to this problem.
please share it.
Affected too.
I had this same issue in D8,
I had this same issue in D8, If you look for the error in the Apache error logs mine pointed me to the title cannot be null. Basically I had hidden the title field from the edit form and thus could not enter a title. Upon saving it then threw the error. I simply un-hid my title field and retried creating the content and all worked. This really should be something which is either auto generated in D8 or a warning is given when hiding the field on the edit form, or just disallow hiding the title field on the edit form.
GAMe
http://www.aprox.co.uk