[geeklog-cvs] geeklog-1.3/docs changes.html,1.14,1.15 history,1.112,1.113 install.html,1.15,1.16

Sun Jul 6 11:17:32 EDT 2003

Update of /usr/cvs/geeklog/geeklog-1.3/docs
In directory internal.geeklog.net:/tmp/cvs-serv14904

Modified Files:
	changes.html history install.html 
Log Message:
Updated documentation


Index: changes.html
===================================================================
RCS file: /usr/cvs/geeklog/geeklog-1.3/docs/changes.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** changes.html	28 Jun 2003 16:29:59 -0000	1.14
--- changes.html	6 Jul 2003 15:17:30 -0000	1.15
***************
*** 68,71 ****
--- 68,74 ----
      new password directly. Otherwise, you can simply ignore the email and your
      old password will remain valid.
+   <li>Topic access was not always checked properly. If Story Admins report
+     getting access denied messages after upgrading to 1.3.8, check your topic
+     permissions carefully.
    <li>The poll editor let you enter one answer too many (i.e. when the max.
      number of answers was set to 10 you could actually enter 11). Please check

Index: history
===================================================================
RCS file: /usr/cvs/geeklog/geeklog-1.3/docs/history,v
retrieving revision 1.112
retrieving revision 1.113
diff -C2 -d -r1.112 -r1.113
*** history	5 Jul 2003 22:40:26 -0000	1.112
--- history	6 Jul 2003 15:17:30 -0000	1.113
***************
*** 1,4 ****
--- 1,19 ----
  GeekLog History/Changes:
  
+ July 6, 2003 (1.3.8rc2)
+ ------------
+ 
+ - When failing to delete an image for a story (from the Admin's story editor),
+   only log this problem in the error.log but don't abort the script (reported
+   by Rob).
+ - When editing a story that used double quotes in the title, the title was cut
+   off after the first quote sign.
+ - Story Admins could edit stories in a topic they didn't have access to, if
+   they somehow found out the story id.
+ - When $_CONF['listdraftstories'] was enabled, moderation.php listed all stories
+   that had the "draft" flag set without checking for topic permissions (this
+   option was only introduced in 1.3.8rc1).
+ - For Story Admins, the Admin menu may have listed a greater number of stories
+   than the user actually had access to (didn't check for topic permissions).
  - Fixed "Google paging" on the Admin's list of stories when the current user
    didn't have access to all the topics (paging was only introduced in 1.3.8rc1).
***************
*** 12,18 ****
  - Changed the "getBent" block to test the real admin directory in case it has
    been renamed (bug #762881).
! - Don't save the privacy options when saving the user profile - since they are
!   part of the user's preferences and would be set to "off" that way ...
!   (reported by Dwight Trumbower).
  - Check the topic permissions when doing a search on stories and comments.
  - Check the topic permissions when displaying the new stories and comments in
--- 27,32 ----
  - Changed the "getBent" block to test the real admin directory in case it has
    been renamed (bug #762881).
! - Saving the user profile also saved the privacy options, setting them all to
!   "off" (reported by Dwight Trumbower).
  - Check the topic permissions when doing a search on stories and comments.
  - Check the topic permissions when displaying the new stories and comments in

Index: install.html
===================================================================
RCS file: /usr/cvs/geeklog/geeklog-1.3/docs/install.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -d -r1.15 -r1.16
*** install.html	5 Jul 2003 13:26:34 -0000	1.15
--- install.html	6 Jul 2003 15:17:30 -0000	1.16
***************
*** 139,143 ****
  			<li>Unpack the tarball *within* your web tree by running the following in your shell (this assumes you have ssh access and that you are working with the tarball <i>on the designated server </i>- this can be locally or hosted elsewhere):<br>
  				<br>
! 				<code>tar -zxvf geeklog-1.3.8rc1.tar.gz</code><br>
  				<br>
  				<b>FTP, Windows Users:</b> unpack the tarball on your <i>local computer</i> and upload the result to your designated server. Everything uploads as ASCII except the images.<br>
--- 139,143 ----
  			<li>Unpack the tarball *within* your web tree by running the following in your shell (this assumes you have ssh access and that you are working with the tarball <i>on the designated server </i>- this can be locally or hosted elsewhere):<br>
  				<br>
! 				<code>tar -zxvf geeklog-1.3.8rc2.tar.gz</code><br>
  				<br>
  				<b>FTP, Windows Users:</b> unpack the tarball on your <i>local computer</i> and upload the result to your designated server. Everything uploads as ASCII except the images.<br>
***************
*** 169,173 ****
  			</table>
  			<br>
! 			<li>Create the database you want Geeklog to reside in. If you are not familiar with using MySQL, you are urged to get <a href="http://www.phpmyadmin.net/" target="_blank">phpMyAdmin</a> and use it to create a new database. If you have no idea what the previous two sentences mean, contact your sysadmin for help.<br>
  				<br>
  			<li>Edit config.php with the appropriate settings for your server. For installation, this basically means "set your paths," as all other variables can be changed after a successful installation. The config.php file contains comments to help you out.<br><br>
--- 169,173 ----
  			</table>
  			<br>
! 			<li>Create the database you want Geeklog to reside in. If you are not familiar with using MySQL, you are urged to get <a href="http://www.phpmyadmin.net/">phpMyAdmin</a> and use it to create a new database. If you have no idea what the previous two sentences mean, contact your sysadmin for help.<br>
  				<br>
  			<li>Edit config.php with the appropriate settings for your server. For installation, this basically means "set your paths," as all other variables can be changed after a successful installation. The config.php file contains comments to help you out.<br><br>