Active
Project:
Profile Enforcer
Version:
5.x-1.1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
28 Jun 2007 at 03:02 UTC
Updated:
17 Apr 2008 at 11:22 UTC
Jump to comment: Most recent
Everything is fine if I leave "Other Fields" empty, but once I add something, e.g. "profile_lastname|user/%uid/edit", I get this error:
SQL ERROR: $statement
--------------------------------------------------------------------------------
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') FROM profile_lastname WHERE uid = 3' at line 1
Comments
Comment #1
Anonymous (not verified) commentedThe code appears to indicate that the "other fields" entry is for fields which are in other tables than profile_values. It separates each entry into 3 parts, not the 2 as expected. First part is the name of the table, second is the name of the field in the table, third part is the expected URL.
Try something like
table.field|URL
Comment #2
Joonas T commentedI had the same proplem.
Now I have a nother.
When I conficurate the Profile Enforcer to require info of membership by placing this to the "Other Fields:"
profile_values.profile_member|http://www.parkour.fi/drupal/?q=user
And enable the profile Enforcer block, I get this error message every where on the website.
SQL ERROR: $statementUnknown column 'profile_member' in 'field list'
The profile_member exist in the table by that name.
What am I missing?
Comment #3
Joonas T commentedThe same proplem occur when I place this line to the
profile_fields.profile_member|http://www.parkour.fi/drupal/?q=user
-->
SQL ERROR: $statementUnknown column 'profile_member' in 'field list'
Comment #4
peterd12 commentedI can confirm this bug. The "other fields" option is very misleading. It seems to say that fields you list here are required, but it's actually other custom tables and values that you list are required. How can I make regular profile fields created w/the profile module mandatory? For example, a user I created has 5 empty profile fields but is still allowed access, and the debugger says his profile is complete. Any ideas?
Comment #5
ineffable commentedAny news on this issue?
Comment #6
suydam commentedI haven't had time to address it yet. I think it's an easy fix though....just need to find time to do it. :(
Comment #7
holydrupal commentedThe same problem here!
any one planning to fix this issue!?
Comment #8
suydam commentedI am the only one working on it right now and it's lower in my priority list than I'd prefer.
Subscribe to this post and you'll get a notice when I post a fix.
Comment #9
aznboy commentedsubscribing