Feature #4183, how is the description to be understood, and is CB 1.10.0, on time?

Hi Guys

I'm looking at the road map, and as I can see it there are a ton of open issues, will the 1.10 be released in four days (or thereabout) or is it going to be 'delayed'?

Oh, and the feature I'm waiting for is #4183 (content plugin), but I don't understand the description:
"Added parameter to optionally enable processing of delimiter field description through content.prepare. Content bot processing happens before substitutions to avoid field values from injecting content bot usages."

But will that enable the output from the delimiter field to be interpreted? Ie. the request originally was for a way to convert a delimiter field output to QR code.
But if it is converted before substitutions, how is that possible? Or am I misreading it somehow?

I'm looking at the road map, and as I can see it there are a ton of open issues

I'm not sure where you're seeing a ton of open issues. More than half are marked resolved, which means they are done and pushed to our internal GIT.

will the 1.10 be released in four days (or thereabout) or is it going to be 'delayed'?

No it won't be out in four days, it's delayed by probably a month. There's more work than I thought and it's taking longer to ensure everything is implemented properly.

Oh, and the feature I'm waiting for is #4183 (content plugin), but I don't understand the description:
"Added parameter to optionally enable processing of delimiter field description through content.prepare. Content bot processing happens before substitutions to avoid field values from injecting content bot usages."

It allows you to enable Joomla content bots to process delimiter fields.

But will that enable the output from the delimiter field to be interpreted? Ie. the request originally was for a way to convert a delimiter field output to QR code.
But if it is converted before substitutions, how is that possible? Or am I misreading it somehow?

I've changed it to process after substitutions. So this isn't an issue anymore. I can't guarantee it'll help provide exactly what you want. All it does is pass the delimiter fields content through Joomla content bots.

krileon wrote:

I'm looking at the road map, and as I can see it there are a ton of open issues

I'm not sure where you're seeing a ton of open issues. More than half are marked resolved, which means they are done and pushed to our internal GIT.

Well it says: 84 issues (7 closed — 77 open)
So it could be me reading it wrong, but it seems to have more open than closed on the roadmap. But when I look at each of them (those that I did open) it says 100% complete, so I'm not sure how to read it.

will the 1.10 be released in four days (or thereabout) or is it going to be 'delayed'?

No it won't be out in four days, it's delayed by probably a month. There's more work than I thought and it's taking longer to ensure everything is implemented properly.

Excellent, thanks for the info, and the hard work, wish I had the knowledge to help out.

Oh, and the feature I'm waiting for is #4183 (content plugin), but I don't understand the description:
"Added parameter to optionally enable processing of delimiter field description through content.prepare. Content bot processing happens before substitutions to avoid field values from injecting content bot usages."

It allows you to enable Joomla content bots to process delimiter fields.

But will that enable the output from the delimiter field to be interpreted? Ie. the request originally was for a way to convert a delimiter field output to QR code.
But if it is converted before substitutions, how is that possible? Or am I misreading it somehow?

I've changed it to process after substitutions. So this isn't an issue anymore. I can't guarantee it'll help provide exactly what you want. All it does is pass the delimiter fields content through Joomla content bots.

Well, in that case it should do it, as I can install a QR code plugin that will convert text to QR.
Thanks, I'll look forward to the release

Well it says: 84 issues (7 closed — 77 open)
So it could be me reading it wrong, but it seems to have more open than closed on the roadmap. But when I look at each of them (those that I did open) it says 100% complete, so I'm not sure how to read it.

Tickets marked resolved are still open until marked closed, but you can see the general completeness of 1.10 by checking its completeness bar on the roadmap. As it stands 1.10 is considered 90% complete.

Well, in that case it should do it, as I can install a QR code plugin that will convert text to QR.

Yup, that should work.