631022 - Enable new Features of getfirebug.com MediaWiki 1.16

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Sebastian Zartner [:sebo]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
Build Identifier: 

Now, that the MediaWiki got updated to 1.16, the new features for it like the WikiEditor enhancements and the new Vector skin should be enabled for the getfirebug.com wiki.

Reproducible: Always

Comment 1

[John J. Barton]

Standing alone at the top of my list is a MediaWiki support for ConfirmEdit
http://www.mediawiki.org/wiki/Extension:ConfirmEdit

Currently we have to manually add users after they enter a bug request, very tedious and discouraging.

Comment 2

[Shyam Mani [:fox2mike]]

Can we have a list of stuff you need to be done please? So I can go ahead and look into it. Comment #0 seems vague :)

Comment 3

[Sebastian Zartner [:sebo]]

We need:
http://www.mediawiki.org/wiki/Extension:UsabilityInitiative
http://www.mediawiki.org/wiki/Extension:ConfirmEdit

Also we definitely need a syntax highlighting extension for at least JavaScript and XML. I am not aware of which one is good, so maybe someone else already knows one:
http://www.mediawiki.org/wiki/Category:Syntax_highlighting_extensions

Furthermore for some pages it would be useful to have a PDF-Export function. Therefore we'd need:
http://www.mediawiki.org/wiki/Extension:Pdf_Export

John, Honza, if you think we need something else, here's the list:
http://www.mediawiki.org/wiki/Category:Extensions_by_category

Comment 4

[Shyam Mani [:fox2mike]]

Going to need infrasec to approve these extensions before I can install them. Moving the bug over.

Comment 5

[Sebastian Zartner [:sebo]]

As of http://code.google.com/p/fbug/issues/detail?id=4142#c7 it would also be good to have enhanced search capabilities. So one of the following two search extensions should be implemented:

http://www.mediawiki.org/wiki/Extension:Lucene-search
http://www.mediawiki.org/wiki/Extension:SphinxSearch

Comment 6

[Marc Jessome[:mjessome]]

I ran across this bug while looking for bugs related to Syntax Highlighting on the wiki. I feel this is a very useful feature, and as mentioned in Comment 3, there are plenty of good and easy to use extensions for this.

Is there any estimate on when this feature may be made available?

Comment 7

[Sebastian Zartner [:sebo]]

After reading your comment I had a look at our wiki's version page (http://getfirebug.com/wiki/index.php/Special:Version) again and saw, that we already have GeSHi Highlighter as syntax highlighting extension.
Was that added when updating the wiki? Because I didn't see that before and nobody told us about it.
So just the other extensions are still missing.

Comment 8

[Sebastian Zartner [:sebo]]

Brian, I added you to ensure this doesn't get missed while moving the wiki to the getfirebug.com repository.

Comment 9

[Curtis Koenig [:curtisk-use curtis.koenig+bzATgmail.com]]]

What extensions are needed and is this work still needed?

Comment 10

[Sebastian Zartner [:sebo]]

Of course we still need them.

As of the commments before and new requirements we would like to have (sorted by priority):

- ConfirmEdit
- UsabilityInitiative (especially the new WikiEditor and the Vector skin)
  which seems to include all the features of this extension
- User Merge and Delete (or another extension that is capable of deleting users)
- Lucene-search or SphinxSearch
- Pdf Export

Instead of installing the WikiEditor as extension it would probably be better to update the wiki to the brand new 1.19.0 version to also get security and bug fixes.

Sebastian

Comment 11

[Frederik Braun [:freddy]]

I will file a bug to get the wiki updated to something less outdated.
In the meantime, can you please confirm that you still need all of these extensions when the update is completed Sebastian?

Comment 12

[Sebastian Zartner [:sebo]]

Yes, we still need all those extensions.

Sebastian

Comment 13

[Frederik Braun [:freddy]]

I'll have to know which backend you choose if you intend to install the PdfExport extension.
There is little use in me testing all Html2PDF libraries out there ;)

If you're unsure about which to pick, I'll try to find out which suits best and is easiest to review and maintain.

Comment 14

[Sebastian Zartner [:sebo]]

I don't have any experience with Pdf Export or it's backends, though from the description I'd say MWLib is the one to choose.

Anyway, I assume before we start adding the extensions, our Media Wiki installation should be updated again first, because this issue is already waiting for more than two years and we're still on Media Wiki 1.16.5.
I guess I should create another report for that, right?

Sebastian

Comment 15

[Frederik Braun [:freddy]]

It's covered in bug 874621 already, I CC'd you

Comment 16

[Sebastian Zartner [:sebo]]

Ah yes, I just missed the previous comment there before.

Sebastian

Comment 17

[Frederik Braun [:freddy]]

As I said in comment 13, the backend in PdfExport has not been tested.

Comment 18

[Sebastian Zartner [:sebo]]

I wonder why this bug was closed. None of the new features got enabled yet.
Also it should be blocked by bug 881896, which is asking for the wiki update.

Sebastian

