## E Series Plugins — Community initiative or officially adopted by e107?

[Kanonimpresor]

While exploring the e107 plugin ecosystem on GitHub, I came across the E Series plugins by @rica-carv:

• euser — Enhanced User
• enews — Enhanced News
• epm — Enhanced Private Messages

The concept is interesting — taking native e107 modules and rewriting them with modern standards: Bootstrap 5, PHP 8.x, proper shortcodes, and template separation. Exactly the kind of work the community needs.

My questions

1. Official status?
Are these plugins officially adopted or endorsed by the e107 core team, or are they a solo initiative by rica-carv? I couldn't find any reference to them in the official e107 documentation or e107.org.

2. Current state / compatibility?
I tried to get some of these plugins working on a fresh e107 2.3.x install and couldn't. No visible errors in some cases, broken functionality in others. Are they actively maintained and compatible with the current core?

3. Should these be part of a curated plugin list?
This connects directly to the discussion in #5608 about a GitHub-based plugin directory. If quality plugins like the E Series already exist but aren't discoverable or verified, that's exactly the gap we need to close.

Happy to share specific install issues if that helps narrow things down.

— Martin / LandingPro

[Jimmi08]

Did you find them only now? Aren't you on gitter? And have you see this?

https://github.com/Jimako-e107-plugins

If I find some, I fork them.

Plugins by @rica-carv are unofficial, the same as my plugins.
We have a name conflict, and my eplugins are private, so I can't comply.

How should plugins work? They should be independent from the core so error in one plugin doesn't crash the entire site.

Plugins that should be extracted from the core should:
news
gallery
contact
comment
rater
and probably search too.

in fact, it is easy, I wish I knew this when I started with news.

	'comment'                        => '{e_PLUGIN}comment/handlers/comment_class.php',

	/**
	 * Retrieve comments handler singleton object
	 * @return comment
	 */
	public static function getComment()
	{
		if (!e107::isInstalled('comment'))
		{
			return null;
		}
		return self::getSingleton('comment');
	}

[Kanonimpresor]

@Jimmi08 I've known about these plugins for a while — but I didn't know the reasoning behind the "E Series" naming or whether it was an official initiative. When information is hard to find... you ask. 😉

That's kind of the whole point of #5605, isn't it?

And yes, I know about Jimako-e107-plugins too. Thanks for that!

[rica-carv]

1. Official status?
Are these plugins officially adopted or endorsed by the e107 core team, or are they a solo initiative by rica-carv? I couldn't find any reference to them in the official e107 documentation or e107.org.

@Kanonimpresor They're unofficial, and as stated in the readme of those plugins, use at own risk....
I've created the e series plugins to extend or enhance core functionality, because the pulls i made to the e107 code aren't being merged, so i solved the issues that way...

2. Current state / compatibility?
I tried to get some of these plugins working on a fresh e107 2.3.x install and couldn't. No visible errors in some cases, broken functionality in others. Are they actively maintained and compatible with the current core?

I got them working on a fresh github install, so i wonder what's the errors you got....
Beware that some are cross linked and require extra plugins, like the ecore plugin. Read the readme files of each plugin....

We have a name conflict, and my eplugins are private, so I can't comply.

Sorry, @Jimmi08 , but that conflict is unintended....
Can we have a work around?

[Kanonimpresor]

I installed them on v2.4 GitHub build, I wanted to see their features and these are the results:

[rica-carv]

I installed them on v2.4 GitHub build, I wanted to see their features and these are the results:

The LAN problem is the english language files of the plugin.
I can guarantee that they work with the portuguese language files....
Sorry...

[rica-carv]

@Kanonimpresor Just updated the English lan files,please check if the lan errors still persists... Thanks

Also updated the user_shortcodes file, it was my fault. Sorry...

[Jimmi08]

@rica-carv, naming problem is not a problem. If you remember, I started my plugins with prefix jm, but it looked too "selfish" - for lack of a better word. When I found that you had the same idea, I moved them to private and started to update/fix plugins under the official names.

After I sync all plugins from admin (with user, repo, and branch settings) it is not an issue anymore. I really plan to review your plugins and check what you changed (especially the forum, because mine is used on the live site), it is on the to-do list.