Extension talk:AutoRedirect

Some bugs after creating the redirect page ?

After creating the redirect page by submiting the editing, the original page cannot be edited sectionally. The link of editing section will be the redirect page. How can I do to fix this(I use 1.11)?

Please show me an example. Jean-Lou Dupont 14:41, 28 March 2008 (UTC)

I am not sure if this is a bug. Thx for help. --TwCareer 15:29, 28 March 2008 (UTC)

Could you try leaving a blank line between the section title and the {{#autoredirect: ...}} magic word? Let me know. Jean-Lou Dupont 18:06, 28 March 2008 (UTC)

I have tried leaving a blank line between the {{#autoredirect: ...}} and the other text. But if it create a new page, It would lead the same problem.

Do you have this problem while creating the direct page?

I have done a couple of test on my side but I can't reproduce the problem you describe (on 1.11). Jean-Lou Dupont 16:32, 30 March 2008 (UTC)

I have go to your site and the test is ok. So I am sorry to bother you. I will reinstall the extension. Thanks for your help.

internal error

Hi Jean-Lou. When I installed this extension, every time , I go to the page "Special:Version" I will see the following message:

Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'StubManager' was given in D:\AppServ\www\mediawiki-1.11.0\includes\Hooks.php on line 113
內部錯誤

Set $wgShowExceptionDetails = true; in LocalSettings.php to show detailed debugging information.

Then, I set the $wgShowExceptionDetails = true; and refresh the page. I will see the following code:

Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'StubManager' was given in D:\AppServ\www\mediawiki-1.11.0\includes\Hooks.php on line 113
內部錯誤

Detected bug in an extension! Hook StubManager failed to return a value; should return true to continue hook processing or false to abort.

Backtrace:

#0 D:\AppServ\www\mediawiki-1.11.0\includes\SpecialVersion.php(101): wfRunHooks('SpecialVersionE...', Array)
#1 D:\AppServ\www\mediawiki-1.11.0\includes\SpecialVersion.php(32): SpecialVersion->extensionCredits()
#2 D:\AppServ\www\mediawiki-1.11.0\includes\SpecialVersion.php(17): SpecialVersion->execute()
#3 D:\AppServ\www\mediawiki-1.11.0\includes\SpecialPage.php(653): wfSpecialVersion(NULL, Object(SpecialPage))
#4 D:\AppServ\www\mediawiki-1.11.0\includes\SpecialPage.php(459): SpecialPage->execute(NULL)
#5 D:\AppServ\www\mediawiki-1.11.0\includes\Wiki.php(201): SpecialPage::executePath(Object(Title))
#6 D:\AppServ\www\mediawiki-1.11.0\includes\Wiki.php(45): MediaWiki->initializeSpecialCases(Object(Title), Object(OutputPage), Object(WebRequest))
#7 D:\AppServ\www\mediawiki-1.11.0\index.php(89): MediaWiki->initialize(Object(Title), Object(OutputPage), Object(User), Object(WebRequest))
#8 {main}

• MediaWiki: 1.11.0
• Win XP
• The AppServ Open Project - 2.5.7 for Windows
  • Apache Web Server Version 2.2.3
  • PHP Script Language Version 5.1.6
  • MySQL Database Version 5.0.24a

Could you give me a hand?--Roc michael 20:31, 21 May 2008 (UTC)

Which version of StubManager are you running? Upgrade to the latest version (1.3.0) if not. Let me know. Jean-Lou Dupont 20:35, 21 May 2008 (UTC)

When I see the special:version, it shows StubManager (version @@package-version@@). Then, I see the source code "StubManager.php". It say * @Id $Id: StubManager.php 1027 2008-04-22 17:01:23Z jeanlou.dupont $--Roc michael 20:55, 21 May 2008 (UTC)

This means you haven't installed the extension through either PEAR or the tarball provided. You probably just have copied the files from the SVN directory instead. Please make sure you have the latest version installed before we continue this discussion. Jean-Lou Dupont 21:03, 21 May 2008 (UTC)

I use the cmd.exe then do the following:

C:\Documents and Settings\Michael>pear channel-discover mediawiki.googlecode.com
/svn
Channel "mediawiki.googlecode.com/svn" is already initialized

C:\Documents and Settings\Michael>pear install mediawiki/stubmanager
mediawiki/StubManager requires PEAR Installer (version >= 1.6.2), installed vers
ion is 1.4.9
No valid packages found
install failed

C:\Documents and Settings\Michael>pear install D:\AppServ\www\mediawiki-1.11.0\e
xtensions\StubManager
Cannot initialize 'D:\AppServ\www\mediawiki-1.11.0\extensions\StubManager', inva
lid or missing package file
Package "D:\AppServ\www\mediawiki-1.11.0\extensions\StubManager" is not valid
install failed

C:\Documents and Settings\Michael>pear install D:\AppServ\www\mediawiki-1.11.0\e
xtensions\StubManager/stubmanager
Cannot initialize 'D:\AppServ\www\mediawiki-1.11.0\extensions\StubManager/stubma
nager', invalid or missing package file
Package "D:\AppServ\www\mediawiki-1.11.0\extensions\StubManager/stubmanager" is
not valid
install failed

Did I miss something?--Roc michael 21:54, 21 May 2008 (UTC)

First line where PEAR tells you that you do not have a valid version of PEAR to install this package. Please use pear upgrade pear command prior to try and install the extension. Jean-Lou Dupont 22:23, 21 May 2008 (UTC)

Thank you, Jldupont for your quick replies. I will try. Then, tell you the what's the result.--Roc michael 22:50, 21 May 2008 (UTC)

Hello, I'm having the exact same error on the Special:Version page. -- Bob ten Berge

I'm running StubManager 1.3.1 and I installed it under Linux using pear install mediawiki/stubmanager. I had no errors during this installation.

Is there anyone around who knows how to fix this?

No work

When I save the message {{#autoredirect:test|test970521 }} to a page (e.g Sandbox), the page Test:test970521 remain empty, through, the page "Special:RecentChanges" say the page "Test:test970521" has been created. --Roc michael 20:54, 21 May 2008 (UTC)

UNIQ issue in 1.15

I admit that out of the box this works perfectly, but for hierarchical reasons I need the redirect page to have a category. So I toyed around with the script, just a little, but now my new page has left over UNIQ tags (not the redirect page - that still works perfectly). Just wondering if you have any idea as to how I can fix this. All I changed was the i18n file and used the alternateText variable as the category name. Below was the only real change, besides editing out the other code.

'autoredirect-page-text' => '#REDIRECT [[$1:$2]]'."\n".'[[Category:$3]]',

http://pastebin.com/f614818cf - changes to the code

After a little testing I have made sure that it is my edits. Then I thought that it might be because I'm using the magic word in a template, but making a single page without the template resulted in the same problem when I used the magic word. But even after using the recursiveTagParse function on the output I still end up with the same problem. Though clicking edit and submitting fixes it, I'd like to figure out what this error comes from and how to fix it. Thanks!

Pages in the "Main" namespace

How do you designate pages in the Main namespace to be re-directed to the page in question? I have tried leaving the first field blank, and also putting in only one field -- error: AutoRedirect: invalid textual namespace --Susan 18:38, 4 December 2010 (UTC)

Got it -- after a little code reading, I discovered that namespaces can be designated numerically; Main is namespace 0 --Susan 18:56, 4 December 2010 (UTC)

MediaWiki 1.16.0 and <autotedirect-invalid-namespace-numeric>

We are working with a MediaWiki 1.16.0 PHP 5.2.13 system and while using (0 indicating main namespace)

{{#autoredirect:0|0415553474}}

the only message we get is

<autotedirect-invalid-namespace-numeric>

not matter what we tried.--MWJames 05:07, 2 January 2011 (UTC)

MW 1.18 breaks this extension

The deprecation of $wgMessageCache breaks this extension, as does the use of PHP 5.3 (Namespace is reserved for use by PHP). I was able to hack around the Namespace problem, but my non-existent PHP skills were not able to deal with the rest. This is unfortunate, because this extension looks like it would do exactly what I need, and I don't see anything else out there similar to it. If anyone tackles this problem and can fix it, please let me know (according to other pages for the author's extensions, he is no longer supporting them). Twisted86 (talk) 21:26, 2 March 2012 (UTC)