Replies: 3 comments 11 replies
-
|
I don't understand but, I think the admin area needs an update, at least in terms of styling. Now, let's talk. Why did e107 lose, or continue to lose, credibility? There were so many dedicated people! I love e107 even more than WordPress. Today, after a year of updating my knowledge, I chose to create new websites. I help my daughter with a marketing agency. With AI, I'm using plugins that I created myself, and I'm not a programmer (I'm learning by ear), but I've already created and updated the form, cookie, and testimonial plugins (they work wonderfully). But you, who are great code professionals, why isn't e107 growing as a true CMS? There's a lack of documentation; the plugins never have user guides, help, or tips... Open source isn't free, nor is it just a hobby; it should already be competing in the big leagues... We all need to focus on the same direction. Hugs! |
Beta Was this translation helpful? Give feedback.
-
|
The professionals in the web industry have moved onto modern technologies. I reckon most of those who were with e107 have also moved on or even retired. Then, with the backwards incompatibility of PHP 8 affecting the core as well as plugins, e107 was left behind without a critical mass to carry it forwards. As the issue stands, maintaining e107 is high-effort and low-reward. Sure, present-day AI helps bring the effort level down considerably, but somebody still has to spend the time orchestrating such agents to make forward-thinking design decisions for ongoing and long-term maintainability. I'm still with e107 for sentimental reasons, but I can't deny the technical debt that we can't easily fix due to architectural limitations in the e107 framework. I'm happy to chat more if you'd like to interview me about my take on e107. |
Beta Was this translation helpful? Give feedback.
-
|
I am not a professional either; I must be a "programmer" before I retire and just maintain my own sites. There are almost no people left, but not everything is about reward. Deltik is right. There are modern technologies. But not everybody is into them (I meant clients - some specifically forbid WordPress). The only alternative for PHP-built sites is a custom-made solution on some framework (like Laravel). I am too old to learn it so I use e107 as a framework. There is no competitor for e107 in implementing an HTML template as design. It is the best. My opinion: each solution/client needs something different. Time when you install CMS with tons of plugins is gone. I have 4-5 sites and each one needs a different registration system, a different set of plugins. Different dashboard. After digging in the admin area code, I am sure I am going the right way. Continue with your plugins. I will test them when I find time. But. For the site I am now working on, it may be easier to build a new, simple plugin for FAQs with their exact demands than study and check somebody else's code. I will see. My last cent - I think that my main problem is a lack of communication and a language barrier. I was so afraid of the new language system when I saw code changes - there was no explanation of what it meant for existing translations, why it was done this way etc. I had to learn it myself, and after it, I was able to implement it in my stripped version. I am so proud of myself for this :) |
Beta Was this translation helpful? Give feedback.
-
|
E107 loose it because the competition is more GUI user frinedly, but lacks a lot of power, something that not everybody can undesrstand. So, for me, e107 is the underdog of CMS, but i hope it stays that way, because the strongest competition is always a target for hackers & exploiters... I'll always stick to it and hope i can still customize it as i want it to work, despite the major core faults... |
Beta Was this translation helpful? Give feedback.
-
Hi Jimi08, let me understand your point. I understand that the admin theme needs to be updated and should have all sorts of custom settings, but why do you want to put it alongside the frontend themes? I still see that your admin theme also has, or could have, several possible skins. |
Beta Was this translation helpful? Give feedback.
-
|
Don't we already have different skins for the admin theme??? I disagree in having a single theme with both the admin & frontend theme "linked" together. since that would force a admin to have no control over the look of the site... I can't seem to understand the issue in having both admin & bootstrap themes different. So, just for curiosity, what's the issues? |
Beta Was this translation helpful? Give feedback.
-
|
@rica-carv, who is your question or comment for? :) Skin has nothing to do with functionality - f.e. white labeling theme (example), or branding it for the customer, with changing the source of news in the dashboard (example) etc , custom dashboard plugins ... on the other side, there were advanced settings for flexpanel - like columns, rows... I have never used it. It just showed e107 possibility, but real use... Backend is my new theme for the admin. Nothing more. Try to think a bit differently - when you need to produce a solution for a client, and each one has different demands for the admin area (they are 90 percent the same, but the rest needs to be customized to satisfy the client's needs) I would never play with admin if the site was only for me to manage. This: "I disagree in having a single theme with both the admin & frontend theme "linked" together." - it is the actual core solution, so you are for it or against separation? |
Beta Was this translation helpful? Give feedback.
-
Sorry, i expressed myself wrong, probably.
Of course that if you want to "brand" the admin area, it will get messy with two separated themes. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
You can "kill " those things simply with JS and/or CSS rules. I've been really messing around with the admin interface, and until now, i can do anything with it, even with the BS3 core theme... |
Beta Was this translation helpful? Give feedback.
-
|
In my opinion, every CMS should have the ability to customize both the front-end and the back-end to your liking; the latter has been blocked in the code by Cameron. There is, of course, a reason for this, but we won't go into that now. There is also a reason why BS now has a version 5. If you, as a CMS, don't go along with that but still position yourself as a BS CMS, then something is wrong. And if Cameron releases this, you can simply build a separate admin theme without a front-end, but why would you? It is easy to let the front-end use what is already available to build a front-end theme. Because of the blocking of the admin theme, you are forced to resort to desperate measures to make what you actually want possible, so this whole discussion revolves around only one thing: just make creating an admin theme free so that you can create something you like. The BS5 theme has no admin, so what is the discussion actually about? And finally, e107 is entirely based on BS3; you will have to make adjustments throughout the code, wherever tbox appears you will have to add something, and so on. I have already done all of that and enjoy working with a tabler.io admin theme. But it is always nice working with e107! opname_e107theme2_4_15032026.mp4 |
Beta Was this translation helpful? Give feedback.
-
|
I don't mind to use bootstrap 3 for admin (I prefer stability before modern), but it shouldn't be mentioned in the theme name. By the way, I bought tabler licence myself to support them. It was a really good catch, and their license policy is very nice. I was surprised that there is no Sass version, but then I found that it is so very well written that css variables are enough. You did very well with etabler theme. I am behind you maybe 2-3 years :) |
Beta Was this translation helpful? Give feedback.
-
|
I made sure that e107 dev had the code.... you know how i am, but nothing has been done with it, only a new css that makes mobile use even worse... And you are right, This: "I disagree in having a single theme with both the admin & frontend theme "linked" together." - it is the actual core solution. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have been asking for this for a very long time. Because Bootstrap 3 is used for both the admin area and the frontend, it is confusing for new users. When someone creates a copy, it also copies admin-related files.
As soon as you do this, you start noticing some strange things in the admin area that work only because Bootstrap 3 is also used as the frontend theme (because it contains frontend code and does not actually need to be set as the frontend theme).
My opinion:
Have at least one good admin theme that can be customized or have multiple skins.
Do not mix admin and frontend code.
Make it easy to create admin themes.
Since I already use my own Lite version, I tried this approach and this is the result.
The visual design was done by Alex from e107.nl — thanks again.
You can see the installation process here:
https://www.youtube.com/watch?v=eN3NN2wKorQ
If I was able to manage this, it should be easy for core developers to implement it the correct way. I’m not sure if I covered everything, but I will find out while using it.
Beta Was this translation helpful? Give feedback.
All reactions