Hello.

I am currently hacking in views support. We need this on a very short basis, so I am not sure if any of the code is commit-worthy. However, I will use this thread to post patches and progress reports.

I also like to us this issue/thread for feedback, ideas and/or code by others.

So: did you already work with any flexinode views integration? Do you have some Code online? Or can you mail me some code? Please do so. All ideas are welcome.

Here is the idea so far:
* Introduce a new hook function in each.inc Every .inc can register itself as filter.
* Introduce a views API hook to register every active field as possible "field" for tables and lists.

As said, we are under pressure of time, so the first part will only be introduced for some of the more often used .incs. like
the last part is possibly done in a separate module. That way, those who do not want/have/need views do not need to load all that code in flexinode.

CommentFileSizeAuthor
#11 flexinode_views.module.txt3.62 KBgushie

Comments

Bèr Kessels’s picture

Bèr Kessels commented

Some background info. FYR: http://drupal.org/node/42162 http://drupal.org/node/52032

telex4’s picture

telex4 commented

Pointless comment so I can follow this in my tracker...

egfrith’s picture

egfrith commented
Version: » 4.6.x-1.x-dev

I was wondering if any progress been made on this -- it looks like I'm need of views-flexinode integration.

egfrith’s picture

egfrith commented
Version: 4.6.x-1.x-dev » master

Changed the version back (?) to CVS. I must have accidentally ckicked on 4.6.0 on the previous post.

rickvug’s picture

rickvug commented

another pointless post to follow this in my tracker. I'd love for this functionality as well and may need it for a current project.

Thanks for all of the hard work!

Bèr Kessels’s picture

Bèr Kessels commented
Assigned: Bèr Kessels » Unassigned

pointless. thank you.....

We work for FSKING free. PLease do not be this insulting...

Thank you,

Bèr Kessels’s picture

Bèr Kessels commented

@egfrith, sorry.

I noz see you referrred to telex's comment with "pointless" I am terribly sorry.
I misread it as: "this is yet another completely pointless thread in Drupal", "another thread where nothing happens, but where I want stuff to be done".

Sorry. Sorry Sorry. I wish I could remove issues followups now. :)

egfrith’s picture

egfrith commented

No worries Bèr -- I really do appreciate the fantastic work you drupal hackers do ... I dare say your eyes were a bit bleary after too much hacking.

I am still wondering if you've been working on this. I'm trying to work out whether I should use CCK or flexinode. Views support would be cool, but images are essential, so it looks like it will be flexinode with some kind of custom db query to ordert the nodes correctly.

2sheds’s picture

2sheds commented

I'm very curious about this as well -- it could really be a lifesaver for me if it worked! Unfortunately, I "inherited" a live production system (running 4.6), compounded by some intense time pressure, so an upgrade or significant reorganization isn't an immediate option for me. I made an attempt at exposing the flexinode_data table by way of a 3-way join with the flexinode_field and node tables, but that was a pretty spectacular failure.

(My PHP "skills" are less than fantastic, so I'm feeling a bit dead-ended right now.)

gushie’s picture

gushie commented
Component: Code » flexinode.module (core)

Just curious to find out if this is "active" as in someone is actively working on it... or whether it is "active" as in actively waiting for someone to volunteer to do it!

Views support would really help me as I've been hesitant in moving to CCK since I have a fair bit of custom code which I would need to change. However if Views support is just around the corner I don't mind hanging on to Flexinode just a little longer!
(Would I be right in assuming that the fact that it hasn't been done yet means it's complicated, and a novice such as myself is unlikely to make any headway with trying to implement it..?)

gushie’s picture

gushie commented
StatusFileSize
new flexinode_views.module.txt3.62 KB

I wrote myself a small flexinode_views module just so I can include basic flexinode textfield's in a view. I've attached it to this comment, just in case it is of use to anyone else.

Remove the .txt extension and copy it into the modules/flexinode folder, and activate it in administer->modules.
Views keeps a cache of it's fields, so if any new fields are added to a content type, then it will be necessary to go to administer->modules and click "Save configuration" to rebuild this cache.

Please don't submit any bug reports for this. If it doesn't work for you I'm afraid you'll have to try and fix it yourself, or continue to wait for official flexinode/views support! I only included the functionality I needed and I sadly I don't have the time to support it beyond that.

Treat it as an pre-alpha version... i.e. probably best not to install it on a live website without being completely confident it works and is secure enough for your needs! I'm a newbie to this module writing lark, so there may be fundamental errors!