Closed (fixed)
Project:
Flexifilter
Version:
6.x-1.2
Component:
Code - Misc
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Apr 2008 at 14:53 UTC
Updated:
15 May 2010 at 04:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
scor commentedthis should have been fixed in the dev version. Are you sure you are using the latest dev version and that you ran update.php?
Comment #2
scor commentedwill be fixed once http://drupal.org/node/235039#comment-810199 is done.
Comment #3
rovoI'm using 6.2 and the latest dev version, ran update.php; and still get the access denied message. Is there something else I should do? I'm not sure where to implement the above mentioned code. Thanks
Comment #4
siliconmind commentedjust edit flexifilter.module file and replace flexifilter_menu() function with this code:
don't forget to add this:
Comment #5
siliconmind commentedscor, i am sure :)
just checked filedates.
flexifilter.info is dated April 15th so i'm pretty sure it's one of the latest. but flexifilter.module - the one that implements hook_menu() is dated way back to Feb 29th :/
Comment #6
cwgordon7 commentedYes all this stuff is already fixed in HEAD, I'm experiencing CVS difficulties, grr...
Comment #7
rovoThe above code worked for me, thanks.
Comment #8
cwgordon7 commentedI have fixed several CVS issues, the code already in HEAD should now be available in the dev release.
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #10
sibidiba commentedStill not in the release version.
Mentioned patch seems functional, but new error message appears if I edit a filter, and click on preview:
warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'flexifilter_filter_preview_form' was given in /home/czigola/public_html/online/includes/form.inc on line 358.
Comment #11
cwgordon7 commented..yeah. When it's stable enough.
Comment #12
wayland76 commentedCan I recommend creating a flexifilter 6.x-1.1-rc1 or even a flexifilter 6.x-1.1-alpha1? And setting it so that it appears on the front page?
Comment #13
Flying Drupalist commentedIs the dev version as unstable as warned? I'm looking forward to a fix of this issue.
Comment #14
arhak commentedsubscribing
Comment #15
icouto commentedPlease note, that the current rc1 version is from January '08, and still throws the error mentioned. Should perhaps the 1.1-dev version be listed in the front page, as a '1.1-rc2'? The currently listed rc1 - which is 'recommended' for D6 - is actually unusable with the latest D6.4, because of this error...
Many thanks in advance! :-)
Comment #16
chasz commented+1
Comment #17
Antinoo commented+1
Comment #18
arhak commented+1
Comment #19
Roi Danton commentedCode of post #4 (http://drupal.org/node/247416#comment-811270) works. It is necessary that the current rc version gets this update. Marked as critical because the current version isn't usable without modification.
Comment #20
avpadernoComment #21
cwgordon7 commentedThis weekend. I promise. Now stop messing with the issue queue, please.
Comment #22
avpadernoI am not messing the issue queue; I simply changed the issue title to something more significant.
Create a 6.x-1.1 release could be a title for a feature request, not a bug report; as the issue described here is exactly the access denied problem caused by an incomplete implementation of
hook_menu(), I titled the issue Access denied for UID 1.Giving to the issue report a wrong name will cause other people to report the access denied issue again, and again simply because they will not see any issue which reports about that.
Comment #23
cwgordon7 commentedBut its category is set as "bug report". That seems pretty self-explanatory to me.
This is actually not the wrong title, believe it or not. There were multiple issues with the present release, that eithere were already fixed or still need to be fixed in the dev version and an updated release needs to be published for them, too. Renaming this issue to the specific bug you encountered does not help me in my organization here; the more organized I am, the faster bugs get fixed, the faster the new release gets out there. I promised a release for this weekend, and I intend to live up to my word. But please, leave the issue title reflective of the actual issue here. The issue is not that I have to solve the access denied for uid 1 stuff; it's that I need to reverse several bad cvs commits to the wrong branch and re-commit them to the right branch and tag everything properly.
Comment #24
avpadernoAn issue title is not thought to be used by the maintainer to organize better the work to do on a project.
The title helps who wants to report an issue he found with a module, without to write an issue report for an already reported issue; or it can be used by who can be interested in the use of the module, and wants to check first if there are any problems using the module.
The title doesn't reflect the actual issue which is the access denied problem that happens with the last releases of Drupal 6.
It seems that the intent is to hide that there is such a problem with the module; there was another issue titled Access denied for UID 1 but first it has been reported like fixed (which is not true), and then reported like duplicated.
Comment #25
arhak commented+1 for Kiam, it makes a lot of sense, since a new release should be issued as a "task" which is different for the issue to be followed (whether it's fixed or not)
Comment #26
avpadernoI think that the next release could rather difficulty be called 6.x-1.1.
It would be better to fix the problem introduced with Drupal 6.2, and release a 6.x-1.1-rc2; only after that, a version 6.x-1.1 can be planned.
Comment #27
justindavis commentedIs there an estimated date planned for this next bug-fix release? I can't find any recent commits in the CVS repository.
Comment #28
cwgordon7 commentedCommitting a few other patches and then releasing a new release candidate (not at 6.x-1.1 yet, sorry).
Comment #30
Michali commentedThis is an issue again. I'm trying to make Flexifilter (version 1.1) work with Drupal 6.15, and got the Access Denied error. The solution described here fixed it.
Comment #31
marcvangendThis is an annoying bug. I don't quite understand why there still isn't a proper version released. Here is a patch against 6.x-1.1.
Comment #32
cwgordon7 commentedMy understanding is that this isn't a problem on the development branch. If someone can confirm that development branch works for them, I'd be happy to create a new official release for it.
Comment #33
Roi Danton commentedThe 6-1 branch contains the fixes, however
1) There is no release for 6-1 branch at do.
2) When browsing the CVS repository one has to know that 6-1 is the newest and not 6-2, Main or Head. For most users this will be confusing.
So create a release for the 6-1 branch or create a 6-1.2 tag of the 6-1 branch, please.
Comment #34
TripleEmcoder commentedSubscribing and confirming patch from #31 works.
Comment #35
larowlanI can confirm the DRUPAL-6--1 branch works fine when checked out from CVS but the release on the project page does not.
Comment #36
Frank Leith commentedI waited for some month's now but the version on the project page is still broken. Reading the last updates I understand that development version is working fine. Can someone explain to me how I can download that version?
Comment #37
Roi Danton commentedDownload these files: cvs repository Flexifilter branch 6.1.
Comment #38
Frank Leith commentedI don't get a working version using the development versions or the patch. Maybe I am doing something wrong. Can anybody put a full working module somewhere online. This project seems to be without a maintainer.
Comment #39
ianchan commentedsubscribe
Comment #40
cwgordon7 commentedThis has been fixed for a while on the development release. In addition, this is fixed in the latest release.