UPDATES EasyBlog 6.0.11 Released! Update to the latest version now!

Helpdesk

Your Time
Our Time
Response Time
24 — 48 hours
We strive to provide the fastest ever response possible. However, we are not super beings.

Allow at least 24 — 48 hours
  Support is offline
Our team is away during the weekend. Some answers may already be available on our documentation

Rest assured that we will get back to your posts as soon as the week starts!
  Support is offline

Splitting ES up

CK · ·
8:59 AM Friday, 19 December 2014
Low
Hi Guys,

I've been meaning to ask this question for a while but haven't gotten around to it.

With every release, the extension becomes a bit larger and more complex, how about breaking it down to a couple different extensions and have a single core extension/framework that the other extensions are built one. this would help in 2 way

  • Easier to make changes (add/enhance features [new extensions], implement bug fixes) to the whole suite of extensions.
  • Less code needed on the server (reduces maintenance and attack surface).


Let me highlight an example. If I want to run a site that doesn't make use of groups and events, instead of turning off the feature (and keeping all the extra code on the site), I should just install the core extension, if in the future the needs of the community change and they need an event system, I install the event "plugin."

I'm not suggesting this for the immediate future, rather something to have in mind for future release (think about adding the videos and pages feature, instead of having to modify the entire extension, you can write an extension that plugs into the existing one).

What are you thoughts?
The replies under this section are restricted to logged in users or users with an active subscription with us