Zikula Community

Anything input into new fields I create is not being inserted into the database. What might be the trouble?

I searched the forums and Google, but the only info I could find was "where does DUD go and how do I get it out"... I already know where it goes and how to get it out; it's just not getting there.

PN 7.5
PHP 4.3.11
MySQL 4.0.24

Are you sure? Are you looking in the right place?

--
Regards,
Simon

itbegins.co.uk - Zikula Consulting

Please read the Support Guide

Considering there are no rows at all in the 'nuke_user_data' table; considering I've gone so far as to run a search of the entire database for a specific phrase entered into a DUD field; yes, I am fairly sure it is not being stored *anywhere* in the database.

Can you give with details how you create and how you store the information ? Might be something you do (or not do) that is causing the behavior.

I personally have no problem adding new fields and going to my profile and inserting new info on a 0.750.

--
Chestnut !
Support via Private message won't be answered...
http://dev.pnconcept.com
http://www.postnuke-france.org

Admin > User Administration > Dynamic User Data > Add Fields

For instance, tested using:

Field label: _MYTEXT
Data type: text
Length: (empty)

The new field appears in the user account page, with its language definition intact. However, entering any text into the field does nothing upon submit.

This IS an upgrade of an upgrade of an upgrade of an upgrade of PN. However, I assumed that bug was fixed ages ago.

Well... apparently, some of your files might not be exactly up to date.

You might need a little check on the (NS-)YourAccount, (NS-)User and includes/pnUser.php...

--
Chestnut !
Support via Private message won't be answered...
http://dev.pnconcept.com
http://www.postnuke-france.org

That was my first thought, even though whenever I upgrade most any script, I move the old files to a separate directory, as overwriting cannot always be relied upon. I've already checked and even replaced those modules and files, just in case, to no avail.

I have solved the issue on my own, however.

I checked the _user_data table of the problematic old install against a fresh install, and I see that the field names for the ID field are different. The old install is "pn_uda_pid", rather than "pn_uda_id". All works as it should, now.

So, what did I do wrong to keep that table field from being properly renamed during the upgrade process? (I use PN enough on various hosts, with various people, that I'd like to avoid this annoyance in the future.)

You got it... I don't recall exactly when this change occured (probably between 71x and 72x or 720 and 721) but now I remember.

Your site must be old to still have that glitch. :)

It might have happened in an upgrade where it was done "files only" while it needed upgrade script or something like that.

You are probably the first one I see this year and I wouldn't be surprised if you were the last. :wink:

But it is still good to know.

--
Chestnut !
Support via Private message won't be answered...
http://dev.pnconcept.com
http://www.postnuke-france.org

I've been with PN since... well, whatever version was out in 2000. I just looked, and I am registered user #2808 at PN.com, while there is now 72321. So yes, it's an old installation. I told you it was an upgrade of an upgrade of an upgrade.

Do I get a cookie?