Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
My site already installed Views Custom Field 6.x. Since Views PHP now has D6 version then, do I need to uninstall Views Custom Field before install Views PHP?
How about my previous PHP code using Views Custom Field?
Comments
Comment #1
thedavidmeister CreditAttribution: thedavidmeister commentedsubscribe
Comment #2
lpalgarvio CreditAttribution: lpalgarvio commenteddon't do that.
Views PHP isn't ready for production use.
something i tried to do with it wouldn't work for example... it worked right away on the older module, Views Customfield.
when the developers feel Views PHP is ready, they will likely announce it, and a stable release will surely be made.
Comment #3
thedavidmeister CreditAttribution: thedavidmeister commentedi'm using both at the moment without any glaring conflicts/issues.
totally anecdotal of course, but the added convenience/power provided by this module makes it worth having a play.
Comment #4
drupalnesia CreditAttribution: drupalnesia commented@thedavidmeister: i'm agree, at least we can help maintainers buy reporting any bugs quickly. thanks for sharing.
edit: confirmed, both modules run together perfectly.
Comment #5
webservant316 CreditAttribution: webservant316 commentedsubscribe. views_php still seems half baked to me at this time. so I plan to check out views_customfield.
Comment #6
webservant316 CreditAttribution: webservant316 commentedviews_customfield meets my needs
Comment #7
thedavidmeister CreditAttribution: thedavidmeister commentedviews_php has the advantage that you can easily drop in a custom PHP filter, but I've recently had problems where the PHP sort is really slooooow for even small views with only 15 or so rows being displayed so you do have to be careful with the performance of what you put into views_php.
Comment #8
webservant316 CreditAttribution: webservant316 commentedplus the $value, $php, and $data variables do not appear to be properly populated in the latest dev of views_php.
Comment #9
thedavidmeister CreditAttribution: thedavidmeister commented@webservant - that sounds like a code issue that should be in this queue if it isn't alread, my point was more of a general comment that probably has more to do with lower level PHP eval() and SQL performance than this module.
Comment #10
webservant316 CreditAttribution: webservant316 commented@thedavidmeister - yes good point, I was straying from the original post question. Regarding the original question I think that views_customfield and views_php can both operate side by side without a problem (as far as they are functioning). views_customfield is the predecessor with less features and no filter option, but it appears to work as advertised. views_php is more full-featured and with filters, but the current dev just doesn't work as advertised.
Comment #11
thedavidmeister CreditAttribution: thedavidmeister commentedI'm using a version of views_php from at least 6 months ago and I've managed to get filters, fields and sorts all working ok with a minimum of fuss. Can't comment on the latest dev version though.
Comment #12
webservant316 CreditAttribution: webservant316 commentedit would appear something is broken in the lastest dev.
Comment #13
RaulMuroc CreditAttribution: RaulMuroc commentedTo met it just does not interpret PHP. I put code like " print "hello"; " in Output field and in the screen is show the literal text: print hello. instead of the value "hello".
The same in value field.
I don't know if I do something wrong or what but is really simple php statement as to fail.
Comment #14
Liam MorlandDrupal 6 is no longer supported. If this applies to a later version, please re-open and update the version.