I'm trying to add some new fields to some new content types I've created. All seems fine, and I don't get any error messages when doing so, but the fields are not visiable on edit forms or elsewhere....

Comments

ultraBoy’s picture

Just now I had the same problem, seems like db schema upgrade fixed the issue. I just runned .../drupal-cvs/?q=flexinode/upgrade . You can try this also.

pulpzebra’s picture

Getting same error, but since I am a bit new to Drupal Community I just can't figure out how to search for the upgrade. Could you please be a little more explicit? thanks

Robardi56’s picture

Same problem here, wish to know how to fix this.

Thanks

RayZ’s picture

I believe the correct way to upgrade the database schema is:

http://example.com/?q=flexinode/update

as opposed to

http://example.com/?q=flexinode/upgrade

Bèr Kessels’s picture

simply updating does not seem to help.

usharf’s picture

I believe the correct way to upgrade the database schema is:
http://example.com/?q=flexinode/update

Can you explain this please? I'm not sure I understand. Is this something to run from within my drupal installation?

Bèr Kessels’s picture

Assigned: Unassigned » Bèr Kessels
Priority: Normal » Critical
Bèr Kessels’s picture

Status: Active » Fixed

fixed in HEAD. It was a really odd issue on the erronously tagged 4.7

I removed the 4.7 branch.

Let us only tag 4.7 when it is *stable*.

Ber

Mojah’s picture

To clarify for anyone trying to figure this out...

I was running 4.7 b4 then upgraded to b5 and experienced the problem of not being able to add fields to a new content type. I downloaded the latest release of flexinode and replaced the flexinode.module file with the one from cvs...

Here's the link
http://drupal.org/files/projects/flexinode-cvs.tar.gz

It works fine now.

bryan kennedy’s picture

Agreed Ber. This version of flexinode seems to have many problems in 4.7 that are pretty critical still.

Anonymous’s picture

Status: Fixed » Closed (fixed)