Flexinode upgrade problems
| Project: | Flexinode |
| Version: | 4.7.x-0.3 |
| Component: | flexinode.module (core) |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Hey there,
As promised I started testing a flexinode upgrade from version :
// $Id: flexinode.module,v 1.77.2.1 2006/08/22 12:11:32 ber Exp $
To the latest version 4.7-0.3
I have noticed two problems at this point in the upgrade:
Values are not passed in the upgrade for the following fields:
dropdown menu: values have been erased, entering them again in the content type settings seems to have fixed the problem, as the data reappeared once the values have been inserted again in the field settings, which was empty after the upgrade.
My content type had a taxonomy term link attached, it does not link to it anymore on the content. Has thepath to get the taxonomy changed? We are using a custom theme for the content type so it's possible that we should change how we display the taxonomy field??
here is the code used for the taxonomy field and another dropdown who does not seem to work in the latest version:
<div id="flexifield_prop"><b>Race principale : </b><?php if ($terms): ?>
<?php print $terms; ?>
<?php endif; ?></div>
<div id="flexifield_prop"><b>Race secondaire :</b>
<?php
$flexinode = flexinode_load_field(25);
print $flexinode->options[$node->flexinode_25];
?></div>So I guess the content is still assigned to the taxonomy, but how to pull it in this latest version.
A third field that is empty after the upgrade, is the "Race Secondaire" field. Again, I'm not sure if it's because there is a problem in the upgrade or it's if the code we used to pull the info is not adequate.
Overall, the upgrade went smoothly, and most of the fields seem to work, I have still to test upgrading the image fields tho.
I'll keep in touch to give more feedback about the image fields, would yo be so kind as to comment on the small issues I encountered here?
Thanks,
Patchak
#1
Some infos about the "Race secondaire" field. It is a dropdown that had values added directly in the db,and not using the admin interface, maybe it's related to the fact the the values have not been transfered??
I'll ask my partner for more details about this field, to giveyou details on what he did to import the values.