Changeset 89


Ignore:
Timestamp:
Apr 8, 2006 8:30:29 AM (18 years ago)
Author:
scdev
Message:

fixed a little bug in dieBoomerangURL

Location:
trunk/lib
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/lib/App.inc.php

    r88 r89  
    894894        } else if (isset($default_url)) {
    895895            $url = $default_url;
    896         }
    897896        } else if (!refererIsMe()) {
    898897            // Ensure that the redirecting page is not also the referrer.
  • trunk/lib/Hierarchy.inc.php

    r88 r89  
    11<?php
    22/**
    3  * Heirarchy.inc.php
     3 * Hierarchy.inc.php
    44 * Code by Strangecode :: www.strangecode.com :: This document contains copyrighted information
    55 */
     
    77/**
    88 * Objective: This class provides the tools to organize pieces of data into a
    9  * heirarchy of nodes. Any form of data (article, product, image) can be
    10  * represented as a node in this heirarchy. This class does not manipulate the
     9 * hierarchy of nodes. Any form of data (article, product, image) can be
     10 * represented as a node in this hierarchy. This class does not manipulate the
    1111 * data, nor is it involved in storing or retrieving the data. In fact it does
    1212 * not access the tables where data exists and cannot find out info about the
    1313 * data. You must provide identification of a piece of data (type and ID) to
    14  * insert it into the heirarchy. The node heirarchy is completely
     14 * insert it into the hierarchy. The node hierarchy is completely
    1515 * separate from data storage and retreival. You must separatly store the data
    1616 * using whatever logic is specific to the data then also call these functions.
    1717 * Nodes are not the data. The nodes are mere singularities in virtual space
    18  * that represent a piece of data's relationship with another. The heirarchy
     18 * that represent a piece of data's relationship with another. The hierarchy
    1919 * is an inverted tree structure. Each node can have virtually infinite
    2020 * children. Each child can have multiple parents.
     
    2424 */
    2525
    26 class Heirarchy {
     26class Hierarchy {
    2727
    2828    /**
     
    6262     *                          configuration or connection parameters.
    6363     */
    64     function Heirarchy($params=array())
     64    function Hierarchy($params=array())
    6565    {
    6666        $this->params = $params;
     
    542542     * the specified node IS an ancestor of a node made into it's parent, we would
    543543     * have a circular reference that would cause an infinite loop with any
    544      * recursive queries of the heirarchy.
     544     * recursive queries of the hierarchy.
    545545     * @param  string    $child_type
    546546     * @param  string    $child_id
     
    568568     * ALL ancestors to the specified node. I'm not sure what the order will be
    569569     * but that probably isn't useful anyways. I use this to prevent circular
    570      * references in the heirarchy.
     570     * references in the hierarchy.
    571571     * @param  string    $child_type
    572572     * @param  string    $child_id
     
    677677     * @return array  Details of from the node table of all nodes below the
    678678     *                specified node: (type, id, title, indent level, selected status)
     679     *
     680     * FIX ME: $include_curr doesn't work because the current node will break with an infinite loop.
    679681     */
    680682    function &getNodeList($preselected=null, $child_type=null, $child_id=null, $type_constraint=null, $include_curr=false, $order='', $_indent=0, $_return_flag=true)
Note: See TracChangeset for help on using the changeset viewer.