http://coldfusion.com logo
Join Slack
Powered by
Could someone point me to where "ColdBox@be" is? ...
# box-products
h
Could someone point me to where "ColdBox@be" is? I submitted a Jira ticket for a Coldbox issue I'm having and Luis is asking if I can try reproducing the issue on ColdBox@be
b
Just install it via CommandBox
Copy code
install coldbox@be
The semantic version range 
be
is a special placeholder that grabs the "highest" version, including non-stable versions.
You can see all versions of coldbox here https://www.forgebox.io/view/coldbox#versions
h
what is coldbox@be ?
b
And on the latest version of CommandBox, you can use this command to find out what it will install
Copy code
forgebox version-debug coldbox@be
"be" stands for *B*leeding *E*dge
I explained what it does above
h
neat, so i should upgrade my dev environment to something that is potentially unstable to see if the issue is resolved. no thanks.
what's the point in submitting an issue for a specific version?
b
Well, I mean you can take 2 minutes of your time to see if a bug fix works or you can wait 3 months for the release and see. Your call
It's not like you can't just
Copy code
uninstall coldbox
install coldbox@stable
when your done to go back to normal
what's the point in submitting an issue for a specific version?
I don't understand what you're asking-- it seems unrelated to this discussion.
h
The Jira ticket asked what version this issue relates to. I input 6.8.1 Then I'm asked to test with a potentially non-stable verson. Brad, not everyone knows absolutely everything about your product with installing "be" and reverting installations, etc. etc. Please have a little grace with your responses.
b
I don't mind people not knowing everything. It's just that you came across as though you already did. ¯\_(ツ)_/¯
s
Coldbox 7 is right around the corner so I expect they want to know if they've already fixed an issue that might pop up in CB6. 'test with a non-stable version' is not routinely something that get advised
👍 1
b
I see the ticket-- basically Luis is hoping that whatever you're running into may be fixed in the latest version. Honestly, he's just guessing but ColdBox 7 has had a lot of work done to it so there's a chance. If you don't have the time (or inclination) to test, that's fine but I'm guessing the error was something specific to your setup/code since I don't recall anyone else hitting it before.
If you can still reproduce it with that simple test case, finding the datamarshaller code and dumping out the values being passed will probably shed some light on what's going on https://github.com/ColdBox/coldbox-platform/blob/v6.8.2/system/core/conversion/DataMarshaller.cfc#L145-L149
The inputs to that tag aren't dynamic so the error message is a bit of a head scratcher since I thought 
Attribute validation error for tag cfcontent.
generally meant the combination of attributes was invalid. But perhaps just one of the values was invalid.
h
I will try dumping the datamarshaller to see if i can identify why it's having an issue when the 'PDF' type is sent. I'm leary of installing/uninstalling coldbox because I don't know if things like router.cfc, and a few settings i've added to coldbox.cfc will be lost/overwritten.
b
When you install ColdBox, that only touches the coldbox framework in the 
/coldbox
folder. It won't affect anything in your app code.
You can also undo any changes made for testing from your source control
h
ah, okay so only /coldbox is updated/removed. /config, /handers, etc shouldn't be touched (by the update/install/uninstall process).
b
Correct. Those are part of the app. The package manager will never touch your app code unless you're using a scaffolding command like 
coldbox create app
which creates a new app
h
so would you recommend I omit the /coldbox folder from git ?
b
Yes, all dependencies are recommended to not be committed. Only the 
box.json
Then, as part of your build/deploy, you run
Copy code
box install
to bring in those dependencies. or
Copy code
box update
to check for new versions.
👍 1
h
in case you're curious, i commented out everything in dataMarshaller.cfc renderContent method and added a writeDump(arguments). If I specify 'html' for the renderData type argument, 
event.renderData(data="<b>this is a test</b>", type="html");
I get the following:
If I change the type to "pdf", I get the following:
b
Seems reasonable
Is there a detail or other info in the error message that says what the attribute validation issue is?
I'm still not clear on what exactly CF is even complaining about
h
I thought it was because "variable" was initially undefined but further testing hasn't shed any light on this.
Since another user in Slack mentioned they have the same issue when type is "pdf", I wonder if this relates to how we have our servers lockdown applied.
Curious if ColdBox attempts to write the PDF into a folder that we've locked down before rendering it to the screen.
l
no, we just use the basic pdf tags in CF
it's really a basic PDF converter
Open in Slack
PreviousNext
Powered by