2012-06-28, 03:06:31
It's okay :-) I'm just hoping that your problem is actually being sorted with this assistance.
My only reasoning for not wanting to use the custom_field syntax is because I had to fix a slightly messy syntax-related problem for my news stemming from calling both the custom and special fields. That was my own fault though: it could have easily been avoided if I wasn't lazy xD
If custom fields work for you then just use it but be wary of that for now. If you still need to have a default value in place, using the following:
Or for the caching/indexing function:
Both should work in your template files.
My only reasoning for not wanting to use the custom_field syntax is because I had to fix a slightly messy syntax-related problem for my news stemming from calling both the custom and special fields. That was my own fault though: it could have easily been avoided if I wasn't lazy xD
If custom fields work for you then just use it but be wary of that for now. If you still need to have a default value in place, using the following:
Code:
<?php if(return_custom_field('membername')!='') get_custom_field('membername'); else echo 'Default Value'; ?>
Or for the caching/indexing function:
Code:
<?php if(returnPageField(return_page_slug(), 'membername')!='') getPageField(return_page_slug(), 'membername'); else echo 'Default Value'; ?>
Both should work in your template files.