String Argument Handlers

i like the idea.

but your patch writes quite a bit thing other as the existing views_handler_filter_string.inc

There the same stuff is done also, so you could copy some code.
Additional there should be only indentation of two spaces,

anyway i like this idea

No additional work done on this in over a year.

Patch updated.

I've added:

• Is equal to
• Is not equal to
• Start with
• Does not start with
• Ends with
• Does not end with
• Contains
• Does not contain

I'll probably do the patch for Views 3.X in somedays.

And this is the patch for Views 3.

See also #150248: Can $args & Argument Handling Code be Used to Limit Views to a Range or Series (as opposed to a single match)?. The patch here would form part of a solution for the string ranges case described in that issue.

I made a module out of it, you can download the latest version on this thread.

I'm planning to add support for numeric and dates soon.

saved code for posterity (same as above, removed extra __MACOS folder)

p.s. For security reasons, your upload has been renamed to views_extra_operator.tar_.gz.

Updated version here with README, code comments and other stuff.

Module updated with new handlers.

I've added some other handlers but for an unknown reason, they are not included and I'm looking for help about this.

Fixed some typos.

Adding support for Node:Nid and Integers.

Big update !

Now you can apply those operators to strings and integers:

• Is equal to
• Is not equal to
• Start with
• Does not start with
• Ends with
• Does not end with
• Contains
• Does not contain
• Contains any words
• Contains all words
• String length greater
• String length greater or equal
• String length lesser
• String length lesser or equal
• String length different
• String length is between
• String length is not between

Screenshots

Corrected some bugs, Drupal code compliant, files cleaning.

Oops, I forgot to remove the _MACOSX folder!

Here is the tgz.

Nice job. I spend a couple hours to find something to do this without looking at the views code.

Sorry but we don't review new modules in the views issue queue.

You can do two things,

Provide a Patch.

or

Apply for contributions CVS account and share your module in drupal.org

#18: see patches in #3 and #5 for Views 2.x and 3.x respectively.

Mmm, it seems you already apply to a cvs account, here #879118: Pol [pol], but I was marked as won't fix since you didn't follow the http://drupal.org/cvs-application/requirements

So, please read it, and do the thing in the right way.

Mmm, cross post about the status, anyway patches provided in #3 and #5 uses tabs instead of spaces, and have some lines commented, it needs work.

Ok I'll work this out by the end of the week and will be back soon ;)

Pol: Thank you for this, your timing could not be better. I was just about to crack open the code when I found this thread!

@cashbrow, @deleron, @dagmar: I made a module, there is no need to patch the views code.

I've checked the code and it seems that it's drupal code compliant.

I hope it's ok, come back on me if it's not.

I really think this is something we should have in Views proper, and not as an additional module.

#357082: Pull filter value from an argument? would allow this

Here's the patch from #3 cleaned up. I applied it to my site and it works fine.

Oops, forgot to attach patch :)

The patch in #28 is great... but now that I've applied it, and altered my arguments to 'starts with' my views are returning all values. I also had the strange behaviour where some newly altered arguments went missing. I'll see if this is repeatable.

I pulled the package created by Pol in #15, but it only worked for string fields that were not part of "Content" types - i.e. I could not use it with fields that I created using CCK.

I have updated the code to work for string "Content" fields. Attached is an updated package.

Cool, that's really interesting !

It was something I was planning to do those days :-)

Pol, if you have some time, perhaps you can get the numeric arguments working as well, taking a similar approach to how I did the string args.

Should really get a "dev" version of this plugin into CVS - not sure how that even happens, but a plugin like this seems like something that a lot of people would find useful.

Ok I'll do it, it's gonna be ready for tomorrow probably.

The module for D6/Views 2.x/3.x is on Github for now at this address: https://github.com/Polzme/views_extra_operator

I'll add some new features in the next days probably, i've got my head full of new ideas!

Added some new functions, screenshot updated.

Return blank screen when views with this module enabled is in panels.

Return blank screen when views with this module enabled is in panels.

I'll check next week. Do you have any error in the Status Report or in PHP logs ?

Which version have you tried ?

Try this one: https://github.com/Polzme/views_extra_operator that's the latest.

