why did you break htaccess for 4.7?

By t.a. barnhart on 13 Jun 2006 at 04:30 UTC

i have gone thru the forums & checked the handbook, and i'm not finding anything that helps.

the .htaccess file that came with 4.6.x worked just fine; i'd upload it with the rest of the files, enable clean url's and hey-nonny-presto.

with 4.7.2, i do the same thing, and diddly-squat. i've tried the various modifications, everythng short of the apache mods, but a) i have no access to that (few of us will) and b) if it worked before, why isn't it working now?

Comments

Just to piss you off.

binford2k commented 13 June 2006 at 05:17

Seriously, try a less inflammatory approach and I bet you'll get more help.

o that's right

t.a. barnhart commented 13 June 2006 at 05:49

thin-skinned is the rule here. as opposed to reading an extreme subject line and assuming, tongue-in-cheek. which it was. the rest of my post was fine. i'll call you when i need to be scolded like a 6-yr-old. in the meantime, ignore me.

We try really hard to keep

sepeck commented 13 June 2006 at 06:51

We try really hard to keep the sarcasm and extremism out of the forums here. As a result, many people simply won't answer questions phrased as you have done. Your response just adds fuel and reasons not to reward the behavior.

Oddly enough, the 14 sites I have seem to work just fine, so at this point I'll mark it down to user error and skip followups in this thread.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

Hmmm...

venkat-rk commented 13 June 2006 at 07:32

Except for the subject line (which is somewhat provocative), I found nothing extreme or offensive about the post. In fact, I felt it was the person who first responded who converted this into a kind of flame war by using offensive language and pouring scorn. Considering the unnecessary scorn, I think the response of the original poster was quite sober and in no way added fuel to the fire.

Well the first line was offensive.

sepeck commented 13 June 2006 at 15:07

As to the rest of the post, insufficient information beyond the assumption that it was Drupal developers that did this on purpose. As I know Drupal developers did NOT do this on purpose, then we are left with user error. No mention of the cleanurl check working/not working, no mention of what was in the Apache error logs....

As that inital premise of that statement is inflamitory and offensive to me as a contributor of the project. That first line 'assumes' that the folks who released 4.7.x series had nothing better to do than to go out of their way to 'break' this guys upgrade path. That's not true, accurate or even funny. As a result, I see no reason to reward such behavior with my free support.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

You are right. My initial

venkat-rk commented 13 June 2006 at 16:42

You are right. My initial reaction was also that he meant why had the drupal developers deliberately broken this. But that reaction evaporated when I read the rest of the post. I made it very clear to the original poster that I had installed several 4.7 sites and that the .htaccess issue was unlikely to be a drupal problem per se.

I guess we all look at things differently, but IMHO, you are being too sensitive in this situation. You know that I don't normally get into such discussions. I only chipped in was because I was amazed you took offence at just that one slightly provocative line and ignored all the rest of the post, not to mention the more offensive language the first replier used.

I do think there is a bit too much of lecturing on these forums whenever anyone posts something even slightly negative. As someone contributing to the drupal project in my own little way, that detracts from the overall drupal experience for me. I believe I am allowed to express that opinion courteously and that's what I have done now. Let this rest.

lots of htaccess probs

SparkyUK commented 13 June 2006 at 14:46

Actually, I - and many others if you read the forums - have had htaccess problems with 4.7.2.

and believe it or not, us users, even those who make errors, don't appreciate the sarcasm or extremism from developers.

That's strange because I

venkat-rk commented 13 June 2006 at 05:36

That's strange because I have installed several test sites from 4.7 beta versions onwards and never once had a problem with .htaccess.

It is possible that your hosting company has made changes to their server configuration that prevent clean urls from working. Please check with them.

i don't think the host is the problem

t.a. barnhart commented 13 June 2006 at 05:47

my 14 4.6 sites continue to run fine. that's what's so crazymaking about this.

Describe not working

heine commented 13 June 2006 at 09:37

if it worked before, why isn't it working now?

Can you provide more information? What do you mean with "isn't working now"? Did you run the clean url test? Can you check the Apache logs?
--
The Manual | Troubleshooting FAQ | Tips for posting | Make Backups! | Consider creating a Test site.

i did everything correctly

t.a. barnhart commented 13 June 2006 at 16:54

i ran the url test, of course, and it failed.
i searched the forums and tried the various suggestions - none worked (and i did not keep a log of these)

i can't modify apache permissions but that doesn't seem to be the real issue here since my 4.6.x sites work with clean url's

the only part not working is clean url's -- for 4.7.2 only. for 4.6.x, clean url's work fine.

.htaccess was not uploading

t.a. barnhart commented 13 June 2006 at 17:08

this was tricky to find since i don't have command line access to my host's root, or if i do, i'm not trained in that bit of arcane techiness (as is true for a vast number of Drupalists).

with 4.6.x, i would upload .htaccess just by dragging-and-dropping from Finder into Transmit. it worked. for some screwy reason, with 4.7.2, it did not work. Transmit was not set to show invisible files, but that should not have mattered.

i finally went to Direct Admin (the web interface used by my host) and, in "Upload files...." typed in the path to .htaccess (DA does not show invisible files). finally, .htaccess uploaded.

so, in conclusion: make sure you have a tool that shows invisible files at your server and find a way to transfer .htaccess successfully. (Transmit is still, imo, the best tool around, a perfect partner for bbedit & Mac.)

Thanks

heine commented 13 June 2006 at 17:21

Thanks for posting the resolution to your problem.

--
The Manual | Troubleshooting FAQ | Tips for posting | Make Backups! | Consider creating a Test site.

My clean URLs aren't working

llaslo commented 13 June 2006 at 17:09

in my 4.7.2 site either. I've got a 4.7 beta site and clean URLs work fine.

For the 4.7.2 site, I actually copied and pasted the virtual host info in the htaccess file for the 4.7 beta site. So, same server, same virtual host except for the URL/ path, but different clean URL results between 4.7 beta and 4.7.2.

RewriteBase

heine commented 13 June 2006 at 17:20

Did you adapt RewriteBase in .htaccess?
--
The Manual | Troubleshooting FAQ | Tips for posting | Make Backups! | Consider creating a Test site.

I don't have a RewriteBase

llaslo commented 13 June 2006 at 19:19

I don't have a RewriteBase line in the httpd.conf file for either of the virtual hosts.

The more I read the documentation for clean URLs, the more it seems like the first site -- the 4.7 beta site -- shouldn't be allowing clean URLs. But oddly, it is. I could post the details of each virtual host, but they're essentially mirror images, with the only exception being the directories.

Can you elaborate

heine commented 13 June 2006 at 19:34

Your configuration isn't clear for me from the two posts. Can you elaborate?