Guide Category

134

Upgrade Theme 9.4 to 9.6

Upgrade Datalife Engine theme from 9.4 to 9.6 is our upgrade guide project to help users upgrade the theme in single tutorial without having to worry about 9.5 upgrade process, this tutorial will cover the theme upgrade from 9.4 to 9.5 and 9.6. Usually when you upgrade Datalife Engine from version 9.4 to 9.6 you have to upgrade theme from 9.4 to 9.5 and then upgrade 9.5 to 9.6, our all in one tutorial series will make it easy for you so that you can easily upgrade theme for 9.4 to 9.6 step by step in single tutorial.
dlestarter
Upgrade Theme 9.4 to 9.6
Upgrade Theme
9.4 to 9.6
Last Updated: November 20, 2013
Upgrade Datalife Engine theme from 9.4 to 9.6 is our upgrade guide project to help users upgrade the theme in single tutorial without having to worry about 9.5 upgrade process, this tutorial will cover the theme upgrade from 9.4 to 9.5 and 9.6. Usually when you upgrade Datalife Engine from version 9.4 to 9.6 you have to upgrade theme from 9.4 to 9.5 and then upgrade 9.5 to 9.6, our all in one tutorial series will make it easy for you so that you can easily upgrade theme for 9.4 to 9.6 step by step in single tutorial.

Files to change:

  1. addnews.tpl
  2. comments.tpl
  3. fullstory.tpl
  4. shortstory.tpl
  5. pm.tpl
  6. profile_popup.tpl (add tag subscribe to user RSS feed and change tags)
  7. userinfo.tpl (Change tags)
  8. preview.css (add pre code style)
  9. /style/engine.css (add pre code style)
  10. styles.css (or your theme main css style file)
  11. .htaccess (change structure for template protection)

Files to add:

  1. frame.css (popup windows page)
  2. print.tpl (articles print page)
  3. static_print.tpl (static print page)
  4. dleimages/no_image.jpg
  5. bbcodes/typograf.gif
  6. images/button.png
  7. images/loading.gif
  8. images/offline.png
  9. images/online.png
  10. images/shadow.png
  11. images/tableft.gif
  12. images/tabright.gif

Files to change

1) Open addnews.tpl

add the following code on the beginning of the file:

<link rel="stylesheet" type="text/css" href="engine/skins/chosen/chosen.css"/>
<script type="text/javascript" src="engine/skins/chosen/chosen.js"></script>
<script type="text/javascript">
$(function(){
	$('#category').chosen({allow_single_deselect:true, no_results_text: 'No category found or not selected'});
});
</script>
2) Open comments.tpl

Find:

<li>Registration: {registration}</li>

Add after:

<li>Status: [online]<img src="{THEME}/images/online.png" style="vertical-align: middle;" title="Currently Online" alt="Currently Online" />[/online][offline]<img src="{THEME}/images/offline.png" style="vertical-align: middle;" title="Currently Offline" alt="Currently Offline" />[/offline]</li>
The themes are different designed, but the reason of modification is add the online/offline status next to registration, however, you can add the status to anywhere you want the status icon to display
3/4) Open fullstory.tpl and shortstory.tpl

Find:

<div class="ratebox"><div class="rate">{rating}</div></div>

Replace with:

[rating]<div class="ratebox"><div class="rate">{rating}</div></div>[/rating]
The themes are different designed, but the reason of modification is add the open/closed tags for [rating and [/rating to cover rating tag so if the article rating enable or disable then the rating style will be removed
5) Open pm.tpl

Find:

<div class="dpad">[inbox]Inbox[/inbox] | [outbox]Outbox[/outbox] | [new_pm]Send New PM[/new_pm]</div>

Replace with:

<div class="dpad">
<div class="pm_status">
	<div class="pm_status_head">PM Statistics</div>
	<div class="pm_status_content">PM for your account usages:
{pm-progress-bar}
{proc-pm-limit}% out of ({pm-limit} allowed)
	</div>
</div>
<div style="padding-top:10px;">[inbox]Inbox[/inbox]<br /><br />
[outbox]Outbox[/outbox]<br /><br />
[new_pm]Send New PM[/new_pm]</div>
</div><br />
<div class="clr"></div>
The themes are different designed, but the reason of modification is add the PM box status, this status will show you how hoch space you have used for your PM limit assigned to your usergroup account, the following tags are added to this file:
- {pm-progress-bar} this is the bar to show the level of pm box in your account
- {proc-pm-limit}% this is the percentage of usages
- {pm-limit} this is the total PM message allowed for your user account (Set in usergroup manager)
6) Open profile_popup.tpl

