Flexinode searching dropped from 4.7
handelaar - June 12, 2006 - 18:26
| Project: | Flexinode |
| Version: | HEAD |
| Component: | flexinode_miniviews.module (Flexinode pages) |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Filing as requested (Hi Bèr :-) )
Current flexinode has dropped all its former ability to view lists/tables filtered by the content of fields. Previously I could enter (eg) http://example.com/flexinode/search/1?edit[flexinode_1]=5&op=Search and see a table view of only those nodes which have '5' as the value in field 1.
Can we discuss 'repairing' this by allowing flexinode/list and flexinode/table to take additional query string options?
eg: flexinode/table/1/1/5 to recreate the result outlined above
Thanks for listening...
#1
As I know, search capabilities were moved to flexisearch.module which was especially built as an search addition for flexinode.module
#2
John, can you confirm that the flexisearch.module is not what you are looking for?
#3
Flexisearch has not yet made any effort to port to 4.7, so there's really no way of telling.
#4
OK, having hacked it to work with 4.7, the answer is no. Flexisearch doesn't work on flexinode 'SELECT' items at all.
#5
We really need a solution for this asap. But problem is, I was not even aware of this feature in flexinode, let alone that I know why it does not work anymore.
Patches are more then welcome (hint) :)
#6
It was killed right about here.
#7
seems little interest in this problem, so throttling down.
#8
I am very interested in this problem.
My v4.6.9 used menu links to display flexinode searches. I upgrade to v4.7.5 and guess what? The same menu link now returns "your search yielded no results".
I generated the search terms by doing a sort in the table, then I saved the url in the menu. So I saved -
flexinode/table/2?sort=desc&order=date
When I try it now, it won't work.
The url that ends up in the address bar is
flexinode/table/2%3Fsort%3Ddesc%2526order%3Ddate and "your search yielded no results"
It was a great feature. It allowed loads of pre-configured selections from among flexinode content. It was a good way to make sense of content for a user group with a low skill level.
Please could you re-enstate it?
Thanks
#9
If you are really concernded about this feature, then get someone to fix it.
Sorry to be so blunt. Bu I am doing this in my spare time too. ITs all about community plumbing: do it together. Asking for something to be re-enstated will not help the smallest bit.
Getting someone to fix it will.
#10
This post refers to "searching", and that table & list views have been dropped from 4.7. I don't need the search limiting, but only the basic tabular view.
I updated to the latest version of flexinode to test it out. Without going into detail as to HOW it happened (I'm pretty sure I know how it happened), my "backup folder" mysteriously has vanished. So I am trying to go back to the version of flexinode where the tabular view was present. I cant seem to find out where to find it here.
Can anyone direct me where to get that version?
I use the tabular views and until I can upgrade to 5.0 (Many thanks Ber for taking this monster on :) I'm stuck with 4.7
Thanks ~
#11
It is a module inside the flexinode download called 'flexinode_miniviews'. This now handles what you need, and most has been stabilized and fixed.
#12
Thanks Ber, will check that out, I installed the latest 4.7 version, and I dont see that as part of the package? I see flexinode_admin, and the flexinode module only.
#13
Something is amiss. I have no admin and no miniviews even though I have enabled them. I went back and started over completely, downloaded the 4.7.X.03 version, which didnt have the miniviews module in it. I checked, no admin. I then went and found the miniviews file in CVS downloaded and enabled it. No admin, no miniviews. Any suggestions? Other than a page not found when trying to get to the tabular view I had, I get no errors.
#14
Went back, tried HEAD version, gotten a little farther. The actual miniviews module was in there. I still cannot display the tables, but at least under settings I have a flexinode_miniviews item.
#15
Ok my tables are back, I went back and checked all the version of each of the main files in the folder. This is what I have:
flexinode.module,v 1.77.2.6 2007/02/06 08:37:54 ber Exp $
flexinode_admin.module,v 1.5.2.1 2007/02/07 10:08:21 ber Exp $
flexinode_miniview.module,v 1.2.2.3 2007/02/07 10:06:03 ber Exp $
The files from the 4.7.X.03 are these:
$Id: flexinode_admin.module,v 1.5 2007/01/27 14:46:39 ber Exp $ *Note the different version* I got this from CVS Rep.
$Id: flexinode.module,v 1.77.2.6 2007/02/06 08:37:54 ber Exp $
and no miniviews file.
It appears that the box to check for a field to be displayed in the table, are all "empty", even though when I view the table, the fields are there.
#16
The flexinode-miniviews module does not seem to be included with the distribution on the drupal site (flexinode-4.7.x-0.3.tgz). I see that it is in cvs. But the changelog in the CVS version stops at 27/01/07, while the distribution version changelog adds an entry for 06/02/07. So which is the latest version? Is it safe to just use the cvs checkout, even though it seems "older" by changelog?
#17
What I listed above is the versions I used on that date, and it works.
#18
yes, miniviews is not yet released, as it needs testing.
#19
Ber, what type of testing are you looking for? I have it working (using the above mix of versions)
#20
In the end, all I need to know is 'is miniviews stable enough to be included in the release'.
So, if you install miniviews in the latest Drupal 4.7 release, do:
* tables
* teaser lists
* feeds
work?
#21
Here's one thing to observe about miniviews: it doesn't use access control. Even if within the flexinode module one has specified restrictions on who can access which kinds of flexinodes, those restrictions do not apply to the miniviews---anyone with generic "access content" permission can see them.
I fixed my local copy, but unfortunately I don't know enough about the patch process to post the fix. At the very least you probably want this:
foreach (flexinode_content_types() as $ctype) {$items[] = array(
'path' => 'flexinode/table/'. $ctype->ctype_id,
'title' => t($ctype->name) . ' table',
'callback' => 'flexinode_miniview_page_table',
'callback arguments' => array($ctype->ctype_id),
'access' => user_access('access '. $ctype->name .' content') or $admin_access,
'type' => MENU_CALLBACK,
);
}
Note that in the version 1.2 dated 2007/01/27 the callbacks are wrong: they refer to flexinode_page_table when they should refer to flexinode_miniview_page_table
#22
flexinode.module,v 1.77.2.6 2007/02/06 08:37:54 ber Exp $
flexinode_admin.module,v 1.5.2.1 2007/02/07 10:08:21 ber Exp $
flexinode_miniview.module,v 1.2.2.3 2007/02/07 10:06:03 ber Exp $
Using the mix of versions I have listed above:
Feeds are working
Tables are working
List is working
When applying these new versions to an existing site with flexinode, when you go back and edit an already existing content type,
the box to check for a field to be displayed in the table, are all "empty", even though when I view the table, the fields are there.
these fields were checked already, prior to updating the module.
Karger: the version I have (1.2.2.3) has the callbacks set correctly i believe. I ran into a problem when I had referred to flexinode_page_table in a page, that needed to be changed, but not in the module itself.
Hope this helps!
#23
I opened a new issue to deal with the upgrade paths for the checkboxen: http://drupal.org/node/124379