mh2design Forums

Development => Help and Support => Topic started by: RichRawlings on April 21, 2008, 06:34:15 PM



Title: Treasury Component v2.0.2
Post by: RichRawlings on April 21, 2008, 06:34:15 PM
I'm using Joomla 1.5.2 in legacy and SEO Settings YES, mysql 5.0.45 php 4.3.11

FAILED: CREATE TABLE mh2tr_transactions - Specified key was too long; max key length is 1000 bytes
FAILED: CREATE TABLE mh2tr_register - Specified key was too long; max key length is 1000 bytes

Can annyone help me with this?

Thanks,
Rich

P.S. Debug mode activated

mh2Treasury Component

PayPal Instant Payment Notification script

See below for status:
----------------------------------------------------------------
Connection to db - OK!
Assigning Post Variables
Opening connection and validating request with PayPal...
Connected to PayPal
Selecting database...OK!
Executing test query...FAILED
PayPal Receiver Email: richrawlings@xxxxxx.com


Title: Re: Treasury Component v2.0.2
Post by: Mick on April 22, 2008, 12:49:41 AM
Is your SQL running in safe mode by chance?

The reason your verification has failed is because the tables have not been created.

Here are the SQL calls made to create the tables, you can manually add them and if necessary remove the UNIQUE INDEXs but make sure you leave the primary indexs.

CREATE TABLE IF NOT EXISTS mh2tr_subscriptions(
   UID_Register             BIGINT AUTO_INCREMENT,
   UID_member               BIGINT,
   first_name            VARCHAR(64),
   last_name             VARCHAR(64),
   payer_business_name   VARCHAR(127),
   payer_email           VARCHAR(127),
   custom                      VARCHAR(255),
   subscr_status         VARCHAR(20),
   subscr_id             VARCHAR(20),
   subscr_date           DATETIME,
   subscr_effective      DATETIME,
   period3               VARCHAR(5),
   amount3               DECIMAL(10, 2),
   recur_times           INT,
   times_filled          INT,
   times_failed          INT,
   times_refunded        INT,
   PRIMARY KEY(UID_Register),
   UNIQUE INDEX IDX1_register (UID_member, first_name, last_name, payer_business_name, payer_email, subscr_id, subscr_date));
   
CREATE TABLE IF NOT EXISTS mh2tr_transactions(
   UID_transactions       BIGINT            AUTO_INCREMENT,
   business               VARCHAR(127),
   item_name              VARCHAR(127),
   item_number            VARCHAR(127),
   receiver_email         VARCHAR(127),
   receiver_id            VARCHAR(127),
   address_street         VARCHAR(200),
   address_city           VARCHAR(40),
   address_state          VARCHAR(40),
   address_zip            VARCHAR(20)  NOT NULL,
   address_country        VARCHAR(64),
   first_name             VARCHAR(64),
   last_name              VARCHAR(64),
   payer_business_name    VARCHAR(127),
   payer_email            VARCHAR(127),
   payer_id               VARCHAR(13),
   contact_phone          VARCHAR(20),
   status_address         VARCHAR(15),
   status_payer           VARCHAR(15),
   custom                 VARCHAR(255),
   invoice                VARCHAR(127),
   memo                   VARCHAR(255),
   option_selection1      VARCHAR(200),
   option_name2             VARCHAR(200),
   option_selection2      VARCHAR(200),
   payment_date           DATETIME     NOT NULL,
   payment_status         VARCHAR(20),
   payment_type           VARCHAR(10),
   pending_reason         VARCHAR(20),
   reason_code            VARCHAR(20),
   txn_id                 VARCHAR(20),
   txn_type               VARCHAR(20),
   exchange_rate          DECIMAL(5, 2),
   mc_currency            VARCHAR(5)   NOT NULL,
   mc_fee                 DECIMAL(10, 2),
   mc_gross               DECIMAL(10, 2),
   payment_fee            DECIMAL(10, 2),
   payment_gross          DECIMAL(10, 2),
   settle_amount          DECIMAL(10, 2),
   settle_currency        VARCHAR(5),
   subscr_date            DATETIME,
   subscr_effective       DATETIME,
   period3                VARCHAR(5),
   amount3                DECIMAL(10, 2),
   mc_amount3             DECIMAL(10, 2),
   recurring              TINYINT,
   reattempt              TINYINT,
   retry_at               DATETIME,
   recur_times            INT,
   subscr_id              VARCHAR(20),
   PRIMARY KEY(UID_transactions),
   UNIQUE INDEX IDX1_ppipns (UID_transactions),
   UNIQUE INDEX IDX2_ppipns (txn_id, item_number, payer_email, custom, payment_date, payment_status, subscr_date, subscr_id))   


