Aside from some security and anti-spam features, there is Black Wolf's random image feature and the video embedding feature.
Security and anti-spam features are built in to EE, and can be enhanced by add-ons as needed (member accounts are shared between the mainpage and the wiki).
Those other two features... I don't think the EE wiki does. Strike one.
Based on what I'm reading,.. Some security issues (which I'm sure we can resolve our current wiki if it's as popular as it seems to be) and 'integration with the site the forums' (maybe?)... I don't see any reason to move our massive set of content over to a whole new wiki...
Security issues have taken this site down for days, as well as lost days worth of posts. The last I'm aware of, we still haven't figured out the vector of attack used to breach the server.
What does EE give us that we want/need and cannot get on the current wiki? Because given where all of current content lies, it's EE that needs to prove itself to be useful, not MediaWiki.
I've said it before and I'll say it again: that's why I posted this - to get your help in evaluating the EE Wiki's suitability for replacing MediaWiki.
Still borked for me.
Same here. Force-refresh does nothing.
Same here. Nothing changes after refreshing many times. I am using Chrome. (just like Axem and others.)
Gah... I hate browser caching. Ok, try this... those of you using Chrome, go to the member registration page, hit F12 to bring up the Developer Tools, then right-click the Refresh button and choose "Empty Cache and Hard Reload". Lemme know if that works for you... I've attached a screenshot of what I'm seeing to this post, for reference.
Wait, what? Unless there has been something admins haven't mentioned in public, there have been no security issues other than possibly neglecting updates to SMF, MW, Mantis, etc. And if you neglect updates to EE, you're in same boat again. The only saving grace in that situation is that EE is not so popular as to be targeted by newly discovered vulnerabilities like Joomla, Mambo, vBulletin, SMF, phpBB, MediaWiki, etc would be.
As I stated above, we don't yet know how the server was breached. We found malignant PHP code injected into a number of files around the server.
Also, EE's saving grace is not that it's not popular - not at all. It is, as a matter of fact, the most popular commercial CMS on the market. For example, Obama used EE for his original presidential campaign website (change.gov, I think it was?). A List Apart
, a leading site for web developer resources and articles, uses EE. iLounge, Penny Arcade, HelpSpot, Paula Deen, MacObserver, and Campaign Monitor all use EE.
All that to say, it's plenty popular, and it is
targeted by spammers, hackers, etc. EE's security track record doesn't come from obscurity, but from there being a team of people being paid to develop and maintain it. That's their job, their livelihood, and that's where EE's security record comes from.
If you are referring to spammers. I don't think there's anything so unique in EE that would make it better against spammers than SMF and MW do. And I'm including modifications here. Out of the box EE might be better, I don't know.
I can't speak to SMF & MW's anti-spam measures, but I can for the ones available to EE (out of the box it's so-so), and they're superb. For the record, the CAPTCHA being used now is the out-of-the-box one. There are far better methods available.
If you are referring to DDoS, then EE wouldn't help any there either because before the traffic even hits a web application, it hits server's net stack, iptables and apache first.
Wasn't a DDOS attack, nope.
Though I have to admit that if I were to pick a forums software right now, SMF wouldn't be my first choice. It's mod system is flawed for editing source files. MyBB does it right. Pretty much same difference as MediaWiki's stupid ass template system.
SMF is powerful, but you're right, I don't like having to edit PHP files to mod things. I'm unfamiliar with MyBB. Also, I'm not pushing EE's forum here, just to be clear. It doesn't suit HLP's needs.
The problem here is though, that afaik EE does not have dedicated developer resources to develop each individual aspect of EE like forums and wiki into something that can directly compete with MediaWiki and SMF for example. Prime example of this is that EE's forum does not support multiple usergroups per user account. So you have to give up plenty of features to get that level of integration. Not something I would readily give up on. Especially when I'm not even convinced HLP needs CMS in the first place.
I'm not sure what you mean by EE not having dedicated developer resources (there's EllisLab's official Add-On Development documentation
; Official Community forums
; Devot-ee add-on library
; EE StackExchange site
). The only area we make use of multiple membergroups per member is, AFAIK, the forums, which is precisely the area I'm not
suggesting we consider replacing with EE equivalents.
And we all know you're
not convinced HLP needs a CMS. Doesn't change the fact that our frontpage sucks, and we can do so much better at welcoming new members than what it has. So yes, we need a CMS.
[attachment deleted by ninja]