Join us for EEConf 2023, October 4-5 in Orlando. Speakers. Networking. Community powered. Awesome.
Join us for EEConf 2023, October 4-5 in Orlando.Register Now!
I love EE, since many years, used it for client projects back in the day when it was $300 per project …
Yet actually I’m so pissed off, I can’t even believe it, and trying to find a way to chill out and start over.
Recently saw the v7 presentation and seems great, so came back to php/ee for a project, spent a tone of time on setting things up (less then a week before deadline) …but I did a silly thing: Used the CP to add a new images folder. Nothing else, just using the CP to add a folder and everything is bro-ken!
The classic generic Error 500 with everything down, even the frontend (suddenly permission issues, for just using the CP).
If that’s you way to sell Support Packs, keep up the good work but it’s not subtle.
I’m just disappointed (a lot) because of how much I used to love EE, seen it as the most professional & robust CMS in the field …so it hurts to see it turning into that opaque, unreliable pile of code.
To be frank, I don’t even expect anything from that post, as the forums are maybe as dead as they where already a few years ago, but needed to get that off my chest.
Hey Andrei! Sucks that you’re having trouble. I’ve had similar issues like this when setting up projects.
It’s definitely way more robust than it was a few years ago. And the community is way more active.
The good news is that: 1. The forums are definitely active. 2. The Slack Channel is way more active, and you can probably get these questions answered way quicker.
You should ask this question in Slack, as you may be able to get an answer on it. Hope this helps, and hope to connect!
I agree with Doug. And whilst I understand the need to get things off your chest, I do feel you’ve come to unreasonable conclusions using phrases like “opaque, unreliable pile of code” and suggesting there’s deliberate obscurity to sell support packs.
It sounds like just a permissions issue, so should be easily addressed. And since you’ve been away for a while, you won’t know that the EE team are very responsive to genuine issues, so if this is indeed something that needs to be addressed, we can figure it out and open an issue in GitHub and they’ll take a look. But I agree with Doug, check in with the EE Slack community and there’s plenty of folks that can help with stuff like this.
Thanks for your answers, i’m going for the “flames-thrower” fix and re-do a fresh install as I kept my templates and don’t feel like tempting my luck into permissions fixing. The real crazy part is that everything was working fine (permission related) then all of a sudden broke after just using the CP to add a folder. I can’t understand why would such a thing happen, and imagining if it was a real client facing the thing.
What made me try again EE was a blog for my wife’s work (she’s a teacher). The previous one was an Eleventy based, hosted on Netlify’s CDN with …NetlifyCMS as editing tool. It’s not my favorite part but she loved Wordpress by the past, so I thought going back to the good’ol EE instead, maybe some nostalgia.
I’ll just cross my fingers, hope it will hold and call it a ting. For other projects I tink I’ll go back to 11ty, VueJS, Alpine and the rest, leaving PHP back into my nice old dev memories.
Thanks for bringing all of this up! Also, thanks for taking a peek at V7 again!
I’m sorry you have run into this issue! Not fun at all!
We ran a quick test to replicate this, and we’re unable to do so. Similarly I’d probably start by taking a peek at permissions. (As mentioned, there’s a lot of people in Slack that are more then happy to jump in as well!)
I’ll follow up with a DM as well!
The EE eco-system and the software itself is in a far healthier state now than it has been in the recent past. There’s a clear roadmap forward, solid development and frequent updates.
Tom and the team provide excellent free support and advice in the Slack group - along with all of the other experts there you can usually find solutions pretty quickly.
So come on back - the water is fine!