I'm working locally, so I don't know if that has any bearing on this:
delegator_admin_list_form() at one point is busy generating an $actions array. $actions contains all the individual operations that can be taken on a given task handler. These are then passed to theme_ctools_dropdown() which passes the $actions array through delegator_admin_make_dropdown_links() on the way. delegator_admin_make_dropdown_links() calls through $actions formatting them in such a way as to save the key to each action as the url to the accompany the action. These, however, are not unique, and are quite simple (e.g. 'clone'). Thus we would end up with website.com/clone which is not what I think is the intent here.
This is new to me and I've not yet tracked it down to what SHOULD be happening. There's a bit of magic in the menu system I'm not pretending to understand yet, so I'm just filing what I perceive to be a bug. (A very annoying bug as it prevents me from altering task handlers after they've been created... or deleting them or, or...)
Let me know how I can help.
Comments
Comment #1
merlinofchaos commentedThe href on these actions is not actually used; if javascript is not enabled then those links are behind a display: hidden; if javascript is enabled, then the javascript takes over and puts the href into the invisible form widget and clicks an invisible button for you.
Comment #2
chawl commentedI am not sure here is the right place but we have somewhat a related issue anyway. We are on Drupal 6.9
Delegator is definitely needed for Panels 3 Page functionality but when enabled, all textarea fields get "-1" suffix somehow like "edit-body-1", "edit-log-1" etc. instead of "edit-body" etc.
This causes major problems in our case that even native teaser.js (expecting no suffix I think) can not find the textarea properly and causes to fail almost every bit of JS on the page, moreover you can not save the contents of the textareas with JS errors show on Firebug. Though if you click preview, textareas lose their suffixes, all JS's restore back, and you can save succesfully thereafter.
WYSIWYG editors jumbles things more that if you configure them to work with "-1" suffixes, you think that you wrote a whole page of content till you save and see a page with a title only, cause only saveable textarea is "edit-body" according to Drupal I think.
Something unhappy happens with node/%node/edit overrider I'm afraid, fortunately this can not override preview pages then permitting to save the node contents as a temporary workarond.
Sorry if this has no correlation, but I'd like to report anyway as Panels Page functionality is a must for us. Delegator causes this without Panels is installed anyway.
Thank you.
Comment #3
merlinofchaos commentedOk, figured out what was duping the form IDs and checked in a fix.
Comment #4
chawl commentedI checked both with text mode and XStandard WYSIWYG editor, thus I confirm this major problem disappeared indeed, despite there are some JS issues still persisting.
Thank you so much for your fast consideration.
Comment #5
merlinofchaos commentedCan you tell me what JS issues still persist?
Comment #6
chawl commentedActually I filed a new issue on http://drupal.org/node/370487
I hope that is not a false alarm and helps in a constructive way.
Comment #7
summit commentedHi,
I think my bug is complementary to this one, because you also refer to the ids, so setting this bug report to active again.
Trying to get to the cache settings on admin/build/delegator/[panel_name]/[panel_name]_panel_context/content I got the following on the inside blue/white screen:
On all content panel-panes I got
Hope this bugreports helps you and that this is complementary. Otherwise sorry for setting this on active again.
Greetings,
Martijn
Comment #8
summit commentedHi Earl,
I made a new issue report about this http://drupal.org/node/372745 so setting this back to fixed.
Greetings,
Martijn
Comment #9
leanazulyoro commentedI have that same issue... when delegator is enabled all fields get a "-1" suffix ... you said you fixed it merlinchaos, but where? I have the alpha2 release... should I go for 6.x-1.x-dev?
Comment #10
merlinofchaos commentedYes, there hasn't been a new release since this was fixed.