Please Log in or Create an account to join the conversation.
Need to be more specific as to what API you're wanting to use. Foundation and database global for example will still work fine. We do not just delete global functions or API classes, but deprecate them and remove much later (basically same as Joomla, you'll have several releases to get usages up to speed before legacy API is removed).I plan to start a new project using Joomla 3.5 and CB 2.0. I need to develop a custom CB plugin and I would like to know if CB Api as been modified or not.
Use CBTxt and not defines and you'll be fine. We're getting rid of define usage gradually in favor of CBTxt as defines use PHP constants, which can't be changed so it wouldn't be possible to do overrides for example with defines.I need also to get a french CB version and Kyle told me time ago, CB 2.0 will handle language in another way than the current "define" language. Have you already new french language file ? or is necessary to make some conversion ?
Please Log in or Create an account to join the conversation.
Need to be more specific as to what API you're wanting to use.
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.
Yes, production/live site usage is not recommended when using a Beta.You say CB 2.0 must not be used for live site but by "live" you mean probably "in production" ?
I can't guarantee any kind of release schedule. Even when RC is released none of our plugins will be up to date yet. I will be updating all our active plugins after Stable.If yes is not a big deal because I will need few month before finish the site. Meanwhile I suppose you will release at least a RC version which is supposed to be fine even with a production site.
Correct, the loophole is to start with 1.9.1, install the plugins, then upgrade to CB 2.0. However doing this we can not guarantee any sort of compatibility to 1.x plugins. CB will mark them as incompatible in plugin management to let you know this. Incompatible plugins will still load and work, but they maybe using API that is out of date, removed, etc.. The biggest compatibility issues are jQuery based at this time, because I've upgraded our jQuery to 1.11.0 (current) along with all our jQuery plugins (and quite a few awesome new ones). We do load the jQuery migrate file, but it's not a guarantee of backwards compatibility for some jQuery functionality.However if you say is not possible to install CB plugin (such Auto-Action, Conditional and more) under 2.0, I have no other choice than start with 1.9.1 and upgrade later.
Please Log in or Create an account to join the conversation.