[#3265] Few questions about CBSUBS 1.3 RC

Your error is coming from somewhere within CB that is using cbArrayToInts. Disabling CB Conditional results in the error going away however installing a version of CB Conditional that doesn't use cbArrayToInts doesn't resolve the issue. I really need to be able to backtrace the issue, but enabling debug mode on your install just throws a 500 error and sends me to a URL that isn't the one I was previously on. If possible please PM FTP access so can do direct source edits to CB and find what's using cbArrayToInts that is resulting in the error.

Is strange you can't debug.. I don't know why you get an 500 error...

However I sent a PM with my FTP credential..

waiting your news

many thank

Was able to confirm your issue as a bug and have implemented a workaround for you and confirmed resolved. Have also created the below bug ticket to further track the issue.

forge.joomlapolis.com/issues/3265

Ok...

Can you please tell me witch workaround have you apply for solve the problem? In fact you do that on my DEV site and I would like apply this to my LIVE site..

However I don't know if is a good idea to update my LIVE site with CB 1.8 and CBSubs 1.3 due to their RC status... Maybe is better to wait the final release.. I imagine you can't tell us when a final version will be available more less for both components/plugin.. Do you think before the end of month ?

The fact is I would like update because in your last RC CBSubs version you have implement a more efficient Offline payment method and is especially this feature I would like use right now..

What do you suggest ?

The patch for the workaround is on the forge link provided in my earlier post. We've resolved the issue at the source rather then treating a symptom (as this fix does). At any rate you can just copy cb.acl.php from you Dev server to your Live server as it's pre-patched (you'll need CB 1.8 of course).

We're using CB 1.8 RC here at Joomlapolis so we consider it pretty stable, but we did find some ACL bugs for J1.5, but if on J1.6+ it works quite stable. I recommend waiting for a stable release or at least RC2 before pushing to a live site however. We're working to release RC2/Stable this week or next week at most (just an internal goal, not a release date).