Jump to content

BeTheWater

Members
  • Content count

    21
  • Joined

  • Last visited

Everything posted by BeTheWater

  1. OK...hardcode it. In googlesitemap/index.php find this code: tep_db_connect() or die('Unable to connect to database server!'); and change it to this: tep_db_connect(DB_SERVER, DB_SERVER_USERNAME, DB_SERVER_PASSWORD, DB_DATABASE) or die('Unable to connect to database server!'); If that does not work I don't know what to tell you...it's using the defined constants from your configure.php file...
  2. I would recommend that you upgrade all the way to the latest v2.1c Once you do go to the admin control panel and de-activate the redirect script. Then, leave the "old" redirect code in place from the v1.4 install you have now. This will effectively keep what works on your store working (the redirects) and get the benefits of the new code base (which are verified to be compatible). If you don't have the old redirect script in place then there is nothing that should be stopping you from upgrading. With respect to this "Bobby" character...it is a shame but I'm sure he will miss the community and look beyond the political bullshit (and forgive the ones that trashed him after he was gone) and find some way of helping the ones that matter...the store owners...even if that means he has to sneak around. Of course, I don't know the man but know his kind. Words like integrity, dedication, duty, loyalty and honor actually still mean something. BeTheWater
  3. And the user "httpd" is a valid MySQL user on your system and has access to your store database?
  4. It is my understanding that the new v2.1c release is still buggy with respect to the redirect code and the author is tring to get it worked out. The issue is with the $_SERVER['PATH_INFO'] variable population on CGI mode servers versus SAPI mode. It may be of value to upgrade now as the next release (ironically v2.2) will be the final dot release (to my understanding). Hence, upgrade now for the sitemap and then later once the final release is uploaded the procedure to uprgade is simply overwrite the base class and visit the store.
  5. The code should still work for SEO URLs v1.x through the current v2.1c release (at least as a beginner at this whole osC thing I suspect it would be...after all I only have a few posts:)). At any rate, download the latest v1.3 release of the Google Sitemap and overwrite the index.php and sitemap.class.php files. Then, give it another go...
  6. It looks like the required files are not being included and executed that are needed for the SEO URLs to run.
  7. Look at the output from the index.php. If the files are being included it will say: File: XXX is being included. It'll say this twice...once for each file needed to generate SEO URLs.
  8. Mike, In googlesitemap/index.php find this code: if ( file_exists(DIR_WS_CLASSES . 'cache.class.php') ){ include(DIR_WS_CLASSES . 'cache.class.php'); $cache = new cache($languages_id); if ( file_exists('includes/seo_cache.php') ){ include('includes/seo_cache.php'); } and change it to this: if ( file_exists(DIR_WS_CLASSES . 'cache.class.php') ){ echo 'File: ' . DIR_WS_CLASSES . 'cache.class.php exists and is being included' . "\n\n"; include(DIR_WS_CLASSES . 'cache.class.php'); $cache = new cache($languages_id); if ( file_exists('includes/seo_cache.php') ){ echo 'File: ' . 'includes/seo_cache.php exists and is being included' . "\n\n"; include('includes/seo_cache.php'); } Run the index.php script again and see if the files are being included.
×