.763 to .764 module question :: Zikula Community

Get Zikula 1.3.3!New core, modules & more

Quick Links

Donate Today!Support your Software

Documentationlearn, share & develop

Watch

GitHub Core

Show your support for Zikula! Sign up at Github account and watch the Core project!

GitHub Modules

Forum Activity

mazdev responded to »Hide "Register new account" and change template to 3 col« 07:50 AM
mesteele101 created topic »Zikula 1.3.3 - Site Search 1.5.2 - Unable to turn off plug-ins« 07:48 AM
internetking created topic »password problem« 25. May
mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 25. May
mazdev responded to »Pages 2.5.0 and updating - Page not found« 25. May
mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 25. May
mdee created topic »How to implement returnpage ?« 25. May

» Visit forum | » View latest posts

Zikula Blog

Anatomy of Open Source Projects on Mar 07
Continuous Review on Mar 01
Not Invented Here on Feb 24
How to Contribute Your Code at Github on Jan 13
10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
Submitting Bug Report Tickets That Get Results on Aug 17
Cozi Tricks #1: Syntax Highlighting on Aug 07

.763 to .764 module question

Print topic

**unknown user**

Rank: Registered User

Registered: Mar 16, 2002

Last visit: Oct 21, 2009

Posts: 25
Posted: Feb 13, 2007 - 01:20 PM

I had a module designed for me in the past that worked perfectly in .763. Here recently, I upgraded to .764 and I get the "Error! Sorry! Table creatin failed".

Exact error after attempting to initialize module:

Quote
Error! Sorry! Table creation failed CREATE TABLE IF NOT EXISTS pn_venues_reviews ( pn_venues_reviews.review_id int(11) NOT NULL auto_increment, pn_venues_reviews.review_venid int(11) NOT NULL default 0, pn_venues_reviews.review_uid int(11) NOT NULL default 0, pn_venues_reviews.review_name varchar(100) NOT NULL default '', pn_venues_reviews.review_email varchar(100) NOT NULL default '', pn_venues_reviews.review text NOT NULL default '', pn_venues_reviews.review_status int(1) NOT NULL default 0, pn_venues_reviews.review_date datetime NOT NULL, PRIMARY KEY (review_id), KEY `review_venid` (`review_venid`), KEY `review_isfirst` (`review_isfirst`))

I was curious if there were any changes made from .763 to .764 that could be causing this issue? All the other modules I had initialized fine without a hitch.

Any input would be greatly apprciated.

Thanks for your time!
pnDev

Rank: Softmore

Registered: Jul 16, 2004

Last visit: Oct 21, 2009

Posts: 406
Posted: Feb 13, 2007 - 06:17 PM

Perhaps some buggy code in the upgrade functions.
**unknown user**

Rank: Registered User

Registered: Mar 16, 2002

Last visit: Oct 21, 2009

Posts: 25
Posted: Feb 14, 2007 - 11:46 AM

By this do you mean that the PN upgrade process was buggy? If so, I should clarify.

I went from .763 to .764 by means of fresh install and transferred all my modules over. I also enabled legacy support.

Thanks for your reply!
**unknown user**

Rank: Registered User

Registered: Mar 16, 2002

Last visit: Oct 21, 2009

Posts: 25
Posted: Feb 14, 2007 - 04:30 PM

Ok, well.. after sifting through pinit.php and having very little knowledge of PHP and SQL, I finally found the error in case this happens to anyone else (which is doubtful, my module was created sloppy it seems).

Quote
KEY `review_isfirst` (`review_isfirst`))

The code is asking to make a field, that doesn't exist, a KEY index.

Thats my take on it anyways, I removed the above line and the module initialized. I guess .763 allowed this to happen because I checked my backups and this line has always been there.