If we take off the name attribute then it displays an error saying
‘attribute name must be present in cfgrid’ - which implies Lucee does know
about cfgrid
Sorry for kicking the open door, but have you read the error message? “Tag grid is not supported”. And that’s what it is.
The tag is one of the frontend tags that Adobe Coldfusion created, and Lucee/Railo decided to not implement.
Kind regards,
Paul KlinkenbergOp 13 okt. 2015, om 12:15 heeft Paul Hopkinson <@Paul_Hopkinson> het volgende geschreven:
Hi,
Having an issue with cfgrid but cannot seem to find a fix anywhere.
My only thoughts on this are from a pure business point,
It would be wise for Lucee to support the various tags ACF does not support.
Face it, its one more thumbs up for Lucee, and as ACF continues its
destructive track down turning CFML into python, the Lucee Group has a
real chance of picking up customers and expanding its base.
Not saying all tags should be fully supported, but if it can, it should as
its one less hassle / headache for porting an application from an expensive
ACF install to a opensource install that the Lucee Group could offer paid
support options for.
While it may seem trivial for many veteran programmers to not want to use
old tags, for the organizations that simply do not want to re-code an
application yet want the security they had in the past, this would be their
silver bullet.On Tuesday, October 13, 2015 at 6:15:29 AM UTC-4, Paul Hopkinson wrote:
Hi,
Having an issue with cfgrid but cannot seem to find a fix anywhere.
I have always been all for complete compatibility with ACF. However, this
is one area that I think Lucee made the correct decision to deviate from
ACF. Hopefully ACF will break these tags in some upcoming version.On Tuesday, October 13, 2015 at 5:15:29 AM UTC-5, Paul Hopkinson wrote:
Hi,
Having an issue with cfgrid but cannot seem to find a fix anywhere.