inherit
Peabrained Codebreaker
107114
0
Mar 11, 2020 7:47:27 GMT -8
Boy_Wonder
6,249
July 2007
natzy24
|
Post by Boy_Wonder on Dec 11, 2016 11:19:06 GMT -8
You can run the plugin key get() command in the console at any time. No need to do a console log. Apparently its showing just as 'undefined' - would this mean for whatever reason the key isn't being set? How do I bugfix why the key presumably isn't being set?
|
|
#eb7100
33409
0
1
Nov 24, 2024 4:27:37 GMT -8
Brian
48,130
November 2004
smashmaster3
|
Post by Brian on Dec 11, 2016 11:34:00 GMT -8
You can run the plugin key get() command in the console at any time. No need to do a console log. Apparently its showing just as 'undefined' - would this mean for whatever reason the key isn't being set? How do I bugfix why the key presumably isn't being set? That means it isn't being set for the item you're currently viewing. get() will always automatically fill in the object ID with the ID of the conversation you're currently viewing. If multiple conversations exist on the page (for example, in your inbox) it's not going to fill it in automatically and you have to supply the conversation ID. I have no idea if you're still using a conversation key or a message key so whether or not you need to supply an object ID is up in the air. $('input[type="button"][value="Create Message"]') isn't targeting anything because no elements match so chances are the key isn't being set because the click event isn't being assigned to the button. The input type for that button is submit rather than button.
|
|
inherit
Peabrained Codebreaker
107114
0
Mar 11, 2020 7:47:27 GMT -8
Boy_Wonder
6,249
July 2007
natzy24
|
Post by Boy_Wonder on Dec 11, 2016 11:36:02 GMT -8
Apparently its showing just as 'undefined' - would this mean for whatever reason the key isn't being set? How do I bugfix why the key presumably isn't being set? That means it isn't being set for the item you're currently viewing. get() will always automatically fill in the object ID with the ID of the conversation you're currently viewing. If multiple conversations exist on the page (for example, in your inbox) it's not going to fill it in automatically and you have to supply the conversation ID. I have no idea if you're still using a conversation key or a message key so whether or not you need to supply an object ID is up in the air. $('input[type="button"][value="Create Message"]') isn't targeting anything because no elements match so chances are the key isn't being set because the click event isn't being assigned to the button. The input type for that button is submit rather than button. I'm using message - however I suspect that what you've shown is the reason why (I don't know how I missed that!). Edit: I now got an error code 2 but it disappeared before I could copy the full error code out -goes to see what that means-
|
|