Hi. I have a new client who wants to make an Image Board site for full time RVers and live aboard boaters.
They want something like 4chan, but WITHOUT anonymous posting. And they want it to be more modern looking – kinda like NodeBB. So a regular Image Board script won’t work because they don’t seem to support memberships. And a vBulletin-type forum would require a tonnn of hacking to make it right.
So I’m thinking EE might work.
Requirements would be:
Front end member registration
Front end posting by all members
Picture upload required to create an new post
Picture upload optional on all comments
Front end post and comment uploads restricted to images only – .jpg, .gif, .png
Appropriate security to prevent uploading malicious files disguised as images
It’s been a very long time since I’ve used EE – and I’ve never used EE3 – but I’m thinking it’s the most robust platform for this sort of thing. Just wondering how many of these requirements can be accomplished with EE3 out of the box?
Sure this sounds right up ExpressionEngine’s alley, with maybe a snag on #4 only.
Cool man. Thank you for the detailed answer.
Everything is looking good!
But I am concerned about #4 – allowing pictures in comments. My PHP skills are about as advanced as my belly dancing skills – that is to say – nonexistent. So I’ll have to chew on that.
Can you comment on the scalability of something like this? This client is running a couple of old-school forums with nearly 120,000 members combined – and these folks love to share pictures.
So I’m planning to use either Amazon S3 or a separate media server. I think I have that worked out.
But what about EE? Can it handle hundreds of thousands of channel entries, comments, and the associated assets?
Hi Jeremy.
Thanks for that. I know that EE has been a great choice for some very high-profile projects (handling lots of traffic). No worries about the traffic part.
I’m just concerned about how it handles a huge data set (on both the front and back ends). Hundreds of thousands of entries – even with low traffic – could bring a CMS to its knees if it’s not well designed.
I Googled it, and several years ago this issue was discussed. Indeed, it seems EE 2 did have some performance issues with large data sets. Wondering if anything has improved since then.
Much of the issues of scale with content at extreme volumes are an environmental issue. Hardware, network latency, along with web server and MySQL config make a big difference, and at scale, much of the performance is their purview. Implementation also comes into play a great deal. In most circumstances, the Channel Entries tag is going to be using primary keys on tables to find the content, before joining or fetching any data, and with reasonable limits.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.