I created a long text field and attached it to a menu link. On the edit menu link page, I type some text into the field. Drupal msg says the data is saved, but when I go back to the edit form it isn't there. The text is not saved. It does not appear that power link is saving any field contents. Nothing in the Drupal log or in the apache error log to indicate why. I tried both 7.x-2.0-beta2 and 7.x-2.x-dev.

Comments

weri’s picture

weri commented
Title: Data not saved » Power Menu field entity data not saved

With the change of the bundle names in 7.x-2.0-beta2 there was a problem with a overlapping form name. I fixed this in the newest dev version (2013-Mar-29).

Please test the functionality and give me some feedback. When everything works fine, i release a new beta version.

weri’s picture

weri commented
Status: Active » Fixed
chrisakeley’s picture

chrisakeley commented

Testing looks good. I tried to save data from several field types and they all succeeded. Thanks for the quick fix!

mealeyst’s picture

mealeyst commented

Utilizing the Power Menu module on my local site on the "Main Menu" menu. The fields are saved in the Menu List area, but the menu items didn't appear to save.

I went into the power_menu_fields menu and I noticed that the fields were being saved however, the bundle name had been changed from main_menu to main-menu. *Note this is only on the Menu Items, not on the menu in general hence why the value was showing in the Menu List area.

I did a dsm($bundle_name); in the area just below the EntityFieldQuery and the name is being printed out as "main_menu", so somewhere along the line the underscore is being changed to a dash. I am not sure if this is so much an issue with the Power Menu module, but it is affecting usability.

weri’s picture

weri commented

Have you used the newest dev version? Please update to the power_menu 7.x-2.0-beta3 and proceed update.php.

The bundle name has to be changed to underscores in case of the field name handling and problems with the features module.

mealeyst’s picture

mealeyst commented

Just an update:

I downloaded and installed the latest module version and tried it out and the error still seemed to be occurring, but after pulling a fresh copy of our site from our repo and setting up the module again the issue appeared to stop. This could potentially more than likely a configuration issue on my end.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.