Hi,
I have installed placed the within my modules folder and enabled it form the admin/build/modules however in my form settings which I choose 'select options' then press Add I only see
Label: *
Field Key: *
Description:
Default value: = text box
Customize keys (Advanced) = checkbox
Multiple = checkbox
Allow "Other..." option - checkbox
Text for "Other..." option:
Load a pre-built option list: - dropdown
Use a pre-built list of options rather than entering options manually. Options will not be editable if using pre-built list.
Validation
Mandatory
Display
Listbox
Randomize options
Where do I add in the different options? I do not see the multiple text boxes I can use to enter them in with.
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | options_element_wysiwyg.patch | 777 bytes | quicksketch |
| Screen shot 2010-08-30 at 15.08.15.png | 63.21 KB | Sarah_London |
Comments
Comment #1
quicksketchAre there any JavaScript errors on the page? Options Element may not work with the latest versions of jQuery if you have installed jQuery Update module.
Comment #2
Dubber Dan commentedSame thing is happening for me too and I can't see any JavaScript errors. I'm using:
options_element-6.x-1.1
webform-6.x-3.2
jquery_ui-6.x-1.3
but NOT jquery_update-6.x-1.1.tar
Comment #3
quicksketchI ran into this on one of my own sites, though it was because of an incompatibility with Admin module/Rubik theme. If you can try out the patch at #902474: Not compatible with Admin module or Rubik admin theme and let me know if it fixes the problem for you that would be appreciated.
As it is, I can't make Options Element break otherwise though any combination of jQuery Update/UI. Steps to reproduce this problem from a clean installation of Drupal would be appreciated.
Comment #4
Dubber Dan commentedHave tried that patch and it still isn't working.
My site with the problem is far from being a clean installation, so I'm not sure what you actually want. Are you seriously suggesting I need to do a clean install and then add all the modules I'm using and see where it breaks?
Comment #5
quicksketchOptions Element is working on the sites I have installed it on. So unless I can reproduce the problem, I won't be able to fix it. So yes, in a way that's what I'm suggesting. Another option is to make a database backup, then start disabling modules/themes on your existing site and see where it starts working again. That will help determine the cause, but it still won't help me reproduce the problem.
Comment #6
aiphesi've the same issue on a fresh install whith only webform 3.2, options element, ckeditor...so basic
Comment #7
Dubber Dan commentedAh, that's handy.... Try disabling ckeditor and see if that sorts it
Comment #8
aiphesi've install it on a website whith fckeditor and same trouble, but i've jquery update on it...necessary for ddblock...so i cant choose between 2 modules ! how can i change the jquery version ?
on my test website, after disabled ckeditor, all works, there is no jquery module on this website...so its confirmed that ckeditor and jquery'module cause trouble..
EDIT: on my test website, try with jquery ui 1.8.2 and jquery update 1.3.2 , and all seems to work...allready whithout ckEditor
Comment #9
jburdett commentedI can confirm that it is not jquery. We are currently using fckeditor via the module interface, not the wysiwyg api. If a role is enabled to use fckeditor in an fckeditor profile, options element fails. If the role can not use fckeditor or the fckeditor module is disabled, options element works.
Comment #10
aiphesso the editor like fckeditor or ckeditor use a javascript may cause issue with jquery ..no ?
Comment #11
bayousoft commentedLooks like I am having the same issue with Webform 6.x-3.2. I am using fckeditor 6.x-2.1. With Options element 6.x-1.3 enabled I get a javascript error on a select component edit page.
this.manualOptionsElement is undefined on .../options_element/options_element.js?e Line: 39
If I disable Options element the key value text area displays. Rolling with that for now.
Comment #12
ddyrr commentedI have the same problem with webform, and was able to fix it by commenting out these two lines in the js file:
this.identifier = this.manualOptionsElement.id + '-widget';
this.enabled = $(this.manualOptionsElement).attr('readonly') == '';
That element is not used anywhere else, and there is no text area (it gets set to a textarea that does not exist), so I'm not sure why this is here.
Comment #13
quicksketchBoth properties (identifier and enabled) are used throughout the options_element.js file, are you using the latest version of Options Element?
Comment #14
quicksketchPerhaps FCKeditor is removing the textarea element? That would explain why it wasn't existing. I'd suggest disabling FCKeditor on that particular textarea. Or, I STRONGLY recommend using WYSIWYG module instead, which won't hijack textareas inappropriately like that.
Comment #15
quicksketchI've committed this patch, which will prevent CKeditor and FCKeditor modules from hijacking the textarea used by Options Element, though I'm not sure it's the root of the problem. It's not going to hurt either way.
Comment #16
dlaidig commentedthe patch worked for me. I was using CKEditor and no options appeared. THanks for the patch.
Comment #17
macmaci commentedI am having the same issue as above. I turned off CKEditor and select options works but I need CKEditor on so I turned off Options Element module but would really love to have it on. I am not at all comfortable applying a patch. Do you have any idea of when you might be able to update the module. I would be willing to offer you a donation for your time.
Thanks
Comment #18
howartp commentedI've just come up with a quick fix for this, as I was struggling myself. It will work for everyone, in that it allows Options Element to work, but it will probably prevent your users from using CKEditor when filling in webforms - for me this isn't an issue as anyone filling in the form will be unauthenticated and thus cannot use CKEditor anyway. CKEditor will still work on all your other pages.
In Administer >> Site Configuration >> CKEditor, go down to the Profiles section and edit whichever profile(s) you are using. For me, there's only one, called "CKEditor Global Profile". Expand the 'fields to include/exclude' section. Scroll to the bottom of this box and add a new line which says "*/webform*" without the quotes. This means any path which contains /webform will ignore CKEditor altogether.
(For anyone thinking 'surely it depends whether they are using include or exclude?' - it does, but if they're experiencing the issue being discussed, they are likely to be using exclude; if they were using include the issue would only happen if they had added an include line for the webforms themselves)
If anyone has more time, they should be able to look into which field identifiers the select component pages use and thus tighten the above line up to specific fields.
Peter
Comment #19
quicksketchMarking this one fixed, since I committed #15 quite some time ago. Seems like most people had this problem because of FCK/CKeditor.