Title: Re: Treasury Component v2.0.2
Post by: RichRawlings on April 22, 2008, 11:34:27 AM
Thanks for your reply Mick!

Yes, I was in safe mode. I turned safe mode off, and tried to re-install and got the same message. I also tried to manually install database tables and still no luck, but thanks for the help!


Title: Re: Treasury Component v2.0.2
Post by: Mick on April 22, 2008, 12:59:36 PM
Try again with these options:

CREATE TABLE IF NOT EXISTS mh2tr_subscriptions(
   UID_Register             BIGINT AUTO_INCREMENT,
   UID_member               BIGINT,
   first_name            VARCHAR(64),
   last_name             VARCHAR(64),
   payer_business_name   VARCHAR(127),
   payer_email           VARCHAR(127),
   custom                      VARCHAR(255),
   subscr_status         VARCHAR(20),
   subscr_id             VARCHAR(20),
   subscr_date           DATETIME,
   subscr_effective      DATETIME,
   period3               VARCHAR(5),
   amount3               DECIMAL(10, 2),
   recur_times           INT,
   times_filled          INT,
   times_failed          INT,
   times_refunded        INT,
   PRIMARY KEY(UID_Register));

CREATE TABLE IF NOT EXISTS mh2tr_transactions(
   UID_transactions       BIGINT            AUTO_INCREMENT,
   business               VARCHAR(127),
   item_name              VARCHAR(127),
   item_number            VARCHAR(127),
   receiver_email         VARCHAR(127),
   receiver_id            VARCHAR(127),
   address_street         VARCHAR(200),
   address_city           VARCHAR(40),
   address_state          VARCHAR(40),
   address_zip            VARCHAR(20)  NOT NULL,
   address_country        VARCHAR(64),
   first_name             VARCHAR(64),
   last_name              VARCHAR(64),
   payer_business_name    VARCHAR(127),
   payer_email            VARCHAR(127),
   payer_id               VARCHAR(13),
   contact_phone          VARCHAR(20),
   status_address         VARCHAR(15),
   status_payer           VARCHAR(15),
   custom                 VARCHAR(255),
   invoice                VARCHAR(127),
   memo                   VARCHAR(255),
   option_selection1      VARCHAR(200),
   option_name2             VARCHAR(200),
   option_selection2      VARCHAR(200),
   payment_date           DATETIME     NOT NULL,
   payment_status         VARCHAR(20),
   payment_type           VARCHAR(10),
   pending_reason         VARCHAR(20),
   reason_code            VARCHAR(20),
   txn_id                 VARCHAR(20),
   txn_type               VARCHAR(20),
   exchange_rate          DECIMAL(5, 2),
   mc_currency            VARCHAR(5)   NOT NULL,
   mc_fee                 DECIMAL(10, 2),
   mc_gross               DECIMAL(10, 2),
   payment_fee            DECIMAL(10, 2),
   payment_gross          DECIMAL(10, 2),
   settle_amount          DECIMAL(10, 2),
   settle_currency        VARCHAR(5),
   subscr_date            DATETIME,
   subscr_effective       DATETIME,
   period3                VARCHAR(5),
   amount3                DECIMAL(10, 2),
   mc_amount3             DECIMAL(10, 2),
   recurring              TINYINT,
   reattempt              TINYINT,
   retry_at               DATETIME,
   recur_times            INT,
   subscr_id              VARCHAR(20),
   PRIMARY KEY(UID_transactions),
   UNIQUE INDEX IDX1_ppipns (UID_transactions));


Title: Re: Treasury Component v2.0.2 FIXED!
Post by: RichRawlings on April 22, 2008, 03:15:01 PM
Thanks, Mick!

That went down on the database  ;D

I'll be back, going to see if I find other problems in the component, If all is running good, I'll be back to donate.

Thanks for the support!

Rich


Title: Re: Treasury Component v2.0.2
Post by: Mick on April 22, 2008, 06:06:56 PM
Glad we could get it working for you!


Title: Re: Treasury Component v2.0.2
Post by: Dukessa on May 12, 2008, 11:38:31 PM
Hi!

I got the same db issue.
So I tried the last 2 queries you suggested.

The first query worked and created the table, but the second query didnt work.
Should I try to execute the second query the way you suggested it the first time?

Thank you  :)


Title: Re: Treasury Component v2.0.2
Post by: Mick on May 16, 2008, 08:49:38 AM
In order to accurately answer that, I would need to know the error you received when running the query.