Closed (fixed)
Project:
Commerce (Product Display Manager)
Version:
7.x-1.0-alpha3
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Aug 2011 at 14:13 UTC
Updated:
24 Jan 2013 at 21:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
Jason Ruyle commentedNot sure why, but there is an access argument set to a function, I just changed the function till I find out why they did it this way:
Comment #2
adamgerthel commentedThanks! Hopefully the Nylin or Stalski can clarify this.
Comment #3
tyromind commented+1
Comment #4
fonant commentedI've gone with:
and this works fine for me.
Comment #5
Christopher Riley commented+1 Can't see a reason why we need to confuse the users visiting the site with a clearly Administrative function.
Comment #6
minneapolisdan commentedsubscribing
Comment #7
Jason Dean commentedSubscribing
Comment #8
anthonyjhall commentedsubscribing
Comment #9
superstar commentedHere is a patch for this issue:
- corrected permission in commerce_pdm_access_products_tab from "access content" to "access product display manager"
- typo in the comments for the above function
- corrected capitalisation of "Access product display manager" in hook_menu
Comment #10
Jason Dean commentedPatch works fine for me - thanks!
Comment #11
jaymallison commented#9 is a winner! Lets get this committed.
Comment #12
tars16 commented#9 fixed the issue for me as well.
Comment #13
netsensei commentedvote +1 on #9!
Comment #14
jibize commentedPatch on #9 worked for me as well.
Thanks superstar!
Comment #15
summit commentedHi,
I do not see commits from july 20. Is this module still maintained please?
I am looking for a module like this as add on to Commerce_BPC.
Thanks a lot in advance for your reply.
greetings, Martijn
Comment #16
thijsvdanker commented+1 on #9
Comment #17
mariafromatoz commentedYeap, #9 worked for me as well.
Comment #18
ollie222 commentedSuperstar's patch in #9 has worked for me too, thanks.
Comment #19
latulipeblanche commentedTnx superstar , patch #9 worked.
Like@summit I would like to know if this module is still maintained please?
Comment #20
jaymallison commented^ yeah that. It seems this project has been abandoned. It's a total shame considering how vital it is to commerce.
Comment #21
nylin commentedHi guys, I'm looking for maintainers of this module just because I don't have any time for it myself ATM. If there is anyone that would like to become a co-maintainer of the module, please let me know.
Comment #22
latulipeblanche commentedI really would like to help you, but I'm not a developer :(
Comment #23
netsensei commentedThanks! Committed this.
Comment #25
jdln commentedI have the latest version of core and all modules and im still getting this issue.
Comment #26
jdln commentedCould someone provide some instructions for the solution from #4? If I remove the php tags and add it to my template.php file i get a white screen for my site. thanks
Comment #27
globefox commentedHi jdln the patch is applied to the module file not template. See the instructions here for how to apply patches manually. http://drupal.org/node/534548 Easy once they've been explained. Yes, this patch worked for me. I do hope this module gets maintained again.
Comment #28
bogeyman commentedThere is a module named Commerce Auto Product Display which does similar thing like this module. You might want to use it because this module is no longer maintained.
Comment #29
summit commentedHi,
I think now the http://drupal.org/project/inline_entity_form is the way to move forward!
Greetings, Martijn
Comment #30
millzee commentedDoes anyone actually know how to fix this issue which only came about after we updated the core from drupal 7.14 to 7.18.
Comment #31
netsensei commentedThis has been fixed in the 7.x-1.x-dev (development) version. It's waiting to be pushed with a formal stable release. If you really need this fix right now: apply the code in the patch in #9 to your stable module installation.
Closing this for now again.
On a related note: I'm going to take a bit of time to run through the issue queue and revisit bug reports.
Comment #32
netsensei commentedMarking as fixed.