|
|
| Line 40: |
Line 40: |
| | You don't need to understand PHP code to see that this uses the template files profile.thtml, commentrow.thtml, and storyrow.thtml. The first line also indicates that these are taken from the users directory within the theme's layout directory. | | You don't need to understand PHP code to see that this uses the template files profile.thtml, commentrow.thtml, and storyrow.thtml. The first line also indicates that these are taken from the users directory within the theme's layout directory. |
| | | | |
| − | An [[incomplete list of variables]] that can be used in templates files is also included. | + | An [http://www.geeklog.net/docs/themevars.html incomplete list of variables] that can be used in templates files is also included. |
| | | | |
| | | | |
| Line 63: |
Line 63: |
| | '''Polls''': To use multi-colored bars in the graphical display of poll results, you can use the {answer_counter} and {answer_odd} variables in the pollbooth/pollvotes_bar.thtml template file. {answer_counter} will be replaced with a running number for each answer, hence bar{answer_counter}.gif would result in bar1.gif, bar2.gif, etc. Giving each of those GIFs a different color would give you a different color for each answer. | | '''Polls''': To use multi-colored bars in the graphical display of poll results, you can use the {answer_counter} and {answer_odd} variables in the pollbooth/pollvotes_bar.thtml template file. {answer_counter} will be replaced with a running number for each answer, hence bar{answer_counter}.gif would result in bar1.gif, bar2.gif, etc. Giving each of those GIFs a different color would give you a different color for each answer. |
| | {answer_odd} will alternate between 0 and 1 for every answer, hence bar{answer_odd}.gif will result in bar0.gif for the first, third, fifth, etc. answer and bar1.gif for the second, fourth, etc. answer. | | {answer_odd} will alternate between 0 and 1 for every answer, hence bar{answer_odd}.gif will result in bar0.gif for the first, third, fifth, etc. answer and bar1.gif for the second, fourth, etc. answer. |
| − |
| |
| − | == Theme changes in Geeklog 1.3.9 ==
| |
| − |
| |
| − | *In header.thtml, you can now use the new variable {allowed_menu_elements} as an alternative to using {menu_elements}. The new variable takes the $_CONF['XXXloginrequired'] settings into account, i.e. it will only list those entries that the current user has access to.
| |
| − | *The admin/syndication directory, containing feededitor.thtml, listfeeds.thtml, listitem.thtml, and selecttype.thtml has been added.
| |
| − | *Template files comment/comment.thtml and comment/thread.thtml have been added and comment/startcomment.thtml has been changed to implement template-driven comments.
| |
| − | Please note that comment/comment.thtml was changed again in Geeklog 1.3.9rc2.
| |
| − | *A {link_edit} variable has been added to links/linkdetails.thtml so that admins can edit links directly from the links section.
| |
| − | *An "edit" icon has been added: images/edit.gif. The new variable {edit_icon} can be used as an alternative to {edit_link} in the story template files and in links/linkdetails.thtml.
| |
| − | *In the calendar/calendar.thtml file, the "mode" parameter has been added to the << and >> buttons, so that users stay in their personal calendar when browsing through months.
| |
| − | *A new file, admin/group/groupmembers.thtml, has been added and admin/group/listitem.thtml has been changed for the new alternative option to add users to groups.
| |
| − | *A new file, admin/block/listside.thtml, has been added and admin/block/listitem.thtml and admin/block/listblocks.thtml have been changed for the enhanced block list.
| |
| − | *A {google_paging} variable has been added to admin/link/linklist.thtml. Also added a column number to linklist.thtml and admin/link/listitem.thtml.
| |
| − | *All template files where the user can enter a URL are now using a new variable, {max_url_length}, instead of a hard-coded number of characters for the max. length of the URL. Files affected: admin/block/blockeditor.thtml, admin/event/eventeditor.thtml, admin/link/linkeditor.thtml, admin/topic/topiceditor.thtml, submit/submitevent.thtml, submit/submitlink.thtml.
| |
| − | *The hard-coded has been removed from the {welcome_msg} variable. The blank was then added to the header.thtml of the Classic, XSilver, and Yahoo themes (the other themes either look fine without it or didn't use {welcome_msg} in the first place).
| |
| − | *An extra table has been removed from the users/profile.thtml file of the XSilver theme so that the username now lines up properly with the other entries.
| |
| − |
| |
| − | == Theme changes in Geeklog 1.3.8 ==
| |
| − |
| |
| − | Theme changes in Geeklog 1.3.8 were mostly aimed at moving as much of the hard-coded HTML into template files as possible. Other changes were made to give theme authors better control over the layout and a small portion of changes were done to incorporate new Geeklog features.
| |
| − |
| |
| − |
| |
| − | === New template files ===
| |
| − |
| |
| − | This is a list of the new files. You can safely copy these over from one of the standard themes that ship with Geeklog (most of these files contain HTML that was previously hard-coded into Geeklog).
| |
| − |
| |
| − | adminoption_off.thtml<br/>
| |
| − | loginform.thtml<br/>
| |
| − | topicoption.thtml<br/>
| |
| − | topicoption_off.thtml<br/>
| |
| − | useroption_off.thtml<br/>
| |
| − | admin/database/listbackups.thtml<br/>
| |
| − | admin/database/listitem.thtml<br/>
| |
| − | admin/user/edituser.thtml<br/>
| |
| − | admin/user/plainlist.thtml<br/>
| |
| − | comment/commentbar.thtml<br/>
| |
| − | comment/startcomment.thtml<br/>
| |
| − | pollbooth/pollanswer.thtml<br/>
| |
| − | pollbooth/pollblock.thtml<br/>
| |
| − | pollbooth/pollcomments.thtml<br/>
| |
| − | pollbooth/pollresult.thtml<br/>
| |
| − | pollbooth/pollvotes_bar.thtml<br/>
| |
| − | pollbooth/pollvotes_num.thtml<br/>
| |
| − | preferences/boxesblock.thtml<br/>
| |
| − | preferences/commentblock.thtml<br/>
| |
| − | preferences/deleteaccount.thtml<br/>
| |
| − | preferences/digestblock.thtml<br/>
| |
| − | preferences/displayblock.thtml<br/>
| |
| − | preferences/displayprefs.thtml<br/>
| |
| − | preferences/excludeblock.thtml<br/>
| |
| − | preferences/language.thtml<br/>
| |
| − | preferences/privacyblock.thtml<br/>
| |
| − | preferences/profile.thtml<br/>
| |
| − | preferences/theme.thtml<br/>
| |
| − | preferences/username.thtml<br/>
| |
| − | preferences/userphoto.thtml<br/>
| |
| − | search/resultauthdatehits.thtml<br/>
| |
| − | search/resultrowenhanced.thtml<br/>
| |
| − | search/resultsummary.thtml<br/>
| |
| − | search/resulttitle.thtml<br/>
| |
| − | users/newpassword.thtml<br/>
| |
| − |
| |
| − | Note: preferences and admin/database are new directores.
| |
| − |
| |
| − |
| |
| − | === Changed / updated template files ===
| |
| − |
| |
| − | These file have changed since Geeklog 1.3.7, i.e. they may contain new variables, table columns, etc. If you haven't changed these files in your existing theme, it is probably best to simply copy them over from one of the themes that ship with Geeklog (with the exception of style.css and header.thtml, see below).
| |
| − |
| |
| − | style.css (see below)<br/>
| |
| − | header.thtml (see below)<br/>
| |
| − | admin/block/blockeditor.thtml<br/>
| |
| − | admin/block/listblocks.thtml<br/>
| |
| − | admin/block/listitem.thtml<br/>
| |
| − | admin/event/eventeditor.thtml<br/>
| |
| − | admin/event/eventlist.thtml<br/>
| |
| − | admin/event/listitem.thtml<br/>
| |
| − | admin/group/grouplist.thtml<br/>
| |
| − | admin/group/listitem.thtml<br/>
| |
| − | admin/story/liststories.thtml<br/>
| |
| − | admin/topic/listitem.thtml<br/>
| |
| − | admin/topic/topiceditor.thtml<br/>
| |
| − | admin/topic/topiclist.thtml<br/>
| |
| − | calendar/editpersonalevent.thtml<br/>
| |
| − | calendar/eventdetails.thtml<br/>
| |
| − | search/searchform.thtml<br/>
| |
| − | search/searchresults.thtml<br/>
| |
| − | submit/submitevent.thtml<br/>
| |
| − | users/getpasswordform.thtml<br/>
| |
| − |
| |
| − | In style.css, four classes have been added that are used in the new search code of Geeklog 1.3.8. Instead of copying over the entire file, you will probably only want to copy over the code for those four classes: searchAuth, searchDate, searchHits, highlight.
| |
| − |
| |
| − | If the header.thtml of your theme is using the {menu_elements} variable, then you do not need to make any changes to it. If it is not using that variable, then you will need to make one change to it. In that case, search your header.thtml for the link to the story submission form, i.e. something like
| |
| − |
| |
| − | <a href="{site_url}/submit.php?type=story">
| |
| − |
| |
| − | and change it to read
| |
| − |
| |
| − | <a href="{site_url}/submit.php?type=story{current_topic}">
| |
| − |
| |
| − |
| |
| − | === Removed template files ===
| |
| − |
| |
| − | If you have a file named commentheader.thtml in your theme directory, you can safely remove it. It isn't used at all.
| |
| − |
| |
| − |
| |
| − | == Theme changes in Geeklog 1.3.7 ==
| |
| − |
| |
| − | Please note that all the following changes are optional. Themes made for Geeklog 1.3.6 will work just fine with Geeklog 1.3.7 - no changes are necessary.
| |
| − |
| |
| − |
| |
| − | === New features and improvements ===
| |
| − |
| |
| − | *Theme-based topic icons are now supported by setting $_THEME_URL in the theme's functions.php file. The variable should point to a directory that has the same hierarchy as Geeklog's images directory (note that the path to topic images is stored relative to Geeklog's public_html directory).
| |
| − | Example: $_THEME_URL = $_CONF['layout_url'];
| |
| − | *The $_BLOCK_TEMPLATE "hack" can now be applied to the What's Related and Story Options blocks, as well. Use whats_related_block and story_options_block as the block names.
| |
| − | *The What's Related and Story Options blocks are now available as separate variables using {whats_related} and {story_options}, respectively (the {whats_related_story_options} variable for both blocks is still available).
| |
| − | *Several new variables can now be used in the story templates, e.g. {contributedby_fullname} for the full name of a story author and {contributedby_photo} for his/her user photo.
| |
| − | *When the new config variable $_CONF['showfirstasfeatured'] is set to 1, then the first story on every page is rendered using the template files for featured stories, even when the story is not marked as featured.
| |
| − |
| |
| − | === Other changes ===
| |
| − |
| |
| − | *The template file admin/plugins/installform.thtml has been removed since it isn't used any more.
| |
| − | *Two new optional template files, admin/plugins/newpluginlist.thtml and admin/plugins/newlistitem.thml, have been added to support formatting of the list of plugins which haven't been installed yet. If these files do not exist, hard-coded HTML is used to present the list.
| |
| − | *The template file admin/link/listitem.thtml has been changed so that all the links are clickable.
| |
| − | *COM_pollResults() doesn't use the side block templates any more when called from pollbooth.php. Therefore, you can now use different layouts whether the poll results are displayed in a side block or on the separate poll results and comments page.
| |
| − | *Removed the Normal / Archive / Refreshing drop down menus from the admin story and poll editors of the themes that ship with Geeklog. The setting of this dropdown isn't used in Geeklog anyway and has just confused users in the past ... (files admin/story/storyeditor.thtml and admin/poll/polleditor.thtml)
| |
| − |
| |
| − | == Theme changes in Geeklog 1.3.6 ==
| |
| − |
| |
| − | There have been a lot of changes in the themes for 1.3.6 to get rid of the last pieces of hard-coded english texts so as to make localisation easier. Most of these changes have been made in the Admin editors (admin directory) and the calendar (calendar directory). If you created your own theme for an earlier version of Geeklog, we recommend that you copy over these two directories from one of the themes that come with Geeklog (choose one that is similar to your own theme or which it was originally based on). It seems like most Geeklog themes didn't change these files anyway, so this shouldn't be too much of a hassle ...
| |
| − |
| |
| − |
| |
| − | === Other changes ===
| |
| − |
| |
| − | *The template file admin/mail/mailform.thtml has been added. This form for sending emails to other users of the site was previously hard-coded into Geeklog.
| |
| − | ;If you followed the above advice and copied over the admin directory to your theme, you got this file already.
| |
| − | *Two new files menuitem_last.thtml and menuitem_none.thtml have been added to give theme authors better control over the items in menu bars ({menu_elements} and {plg_menu_elements} variables in header.thtml). The template file menuitem.thtml is now used to render the first and any following menu items - with the exception of the last menu item, which is rendered using menuitem_last.thtml. If there are no menu elements for a menu bar, menuitem_none.thtml is used.
| |
| − | *New files have been added and the existing files have been changed for the links section (links directory). Again, we recommend to just copy over those files from one of the themes that ship with Geeklog.
| |
| − | The new files are: categoryactivecol.thtml, categorycol.thtml, categorynavigation.thtml, categoryrow.thtml, pagenavigation.thtml
| |
| − | *The user profile has been extended to include a list of the last 10 stories as well as the total numbers of stories and comments posted by that user. Have a look at the file users/profile.thtml to see the changes or just copy that file over from one of the themes that ship with Geeklog. You should also copy over the file users/storyrow.thtml which describes the block for the last 1o stories.
| |
| − | *The Classic theme has been updated to have an "Edit" link (for StoryAdmins) in every story now.
| |
| − | Files changed: storybodytext.thtml, featuredstorybodytext.thtml
| |
| − | *In the Classic and Digital Monochrome themes the "contact" link now points to the form to send an email to the admin user instead of using a mailto: link with the site's email address from config.php.
| |
| − |
| |
| − | === CSS changes ===
| |
| − |
| |
| − | *The underscore '_' is not a valid character in CSS. Therefore, some class names used by the Geeklog calendar have been changed to use the dash '-' instead. You may need to change your stylesheet accordingly.
| |
| − | Names that changed: cal-oldday, cal-today, cal-futureday, cal-nullday, weekview-curday, weekview-offday
| |
| − | *A new class named pagenav can be used to format the paged navigation.
| |
| − | Please note that this change was made after the release of Geeklog 1.3.6rc1 and affects the use of the paged navigation in admin/user/userslist.thtml and links/links.thtml: In 1.3.6rc1, the navigation was wrapped in <p> tags in those files. As of Geeklog 1.3.6 however, the function producing the navigation will wrap it in a <div> automatically.
| |
| − |
| |
| − | '''Note''': Theme authors are encouraged to specify a character set in the header.thtml of their themes like this:
| |
| − |
| |
| − | <meta http-equiv="Content-Type" content="text/html; charset={charset}">
| |
| − |
| |
| − | Geeklog will replace the {charset} variable with the proper character set based on the currently used language file. Also make sure that you put the above line before the <title> tag in the <head> section of your header.thtml file.
| |
Creating a theme for Geeklog is easy and quite fast. If you can manipulate HTML files then you can create a theme! There's no need to learn PHP.
First, copy an existing theme that is most similar to what you want to implement (if one exists). If what you will do is radically different (and we hope so!) then copying any one will do. Copy the existing theme to the name you want your theme to have (please, no spaces in the theme name):
cp -R /path/to/geeklog/public_html/layout/Yahoo /path/to/geeklog/public_html/layout/My_Theme_Name_No_Spaces
Now edit the templates to suit your needs. Keep in mind that templates, generally are partial HTML files. The directory you just created holds ALL templates Geeklog needs but you will only need to modify a small few to make a huge impact on the look.
When rendering a theme, Geeklog starts with header.thtml which builds the site's header and then goes on to include the left column of blocks (look for the variable {left_blocks} and the leftblocks.thtml file). The middle part of a site consists of the stories which are built using the storytext.thtml and storybodytext.thtml (for normal stories) and featuredstorytext.thtml and featuredstorybodytext.thtml (for featured stories) template files. The footer.thtml file then builds the right column of blocks (variable {right_blocks}, file right_blocks.thtml) and the site's footer. Blocks themselves consist of the blockheader.thtml and blockfooter.thtml files.
The above only described how Geeklog's main page and stories are rendered. More templates exist for the various editors and lists you will see in Geeklog, as well as for the calendar and almost every other part of Geeklog.
There is currently no complete list available that explains which template file is used for which part of Geeklog. However, in most cases the use should be obvious when you have a look at the file and directory names in your theme's layout directory. If you're unsure which template file is used to render a certain part of Geeklog, have a look at the URL. You will notice the name of a PHP file there, e.g. the users.php file when you view a user's profile. Open that file and search for '.thtml'. For the profile you will find these lines (in function userprofile()):
You don't need to understand PHP code to see that this uses the template files profile.thtml, commentrow.thtml, and storyrow.thtml. The first line also indicates that these are taken from the users directory within the theme's layout directory.
After you have edited your themes, you are now ready to test it out. Simply go to http://mygeeklogsite/users.php?mode=preferences - in the theme drop-down select your newly created theme (note the name of your theme is the same name as the directory for your theme).
Finally, you may want to update the logo and other images in your theme's images directory.
