Thread

So, it’s time to dig in a bit more and get further with the Bug Tracker.  Please remember that you can always find the series Table of Contents on the Building a Bug Tracker page.

Today we’re going to set up our template group and variables.  Before we begin, you might like to take a few minutes to add a few entries to your bug tracker weblog. Have fun with it, you’ll be working with this data throughout the rest of the series.

Shall we jump right into the next step?

Onwards!

Thanks for the effort Lisa! Will try to follow the suggested steps to build my own.

Hi Lisa, hey would the other methods you mentioned be better options for anyone who wants to multipurpose their EE site and not have it dedicated to being a Bug tracker.
You mentioned “The Fresh Variables module, Dynamically Assigned Global Variables…”

Any hints on those, digging on my own meanwhile.
If it would make it to hard to follow-along, I’ll stick with your original recommendation, currently my EE install is just for learning anyways.

Thanks.

tzMedia - I don’t quite understand?  Many ExpressionEngine sites are multi-purpose, because there isn’t a limit on weblogs, custom field groups, status groups, or category groups.  So you just create what you need.

I’ll just go with your recommendation, I just wasn’t sure if this would effect anything else I might want to set up later by altering the file as you suggested. Works for me then. I guess I was thinking it might have something to do with setting the site root to be the Bug tracker or something.

Altering what file?

It was just confused thinking on my part, I see it is defining new variables in the path.php global variables.
I was afraid that would mess with any other variables defined.
I imagine now there is no limit to how many global variables that can be defined.
just newbie confusion, nevermind me, thanks for checking.

Yep, you can define other variables. =)

Lisa,

From, “Building a Bug Tracker: Setting up the Templates,” it says:

FTP to your site, make a backup of path.php, then open it in your favorite HTML editor.  Let’s define two new path.php global variables:
“bug_tracker_weblog” => “bug_tracker”,
“bug_tracker_template_group” => “bug_tracker”,

I’m not sure where these new variables get added to path.php. I have path.php opened in TextWrangler which contains the following:

<?php
// DO NOT ALTER THIS FILE UNLESS YOU HAVE A REASON TO
// Path to the directory containing your backend files
$system_path = “./xxxxxxx/”;
$template_group = “”;
$template = “”;
$site_url = “”;
$site_index = “”;
?>

Would you please specify where/how to enter the bug_tracker variables (so I don’t screw up my path file)?

Thanks.

Hey, Ramone,

Sure, this is what my path.php looks like:

<?php

// ------------------------------------------------------
// DO NOT ALTER THIS FILE UNLESS YOU HAVE A REASON TO

// ------------------------------------------------------
// Path to the directory containing your backend files

$system_path = "./system/";

// ------------------------------------------------------
// MANUALLY CONFIGURABLE VARIABLES
// See user guide for more information
// ------------------------------------------------------

$template_group = "";
$template = "";
$site_url = "";
$site_index = "";
$site_404 = "";
$global_vars = array(
    "bug_tracker_weblog" => "bug_tracker",
    "bug_tracker_template_group" => "bug_tracker",
); // This array must be associative

?>

Lisa,

I did a copy and paste of the following from your path.php to mine, but when I add the updated version the browser can’t find my site.

$global_vars = array(
  “bug_tracker_weblog” => “bug_tracker”,
  “bug_tracker_template_group” => “bug_tracker”,
); // This array must be associative

This version works on my site:

<?php

?>

This version does not work on my site:

<?php

?>

Can you see what’s wrong?

Thanks.

What do you mean “can’t find your site”? What exactly happens?

Also, please use [ code ] tags, so that quotes don’t get curli-fied. =)

What do you mean “can’t find your site”? What exactly happens?

When I add the bug_tracker code to path.php when I try to bring up my domain all I see is a blank, white screen in the browser.

Then, after I replace the updated path.php with my original—sans bug_tracker code—the website functions normally.

I suspect that with your edits, you’re introducing some blank space. If that’s not the case, we’ll need to turn on error reporting.

But for now, double check that there is no blank space or lines before <?php or after ?>, in the one with the bug tracker variables.

I suspect that with your edits, you’re introducing some blank space.

It’s working now. Apparently ‘it’ didn’t like the indents for the bug_tracker code.

Here’s what I used to make it work ... and thanks for pointing me in the right direction.

<?php

// DO NOT ALTER THIS FILE UNLESS YOU HAVE A REASON TO

// Path to the directory containing your backend files

$system_path = "./system_xxxxxx/";

$template_group = "";
$template = "";
$site_url = "";
$site_index = "";
$global_vars = array(
"bug_tracker_weblog" => "bug_tracker",
"bug_tracker_template_group" => "bug_tracker",
); // This array must be associative

?>