By rbroberts on

When I click on the Add Content and select, for example, basic page, I get the form to edit the page. When I click save, I am either given a blank form again, or taken back to my home page. Same thing for article, book, and blog.

This is Drupal 7.38, this is a new install with only a few extra modules in place, e.g., Agenda. Which is working.

I was able to create one basic page. If I recall the sequence correctly, I attempted to create another basic page with an iframe linking to a Google calendar. That's what first gave me this behavior, but since then, I can't get anything to save. The logs show no problems, just nothing happening.

I've got the modules Date, Agenda, Insert, Libraries, Nice Menus, and WYSIWYG installed, with CKEditor 3.6.6.

I'm actually setting this up to look like a test site I already had (with just a couple of pages), and that one works fine. I'm baffled as to where to even look at this point.

⋅ Categories: Drupal 7.x

Comments

nevets’s picture

nevets commented

How many pieces of content show up on the content admin page?

rbroberts’s picture

rbroberts commented

One. The "About Troop 13" basic page I first created. None of the other attempts to create a page have produced anything; they don't show up on the content admin, they don't show up in the logs.

rbroberts’s picture

rbroberts commented

This appears to be related to the use anything but Plain Text in the format. But I can't see why. I'm logged in as admin, I have permission to create any of those content types. But, if I use Plain Text to create the page, I can then edit it and change it to anything.

rbroberts’s picture

rbroberts commented

This happens even on a clean install with no extra modules.
If I try to create a new basic page, I can only do so if I either select Plain Text as the format. Or I can select Full HTML, but have to enter only text, no tags. Since there's no editor installed, I have to enter the HTML code myself. If I enter anything other than plain text (e.g., a simple strong), I get sent back to the home page with no page created.

nevets’s picture

nevets commented

Ok, I just tried that and it works for me.

What OS are you on?
What Web server?

rbroberts’s picture

rbroberts commented

It's Apache but it doesn't report a version (hosting service, no direct access, so I can't tell), OS is some Linux variant; reports as 2.6.32-531.29.2.lve1.3.11.10.el6.x86_64. PHP is 5.4.43.

I just tried uninstalling and putting in Drupal 6.36, same problem. There's got to be some simple (and stupid) thing I'm missing. I had no trouble with Drupal 7.38 on another host doing the same install which has PHP 5.4.41. I can't find anything about PHP 5.4.43/42 release notes that would hint at a problem there. There are minor differences in the status report for the non-working vs the working: PHP 5.4.43 vs 5.4.41, PECL uploadprogress installed vs not, no non-core modules vs a few added, 168M upload limit vs 128M.

I'm pulling my hair out on this one. The only extra clue I've got is that for Drupal 6.36, the attempt to save a node is generating a 403 which does show up in the log.

nevets’s picture

nevets commented

I am guessing it is a hosting issue.

rbroberts’s picture

rbroberts commented

I'm guessing the same thing at this point. The closest I've come in tracking down similar issues is https://www.drupal.org/node/110219 which points to a mod_security issue. I've contacted my provider to ask them to look at it. Hopefully that will resolve it or I'm really out of luck....

rbroberts’s picture

rbroberts commented

I don't know exactly what rules they changed, but my hosting provider removed/whitelisted at least two (because I had to go back to them after the first change) to get this to work.

The real issue that made it take so long to figure out was the Drupal 7.38 was not giving any errors, it was just throwing me back to the add/node page or even the home page. Drupal 6.36 was giving a 403 error which made it easier to figure out it wasn't really a Drupal problem.