After updating the module to the latest version and redeploying the htaccess file, it contains a syntax error.
Steps te reproduce:
- Install version 2.4 of the module and deploy the htaccess file.
- Update htaccess to 2.5
- Deploy the htaccess file again
(I used Drush: drusk up; drush ht [profile])
Notice that the site throws an error 500.
The reason; line 11 contains +FollowSymLinks, which should be Options +FollowSymLink. I have not pinpointed the cause of this; perhaps saving the profile again would solve it. But just dropping this here to help others who might ruin into the same problem/
Comments
Comment #2
jibus commentedThis patch should do the trick, but you'll have to recreate your htaccess again.
Comment #3
neograph734I have hotfixed it for now, will try the patch in an hour or so. Thanks for the fast response!
Comment #4
neograph734That did not solve it..
Or did you mean create a new profile? I only redeployed it.
I just had another (better) look at my .htaccess file:
Aligning that with the template file:"
So it seems the
+FollowSymLinksis placed at the%%%prevent_txt%%%position.Almost like all values are shifted in the replacements... (I did notice that
$prevent_txt_rulesis only defined if$prevent_txt_configis TRUE, so there can be an undefined variable in the replacements. Could that be the cause?)Comment #5
neograph734Update, yup that did it. The undefined variable was skipped and the whole replacement array shifted.
Making sure that
$prevent_txt_rulesis always defined:Recreating the profile and deploying it made everything show up again.
UPDATE: Your patch is not required as that now results in
Options Options +FollowSymLinks.Comment #6
jibus commentedOk, i see now.
The value is not properly replaced in the default htaccess config.
The attached patch fixed this, but you'll have to recreate your profil (not very conveniant tough..).
Comment #7
jibus commentedReroll patch according to #5
Comment #8
neograph734@Jibus, did you upload the wrong file? They are identical ;)
Comment #9
jibus commentedWrong file. This patch should be ok
Comment #10
neograph734Yes, that seems to do it. It appeared I was able to re-deploy my old profile now without issues.
I'll check one other site to be sure, but I guess this did it.
Comment #11
neograph734Confirming this is fixed. I have a follow-up though... #2868596: Protect Core text files setting is not persistent.
Comment #13
jibus commentedThanks for confirming this. Committed against 7.x-2.x