Latest News: (loading..)
Harald Ponce de Leon

osCommerce Online Merchant v2.3.3.4

30 posts in this topic

1. Install on hosting. save copy to your computer as backup.

 

2. You can use your hosting file manager to edit files. you can download them to your computer then when edited upload them again using ftp. Dreamweaver is an HTML editor. Oscommerce is php. Either is notepad++ or some other code editor.

 

Dreamweaver is quite capable of editing PHP files amongst a whole lot of others, CSS, JS and much more - depending on the version, you can create projects, add your ftp account and even upload directly from dreamweaver to the server. - I've been using dreamweaver amongst other IDE's for years now.

 

here is a link to a comprehensive list of file types that can be edited in dreamweaver.

 

www.fileinfo.com/software/adobe/dreamweaver

Edited by mommaroodles

Share this post


Link to post
Share on other sites

May I suggest algozone.com. Great prices and customer service. I use them.

Strange I have one from them. Just last week, lots of errors in template and several tickets sent. Ticket system not working and they don't answer any emails.

Share this post


Link to post
Share on other sites

I am in the process of updating from 2.3.3.2 to 2.3.3.3/2.3.3.4 and especially the upgrade to UTF-8 and database conversion to UTF-8 gives me some problems.

 

What I did with relevant changes:

- upload the new/updated functions/database.php - 2.3.3.4 (both in catalog and admin) - RELEVANT function tep_db_connect() with mysqli_set_charset($$link, 'utf8');

- changed  includes/languages/includes/english.php - RELEVANT : 

                   setlocale(LC_ALL, array('en_US.UTF-8', 'en_US.UTF8', 'enu_usa'));

         define('CHARSET', 'utf-8');

- changed  includes/languages/includes/dutch.php - RELEVANT:

         setlocale(LC_ALL, array('nl_NL.UTF-8, nl_NL.UTF8, nld_nld'));;

                  define('CHARSET', 'utf-8');

 

These changes offcourse give a lot of "unknown / badly showed" characters on both admin and catalog. We were running up till now with ISO_8859-1 both english and dutch.

 

So I gave it a try with converting a test table with admin/databasetables.php FROM latin1_swedish_ci to utf8_unicode_ci.This seemed to give the expected result (EG characters like é converted to éé) ...

 

But in an other field (same test table off-course) the text was "deleted" after é. Both columns have Type mediumtext and the new Collation utf8_unicode_ci set by the update.

 

So I am puzzled here over the inconsistency. 

 

Any thgoughts?

Share this post


Link to post
Share on other sites

Strange I have one from them. Just last week, lots of errors in template and several tickets sent. Ticket system not working and they don't answer any emails.

 

they havent been responding to any tickets now for sometime nor do they respond to comments left on their facebook page.  The last template I bought from them was very disappointing to say the least.  I used them quite often over the years and I wont be using them any longer.

Share this post


Link to post
Share on other sites

another thing I've noticed is the inconsistency of the indexes in the oscommerce.sql file.

 

it would appear that the naming convention for the indexes is "idx_table_name_column_name" and  all in lowercase, however there are some which are just the idx_column_name and then some that are in uppercase.

 

take this for example:

DROP TABLE IF EXISTS action_recorder;
CREATE TABLE action_recorder (
  id int NOT NULL auto_increment,
  module varchar(255) NOT NULL,
  user_id int,
  user_name varchar(255),
  identifier varchar(255) NOT NULL,
  success char(1),
  date_added datetime NOT NULL,
  PRIMARY KEY (id),
  KEY idx_action_recorder_module (module),
  KEY idx_action_recorder_user_id (user_id),
  KEY idx_action_recorder_identifier (identifier),
  KEY idx_action_recorder_date_added (date_added)
) CHARACTER SET utf8 COLLATE utf8_unicode_ci;

in the above we can see idx_tablename_columnname

 

below we have  idx_columname

DROP TABLE IF EXISTS banners;
CREATE TABLE banners (
  banners_id int NOT NULL auto_increment,
  banners_title varchar(64) NOT NULL,
  banners_url varchar(255) NOT NULL,
  banners_image varchar(64) NOT NULL,
  banners_group varchar(10) NOT NULL,
  banners_html_text text,
  expires_impressions int(7) DEFAULT '0',
  expires_date datetime DEFAULT NULL,
  date_scheduled datetime DEFAULT NULL,
  date_added datetime NOT NULL,
  date_status_change datetime DEFAULT NULL,
  status int(1) DEFAULT '1' NOT NULL,
  PRIMARY KEY (banners_id),
  KEY idx_banners_group (banners_group)
) CHARACTER SET utf8 COLLATE utf8_unicode_ci;

and even in uppercase - a few tables

DROP TABLE IF EXISTS countries;
CREATE TABLE countries (
  countries_id int NOT NULL auto_increment,
  countries_name varchar(255) NOT NULL,
  countries_iso_code_2 char(2) NOT NULL,
  countries_iso_code_3 char(3) NOT NULL,
  address_format_id int NOT NULL,
  PRIMARY KEY (countries_id),
  KEY IDX_COUNTRIES_NAME (countries_name)
) CHARACTER SET utf8 COLLATE utf8_unicode_ci;

so its very apparent that there doesnt seem to be a set standard and it's def not following any form of 'best practice'

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now