[geeklog-cvs] geeklog-1.3/docs changes.html,1.24,1.25 config.html,1.34,1.35 history,1.224,1.225 install.html,1.29,1.30 support.html,1.10,1.11 theme.html,1.33,1.34 knownbugs,1.6,NONE todo,1.5,NONE

dhaun at iowaoutdoors.org dhaun at iowaoutdoors.org
Thu Aug 12 14:11:25 EDT 2004


Update of /var/cvs/geeklog-1.3/docs
In directory www:/tmp/cvs-serv23008

Modified Files:
	changes.html config.html history install.html support.html 
	theme.html 
Removed Files:
	knownbugs todo 
Log Message:
Some documentation updates ...


Index: install.html
===================================================================
RCS file: /var/cvs/geeklog-1.3/docs/install.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -C2 -d -r1.29 -r1.30
*** install.html	3 Aug 2004 10:57:08 -0000	1.29
--- install.html	12 Aug 2004 18:11:22 -0000	1.30
***************
*** 75,79 ****
  		<p>Before installing Geeklog for the first time, please make sure you have or know the following:</p>
  		<ol>
! 			<li>A web server running PHP 4.04 or higher 
  			<li>A web server running MySQL, with access to a database or the ability to create a database 
  			<li>The ability to create a new database in MySQL or access to an existing one 
--- 75,79 ----
  		<p>Before installing Geeklog for the first time, please make sure you have or know the following:</p>
  		<ol>
! 			<li>A web server running PHP 4.1.0 or higher 
  			<li>A web server running MySQL, with access to a database or the ability to create a database 
  			<li>The ability to create a new database in MySQL or access to an existing one 
***************
*** 140,144 ****
  			<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.9.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>
--- 140,144 ----
  			<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.10rc1.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>
***************
*** 152,155 ****
--- 152,157 ----
  				<br>
  				<code>chmod -R 775 logs/<br>
+ 					chmod -R 775 data/<br>
+ 					chmod -R 775 pdfs/<br>
  					chmod -R 775 public_html/backend/<br>
  					chmod -R 775 public_html/images/articles<br>

Index: changes.html
===================================================================
RCS file: /var/cvs/geeklog-1.3/docs/changes.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -C2 -d -r1.24 -r1.25
*** changes.html	15 Feb 2004 16:31:39 -0000	1.24
--- changes.html	12 Aug 2004 18:11:22 -0000	1.25
***************
*** 23,26 ****
--- 23,135 ----
  of files that have been changed since the last release.</p>
  
