By slimandslam on

It's hard to tell if flexinode is ready for Drupal 4.7.2 or not. On the one hand, it has a lengthy list of
bugs. On the other hand, I downloaded the latest CVS snapshot:
http://ftp.osuosl.org/pub/drupal/files/projects/flexinode-cvs.tar.gz

And it seems to basically work ok.

But, after only a bit of use, I find that dropdown menus don't provide me with any way to fill them in and I get this error in my logs:

Invalid argument supplied for foreach() in /web/public/modules/flexinode/flexinode.module on line 576.

Is this software ready for 4.7 or not?

J

⋅ Categories: Drupal 4.7.x

Comments

Poolio’s picture

Poolio commented

I haven't tried the cvs version, but the 4.7 version works perfectly on my site which is running 4.7.2

Poolitics

slimandslam’s picture

slimandslam commented

Have you been able to add drop-down menus? That doesn't work for me.

J

Poolio’s picture

Poolio commented

I could only get drop-downs to display the number of the selected choice, rather than the selected choice itself.

I dealt with that by using conditional statements in my flexinode templates.

Poolitics

Carlos Miranda Levy’s picture

Carlos Miranda Levy commented

On 4.7.2 works fine.
I don't remember if I installed the 4.7 or the cvs version, although I guess it would have been 4.7

------
Con paciencia y calma,
sube un burro a una palma

linda setchell’s picture

linda setchell commented

Hi -

I'm running 4.7 and the flexinode is throwing errors if I try to enter content into the new content type I created. So for example I created a content type called features. When I click on create content/features the following error is thrown:

* warning: Invalid argument supplied for foreach() in /home/eggplant/shared_drupal_modules_4.7/flexinode/flexinode.module on line 571. * warning: Invalid argument supplied for foreach() in /home/eggplant/shared_drupal_modules_4.7/flexinode/flexinode.module on line 571.

It used to throw the line 576 error mentioned above, but we fixed that and now it's throwing a new error.

Based on other discussions, I'm wondering the following:

1. Does flexinode work for 4.7 or only 4.72?
2. I saw mentioned in another discussion the option of using the CCK module. Would that be a better choice at this point? Is it full of bugs like the flexinode module?
3. Has anyone else had this problem and can you tell me how to fix it?

thanks!

linda

Bèr Kessels’s picture

Bèr Kessels commented

«On the one hand, it has a lengthy list of bugs. On the other hand, the latest CVS seems to basically work ok.»

That is it. Nothing I can add to it.

The main reason I took over management of this module is that is was rather unmaintained for a while. During that time a lot of things went askew, including someone who actually released a completely non-working, and unstable 4.6+ flexinode with all fields (some fields were even only 4.5) as 4.7!
We are still trying to recover from that mistake (most bugs are related to fields that should never have been released). I un-release all fields that have critical bugs. But I have only limited time!

Please, please help: Test patches, close old bugs and comment on feature request, or close old feature requests: http://drupal.org/project/issues/flexinode

Bèr
---
Professional | Personal
| Sympal: Development and Hosting

kdecapite’s picture

kdecapite commented

I realize this is an old thread but maybe someone can help me. I'm trying to install Flexinode 4.7 (on Drupal 4.7.2) but the only database script available is the 'fexinode.install' file. How do I execute this file? I must be missing something obvious and the Flexinode installation instructions don't even talk about the database installation!

Many thanks...

Neil Adair’s picture

Neil Adair commented

Drupal 4.7 uses .install files to run the mysql set-up automatically. When you enable the module in administer >> modules the db tables are created.

kdecapite’s picture

kdecapite commented

NeilAdair, thanks for the information, that's what I thought was supposed to happen. However, when I try to enable the module, Drupal returns the following error:

"user warning: Table 'drupal_4-7-2.flexinode_type' doesn't exist query: SELECT * FROM flexinode_type in C:\path\to\drupal-4.7.2\includes\database.mysql.inc on line 120."

When I check my database, there are no new tables. Sorry to take this thread off-topic, feel free to contact me directly if you have any other ideas to share. Many thanks again!

- Kevin

venkat-rk’s picture

venkat-rk commented

In my opinion, the relative abandonment of flexinode 4.7 (despite Ber's valiant effort) in favour of cck is one of the most of the unfortunate decisions relating to drupal in recent times. It is in line, though, with the overall drupal philosophy of not caring much for backwards compatibility. I wonder if even 5% of the time invested in cck would not have corrected all the problems in flexinode and prepared it for 4.7.

Before anyone jumps on me for criticising drupal or the developers, please take a moment to run a search on flexinode 4.7 related problems. The bottomline is that people who invested heavily in flexinode 4.6 have been left high and dry. I have personally spent a month and a half shuttling between flexinode cvs, flexinode 4.7 and the so-near-yet-so-far CCK. I think I even offered to sponsor/co-sponsor development, but nothing came of it.

dtabach’s picture

dtabach commented

I have lots of flexinodes and corresponding node-flexinode-x.tpl.php's in my site (which took much more than a month and a half to be created), and now I feel like an orphan. Upgrading to 4.7 gave me a lot of new functionalities, but I lost one of the more important.

Durval Tabach

tom611’s picture

tom611 commented

Does flexinode 4.7/cvs support multiple select checkboxes or standard select box? I can't find any way (or discussion) to create a multi-select flexinode field. What am I missing? Thanks.

ledelboy’s picture

ledelboy commented

I have a different version of your problem: one of my site relies heavily in Flexinode. 90% of its content is in node-flexinode-x.tpl.php's. And the site administrators keep asking for more. Flexinode allows, among other things, for a more consistent input of data, particularly when people who do that are mostly web-impaired. I would like to give this site the wonderful functionalities of 4.7, but I simply can't do the upgrade without redoing the whole site. The end result is that I have a site stranded in 4.6. This is bad. It clashes against the whole Drupal spirit.

Bèr Kessels’s picture

Bèr Kessels commented

http://webschuur.com/node/678 ? In other words: I am doing my best to revive flexinode a little and to make a new, actually working 4.7 release, befor emoving over to 5.0.

Bèr
---
Professional | Personal
| Sympal: Development and Hosting