Needs review
Project:
Premium content
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Mar 2012 at 00:05 UTC
Updated:
29 Jun 2014 at 21:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dgtlmoon commentedComment #2
miklLooks good to me.
Comment #3
dgtlmoon commentedcomitted
Comment #5
rurri commentedThis patch needs some work. While it correctly causes the error message to disappear it breaks the default premium type selection for the new node.
It also hides the fact that there is a bug in the way that the value for the premium select box is being selected.
The following code seems to fix both of these problems:
Comment #6
dgtlmoon commentedcan you provide as a patch?
Comment #7
yoran scholiers commentedThis is still a issue, or am I wrong?
I ask this because I get the same notice when I'm creating a node.
Comment #8
Anonymous (not verified) commented#5 fixed the problem for me, fwiw
I was getting the following errors on the add content form, but no longer there, and the premium_content level that the content type is set to default to is appearing as it should:
Comment #9
vparfaniuc commentedSince the latest version of the module still has this issue, here is a patch which fixed the error on my projects
Comment #10
dgtlmoon commented@vparfaniuc code style has broken indentation
Comment #11
pjcdawkins commentedComment #12
pjcdawkins commentedTrimmed irrelevant changes