Hard Light Productions Forums
Community Projects => The FreeSpace Wiki Project => Topic started by: Axem on May 18, 2013, 10:05:46 pm
-
Sidebar? Hello?
(http://lazymodders.fsmods.net/Misc/wikiwhere.jpg)
Where did you go...?
(http://lazymodders.fsmods.net/Misc/youaredrunk.jpg)
Oh silly sidebar. Go home, you are drunk!
(Using latest Chrome btw)
-
Firefox 21.0 still thinks he's here... tricksssie sidebar!
-
Everyone else I've talked to does not have this problem (wiki must hate me). I've cleared cache, forced refreshed... all that's left is sacrificing some goats, but the goat store is closed for the night. :(
-
Messed up for me too but no goats here either sorry.
-
My guess is Chrome hates you. Maybe you should hate it back.
-
(http://www.theforce.net/kids/coruscant/probe_droid/palpatine.jpg)
Edit: on a serious note, yes, the same thing happens here with the latest Chrome. Works fine with FF and Opera.
-
I can confirm this issue exists.
It looks like the problem might be that Chrome has div#column-one inherit width:100% from div#global-wrapper.
Using Chrome version 26.0.1410.64 m on Windows 7 64-bit, I do not experience any of the issues described by Angrogeos Exeunt, except the moved wiki sidebar thing.
-
I'm having the same issue and created a redundant thread (http://www.hard-light.net/forums/index.php?topic=84633.0). Chromium build 201348 also has issues with left-clicks and normal page reloads throughout HLP. The only thing it doesn't have issues with is the Quick Reply function. :wtf:
-
This also happens on Dolphin Browser.
-
MediaWiki's template system is pain in the ass and fixing this problem would require updating MediaWiki, templates and merging newer template with HLP edits.
-
MediaWiki's template system is pain in the ass and fixing this problem would require updating MediaWiki, templates and merging newer template with HLP edits.
Well, ****.
-
It's not really that bad. Quickest solution would be just to get the latest MediaWiki css file and merge HLP edits into it. That alone should fix the problem with Webkit browsers, but HLP's MediaWiki should be updated properly really. I suspect it has not been done in quite a while. Probably more than few security fixes in there too.
-
Yeah, I encoutnered this issue myself a while back and tried to fix it, to no avail.
MediaWiki's template system is pain in the ass and fixing this problem would require updating MediaWiki, templates and merging newer template with HLP edits.
It's not really that bad. Quickest solution would be just to get the latest MediaWiki css file and merge HLP edits into it. That alone should fix the problem with Webkit browsers, but HLP's MediaWiki should be updated properly really. I suspect it has not been done in quite a while. Probably more than few security fixes in there too.
I think we need to leave MediaWiki for the built-in EE Wiki module. Unfortunately there's no direct import process that I know of.
EDIT: So for now, I'd like to see how well people manage with the EE wiki system. The userguide is here: http://ellislab.com/expressionengine/user-guide/modules/wiki/getting_started.html, but basically it uses standard BBCode. So just head on over to the EE Wiki (http://www.hard-light.net/fswiki), register an account if you haven't already (this will also cover the mainpage), and have at it. :) I did some very basic initial styling to the page; basically just changing the foreground & background colors. Much more can be done with it later; right now I'm interested in the content aspect of things.
-
Whoa whoa whoa. As one of the more active wiki users, I'd be very, very strongly opposed to moving away from Mediawiki. Mediawiki is the largest wiki standard on the web and has tonnes of functionality extensions, many of which we've already implemented, many others we could/should, and who knows how many in the future (the sheer user base for mediawiki means stuff like p3d integration will come to it before any other wiki types).
And that's before we then have to reimplement all the existing wiki stuff? What advantages are there to shifting, exactly?
-
Whoa whoa whoa. As one of the more active wiki users, I'd be very, very strongly opposed to moving away from Mediawiki. Mediawiki is the largest wiki standard on the web and has tonnes of functionality extensions, many of which we've already implemented, many others we could/should, and who knows how many in the future (the sheer user base for mediawiki means stuff like p3d integration will come to it before any other wiki types).
And that's before we then have to reimplement all the existing wiki stuff? What advantages are there to shifting, exactly?
This
-
Yeah, I agree with Black Wolf. I've never been convinced HLP needs CMS in the first place.
-
Dumping our entire wiki system for a new one and having to rebuild from the ground up to deal with an issue that not everybody has and doesn't actually stop the show even when it's present is a wee bit overcorrective.
-
Well, I believe it has been Sandwich's intention to move from SMF to EE's built-in forums as well. That way EE would encompass most of HLP's web applications. I've just never liked that idea.
-
I do have a desire to move as much as possible over to EE-based alternatives, primarily due to security reasons, Fury. EE has a superb security track record, and with recent events we've had, we could use secure software.
Integration is another reason, where forum posts, Wiki articles, and site content would all be able to intermingle (trying to avoid getting technical here...).
However, EE's forums do not meet our needs right now, so there's absolutely no intention of switching over to them anytime until and unless they do (specifically, they don't have the ability for a user to belong to multiple membergroups).
That said, I'm less familiar with our Wiki needs than I am with our forum usage. This is why I wanted y'all to try the EE Wiki out, and let me know what you think. I haven't made a unilateral decision to shut down the current MediaWiki by any means, and I'm sorry if that's how it came across. All I'm asking is your help in evaluating whether the EE wiki can suit our wiki needs or not. If it is suitable, I would like to transfer away from the MediaWiki once all the content has been transferred - as has been stated, "MediaWiki's template system is pain in the ass". :)
Whoa whoa whoa. As one of the more active wiki users, I'd be very, very strongly opposed to moving away from Mediawiki. Mediawiki is the largest wiki standard on the web and has tonnes of functionality extensions, many of which we've already implemented, many others we could/should, and who knows how many in the future (the sheer user base for mediawiki means stuff like p3d integration will come to it before any other wiki types).
And that's before we then have to reimplement all the existing wiki stuff? What advantages are there to shifting, exactly?
I'll tell you what I tell my kids: "Try a bite before you state you don't like it." ;)
What special functionality have we added to MW?
-
Okay, I tried to give it a shot, but the registration insists there's an image that I need to type in before I register. I don't see it even with all add-ons/extensions disabled.
Tried Chrome and Pale Moon
-
Ok, I think I know why. Gimme 2 mins.
-
Fixed.
-
What special functionality have we added to MW?
Aside from some security and anti-spam features, there is Black Wolf's random image feature and the video embedding feature.
-
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...
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.
-
Fixed.
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.)
-
Registration works perfectly fine for me on FF22.
-
I do have a desire to move as much as possible over to EE-based alternatives, primarily due to security reasons, Fury. EE has a superb security track record, and with recent events we've had, we could use secure software.
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.
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.
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.
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 (http://www.mybb.com/features/plugin-system). Pretty much same difference as MediaWiki's stupid ass template system.
Integration is another reason, where forum posts, Wiki articles, and site content would all be able to intermingle (trying to avoid getting technical here...).
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.
-
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 (http://alistapart.com/), 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 (http://www.mybb.com/features/plugin-system). 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 (http://ellislab.com/expressionengine/user-guide/development/index.html); Official Community forums (http://ellislab.com/forums); Devot-ee add-on library (http://devot-ee.com/); EE StackExchange site (http://expressionengine.stackexchange.com/)). 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]
-
Are we still talking about the rogue sidebar? I tried to find a registration page on the Wiki but all I found was the Login page, so I hit F12 there and selected "Empty Cache and Hard Reload" after right-clicking the refresh button. No dice.
[attachment deleted by ninja]
-
Have you considered upgrading MediaWiki, if it's causing this much fuss? You're currently at 1.15, the latest stable release is 1.21.
-
I've attached a screenshot of what I'm seeing to this post, for reference.
o rly
-
I've attached a screenshot of what I'm seeing to this post, for reference.
o rly
...oops?
Err, I mean, what? It's there! :nervous:
Are we still talking about the rogue sidebar? I tried to find a registration page on the Wiki but all I found was the Login page, so I hit F12 there and selected "Empty Cache and Hard Reload" after right-clicking the refresh button. No dice.
The refresh thing was in reference to the EE Wiki (http://www.hard-light.net/fswiki) I linked to a few posts ago.
-
If you register for the wiki, please post here to let me know. I'm trying various forms of member registration spam prevention these days, and sometimes it's hard to tell the real members from the spam ones. Specifically, have any of you registered as "earinxw" or "amosrm"?
-
[...] have any of you registered as "earinxw" or "amosrm"?
With a name like that you're just asking for a spambot ban :lol:
I'm "downwash", for the record.
-
Registered as myself without the Exeunt. Hopefully, Dragon's AutoComplete won't mess up my forum login; it automatically input my forum login details when I went to the Wiki's login page.
-
I've implemented reCAPTCHA and Akismet anti-spam measures since we were getting a couple of spam registrations per week. If anyone encounters issues, let me know. Fury, FYI, these measures are merely some of the free methods available. The cream of the crop costs $14 bucks, so I'm waiting to see if it's needed. :)
Also, thoughts on the EE wiki?
-
Just wanted to flag the fact that the sidebar is still misplaced (Chrome, Windows 7).
-
Just wanted to flag the fact that the sidebar is still misplaced (Chrome, Windows 7).
Yep. I honestly have no clue why. I can't quite figure out the odd CSS that MediaWiki uses. At this point, I'd say we should upgrade to the latest release and see what that does.
-
Just wanted to flag the fact that the sidebar is still misplaced (Chrome, Windows 7).
Yep. I honestly have no clue why. I can't quite figure out the odd CSS that MediaWiki uses. At this point, I'd say we should upgrade to the latest release and see what that does.
Dunno how it'll affect other browsers, but removing
#column-content{ margin-left:0; }
from KHTMLFixes.css (http://www.hard-light.net/wiki/skins/hlp115/KHTMLFixes.css) seems to fix the sidebar on Chrome. Sounds like that's there to fix a layout issue with Konquerer, though. The .css file is imported in http://www.hard-light.net/wiki/skins/common/wikibits.js at
var is_khtml=navigator.vendor=='KDE'||(document.childNodes&&!document.all&&!navigator.taintEnabled);
and
else if(is_khtml){importStylesheetURI(stylepath+'/'+skin+'/KHTMLFixes.css');}
So I guess the javascript thinks Chrome is Konqueror because it doesn't support document.all (IE only) or navigator.taintEnabled (IE and Opera only) and doesn't match any other browser. It's quite possible a later release of MediaWiki will fix this.
EDIT: Upon further research, looks like I'm right. Updating to at least MediaWiki 1.16 should solve the issue:
According to http://www.mediawiki.org/wiki/Release_notes/1.16#Bug_fixes_in_1.16
Remove five-year-old KHTMLFixes.css, which is unlikely to be relevant anymore and was causing problems.
And https://code.google.com/p/chromium/issues/detail?id=19586
This was fixed in MediaWiki 1.16, which has not yet been released and has no planned release date right now [as of Nov 18, 2009].
However, basically every MediaWiki installation on the web will suffer from the bug. Specifically, any using a
version of MediaWiki released since 2004, if they use the default skin. And MW is very hard to skin, so the large
majority of sites use the default skin, or only slightly modified. That's countless thousands of small sites, and
some relatively high-profile ones like <http://wikileaks.org>. Trying to convince all of them to blank
KHTMLFixes.css isn't going to work.
-
Ooh, good catch, thanks! I missed that line when I was debugging the problem. ;) I *think* I've fixed the problem, but it seems like there's server caching going on that I don't know how to override or force to refresh from disk. So whenever that happens, the problem should be fixed. :)
-
Ooh, good catch, thanks! I missed that line when I was debugging the problem. ;) I *think* I've fixed the problem, but it seems like there's server caching going on that I don't know how to override or force to refresh from disk. So whenever that happens, the problem should be fixed. :)
Cool, thanks! I'll keep an eye on it. :)
-
I'm sure upgrading to a newer version of mediawiki (1.22.x) would still be a good idea, get the latest security fixes and all that :)
-
I completely concur.
-
Confirmed div#column-content no longer using margin: 0; with a fresh install of Chrome on Windows 8.1 or Android 4.4 (actually CM 11). However, opening the stylesheet alone indicates no change, so maybe it's just this version of Chrome and the chached file is still being used (I didn't have Chrome on my desktop at home before now, and previous report was from Chrome on desktop at work, unknown version). Did you make the change in KHTMLFixes.css or another stylesheet?
-
I commented out the "#column-content{ margin-left:0; }" line in KHTMLFixes.css entirely. I suspect CloudFlare's caching stuff is delaying the fix.
-
I commented out the "#column-content{ margin-left:0; }" line in KHTMLFixes.css entirely. I suspect CloudFlare's caching stuff is delaying the fix.
Yup. Back on my work computer. Still cached, so sidebar still misplaced. If you have access to HLP's cloudflare settings, you can purge an individual file from the cache: https://support.cloudflare.com/hc/en-us/articles/200169386-How-do-I-purge-a-single-file-from-cache-
If not, don't worry about it. A misplaced sidebar isn't really a big deal.
-
I'm sure upgrading to a newer version of mediawiki (1.22.x) would still be a good idea, get the latest security fixes and all that :)
I completely concur.
I'm happy to do this for HLP, starting around the 14th April as I'll be away next week.
And based on these links it would seem that there could be approximately 46 vulnerabilities1 of various impacts in the currently running version (assuming that the reported version of 1.15 is correct)
http://en.wikipedia.org/wiki/MediaWiki_version_history
http://www.cvedetails.com/vendor/2360/Mediawiki.html
1 of course, not all those 46 may be relevant to the current setup, but I don't have time for a detailed analysis of all the issues right now
-
And based on these links it would seem that there could be approximately 46 vulnerabilities1 of various impacts in the currently running version (assuming that the reported version of 1.15 is correct)
http://en.wikipedia.org/wiki/MediaWiki_version_history
http://www.cvedetails.com/vendor/2360/Mediawiki.html
1 of course, not all those 46 may be relevant to the current setup, but I don't have time for a detailed analysis of all the issues right now
Yep. Ubuntu and Debian do backport security fixes into earlier supported versions of their packages, so one can't rely solely on the bug list from the upstream software.
That's not to say that what is installed now shouldn't be updated, but there are other, 'issues', that have to be considered beyond a simple "It's out of date? Ok, apt-get update away!"...
-
Huh? Unless it's been changed since my time as an admin, MediaWiki (or any of the other web applications) was never installed from distro repositories.
-
Huh? Unless it's been changed since my time as an admin, MediaWiki (or any of the other web applications) was never installed from distro repositories.
You are correct on that, I just checked.
I was under the impression that mediawiki was a package installed via apt-get, but I stand corrected. This does make the update path a bit easier, but would require changing any custom templates that might be in use, if any (I'm running into this at work).
Will have to look at finding time to set up a test bed and see if the current data can be updated without problem.
-
So is it just me, or did this fix finally take?
Also, if it's not just me, and you know that the sidebar was still misplaced as recently as the last few days or weeks, please let me know.
-
Works for me now on firefox and chrome (it wasn't working on my end before).
-
It works! Woohoo. :)
-
well, would you look at that. I had assumed it would be broken indefinitely.
-
looking good on chrome