Find:

{news_num} [ {news} ]

Add after:

[rss]<img src="{THEME}/images/rss.png" alt="rss" style="vertical-align: middle; margin-left: 5px;" />[/rss]

Find:

{news_num}

Replace with:

{news-num}

Find:

{comm_num}

Replace with:

{comm-num}

Find:

<li><span class="grey">Last Visited:</span> <b>{lastdate}</b></li>

Replace with:

<li><span class="grey">Last Visited:</span> <b>{lastdate}</b>, <span class="grey">Status:</span> [online]<img src="{THEME}/images/online.png" style="vertical-align: middle;" title="Currently Online" alt="Currently Online" />[/online][offline]<img src="{THEME}/images/offline.png" style="vertical-align: middle;" title="Currently Offline" alt="Currently Offline" />[/offline]</li>
The themes are different designed, but the reason of modification is add the online/offline status next to last visited, however, you can add the status to anywhere you want the status icon to display
7) Open userinfo.tpl

Find:

{news_num}

Replace with:

{news-num}

Find:

{comm_num}

Replace with:

{comm-num}

Find:

<li><span class="grey">Last visited:</span> <b>{lastdate}</b></li>

Add after:

<li>Status: [online]<img src="{THEME}/images/online.png" style="vertical-align: middle;" title="Currently Online" alt="Currently Online" />[/online][offline]<img src="{THEME}/images/offline.png" style="vertical-align: middle;" title="Currently Offline" alt="Currently Offline" />[/offline]</li>
The themes are different designed, but the reason of modification is add the online/offline status next to last visited, however, you can add the status to anywhere you want the status icon to display
8/9) Open the file /style/engine.css and preview.css

Add the following code at the end:

/*--- Code tag highlight [ code ]---*/
pre code {
  display: block; padding: 0.5em;
  background: #f9fafa; 
  border: 1px solid #dce7e7;
  overflow:auto;
  white-space: pre;
}
pre .comment,
pre .template_comment,
pre .diff .header,
pre .doctype,
pre .lisp .string,
pre .javadoc {
  color: #93a1a1;
  font-style: italic;
}
pre .keyword,
pre .css .rule .keyword,
pre .winutils,
pre .javascript .title,
pre .method,
pre .addition,
pre .css .tag,
pre .lisp .title {
  color: #859900;
}
pre .number,
pre .command,
pre .string,
pre .tag .value,
pre .phpdoc,
pre .tex .formula,
pre .regexp,
pre .hexcolor {
  color: #2aa198;
}
pre .title,
pre .localvars,
pre .function .title,
pre .chunk,
pre .decorator,
pre .builtin,
pre .built_in,
pre .lisp .title,
pre .identifier,
pre .title .keymethods,
pre .id {
  color: #268bd2;
}
pre .tag .title,
pre .rules .property,
pre .django .tag .keyword {
  font-weight: bold;
}
pre .attribute,
pre .variable,
pre .instancevar,
pre .lisp .body,
pre .smalltalk .number,
pre .constant,
pre .class .title,
pre .parent,
pre .haskell .label {
  color: #b58900;
}
pre .preprocessor,
pre .pi,
pre .shebang,
pre .symbol,
pre .diff .change,
pre .special,
pre .keymethods,
pre .attr_selector,
pre .important,
pre .subst,
pre .cdata {
  color: #cb4b16;
}
pre .deletion {
  color: #dc322f;
}
pre .tex .formula {
  background: #eee8d5;
}
Different theme designs are different, some of theme use /style/engine.css, some use /styles/engine.css, some use /css/engine.css, some don't use engine.css file but use different name or file, but the point is to add this tag within the theme anywhere in css file
10) Open style/engine.css

