Thread

I’m trying to pull custom fields from the logged_in user’s profile.  No custom fields seem to work, but the standard fields do.

{if logged_in}
    {exp:member:custom_profile_data}
        {test_field}
        {member_id}
    {/exp:member:custom_profile_data}
{if:else}
    not logged in
{/if}

The above code renders out a ‘2’—my member_id, but not my custom field (field name is a direct copy/paste, no typo here).  Not sure what I’m missing here.

(Dev box is running v2.1.0; will upgrade soon)

Hi rwbaker,

We are now several iterations of EE 2.x ahead of your installed version. I don’t recall a specific issue with member custom fields in that version but there may have been. Please do upgrade and then test this again.

Cheers

Greg

Thanks Greg. Upgraded to v2.1.3 Build 20110405; same problem.

Hi rwbaker,

The latest version 2.1.3. should be build 20110411. That’s the build I’m testing against and I’m afraid that I can’t replicate this issue. What kind of custom field is this and what are the contents of it? Which addons do you have installed in this site?

Cheers

Greg

Hm, I just downloaded the upgrade last night. Strange.

Third-party modules: Membrr (subscription member management), Solspace’s User
Third-party plugins: Character limiter, ED Image resizer, Low Replace, Twitter Timeline, RogEE Tweetify

I have also tried {exp:user:stats} but no luck either.

This is to be used in a XML template w/ HTTP Auth. However, I’ve also tried it on a standard HTML template with no access restrictions.

I’ve tried a Text Input field with a value of ‘test’ and Select List with options of ‘No’ and ‘Yes’ (all values set to ‘No’).

Field settings:
Is this a required field? - No
Is this field visible in public profiles? - No (tried yes and no)
Is field visible in registration page? - No (tried yes and no)
‘is_field_cp_reg’ (new since the upgrade, but looks like there is a problem with my upgrade) - No

Hi rwbaker,

There may well be an issue with your upgrade. Let’s make sure that you are up and running properly before continuing to troubleshoot the custom field problem. Can you confirm that you followed these instructions when you upgraded?

Cheers

Greg

I followed those directions exactly. The upgrade actually failed twice. After the first failure, i reverted the files / DB and started over. Both times the Wizard page continuously refreshed but never showed progress—i let it sit for 30 minutes before I just deleted the install directory and moved on. Everything seemed to load fine—pages, images, etc.—so I figured all was well.

What do you recommend next?

Thanks
-rich

Just rolled back my install to 2.1.0 and tried the 2.1.3 update again. Same problem—the upgrade wizard just keeps refreshing and never finishes. I let it run for 1 hour. I tried in Chrome and Safari.

Is there any type of upgrade error log for me to track down whats happening?

Hi rich,

Can you tell us a bit about your site please. Is it a large site with many entries?

Because you are using Solspace’s User Add-on they recommend to upgrade that to latest version before attempting an upgrade. Can you do so and try again please?

When you rolled back to 2.1.0 and restored your database, ensure it was restored into a completely empty database. Otherwise there will be duplicate data.

The site is still pretty small—we have just over 1,000 entries.

Not sure what you mean about duplicate data. Before the upgrade, I took a snapshot of the file system and the DB. When the upgrade failed, I dropped the failed database, imported the backup, then reverted the file system. That seemed to work well.

I didn’t notice the User update, hopefully that does the trick.

Please keep us posted, rwbaker. Also, this isn’t the Freelancer license, is it?

@Brandon - Site uses the commercial license.

I updated User to the latest version and tried to upgrade from 2.1.0 to 2.1.3 again. The upgrade still failed—this time once I agreed to the terms of service and clicked the button, it loads a white page with no content (viewed source and there is no HTML, just a blank page). Ever seen this?

Hi, rwbaker.

A blank page can be caused by insufficient PHP memory.

Have you seen: EEWiki:// HowTo Determine Memory Limits

-and-

EEWiki:// HowTo Override Memory Limitations

How much memory is allocated to PHP? If it is less that 64M, can you adjust it?

Can you also turn on debugging in your new index.php file?

You do that by changing the value of $debug to 1.

When you export your MySQL tables, how big is it? Do you have a lot of Pending or bogus users?

Thanks Sue.
I have 128m allocated for PHP. The box itself is 512mb RAM VPS; I could give PHP more if you think it’ll help.
I turned on debugging, but the page after the ‘agree’ page was still blank—no debugging info on that page. I tried the upgrade twice and I got this same result.
The MySQL dump is about 4.5mb, after I cleared the chache
We have 192 users, but no bogus users since all accounts are tied to a valid PayPal acct.

Thanks for any ideas!

That should be plenty of memory.

192 users and 1000 entries shouldn’t be causing this kind of error.

Do you have a way of attempting to upgrade on a local server?

That’s what I’d try next.