Non-Native Legacy Plugins

15 years 6 months ago #78739 by ratruxal
Non-Native Legacy Plugins was created by ratruxal
What's the downside, if any, of using plugins that are not native requiring legacy support?

Is there a way to implement Community Builder with ALL native plugins for gallery, newsletter, PMS, forum and blog?

Thanks...

Please Log in to join the conversation.

15 years 6 months ago #78751 by Rapunzl

Jamie (Rapunzl)
Community Builder Team Member

Before posting on forums: Read all CB Articles | Specially the FAQ | Help us help you
CB links: Subscribe to CB documentation | [url=http://www.joomlapolis.com/content/view/7363/37/
]Our templates[/url] | [url=http://www.joomlapolis.com/content/blogcategory/61/74/
]Paid Subscriptions[/url] | Get Hosting | Our Forge
Visit my CB Profile

My personal site Rapunzl's Reality always under reconstruction

Please Log in to join the conversation.

15 years 6 months ago #78754 by ratruxal
Replied by ratruxal on topic Re:Non-Native Legacy Plugins
First let me thank you for the quick reply and in general for what appears to be a tremendous (and probably thankless at times) job as moderator on the forum.

I have a problem however with your reply. Did you actually read the thread you directed me to after finding it in a search? I'm asking because it has nothing to do with my two-point question. It was primarily directed to developers who wanted to be "Native" and what constituted "Native".

I wanted to know what the downside was AND what plugins/addons/components/extensions that are Native and are recommended or are supported by CB.

I have already found the answer to the downside - slower performance in legacy mode.

Thanks again for your efforts. :-)

Please Log in to join the conversation.

15 years 6 months ago #78804 by Rapunzl
Replied by Rapunzl on topic Re:Non-Native Legacy Plugins
I'm sorry you don't think my link applied. I thought it made some good points regarding legacy mode.

As far as what extensions are supported in CB, you can look in CB-Specific Joomla Extensions link in my signature. There won't be many claiming compatibility with 1.2 though till the release to make sure there will be no API changes. The good news is that most run anyway if you enable legacy, and legacy only affects those extensions that require it, meaning your Native extensions will not trigger the legacy mode.

Jamie (Rapunzl)
Community Builder Team Member

Before posting on forums: Read all CB Articles | Specially the FAQ | Help us help you
CB links: Subscribe to CB documentation | [url=http://www.joomlapolis.com/content/view/7363/37/
]Our templates[/url] | [url=http://www.joomlapolis.com/content/blogcategory/61/74/
]Paid Subscriptions[/url] | Get Hosting | Our Forge
Visit my CB Profile

My personal site Rapunzl's Reality always under reconstruction

Please Log in to join the conversation.

15 years 6 months ago #78809 by nant
Replied by nant on topic Re:Non-Native Legacy Plugins
Performance is the first downside. Also at some point in time (very far) the Joomla team might chose to drop legacy support all together.

Legacy plugin implications have been discussed to death on Joomla.org forums - I suggest you search there if you haven't already done so.

Post edited by: nant, at: 2008/11/02 20:26

Please Log in to join the conversation.

Moderators: beatnantkrileon
Time to create page: 0.239 seconds

Facebook Twitter LinkedIn