This question about Installation of Foswiki: Asked

Htpasswd CharacterEncoding

According to System/UpgradeGuide#Copy_the_data_using_61tools_47bulk_copy.pl_61

If you want to run Foswiki 2.0 in parallel with Foswiki 1.1.9, you can do this safely if the following conditions are met:
  • The RCS store is used on both installations. (RCSWrap and RCSLite are compatible.
  • The 2.0 {Store}{Encoding} must match the 1.1.9 {Site}{CharSet}
  • The 2.0 {AccessControlACL}{EnableDeprecatedEmptyDeny} setting should be enabled.
  • The 2.0 {Htpasswd}{CharacterEncoding} should match your 1.1.9 {Site}{CharSet}
  • The 2.0 {RCS}{TabularChangeFormat} should be enabled for compatible .changes file format.

Shouldn't this line
The 2.0 {Htpasswd}{CharacterEncoding} should match your 1.1.9 {Site}{CharSet}

actually say
The 2.0 {Htpasswd}{CharacterEncoding} should match your 1.1.9 {Htpasswd}{CharacterEncoding}

i.e. both apache-md5 (not 2.0 {Htpasswd}{CharacterEncoding} set to iso-8859-1).

-- VickiBrown - 19 Sep 2015

1.1.9 doesn't have {Htpasswd}{CharacterEncoding}. The ability to separate htpasswd encoding from the {Site}{CharSet} was added to 2.0. This setting handles encoding of the WikiName and email addresses in the .htpasswd file.

Note however that unless you have users registering with high characters in either their wikinames or email addresses, you don't need to set the encoding. On we had only one address with a high character and manually fixed it.

-- GeorgeClark - 19 Sep 2015

QuestionForm edit

Subject Installation of Foswiki
Status Asked
Related Topics
Topic revision: r2 - 19 Sep 2015, GeorgeClark
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy