Welcome, Guest
Username: Password: Remember me
Forgot your password? Forgot your username? Create an account
Forum
Debug
Closed tickets.
[FIXED] sandbox error caused by default value.
  • Page:
  • 1

TOPIC:

[FIXED] sandbox error caused by default value. 14 Aug 2012 15:51 #3148

FYI: (this only for information already fixed)

Following errors were found when running in sandbox at "install step".
(I prefer not to dump the full message to the forum)
Invalid default value for 'boxsku' SQL=CREATE TABLE IF NOT EXISTS `[PREFIX]demo5021_box` (
I keep the full message in a safe place if you need it let me know.
The source of the problem is due that the default field value is longer than the admitted length. :silly:

JInstaller: :Install: Error SQL DB function failed with error number 1067
There was an error installing the package

PS.:
the dialog box: report to our team is not working.
The following user(s) said Thank You: admin

Please Log in or Create an account to join the conversation.

Last edit: by e-struct.

Re: sandbox error caused by default value. 14 Aug 2012 18:04 #3157

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
Oh yeah, of course, thanks.


PS : In reallity, all the fatal issues are stored in debug, I should simply remove this button 'report to our team' because it send it already, and store it automatically by type of issue, and by user.

I will solve this when I can.
Coding is now a piece of cake

Please Log in or Create an account to join the conversation.

Re: sandbox error caused by default value. 15 Sep 2012 15:16 #3662

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
Fixed
Coding is now a piece of cake

Please Log in or Create an account to join the conversation.
  • Page:
  • 1
Forum
Debug
Closed tickets.
[FIXED] sandbox error caused by default value.
Time to create page: 0.084 seconds
“
”

I jumped and started to work on a demo component... but 2 days later this demo component became the real component. I just showed today the end result to my customer and he turned to me and said... "this is more than I expected"... All of this is because Cook did cut about 70% of my work and provided me more ways to improve the usability of the component. The end result was 17 tables all related between than to generate a full dashboard for the travel agents. Thanks for Cook developers for such great tool. This component would not be possible to be done at short time with all the features in it
Griiettner (Forum)  

Get Started

Log In Sign In