Closed (fixed)
Project:
Classified Ads
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
11 Nov 2008 at 09:08 UTC
Updated:
13 Jul 2009 at 07:50 UTC
Jump to comment: Most recent file
There is all user's Ads are coming in 'My Classified Ad list' link
eg. URL Path:
index.php?q=user/1/ed-classified
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | ed_classified-my-classified-ad-list.patch | 1.29 KB | phdhiren |
Comments
Comment #1
phdhiren commentedI've find out my self this patch to this problem. It works for me.
Comment #2
mcurry commentedThanks for the patch.
This patch doesn't seem right to me; why the line:
?
From what I can see, the argument to the page function should be a user object representing the current user, not an array containing the value '1'... or have I missed something?
Comment #3
phdhiren commentedIt is correct and as per D6 Menu system overview
Instead of %node here it is %user and on 1st argument we get $account value
Comment #4
tomws commentedEDIT: Correction. The patch does solve the first problem below. Looks like I was having a caching issue. Now I just need to get my permissions issue sorted.
I made the adjustments from this patch to the three lines manually, but it doesn't change anything here. I'm still seeing all users' ads on the 'My @name list'. Dropping in some debug output also still shows that $uid == 0 in the body of ed_classified_admin_overview.
I put this right under the $can_edit test at line 319:
Output for authenticated user with 'edit own classified ads' permission (user 5):
Output for admin (user 1):
These are the same results as before making the 3 line changes from the patch.
The initial cause for my looking for a solution is that users with the 'edit own' privileges don't get a link to edit their ads. Attempting to visit the edit page for the ad (/node/##/edit) results in access denied. I'm assuming these problems are related and have the same root cause in the uid handling.
Comment #5
NoFuel commentedPatch not working for me too. Any suggestions?
Comment #6
milesgillham commentedI've tested and I think the patch does work, just have to be sure you've flushed any caches. I'll roll it into the alpha release.
Cheers,
Miles
Comment #7
milesgillham commentedApplied to 6.x development branch.
Comment #8
phdhiren commented@milesgillham: thanks applying patch to dev branch.