+ <h2><a name="changes1310">Geeklog 1.3.10</a></h2>
+ 
+ <!--
+ <h3>New Default Theme</h3>
+ 
+ <p>This release comes with a new default theme: We've chosen the Professional
+ theme, kindly provided by Victor B. Gonzales (of <a href="http://aeonserv.com">Aeonserv</a> fame). The theme has been modified slightly and is now fully HTML 4.01 and CSS compliant.</p>
+ 
+ <p>We've also decided to remove the old set of themes (Classic, Clean, Digital Monchrome, Gameserver, Smooth Blue, XSilver, Yahoo) from the distribution. They are now available as a separate tarball.</p>
+ -->
+ 
+ <h3>New Features</h3>
+ 
+ <ul>
+ <li>Story Archive feature: It is now possible to move stories to an "archive"
+     topic or have them deleted automatically at a given time.</li>
+ <li>PDF support: Stories can be converted into PDFs (requires installation
+     of third-party software - see config.php for details).</li>
+ <li>Customizable menu bar: The site's menu bar can now be configured in
+     config.php, i.e. you can choose which entries should be displayed there and
+     in which order. It's also possible to add custom entries by providing a
+     function in lib-custom.php.</li>
+ <li>Clickable links in text postings: URLs in non-HTML postings are now
+     recognized by Geeklog and displayed as clickable links.</li>
+ <li>Customizable welcome email: The email that is sent out to users
+     registering with your site is now fully customizable by providing the
+     text in a text files (/path/to/geeklog/data/welcome_email.txt).</li>
+ <li>Timezone hack: The popular "timezone hack" is now included. It lets you
+     set the site's timezone for when your server is located in another
+     timezone.</li>
+ </ul>
+ 
+ <h3>Other Improvements</h3>
+ 
+ <ul>
+ <li>Various changes have been made to improve the overall performance.</li>
+ <li>The calendar's week can now either start on a Sunday or a Monday.</li>
+ <li>The Static Pages plugin now has an option to display a printer-friendly
+     version of a static page.</li>
+ </ul>
+ 
+ <h4>Comments</h4>
+ 
+ <ul>
+ <li>The comment code has undergone major changes to improve performance and
+     add improvements like the ability to link to individual comments,
+     paging comments, etc.</li>
+ <li>Users can now report abusive comments to the site admin.</li>
+ <li>The site admin can get an email notification when a new comment is
+     posted (similar to the notification emails for new stories, links,
+     events, and users).</li>
+ <li>The IP addresses of comment posters are now tracked and can be looked up
+     directly by linking to a Whois service (or you can install Tom Willet's
+     <a href="http://sf.net/project/showfiles.php?group_id=68255&package_id=95743">NetTools</a>, which include a Whois function).</li>
+ </ul>
+ 
+ <h3>Bugfixes</h3>
+ 
+ <ul>
+ <li>Previewing and saving a story submission left the submitted story in the
+     submission queue, but did additionally save it as a new story.</li>
+ <li>Deleting an event from the personal calendar didn't work.</li>
+ <li>Old userphotos weren't removed when the new photo had a different file
+     type (e.g. when changing from a .gif to a .jpg).</li>
+ <li>Scaling images didn't work when the image exceeded the max. height but
+     not the max. width.</li>
+ <li>Keeping an unscaled image wasn't possible when using gdlib to rescale
+     images.</li>
+ </ul>
+ 
+ <p>This release contains various improvements provided by the Geeklog community
+ (see the <tt>docs/history</tt> file for proper credits). Thank you!</p>
+ 
+ 
+ <h2><a name="changes139sr1">Geeklog 1.3.9sr1</a></h2>
+ <p>This release addresses the following security issues:</p>
+ 
+ <ol>
+ <li>It was possible to post anonymous comments, even when anonymous comment
+     posting had been switched off in config.php.<br>
+     This bug was apparently exploited by spammers to send hundreds of spam
+     posts to certain Geeklog sites.</li>
+ <li>Added additional speed limit checks for comments and submissions.</li>
+ <li>If none of the topics were visible for anonymous users, the site's index
+     page may still have displayed some stories for anonymous users, depending
+     on the stories' permissions.</li>
+ <li>Users still got Daily Digest emails for topics from which they had been
+     removed (bug #178).</li>
+ <li>It was possible to subscribe to the Daily Digest for all topics, even if
+     the user did not have access to certain topics.</li>
+ <li>Comments to stories were sometimes listed in a user's profile, even if the
+     user viewing the profile didn't have permissions to access the story the
+     comments belonged to.</li>
+ </ol>
+ 
+ <h3>Other fixes</h3>
+ <ul>
+ <li>Fixed an SQL error in <code>COM_showTopics</code> if users excluded topics
+     from their preferences.</li>
+ <li>Fixed sporadic "Duplicate entry '...' for key 1." messages in error.log,
+     caused by the handling of pseudo-session ids for anonymous users.</li>
+ <li>Fixed incorrect author names in Daily Digest (bug #207).</li>
+ <li>The <code>plugin_profileblocksedit_<i>plugin-name</i> Plugin API function
+     wasn't working due to a missing piece of code in usersettings.php.</li>
+ <li><code>COM_extractLinks</code> will now ignore anchor tags that do not
+     contain "<code>href</code>" (bug #183).</li>
+ </ul>
+ 
+ 
  <h2><a name="changes139">Geeklog 1.3.9</a></h2>
  

Index: theme.html
===================================================================
RCS file: /var/cvs/geeklog-1.3/docs/theme.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -C2 -d -r1.33 -r1.34
*** theme.html	31 Jul 2004 03:30:32 -0000	1.33
--- theme.html	12 Aug 2004 18:11:22 -0000	1.34
***************
*** 150,159 ****
  <h2><a name="changes">Theme changes in Geeklog 1.3.10</a></h2>
  
  <ul>
! <li>Added two new templates for the new story archive feature. This allows you to theme olderstories differently. By default Geeklog 1.3.10 ships with these template files not themed and the same as a standard story. The new template files are <ul><li>archivestorytext.thtml<li>archivestorybodytext.thtml</li></ul></li>
  </ul>
  
  
! <h2><a name="changes">Theme changes in Geeklog 1.3.9</a></h2>
  
  <ul>
--- 150,163 ----
  <h2><a name="changes">Theme changes in Geeklog 1.3.10</a></h2>
  
+ <p>General note: To upgrade your custom theme for use with Geeklog 1.3.10, you can simply copy over any new template files from the Geeklog default theme.</p>
+ 
  <ul>
! <li>Added two new templates for the new story archive feature. This allows you to theme olderstories differently. By default Geeklog 1.3.10 ships with these template files not themed and the same as a standard story. The new template files are <ul><li>archivestorytext.thtml</li><li>archivestorybodytext.thtml</li></ul></li>
! <li><tt>admin/mail/mailform.thtml</tt> has been changed to look slightly less ugly ...</li>
! <li>Due to changes in the comment engine, it is recommended that you copy over all the comment template files from the comment directory (<tt>reportcomment.thtml</tt> is actually a new file).</li>
  </ul>
  
  
! <h2><a name="changes139">Theme changes in Geeklog 1.3.9</a></h2>
  
  <ul>

Index: config.html
===================================================================
RCS file: /var/cvs/geeklog-1.3/docs/config.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -C2 -d -r1.34 -r1.35
*** config.html	8 Aug 2004 17:00:09 -0000	1.34
--- config.html	12 Aug 2004 18:11:22 -0000	1.35
***************
*** 93,96 ****
--- 93,99 ----
      <td valign="top">Base path with "/backups/" suffix</td>
      <td valign="top">location where mysqldump (see above) will store database backups</td></tr>
+ <tr><td valign="top"><a name="desc_path_data">path_data</a></td>
+     <td valign="top">/path/to/geeklog/data/</td>
+     <td valign="top">File system path for the data directory, used e.g. for the user batch add feature</td></tr>
  </table>
  
***************
*** 569,573 ****
    <td valign="top"><i>not set</i></td>
    <td valign="top">The IP addresses of comment posters are logged and displayed for admin users. When this variable is set to point to a service that can do IP address lookups, it's possible to lookup the owner of an IP address by clicking on it, making it easier to report missuse to ISPs, etc.<br>
! <code>$_CONF['ip_lookup']</code> should hold the complete URL to the lookup service, with a '<code>*</code>' marking the place where the IP address should go. It's also possible to use Tom Willet's Nettools package, in wich case the correct setting would be <code>$_CONF['ip_lookup'] = $_CONF['site_url'] . '/nettools/domain=*';</code></td></tr>
  </table>
  
--- 572,576 ----
    <td valign="top"><i>not set</i></td>
    <td valign="top">The IP addresses of comment posters are logged and displayed for admin users. When this variable is set to point to a service that can do IP address lookups, it's possible to lookup the owner of an IP address by clicking on it, making it easier to report missuse to ISPs, etc.<br>
! <code>$_CONF['ip_lookup']</code> should hold the complete URL to the lookup service, with a '<code>*</code>' marking the place where the IP address should go. It's also possible to use Tom Willet's <a href="http://sf.net/project/showfiles.php?group_id=68255&package_id=95743">NetTools</a> package, in which case the correct setting would be <code>$_CONF['ip_lookup'] = $_CONF['site_url'] . '/nettools/domain=*';</code></td></tr>
  </table>
  

--- knownbugs DELETED ---

--- todo DELETED ---

Index: support.html
===================================================================
RCS file: /var/cvs/geeklog-1.3/docs/support.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** support.html	15 Feb 2004 16:31:40 -0000	1.10
--- support.html	12 Aug 2004 18:11:22 -0000	1.11
***************
*** 16,61 ****
  </table>
  
! <h1>Support</h1>
  
! <ul>
!   <li><a href="http://www.geeklog.net/">Webpage</a>
!     - The Geeklog website is the best place for the latest news and updates</li>
!   <li><a href="http://project.geeklog.net/tracker/?group_id=6&atid=105">Bug reports</a>
!     - Submit bug reports on our project site. Please remember to search the bugs so you don't post a duplicate.</li>
!   <li><a href="http://lists.geeklog.net/listinfo/">Mailing lists</a>
!     - Join the <b>geeklog-users</b> mailing list, and join in the discussion.
!       Additional mailing lists exist for specific Geeklog-related topics.</li>
!   <li><a href="irc://irc.freenode.net/geeklog">IRC</a>
!     - Meet the developers and other Geeklog users on IRC (server: 
!       irc.freenode.net, channel #geeklog)
!   <li><a href="http://project.geeklog.net/tracker/?group_id&atid=107">Patches</a>
!     - Please submit patches on the project site. </li>
!   <li>General Help - A better place for general "I can't do it!" help is the <a 
!     href="http://lists.geeklog.net/listinfo/geeklog-users">mailing list</a>. Stuff 
!     that may be of more general interest is welcome here; but you will probably 
!     get better help on the lists.</li>
!   <li><a href="http://www.geeklog.net/submit.php?type=link">Link submissions</a>
!     - Use "<a href="http://www.geeklog.net/submit.php?type=link">Add A Link</a>" to tell us about your new site running GeekLog.</li>
!   <li><a href="http://www.geeklog.net/forum/">Story submissions</a>
!     - Use the <a href="http://www.geeklog.net/forum/">Forum</a> to tell us your
!       ideas for the GeekLog site and questions.<br>
!       <strong>DO NOT</strong> use this for bug reports. Use <a
!       href="http://project.geeklog.net/">our project site</a> for bug
!       reports.</li>
!   <li><a href="http://project.geeklog.net/tracker/?group_id=6&atid=108">Feature requests</a>
!     - Where to send feature requests depends a bit on what the request is. In 
!       general, the mailing list is a decent place, and if it is something 
!       significant, you may want to post it in the <a href="http://www.geeklog.net/forum/">Forum</a> or send it in as a <a href="http://www.geeklog.net/submit.php">story submission</a>. You may 
!       also want to go over to our <a href="http://project.geeklog.net/">project site</a> and submit it as a <a href="http://project.geeklog.net/tracker/?group_id=6&atid=108">Feature Request</a>, so we can have it 
!       filed and we can track it easily.</li>
!   <li><strong>Security issues:</strong> Should you need to report any security
!       issues with Geeklog, please do so at <a href="mailto:geeklog-security at lists.geeklog.net">geeklog-security at lists.geeklog.net</a>. 
! </ul>
  
! <p><strong>Please note:</strong> There are still some bug reports and feature
! requests left over on our old SourceForge site. However, new new bug reports
! and feature requests should <em>only</em> be submitted on the <a
! href="http://project.geeklog.net/">Geeklog Project Website</a>. Thank you.</p>
  
  
  <h2>Staying up to date</h2>
--- 16,56 ----
  </table>
  
! <h1>Support options</h1>
  
! <h2>Documentation</h2>
  
! <p>The very documentation you're currently reading includes information about <a href="install.html">installing</a> and <a href="install.html#upgrade">upgrading</a> Geeklog, and it also lists <a href="install.html#installprob">common problems</a> and their solution. Detailed information about the <a href="config.html">config.php</a> configuration file is also available, as is information about <a href="theme.html">themes</a>.</p>
! 
! <p>Further information about using Geeklog can be found in our ever-expanding <a href="http://wiki.geeklog.net/">Documentation Wiki</a>, provided by the Geeklog community.</p>
  
+ <p>The most frequently asked questions are covered in our <a href="http://www.geeklog.net/faqman/">FAQ</a> - see if you can find the answer to your question there.</p>
+ 
+ <p>Still can't find what you're looking for? Try <a href="http://www.geeklog.net/search.php">searching</a> the Geeklog Homepage. Chances are that someone already had the same question or problem and it has been covered there before.<br>
+ <strong>Hint:</strong> If you're trying to resolve an error message you're getting, try searching for that error message first.</p>
+ 
+ <h2>Interactive Help</h2>
+ 
+ <p>The best place to ask your questions are the <a href="http://www.geeklog.net/forum/">forums</a> on the Geeklog Homepage. Many Geeklog users frequent the forums, so you'll usually get a quick response there.</p>
+ 
+ <p>If you prefer email, there are also several <a href="http://lists.geeklog.net/listinfo/">mailing lists</a> that you can use. Questions regarding installing and running Geeklog are best posted on the <a href="http://lists.geeklog.net/listinfo/geeklog-users">geeklog-users</a> mailing list.<br>
+ <strong>Note:</strong> Please note that due to the ever-increasing amount of spam, you have to subscribe to the mailing lists before you can post there.</p>
+ 
+ <p>Want to meet the Geeklog developers and other Geeklog users? Join us on <a href="irc://irc.freenode.net/geeklog">IRC</a>: channel #geeklog on irc.freenode.net.<br>
+ <strong>Note:</strong> The channel is often very quiet. It's usually best to "just ask your question" and be willing to wait a bit for a response.</p>
+ 
+ <h2>Other Options</h2>
+ 
+ <p>Found a bug? <a href="http://project.geeklog.net/tracker/?group_id=6&atid=105">Submit a bug report</a> on our project website. There's also a tracker for <a href="http://project.geeklog.net/tracker/?group_id=6&atid=108">feature requests</a>.<br>
+ <strong>Note:</strong> Before submitting a new bug report or feature request, please do a search first (on the project site as well as on the Geeklog Homepage) to make sure it hasn't been covered before. Thanks.</p>
+ 
+ <p>Want to develop a plugin or some other add-on? Read the <a href="http://gplugs.sourceforge.net/pluginman/">Plugins Developer's Guide</a> and join the <a href="http://lists.geeklog.net/listinfo/geeklog-modules">geeklog-modules</a> and <a href="http://lists.geeklog.net/listinfo/geeklog-devtalk">geeklog-devtalk</a> mailing lists.</p>
+ 
+ <p>Want to help in Geeklog development? See <a href="http://www.geeklog.net/article.php/20030803155454822">this story</a> for suggestions on how to get started. And if you already made a modification, why not <a href="http://project.geeklog.net/tracker/?atid=107&group_id=6">submit a patch</a>?
+ 
+ <h2>Security Issues</h2>
+ 
+ <p>The Geeklog developers take security very seriously. Should you need to report a security issue with Geeklog, please email details to <a href="mailto:geeklog-security at lists.geeklog.net">geeklog-security at lists.geeklog.net</a>. Thank you.</p>
+ 
+ <p>Also see our <a href="http://www.geeklog.net/staticpages/index.php/GeeklogSecurity">Security statement</a> on the Geeklog Homepage.</p>
  
  <h2>Staying up to date</h2>
***************
*** 70,79 ****
  see if your install is up to date.</p>
  
- 
  <h2>International Support</h2>
  
! <p><img src="images/germany.gif" width="16" height="12" align="middle"
! alt=""> <a href="http://geeklog.info/">geeklog.info</a> - Geeklog-Support in 
! Deutsch</p>
  
  <table border="0" width="100%" class="footer">
--- 65,75 ----
  see if your install is up to date.</p>
  
  <h2>International Support</h2>
  
! <p><img src="images/germany.gif" width="16" height="12" border="1" align="middle" alt=""> <a href="http://geeklog.info/">geeklog.info</a> - Geeklog-Support in Deutsch</p>
! 
! <p><img src="images/poland.gif" width="16" height="12" border="1" align="middle" alt=""> <a href="http://www.geeklog.now.pl/">GeeklogPolska</a>  - Geeklog support po Polsku</p>
! 
! <p><img src="images/japan.gif" width="16" height="12" border="1" align="middle" alt=""> <a href="http://geek.ecofirm.com/">Geeklog Japanese</a> - Geeklog-Support in Japanese</p>
  
  <table border="0" width="100%" class="footer">

Index: history
===================================================================
RCS file: /var/cvs/geeklog-1.3/docs/history,v
retrieving revision 1.224
retrieving revision 1.225
diff -C2 -d -r1.224 -r1.225
*** history	11 Aug 2004 21:22:17 -0000	1.224
--- history	12 Aug 2004 18:11:22 -0000	1.225
***************
*** 4,7 ****
--- 4,9 ----
  ------------
  
+ - Replaced 'ppmtojpeg' with 'pnmtojpeg' when using NetPBM for scaling
+   uploaded JPEG images (bug #257) [Dirk]
  - Added a check (and a warning message) for PHP 4.1.0 to the install script,
    as that is our new minimum requirement [Dirk]




More information about the geeklog-cvs mailing list