Whoops, use the below.Well your code only gives a fatal error with : not being interpreted by string replace function.
Don't know what to tell you. Could of been a hardcoded usage somewhere that was then fixed. It's uncommon, but it happens that people could be using something in a way that's actually bugged. It eventually is going to be fixed, which breaks that usage. Can't say for sure. All I can say for sure is the substitution is working as expected.The only things that we changed are upgrade to the latest CB builds for CB, auto action, privacy, anti spam, conditionals and CBsubs
That's all, so I really cannot see why this scheme substitution problem and the antispam recaptcha problem that we have could come from anything else that CB
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.