Add at the end of file:

/*---progress bar length for personal messages---*/
.pm_progress_bar {
	border: 1px solid #d8d8d8;
	padding: 1px;
	margin-top: 10px;
	margin-bottom: 10px;
}
.pm_progress_bar span {
	background: #000000;
	font-size: 0em;
	text-indent: -2000em;
	height: 10px;
	display: block;
	overflow: hidden;
}
Some themes use different folders like "styles" or "css", but what you need is add the code to engine.css within those folders, if your theme doesn't have engine.css, you can add the code to one of your css files
11) Open style/styles.css

Add to the end of the file:

.pm_status {
	float:left;
	border: 1px solid #d8d8d8;
	padding: 0px;
	background-color: #fff;
	width: 280px;
	height: 100px;
	margin-left: 20px;
	margin-right: 5px;
}
.pm_status_head {
	border-bottom: 1px solid #d8d8d8;
	font-size: 0.9em; 
	background: #fff url("../images/bbcodes.png") repeat-x 0 100%;
	height: 22px;
	padding: 0;
	font-weight: bold;
	text-align: center;
	color: #4e4e4e;
}
Some themes use different folders like "styles" or "css", but what you need is add the code to styles.css or style.css within those folders, if your theme doesn't have styles.css, you can add the code to one of your css files
12) open the {THEME}/.htaccess
The .htaccess file in your "templates/your_theme" folder

replace all the code inside the file with the following contents:

Order allow,deny
Deny from all
<FilesMatch ".(css)$|^$">
   Order deny,allow
   Allow from all
</FilesMatch>
For example if you are using theme "WStarter" then the file /templates/WStarter/.htaccess must contain the code above

Files to add (Download from attached file)

Please download the attached file and place them within folder /templates/YOUR THEME/

The following files are included in the package (You can use your own images if you like)
  1. frame.css (popup windows page)
  2. print.tpl (articles print page)
  3. static_print.tpl (static print page)
  4. dleimages/no_image.jpg
  5. bbcodes/typograf.gif
  6. images/button.png
  7. images/loading.gif
  8. images/offline.png
  9. images/online.png
  10. images/shadow.png
  11. images/tableft.gif
  12. images/tabright.gif
relatednews.tpl
relatednews.tpl: this file is used for tag {related-news} for related news in fullstory.tpl, the purpose of this file to be added independently because Datalife Engine have added and improve the new way to display related news, they have added some tags that are very helpful for those who want to customize the way related news to display, now you can use additional tags to display images and text from the article for additional enhanced look...the following tags are applied within the file relatednews.tpl:
  • {image-X}: This will display the image you have uploaded and added in the article, the X indicates the image number, if you add only 1 image then the tag will be {image-1}, if you have added more than 1 image, you can specify the image number like {image-2}, {image-3} and so on...the tag only identify the image name, but it will not give you the full html code, so you must manually input the proper img code like:

    Example Code:

    <img src="{image-1}" alt="" width="xxx" height="xxx" />
    <img src="{image-2}" alt="" width="xxx" height="xxx" />
    <img src="{image-3}" alt="" width="xxx" height="xxx" />
    
  • {text limit="XXX"}: This will display the short story description as additional details than title, the older version you can only use title for related news unless you use some hacks to get anything else display, now you add additional text description, the XXX indicates how many letters and characters you want the short description to display, if the max text has reach the number you specified then it will be cut out the rest of shortstory automatically. Please note that the tag {text limit="xxx"} will only grab everything in regular text format, it will not grab any styles, bbcode styles or html code styles
  • New in 9.5, you can now use all xfields in your topnews and related news, for example:

    Example Code:

    <img src="[xfvalue_poster]" alt="" width="xxx" height="xxx" />
    
