Jump to content

Extension talk:AjaxShowEditors

Add topic
From mediawiki.org
Latest comment: 11 years ago by Jamesmontalvo3 in topic Semantic Forms?

contents of the JS file have to be included somewhere

[edit]

You might want to add that the contents of the JS file have to be included somewhere, like MediaWiki:Common.js or MediaWiki:Monobook.js. It took me a while to figure out that the script wasn't loading, and that's why nothing was showing up. — Tuvok[Talk/Contribs] 23:28, 28 March 2007 (UTC)Reply
Question So how do you set it up? Thanks

more information would be nice

Missed some double edits with MW 1.16

[edit]

It didn't work well in the MediaWiki 1.16.0 version. It only listed one editor in several cases where two of us were editing a page at the same time.

Disallow editing if page is being edited

[edit]

Is this possible? -Eep² 19:19, 30 July 2007 (UTC)Reply

Not working with MW1.11

[edit]

Not working with MW 1.11. he classic function "return problem". how to solve it?

Strange problem with MW 1.11

[edit]

Anyone using the AjaxShowEditors extension with MW 1.11?

I have a problem with this extension. When 2 people Jack and John are editing a page, it's showing only Jack's name as currently editing to Jack. And to John it's showing "John is editing". Though the DB table has 2 rows for jack and john. Any clues?

Regards,

Jack

Same here with ver 1.15.0 --The IceMan 20:06, 23 June 2009 (UTC)
Working just added :
$wgAllowUserJs  = true;
$wgAllowUserCss  = true;Reply

MediaWiki 1.11.0

[edit]

Don't work with me too... Waiting a fix for this great extension ;)

This is fixed in rev:26485. --Sayuri 13:53, 8 October 2007 (UTC)Reply

Error messages not internationalized

[edit]

In a previous version of this extension, I created three messages in the database: 'ajax-se-invalidpage', 'ajax-se-invaliduser', and 'ajax-se-usernotfound'. They showed up when there were errors returned by the script. Now, Response.php has been altered to return hard-coded error messages that can only be changed by editing the code. I have patched my own installation to use the messages in the database.

You need only change three things: the return statement of the first three if statements in wfAjaxShowEditors. Here is my code up to the database read ($dbr):

function wfAjaxShowEditors( $articleId, $username ) {
	global $wgOut;
	$articleId = intval($articleId);

	// Validate request
	$title = Title::newFromID( $articleId );
	if( !($title) ) { return wfMsg( 'ajax-se-invalidpage' ); }

	$user = User::newFromSession() ;
	if( !$user ) { return wfMsg( 'ajax-se-invaliduser' ); }

	$username = $user->getName();
	if( !(  $user->isLoggedIn() or User::isIP( $username )  ) ) { return wfMsg( 'ajax-se-usernotfound' ); }


	// When did the user started editing ?

That will allow editing the messages by creating pages in the database for them. Note that AjaxShowEditors.i80n.php also has to be changed. For example, change:

$wgAjaxShowEditorsMessages['en'] = array(
    'ajax-se-title' => 'Currently editing:',
    'ajax-se-pending' => 'pending refresh ... (click this box or start editing)',
    'ajax-se-idling' => '($1s ago)',
);

to

$wgAjaxShowEditorsMessages['en'] = array(
    'ajax-se-title' => 'Currently editing:',
    'ajax-se-pending' => 'pending refresh ... (click this box or start editing)',
    'ajax-se-idling' => '($1s ago)',
    'ajax-se-invalidpage' => 'ERR: page id invalid',
    'ajax-se-invaliduser' => 'ERR: invalid user',
    'ajax-se-usernotfound' => 'ERR: user not found',
);

For each language in use on your wiki, add those three messages. Even if you don't define customized messages, it will still work and show something, even if it's not in the local language.

I hope that sometime in the future, Ashar will see this and patch the SVN version, since I don't have write access (nor would I want to commit on someone else's extension). — Tuvok[Talk/en.wp] 17:53, 30 December 2007 (UTC)Reply

Another Problem with MW 1.11.0

[edit]

I had another Problem with this great extension
It works only for articles in main namespace, not for those I created in my userdefined namespaces. Anyone having the same problem?
Ben

MW 1.12.0: Sections and editing > 60 sec.

[edit]

2 Problems:

  • If User A edits a page and after less than 60 sec. User B wants to edit the same page, there will be a message that User 1 is already editing the page. So, everything works fine. But: If User A edits a page and after 60 sec. User B will wants to edit the same page, there will be no message that User 1 is already editing the page. How can this be fixed?
  • Is it possible to change the script in the way that there will be no conflict-message if User A and User B edit different Sections on the same page at the same time?

~ 26 September 2008

About comment one

[edit]

Would you be able to describe more indepth what you did to install this extension? I'm still not sure where to save all the files, and you seemed to mention that one of them actually nees to be copied into another?

FCKeditor support

[edit]

add this to AjaxShowEditors.js (or some more appropriate spot)

function FCKeditor_OnComplete( editorInstance ) {
    editorInstance.Events.AttachEvent( 'OnSelectionChange', wgAjaxShowEditors.refresh ) ;
}

FCKeditor keystrokes will now be captured.

How to show Editor pre Line

[edit]

Q. All the Editors are shown in one line, How can i show Editor pre Line ?

Localisation

[edit]

I am working on the localisation of messages on translatewiki.net. It would be very helpful to have a screenshot of this extension in action, especially a screenshot showing the message 'pending refresh...(click this box or start editing)' in use. Could someone add this to this documentation page? Lloffiwr 11:56, 26 December 2009 (UTC)Reply

Semantic Forms?

[edit]

Has anyone considered making this work with Semantic Forms? --Jamesmontalvo3 (talk) 19:59, 13 May 2013 (UTC)Reply

Allright..

[edit]

Some response to this interesting extension.

  • First off require MediaWiki >= 1.35.0 throws an update.php error when you have MW 1.35.6
  • Second.. the API throws an error : internal_api_error_BadMethodCallException. Exception caught: Cannot use User::newFromActorId when $wgActorTableSchemaMigrationStage is MIGRATION_OLD