Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.go to admin > content management > forum.
create forum.
click on edit forum: it doesn't work.
| Comment | File | Size | Author |
|---|---|---|---|
| #18 | forum_22.patch | 1.25 KB | eaton |
| #10 | forum.module-cannot-edit-forum_0.patch | 722 bytes | paranojik |
| #8 | forum.module-cannot-edit-forum.patch | 740 bytes | paranojik |
Comments
Comment #1
pwolanin CreditAttribution: pwolanin commentedYes- I see the same bug. Probably a lingering effect of the recent admin interface upgrade.
Comment #2
pwolanin CreditAttribution: pwolanin commentedseems to be something lacking in function forum_form_forum($edit = array()).
Comment #3
paranojik CreditAttribution: paranojik commentedThe arg() problem again....
Comment #4
beginner CreditAttribution: beginner commentedAre you sure that's the right patch?
The problem described is in admin/content/forum, and you patch modifies the /forum menu.
???
Comment #5
paranojik CreditAttribution: paranojik commentedyeah, I'm sure. I tested it. You have to look at the code the patch doesn't include....
Comment #6
paranojik CreditAttribution: paranojik commentedOMG. I'm sorry beginner, I guess it's me who should take a look again. Hope this is the right one....
Comment #7
paranojik CreditAttribution: paranojik commentedok now! It seems like the issue tracking sistem keeps linking to the already uploaded patches.... I changed the name of the patch now...
Comment #8
paranojik CreditAttribution: paranojik commentedthis is my last attempt to upload the patch...
Comment #9
beginner CreditAttribution: beginner commentedIt seems the tracker is having issues of its own :).
Can you confirm that patch #8 is the right one?
it seems it isn't, because it doesn't work for me.
Also, I had to manually apply the patch: can you provide standard unix patches (i.e. not with ^M end lines).
Comment #10
paranojik CreditAttribution: paranojik commentedconverted (sorry for that). It sure works for me (editing forums and containers).
Comment #11
beginner CreditAttribution: beginner commentedok, this patch applies cleanly, and it works (I may have made a mistake when applying manually the previous one).
Code change is simple.
Thanks.
Comment #12
beginner CreditAttribution: beginner commentedComment #13
drummcommitted to HEAD.
Comment #14
(not verified) CreditAttribution: commentedComment #15
beginner CreditAttribution: beginner commentedthis bug has reappeared, though the cause may be different.
Comment #16
eaton CreditAttribution: eaton commentedOn a clean HEAD I just walked through the process of enabling forums, adding a container, and adding a new forum. No hitches.
Can you explain the steps you took to reproduce the error?
Comment #17
beginner CreditAttribution: beginner commentedyou have the list of forums/container here:
?q=admin/content/forum
try editing any container/forum:
?q=admin/content/forum/edit/forum/4
?q=admin/content/forum/edit/container/8
The page simple prints 'array'.
Comment #18
eaton CreditAttribution: eaton commentedGood catch. This should do the trick.
Comment #19
beginner CreditAttribution: beginner commentedThe patch failed to apply for me.
Is this patch compatible with linux (line endings)?
Comment #20
webchickPatch applies fine for me, and solves the problem stated.
@beginner: Yes, there are CRs in the patch, but a more modern version of patch deals with them just fine.. I recommend you update.
Comment #21
beginner CreditAttribution: beginner commentedApparently I do have the latest version, so I couldn't upgrade:
$ patch -v
patch 2.5.9
http://www.gnu.org/software/patch/patch.html
ftp://ftp.gnu.org/gnu/patch
Comment #22
Dries CreditAttribution: Dries commentedCommitted to CVS HEAD. Thanks.
Comment #23
Dries CreditAttribution: Dries commentedCommitted to CVS HEAD. Thanks.
Comment #24
(not verified) CreditAttribution: commented