Pol,

Correct me if I'm wrong, but it seems that your module breaks the 'break_phrase' option in Views 2. The 'break_phrase' option is the option labeled "Allow multiple terms per argument." on the Views UI. With your module enabled, this option seems to be totally ignored, preventing me from querying an object based on multiple values (i.e. WHERE my_val IN ('val1', 'val2', 'val3')

In addition, all arguments are being treated as strings. i.e. when selecting on nid, which is a number, the resulting query is "WHERE nid = '123'" instead of "WHERE nid = 123". Maybe MySQL handles this w/no inefficiency at all, but my concern would be that using a string instead of a number when the column in the DB is a number could potentially degrade performance by not using an index.

Attaching a patch for the "Allow multiple terms per argument." option on the Views UI to work once again. This isn't really meant to be an end-all solution, but is sufficient for my needs, and may give some direction on how to correctly implement.

Came across another bug - this time with the sort_by clause. This patch fixes an issue where the sort by field was not being correctly prefixed. i.e. I was getting "ORDER BY title" instead of "ORDER BY node_title", which was causing SQL errors due to field ambiguity.

Hello @HitmanInWis,

I've committed your patches, thanks !

Find the latest version here: https://github.com/Polzme/views_extra_operator

Pol,

In one of your recent revisions, it seems you changed how the selected argument type is specified in code behind the scenes - i.e. the default "op_equals" from CCK/Views is no longer interchangeable with your Equals value. What this results in is that if I have a bunch of views using the default CCK/Views op_equals value for arguments, and then I enable your module (views_extra_operator), all of my views using the old op_equals are broken until I go to each of the arguments in each of the views and re-save. I would strongly suggest working around that issue - otherwise many people may immediately stop using your module when they enable it and it seemingly breaks all of their existing views.

Just a suggestion. Thanks for your hard work on this Pol.

True, I'll sort this out tonight from home :-)

Thanks for reporting this.

Voila: https://github.com/Polzme/views_extra_operator/commit/3e7fd45edc2e177604...

This is the fix I did, if you have a better suggestion, just let me know.

Great work, Pol. Thanks! Your module is very usefull but I've found the bug in a sort handler. #43 doesn't work for me for simple fields (with no veo function). I've attached the patch for latest version at https://github.com/Polzme/views_extra_operator. Now it works for me. BTW - is $this->sort_field used anywhere?

Hello Kndr,

I've committed your patch, thanks :-) Let me know if everything works now.

Everything is OK. Thank you.

I'm wondering whether you can create a project on drupal.org and use the issue queue there?

Then everyone would profit from it.

Hi all,

I removed master branch and created 2 branches.

• 6.x-1.x
• 7.x-1.x

I've also updated the code to get it working with Views 3, I'm waiting for your feedback.

@Dereine: I do not put the code on D.O. because I don't have access to git at work and I cannot commit changes. As soon as we will be able to commit through https, I'll switch.

Pol, big thanks for your module. I think it should be added to the core views!

This module looks awesome, have tried to accomplish this before but ended up with a simple module with custom SQL instead of views. I have installed the module on Drupal 6.26 with Views 6.x-3.0+76-dev, but it looks like the argument settings are not saved, they revert to default value for both SQL Function and Parameters. No errors or warnings.

Any ideas ?

Suppose it makes a lot of sense, views could be used for autocomplete tasks in core

this should move to views core, thanks :)

Current head is 8

2 Pol, Your module now is not compatible with new Views 7-36 :(

Hi,

I didn't know that it was still used!
Anyway, I'm quite busy with OpenLayers and I don't have time to put into this module unfortunately.

Thanks.

The patch in #48 seems to be very hardcoded, so I don't think this is core-worthy.

Is there a similar module to do this. I'm searching for this for 1 week now. I have a big project and it depends on search for tags to be an exact match as in node.

Like, if I search for tags "a,b and c" I want to see the nodes only containing "a,b and c", or less. "a,c" or "b,c". Not "a,b,c,d,e"

Maybe better to move this core, there's some sprints happens so bring this to radar

As far as I can tell, this functionality now already is available in core, so closing as outdated. If you feel that there is still something we should address, please feel free to reopen this