I need to add three mandatory fields to the user information
You can create a separate table for this and add the sql for the table creation wherever it makes the most sense for you. Key that table on object_id. OR you could modify the default object creation code and add these as attributes of the user object. If you don't ever think you will have to add other attributes to the object on a production server after you deploy this would be the way to go.
text/html; charset=windows-1251 need be listed both in server response and in the HEAD section
For the head section, modify the default-master template. I'm not sure about the server response.
Are there any problems with PostgreSQL if I feed it characters in 128-255 code range
Make sure your postgres installation was created with the right charset. I don't know them offhand. Or are they all 8 bit nowadays?
Is it an OK workflow to modify the files on the development server, debug it there and then copy everything to the production one? If I'm developing alone, can I get away with not using CVS for some time?
I recommend going with CVS right from the beginning. You can tag your files when you push to production so if you find something that worked on development but is hosing production you can roll back.
If I modify the files that make log in, workspace, etc. in the core,
You always run that risk. Read
these:
-
https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=00036T&topic_id=11&topic=OpenACS
- http://www.cvshome.org/docs/manual/cvs_13.html#SEC104
- https://openacs.org/new-file-storage/download/cvs.html?version_id=140
- http://www.piskorski.com/cvs-conventions.html
for people's musings on this.
