Closed (fixed)
Project:
Blog Information
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
13 Oct 2006 at 00:31 UTC
Updated:
13 Nov 2006 at 19:45 UTC
Jump to comment: Most recent file
Comments
Comment #1
mfer commentedok, looks like we have some issues here.... I would like to clear them up quickly.
What database are you using? Once you save it does it display on your blog pages at all? When you load the edit page does it display the old values that were saved?
Thanks... I would like to get this all fixed and working asap and I can't reproduce the problems you are having.
Matt
Comment #2
lennart commentedI am using mySQL 5.
Yes, it displays on my blog pages *until* I go and upload a picture to my profile or some other change.
No, the old values are not displayed after making these changes. The fields are cleared.
Thanks,
Lennart
Comment #3
lennart commentedsorry - I am using mySQL 4 on that site not 5
Comment #4
mfer commentedI can't seem to reproduce this error. Is it still happening after fixing the issue with OG (http://drupal.org/node/89016)?
Comment #5
lennart commentedI applied the patch.
The info *still resets* when going to edit one of the profile(.module) fields - in my case a select list.
I think it has nothing to do with uploading a picture. Sorry for stating that earlier.
It has to do with editing profile fields.
Comment #6
lennart commentedspecifying
Comment #7
lennart commentedThe problem is still there with the newest tarball.
Am I the only one with this problem?
Comment #8
mfer commentedBack from vacation and I can reproduce this. I'm on it.
Comment #9
mfer commentedTry this patch out. It worked to fix the problems with the profile module for me on a 4.7.4 install.
Comment #10
lennart commentedApplied the pacth, but it only partly fixes the problem. Whenever I change a field provided by the profile.module the text in the bloginfo fields as cleared.
Comment #11
lennart commentedIt only seems to happen with the freeform list field. Not the other fields, so maybe we are conering the problem.
Comment #12
lennart commentedWeird. I am not able to reproduce this problem anymore. It only occured the first time I enabled the block for the module. The module was activated all along, though.
Anyway, It seems to have been fixed with the pacth, I think!
Thanks!
Comment #13
(not verified) commented