Not able to save badges
Sagar Ramgade - February 11, 2009 - 12:40
| Project: | User Badges |
| Version: | 5.x-1.4 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Sagar Ramgade |
| Status: | closed |
Jump to:
Description
Hi...Great module, read the description and fits my needs.
I installed the module and activated it....I uploaded an image and tried creating a badge but the badge is not getting saved.The error message which i received is " There was a problem saving the badge information into the database."
Can anyone help me on this error message, tried uninstall and reinstall, public download method active and dropped the tables and reinstalled nothing happened,,,,same issue.
Any help will be truly appreciated.
#1
The user_badges_badges table does not appear to be created during installation. At the end of the SQL query in user_badges.install, there is an extra comma (,) on line 33 following
href VARCHAR(80) default ''. Removing the comma and running the installation places the table back into the database.#2
Patch to fix, problem really in comma
While issues still without files
Index: user_badges.install
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/user_badges/user_badges.install,v
retrieving revision 1.1.4.6
diff -u -p -r1.1.4.6 user_badges.install
--- user_badges.install 6 Jan 2009 17:48:17 -0000 1.1.4.6
+++ user_badges.install 19 Feb 2009 06:53:39 -0000
@@ -30,7 +30,7 @@ function user_badges_install() {
name varchar(50) NOT NULL default '',
image varchar(80) NOT NULL default '',
weight int(2) NOT NULL default '0',
- href VARCHAR(80) default '',
+ href VARCHAR(80) default ''
)");
db_query("CREATE TABLE {user_badges_product} (
#3
hi, thanks all removed that extra comma on line in 33 resloved....great its working now....cheers
#4
hi, thanks all removed that extra comma on line in 33 resloved....great its working now....cheers
#5
Hello! Sorry for being away but I have been very very busy lately.
This issue is fixed on dev version of Drupal 6 release.
Thank you.
#6
Automatically closed -- issue fixed for 2 weeks with no activity.