trouble moving existing site that has "self-contained" Pear packages defined within own directories

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Paul
    #1

    trouble moving existing site that has "self-contained" Pear packages defined within own directories

    I am moving an existing app written years ago to a new server. It uses
    Sigma Template 1.3 and Quickform 1.1.1 and PEAR.php,v 1.1.1.1 2004/02/16

    The directory structure is like this:
    /site
    /site/html/Pear.php
    /site/html/Sigma.php
    /site/html/Common.php
    /site/html/Quickform.php
    /site/html/Quickform/
    /site/Mail/mail.php
    /pages/page1.php
    ....

    In the file Quickform.php, it starts off with:
    ini_set('includ e_path','.:..') ;
    ....
    (line 23)require_once ('PEAR.php');
    (line 24)require_once ('HTML/Common.php');
    require_once '../HTML/Sigma.php';
    ....

    This throws the error:
    Warning: main(HTML/Common.php) [function.main]: failed
    to open stream: No such file or directory in
    C:\...\HTML\Qui ckForm.php on line 24

    If I change:
    (line 24)require_once ('HTML/Common.php');

    to

    (line 24)require_once ('Common.php');

    it throws MANY more errors but the first of which is:

    Warning:
    defaultrenderer (HTML/QuickForm/Renderer/Default.php)[function.defaul trenderer]:
    failed to open stream: No such file or directory in C:\..\HTML\Quic kForm.php
    online 1416

    which is where the default renderer is referenced using
    'HTML/QuickForm/Renderer/Default.php'

    I want to move this site over with as little change as possible and still
    work without updating it too much because updating one thing is going to
    make me change many things.

    I have tried installing the standard pear packages and changing the
    references in the code. there is one particular error throw that calls
    getBlockContent () in SIGMA that is not in the current version.

    I am wondering if I shouldn't set up an Apache.conf alias for HTML to that
    directory for that virtual host.

    Any ideas or experience in moving an existing site sites where all the pear
    packages are self-contained, is MUCH appreciated!!


    Tags: None
    • Jerry Stuckle
      #2
      Re: trouble moving existing site that has "self-contained" Pear packagesdefined within own directories

      Paul wrote:
      I am moving an existing app written years ago to a new server. It uses
      Sigma Template 1.3 and Quickform 1.1.1 and PEAR.php,v 1.1.1.1 2004/02/16
      >
      The directory structure is like this:
      /site
      /site/html/Pear.php
      /site/html/Sigma.php
      /site/html/Common.php
      /site/html/Quickform.php
      /site/html/Quickform/
      /site/Mail/mail.php
      /pages/page1.php
      ...
      >
      In the file Quickform.php, it starts off with:
      ini_set('includ e_path','.:..') ;
      ...
      (line 23)require_once ('PEAR.php');
      (line 24)require_once ('HTML/Common.php');
      require_once '../HTML/Sigma.php';
      ...
      >
      This throws the error:
      Warning: main(HTML/Common.php) [function.main]: failed
      to open stream: No such file or directory in
      C:\...\HTML\Qui ckForm.php on line 24
      >
      If I change:
      (line 24)require_once ('HTML/Common.php');
      >
      to
      >
      (line 24)require_once ('Common.php');
      >
      it throws MANY more errors but the first of which is:
      >
      Warning:
      defaultrenderer (HTML/QuickForm/Renderer/Default.php)[function.defaul trenderer]:
      failed to open stream: No such file or directory in C:\..\HTML\Quic kForm.php
      online 1416
      >
      which is where the default renderer is referenced using
      'HTML/QuickForm/Renderer/Default.php'
      >
      I want to move this site over with as little change as possible and still
      work without updating it too much because updating one thing is going to
      make me change many things.
      >
      I have tried installing the standard pear packages and changing the
      references in the code. there is one particular error throw that calls
      getBlockContent () in SIGMA that is not in the current version.
      >
      I am wondering if I shouldn't set up an Apache.conf alias for HTML to that
      directory for that virtual host.
      >
      Any ideas or experience in moving an existing site sites where all the pear
      packages are self-contained, is MUCH appreciated!!
      >
      >
      Sure, you can set up a virtual directory for it. Try
      alt.apache.conf iguration for what you need.

      --
      =============== ===
      Remove the "x" from my email address
      Jerry Stuckle
      JDS Computer Training Corp.
      jstucklex@attgl obal.net
      =============== ===

        Comment

        • Paul
          #3
          Re: trouble moving existing site that has "self-contained" Pear packages defined within own directories

          "Jerry Stuckle" <jstucklex@attg lobal.netwrote in message
          news:ov2dnarTX7 T1W5fbnZ2dnUVZ_ tfinZ2d@comcast .com...
          Paul wrote:
          >I am moving an existing app written years ago to a new server. It uses
          >Sigma Template 1.3 and Quickform 1.1.1 and PEAR.php,v 1.1.1.1 2004/02/16
          >>
          >The directory structure is like this:
          >/site
          >/site/html/Pear.php
          >/site/html/Sigma.php
          >/site/html/Common.php
          >/site/html/Quickform.php
          >/site/html/Quickform/
          >/site/Mail/mail.php
          >/pages/page1.php
          >...
          >>
          >In the file Quickform.php, it starts off with:
          >ini_set('inclu de_path','.:..' );
          >...
          >(line 23)require_once ('PEAR.php');
          >(line 24)require_once ('HTML/Common.php');
          >require_once '../HTML/Sigma.php';
          >...
          >>
          >This throws the error:
          >Warning: main(HTML/Common.php) [function.main]: failed
          >to open stream: No such file or directory in
          >C:\...\HTML\Qu ickForm.php on line 24
          >>
          >If I change:
          >(line 24)require_once ('HTML/Common.php');
          >>
          >to
          >>
          >(line 24)require_once ('Common.php');
          >>
          >it throws MANY more errors but the first of which is:
          >>
          >Warning:
          >defaultrendere r(HTML/QuickForm/Renderer/Default.php)[function.defaul trenderer]:
          >failed to open stream: No such file or directory in
          >C:\..\HTML\Qui ckForm.php online 1416
          >>
          >which is where the default renderer is referenced using
          >'HTML/QuickForm/Renderer/Default.php'
          >>
          >I want to move this site over with as little change as possible and still
          >work without updating it too much because updating one thing is going to
          >make me change many things.
          >>
          >I have tried installing the standard pear packages and changing the
          >references in the code. there is one particular error throw that calls
          >getBlockConten t() in SIGMA that is not in the current version.
          >>
          >I am wondering if I shouldn't set up an Apache.conf alias for HTML to
          >that directory for that virtual host.
          >>
          >Any ideas or experience in moving an existing site sites where all the
          >pear packages are self-contained, is MUCH appreciated!!
          >>
          >>
          >
          Sure, you can set up a virtual directory for it. Try
          alt.apache.conf iguration for what you need.
          >
          --
          =============== ===
          Remove the "x" from my email address
          Jerry Stuckle
          JDS Computer Training Corp.
          jstucklex@attgl obal.net
          =============== ===
          Jerry - thanks. I have that already and am still running into PEAR packages
          being contained and referenced in the directory structure as opposed to it
          being a normal pear install.


            Comment

            Previous template Next
            Working...