hi all, how to add a module to Lucee inside box environment? Some part of code uses CFSPREADSHEET which works ok on classic Lucee, but not works under box-ed Lucee. I understand there's Google but today is Friday and this channel is always so helpful! 🙂

Its great when our Doppelganger, comes to the rescue! 🙏 https://github.com/Leftbower/cfspreadsheet-lucee-5 Download & install: https://github.com/Leftbower/cfspreadsheet-lucee-5/blob/master/cfspreadsheet-lucee-5.lex

The only caveat to using

install

to pull the Lucee extension from ForgeBox is • if the CommandBox server is already defined, it will put the lex file in Lucee's

deploy

folder automatically like you want • If you run the install FIRST before ever starting the server, CommandBox won't know what to do with the lex so it will just dump it in the current working directory, which won't install it.

Just curious @rodyon and @Charles Robertson - have you checked out https://forgebox.io/view/spreadsheet-cfml? Is there a reason you are using the extension vs this package? We’ve cfsimplicity’s package for years now and it has been great, but just wondering if I’m missing out on something.

@danmurphy Tag support: It’s actually pretty simple [no pun intended 😊], cfsimplicity has no support for the tag:

<cfspreadsheet />

Now, this may not be a big deal for your project, but we are in the middle of a massive migration, which uses the tag extensively. Scripting support: Also, we found that cfsimplicity failed in Lucee, straight off the bat, whereas

cfspreadsheet

just parsed the ACF spreadsheet scripting syntax, without any trouble. We didn’t really analyse where the issue was, we just ran 5 or 6 templates/CFCs that contained spreadsheet syntax and

cfspreadsheet

successfully handled all of them, even after we added the necessary, component path syntax, before the spreadsheet methods, in cfsimplicty So, I am not entirely sure that the scripting syntax in cfsimplicity matches the current ACF directive? But I cannot really comment on this, with any confidence, as we didn’t have time to do a deep dive into the pain points. Installation: Installing the extension is not a big deal. Just log into the administrator and install. In fact, I would say it’s easier to install the extension than add the necessary mapping and paths that cfsimplicity requires? Usage: This is how I see it. If you are doing an ACF to Lucee migration, you might find

cfspreadsheet

is a better option. If you are building a new application from scratch, you might find cfsimplicity is better? And, hey, you could use both! 👊 Editing: The more difficult prospect is trying to edit the extension. But that’s for me to worry about. 😀

I am not entirely sure that the scripting syntax in cfsimplicity matches the current ACF directive?

spreadsheet-cfml was never meant to support the ACF syntax directly, although the function calls are similar enough to be easily adapted. However it is intended to match and exceed the functionality available in both ACF and the Lucee extension, and fix issues.

I would say it’s easier to install the extension than add the necessary mapping and paths that cfsimplicity requires?

spreadsheet-cfml doesn't require a mapping.

If you are doing an ACF to Lucee migration, you might find

cfspreadsheet

is a better option.

If you are building a new application from scratch, you might find cfsimplicity is better?

Totally fair!