OK, this is weird.

I've set up a fresh install of Drupal 5.0. Currently it isn't running anything other than the default modules that come with the package.

I've been going through the rather laborious process of moving all of my posts from my old site (which had been running WordPress) into Drupal. I've been doing this by exporting my wordpress posts as text and then cutting and pasting them into the story module one by one. Wheee.

Out of some 30 or so articles, two of them generated 404 errors when I tried to publish them -- the others had no difficulties whatsoever. I decided to figure out exactly what was triggering the 404, so I took one of the posts and I entered just the title, category, and time stamp, putting the words "placeholder text" in the body.

That worked.

I then began to edit the document, slowly replacing the placeholder text with text from the actual article... two paragraphs at a time.

The first few cut & paste's worked just fine. Six paragraphs in, however, I received a 404. This was the text I was trying to post:

This quote is offered as an explanation as to why the laptop isn't powerful enough to play the latest and greatest games available on the market today, and it makes me want to bang my head against the wall until I lose consciousness, just to grant me a moment of sweet respite from the sheer silliness of the idea.

There aren't any strange codes in it. The only thing I can think of to explain it is that Drupal thought it was lousy writing and refused to publish it. :)

Then I decided to experiment. I took that text and inserted it into another article that had already been posted successfully. As soon as I did that and tried to update the article, I received a 404 message.

Basically, that snippet of text spells certain death for any article I try to place it in -- inserting that text creates a 404 error on my site... and I have no idea why.

Can anyone guide me through this?

Comments

ubersoft’s picture

... it did not create a 404 error here. So it's something I configured on my own site, I suppose, though I can't for the life of me figure out what it could be...

ubersoft’s picture

Omitting that paragraph allowed me to publish the rest of the article. After that I decided to work on the second article that was giving me trouble. I cut and paste paragraph after paragraph of that article until I hit another 404 error. This was the paragraph that did it to me:

Some decide that the reason we do what we do is to ensure that we sustain our market. If we created stable products, they reason, people would no longer need to buy new computer software, and we would be out of business. This is a ludicrous position, of course: when you solve a problem, that problem changes. When you create a database that reliably stores a certain kind of data, there is suddenly a market for using that data in a way no one has ever used it before... and thus there is impetus to extend the original application, and there is still demand for a new release.

I decided to be a bit sneakier this time, however -- I then decided to cut and paste each sentence in the paragraph individually into the article. This is the sentence that triggered the 404:

When you create a database that reliably stores a certain kind of data, there is suddenly a market for using that data in a way no one has ever used it before... and thus there is impetus to extend the original application, and there is still demand for a new release.

Then I decided I would paste the first half of the sentence (up to the elipses) to see if that would work. That triggered the 404 error. So then I pasted in one word at a time, and I hit the 404 when I reached the word "that." But it can't be that, since it already appears in the !@#$% paragraph. Still, I decided to monkey around with the sentence structure again, and I replaced

When you create a database that reliably stores a certain kind of data, there is suddenly a market for using that data in a way no one has ever used it before... and thus there is impetus to extend the original application, and there is still demand for a new release.

with

Creating a database that reliably stores a certain kind of data also creates a market for using that data in a way no one has ever used it before... and thus there is impetus to extend the original application, and there is still demand for a new release.

The article updated just fine.

I have no idea what's going on.

Heine’s picture

*Sigh*, mod_security makes me want to bang my head against a wall..., the lying bastard.

Would be interesting to see what trips it this time? grant, perhaps?

mod_security is an Apache module that can be disabled in .htaccess with the line:

SecFilterEngine Off

If you can't use this, ask your host to use a less agressive setting.
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.

ubersoft’s picture

So mod_security thinks I'm trying to push through some kind of malicious code in my posts...

Geeze, that's annoying.

ubersoft’s picture

it doesn't look like the .htaccess entry helps. I'll have to talk to my admins...