If Substitution in CB Content Bot still has a limitation of chars

Hi!

I was bumping into an issue I reported years ago. If you use if Statements in the Content Bot plugin, it crashes the site when the amount of chars is too big...


This is the link to the old thread:
www.joomlapolis.com/forum/153-professional-member-support/197501-solved-hide-content-depending-on-cbsubs-plan?start=12

You confirmed this as bug here: forge.joomlapolis.com/issues/3471 four years ago, but considered it not to be "really an issue" :whistle:

Sorry, I would really need a fix for this. To be honest: Maybe you underestimate your own plugin! I really like it and use it quite often. In this case,I used it inside of a SobiPro template and it works very fine and gives me the opportunity to show or hide fields, depending on the subscription. But unfortunately, if the text in the SobiPro field is too long, it crashed my site.

Would be interesting why you consider this not to be an issue!?

Cheers,
Tim

There is no reasonable fix for it beyond increasing the stack overflow size as noted in the ticket. Only way we could fix it is to break large text into chunks which just breaks other stuff. We've yet to come up with a better solution. It's noted not being really an issue for CB as it's largely a server configuration problem.

As a followup what server OS are you running? Windows or Linux? This really shouldn't happen on Linux unless the string is absolutely massive.

Hi krileon,

I am on a dedicated Server at Siteground, Linux!
I did some testings and if I remembered right it was about 300 chars or so until the problem occured.

But I also had other substitutions on the page. So are they cumulating and causing the issue? So if I have 10 substitutions or so?

I think the bot could really be powerful, especially for components that have a weak ACL, could be a good selling point in my opinion! There is no extension that offers quick substitution options depending on the Joomla ACL...

Cheers,
Tim

No, they're not accumulating. It's due to preg_replace on large strings, but linux should have its stack size configured to allow for much larger strings. It's really a server limitation though that we don't really have a way of working around. I understand you want to use it for large strings, but we can't just suddenly surpass a hard server limit. Breaking a string into chunks just isn't an acceptable fix either as where it breaks could easily break the usage even further (e.g. breaks in the middle of a word or substitution usage). So I don't have a workaround other than contact your host and have them increase the stack overflow size or use smaller strings.