Your username here MUST MATCH your XenForo username (connected to your XF license).

    Once you have registered here, then you need to start a conversation at xenforo.com w/Bob and provide the following:
    1. Your XenForo License Validation Token
    2. The Domain Name associated with the License
    NOTE: Your account will be validated once ALL requirements are verified/met. Thank you for your patience.

Fixed SQL Error

Not open for further replies.


SC Premium
UBS Premium
When updating week name on this page:

Screen Shot 2012-11-27 at 1.24.26 PM.png

Server Error
Mysqli statement execute error : Data too long for column 'week_name' at row 1
Zend_Db_Statement_Mysqli->_execute() in Zend/Db/Statement.php at line 297
Zend_Db_Statement->execute() in Zend/Db/Adapter/Abstract.php at line 479
Zend_Db_Adapter_Abstract->query() in Zend/Db/Adapter/Abstract.php at line 632
Zend_Db_Adapter_Abstract->update() in XenForo/DataWriter.php at line 1607
XenForo_DataWriter->_update() in XenForo/DataWriter.php at line 1576
XenForo_DataWriter->_save() in XenForo/DataWriter.php at line 1381
XenForo_DataWriter->save() in NFLJ/Pickem/ControllerAdmin/Week.php at line 74
NFLJ_Pickem_ControllerAdmin_Week->actionSave() in XenForo/FrontController.php at line 310
XenForo_FrontController->dispatch() in XenForo/FrontController.php at line 132
XenForo_FrontController->run() in /home/sec/www/admin.php at line 13
field is only char(20). If you want longer weeknames, you will need to change the field type for the week_name field on the xf_nflj_pickem_week table. You know how to do that right? simple with phpMyAdmin.
Im going to change this in the next version (which should be out today). Going to change it to a varchar(50) and change the DW to throw an error @50 instead of 100 (I had the dw set @100 instead of 20, thats the the dw (datawriter) didn't throw an error).

I had it set low because the length of the title effects the layout in certain places (like the leaderboard) as well as widgets and blocks that are in this next version.
Not open for further replies.