topnews.tpl
topnews.tpl This file is used for the tag "{topnews}" in either main.tpl or sidebar.tpl (depending on design), the purpose of this file and the additional tags are exactly the same as relatednews.tpl above, you can use tags {image-X} and {text limit="XXX"}, you can also use xfield as same as relatednews.tpl, so please refer to the details above the additional tags
Both files are using the default tag

Example Code:

<li><a href="{link}">{title}</a></li>
  • {link}: is the full link url for the article, it will automatically converted to any link formats of your SEO settings or none SEO
  • {title}: is the actual article title
Additional Tags for DLE 9.5,9.6 in user profile and commnets
There are a few tags added in 9.5,9.6 but we don't seem to find the information anywhere, even the themes come with the DLE 9.5,9.6 package don't even add these tags in the themes so this information you can only find in DLEStarter.com!...

The following tags are applied to template files userinfo.tpl and comments.tpl

  1. [fullnamexxx[/fullname is used for open and close tag if full name field {fullname} was input, for example, in templates/Default/userinfo.tpl,

    Find:

    <li><span class="grey">Full name:</span> <b>{fullname}</b></li>
    

    Replace with:

    [fullname]<li><span class="grey">Full name:</span> <b>{fullname}</b></li>[/fullname]
    
    If the user input the information in Full name filed then it will show, if not then nothing will show, this tag is intended for remove empty fields in user profile and comments
  2. [icqxxx[/icq is used for open and close tag if icq field {icq} was input, for example, in templates/Default/userinfo.tpl,

    Find:

    <li><span class="grey">ICQ:</span> <b>{icq}</b></li>
    

    Replace with:

    [icq]<li><span class="grey">ICQ:</span> <b>{icq}</b></li>[/icq]
    
    If the user input the information in icq filed then it will show, if not then nothing will show, this tag is intended for remove empty fields in user profile and comments
  3. [landxxx[/land is used for open and close tag if location field {land} was input, for example, in templates/Default/userinfo.tpl,

    Find:

    <li><span class="grey">Location:</span> {land}</li>
    

    Replace with:

    [land]<li><span class="grey">Location:</span> {land}</li>[/land]
    
    If the user input the information in location filed then it will show, if not then nothing will show, this tag is intended for remove empty fields in user profile and comments
  4. [infoxxx[/info is used for open and close tag if short information field {info} was input, for example, in templates/Default/userinfo.tpl,

    Find:

    <li><span class="grey">Information:</span> {info}</li>
    

    Replace with:

    [info]<li><span class="grey">Information:</span> {info}</li>[/info]
    
    If the user input the information in short information filed then it will show, if not then nothing will show, this tag is intended for remove empty fields in user profile and comments
  5. [signaturexxx[/signature is used for open and close tag if signature field {signature} was filled, for example,

    Example Code:

    [signature]<hr /> <b>{signature}</b>[/signature]
    
    If the user filled the information in signature filed then it will show, if not then nothing will show, this tag is intended for remove empty fields in user profile and comments
  6. [news-numxxx[/news-num is used for open and close tag if the user have posted article in your website for example,

    Example Code:

    [news-num]<li style="margin-top:10px;">Posts: <b>{news-num}</b>  <span class="button">{news}</span> 
        [rss]<img alt="" src="{THEME}/images/ico/ico_rss.png" border="0" style="vertical-align:middle; margin-bottom: 3px;" title="Feed - Bookmark Posts" />[/rss]</li>[/news-num]
    
    If the user had posted at least 1 article in your website then it will show, if not then nothing will show, this tag is intended for remove empty fields in user profile and comments
  7. [comm-numxxx[/comm-num is used for open and close tag if the user have posted comment in your website for example,

    Example Code:

    [comm-num]<li style="margin-top:10px;">Comments: <b>{comm-num}</b> <span class="button">{comments}</span></li>[/comm-num]
    
    If the user had posted at least 1 comment in your website then it will show, if not then nothing will show, this tag is intended for remove empty fields in user profile and comments

Related Tutorials

Review/Leave Comment

comments powered by Disqus