Comment 19

[David Chan [:dchan]]

I think the bug closing was a process error on our part. We normally closed bugs as RESOLVED once a security review is completed. However since this bug is not in our component, it should remain open until the feature is actually implemented / landed. freddyb has already set the need flags, so I will reopen this bug

Comment 20

[Frederik Braun [:freddy]]

Sorry, my bad.

Comment 21

[Frederik Braun [:freddy]]

I suppose for this bug to move forward it should be moving to a different component/person?
If this is the wrong one, feel free to change.

Comment 22

[Sebastian Zartner [:sebo]]

We'd also like to have the ParserFunctions extension[1] in order to create more sophisticated templates.

Sebastian

[1] http://www.mediawiki.org/wiki/Extension:ParserFunctions

Comment 23

[Ryan Watson [:w0ts0n]]

I've taken: BZ 881896

I'll get that done first (if I hear back) see what we still need and revisit this bug.

Comment 24

[Ryan Watson [:w0ts0n]]

Howdy. With BZ 881866 done, we can now move on to this bug. 

Is this still the current list of things that need to be enabled?:

http://www.mediawiki.org/wiki/Extension:UsabilityInitiative
http://www.mediawiki.org/wiki/Extension:ConfirmEdit

Also we definitely need a syntax highlighting extension for at least JavaScript and XML. I am not aware of which one is good, so maybe someone else already knows one:
http://www.mediawiki.org/wiki/Category:Syntax_highlighting_extensions

Furthermore for some pages it would be useful to have a PDF-Export function. Therefore we'd need:
http://www.mediawiki.org/wiki/Extension:Pdf_Export

John, Honza, if you think we need something else, here's the list:
http://www.mediawiki.org/wiki/Category:Extensions_by_category

Comment 25

[Sebastian Zartner [:sebo]]

http://www.mediawiki.org/wiki/Extension:UsabilityInitiative got split up into several extensions. What is mainly needed from that is the WikiEditor.
https://www.mediawiki.org/wiki/Extension:ConfirmEdit would be good to block spammers, though it basically makes only sense when users are allowed to register themselves.
Syntax highlighting is already enabled.
PDF export would be nice, though is not a must-have.

So, IMO the only two extensions required are the following:

https://www.mediawiki.org/wiki/Extension:WikiEditor (to make page editing easier)
https://www.mediawiki.org/wiki/Extension:ConfirmEdit (if user self-registration is enabled)

I assume with Firebug 3 the wiki will be obsolete, 'cause docs for it are on GitHub and MDN. So it may not make sense to put too much effort into that.

Honza, what do you think in regard of the extensions and what are your future plans for the wiki?

Sebastian

Comment 26

[Jan Honza Odvarko [:Honza] (always need-info? me)]

(In reply to Sebastian Zartner [:sebo] from comment #25)
> I assume with Firebug 3 the wiki will be obsolete, 'cause docs for it are on
> GitHub and MDN. So it may not make sense to put too much effort into that.
Correct

> Honza, what do you think in regard of the extensions and what are your
> future plans for the wiki?
We should go with Wikieditor only (if it's simple to install) and do not enable self-registration for users.

The wiki should mostly stay as is being available for current Firebug community. Otherwise, contributors should be encouraged to put effort intto MDN.

Honza

Comment 27

[Ryan Watson [:w0ts0n]]

In the interest of closing this 200+ old day bug. I've installed the plugins WikiEditor and ConfirmEdit then added the following lines to the Config to enable them:

require_once "$IP/extensions/ConfirmEdit/ConfirmEdit.php";
require_once "$IP/extensions/WikiEditor/WikiEditor.php";

Comment 28

[Ryan Watson [:w0ts0n]]

Registration is locked already from what I can see.
So Provided all is well. I believe we can close this bug.

Comment 29

[Sebastian Zartner [:sebo]]

(In reply to Ryan Watson [:w0ts0n] from comment #27)
> In the interest of closing this 200+ old day bug.

To be precise, 1806 days. ;-)

> I've installed the plugins
> WikiEditor and ConfirmEdit then added the following lines to the Config to
> enable them:
> 
> require_once "$IP/extensions/ConfirmEdit/ConfirmEdit.php";
> require_once "$IP/extensions/WikiEditor/WikiEditor.php";

They don't seem to be enabled, yet. You can check that by editing any page on https://getfirebug.com/wiki.
I am not available for a few hours now, so maybe that can be clarified with Honza.

Sebastian

Comment 30

[Ryan Watson [:w0ts0n]]

wow! 

I don't have an account so can't verify. But I note that on the page I see:

"WikiEditor may not show in your browser after the installation. Clearing your browser cache will solve the problem."

Comment 31

[Sebastian Zartner [:sebo]]

Yes, it's working now. Yay!

I previously already reloaded the page via Ctrl+F5, but that didn't work. Now, testing on another PC, everything's working fine.

Thank you a lot for fixing this, Ryan! Almost five years after I reported it, I can finally close this bug!

Sebastian