Jump to content

datagnostics

Members
  • Content count

    7
  • Joined

  • Last visited

Profile Information

  • Real Name
    ME Curtin
  1. datagnostics

    [Contribution] STS v4

    Well I did that, and it didn't work. Right now I'm working on uninstalling everything to do with STS, while dealing with a backup file that turns out to be corrupt. wailing, gnashing, etc. ME DataGnostics.com
  2. datagnostics

    [Contribution] STS v4

    And it makes no difference. I can't find any other .htaccess files lurking in the crevices, either. What is going on? How can I test where the missing step is? yrs groggily, DataGnostics.com
  3. datagnostics

    [Contribution] STS v4

    But look what I just found in includes/: # $Id: .htaccess 1739 2007-12-20 00:52:16Z hpdl $ # # This is used with Apache WebServers # The following blocks direct HTTP requests in this directory recursively # # For this to work, you must include the parameter 'Limit' to the AllowOverride configuration # # Example: # #<Directory "/usr/local/apache/htdocs"> # AllowOverride Limit # # 'All' with also work. (This configuration is in your apache/conf/httpd.conf file) # # This does not affect PHP include/require functions # # Example: http://server/catalog/includes/application_top.php will not work <Files *.php> Order Deny,Allow Deny from all </Files> Could this be the issue?
  4. datagnostics

    [Contribution] STS v4

    Here's what's in the htaccess file (which I didn't put there or edit): RewriteCond %{HTTP_REFERER} !^http://DOMAIN.com/.*$ [NC] RewriteCond %{HTTP_REFERER} !^http://DOMAIN.com$ [NC] RewriteCond %{HTTP_REFERER} !^http://www.DOMAIN.com/.*$ [NC] RewriteCond %{HTTP_REFERER} !^http://www.DOMAIN.com$ [NC] RewriteRule .*\.(jpg|jpeg|gif|png|bmp)$ - [F,NC] -- where DOMAIN, of course, is the client's domain. I don't know if it makes a difference, but it *is* set up so that where on the test site I had testdomain.com/catalog/index.php, on the live site it displays as domain.com/index.php. But that change is strictly made in configure.php, right?
  5. datagnostics

    [Contribution] STS v4

    On the right sidebar: Default template (v2.1.1) Use Templates? true Code for debug output debug Files for normal template sts_user_code.php Base folder includes/sts_templates/ Template folder test Default template file sts_template.html Use template for infoboxes false ------- is that what you mean?
  6. datagnostics

    [Contribution] STS v4

    In catalog\includes\modules\sts\sts_default.php starting on line 52: function capture_fields () { // Returns list of files to include from folder sts_inc in order to build the $template fields return 'general.php;'.MODULE_STS_DEFAULT_NORMAL; } ME DataGnostics.com
  7. datagnostics

    [Contribution] STS v4

    Downward compatibility? I'm building a site using STS. I built and tested it on my local machine, then on a remote test site. Everything looks fine, so the client said "go live". I uploaded everything (except configure.php) to the client's site, and now the template variables aren't being parsed. partial screenshot, client name blacked out, using the STS default template for easy comparison: I used the sts_debug function to see if there was any difference between the two sites. I can't see anything that would cause this, but I did notice that the live (problematic) site is running PHP 4.4.8, while my localhost is using PHP 5.2.6 and the test site is on 5.2.8. Could this be causing the problem? I don't know if the live site can be updated to PHP 5.2x (shared server, control issues) -- is there something I need to do to make STS 4.5.5 downward-compatible? Or is the problem something else entirely, and if so where is it likely to lurk? yours in wailing and gnashing of teeth, Datagnostics.com
×