Dear Sir.
I installed everything and working fine but when i click on recent changes
or difference i got unserialized error in localizationcache.php at 794. and
one problem i got in articletocategory extension which is undefined index
error at 26,27 line.
what can be the reason.
--
Thanks & With Regards,
*Rahul*
Running into api.php returning an 500 error when attempting to run the
following query api.php?action=query&meta=siteinfo
The exact error is :
Fatal error: Call to a member function getPrefixedText() on a non-object in
/var/www/html/SupportWiki/includes/api/ApiQuerySiteinfo.php on line 110
I have installed an "Test" database along side my existing and if I change
to the "fresh" database it works without fail. I THINK the error is related
to $mainPage = Title :: newFromText( wfMsgForContent( 'mainpage' ) );
what should I be looking for inside my database as switching to the "new"
instance resolves the API issue.
Thanks in advance for any assistance.
Zach
Hi all,
I'd appreciate your help: I'd like to add a message to the account
creation form. The message contains an internal link, it should appear
right above the submit button.
The hook I tried is $template->addInputItem, although no interaction is
actually needed. The problem is that whatever way I try to output the
message, the link appears as plain text.
This is what I did:
$wgHooks['UserCreateForm'][] = 'efAddTerms';
function efAddTerms (&$template) {
$template->addInputItem( 'terms', false, 'checkbox', 'Create-terms' );
return true;
}
Create-terms is the system-message containing the link.
Could someone please show me how to do this?
Thanks in advance
Mirko
Hey,
for my skin I would like to move the category links of a page into the
sidebar, looking like the other boxes in there. However, the markup is
not really suitable for styling since I don't want the | seperators and
the : at the beginning. I would prefer having an <ul> with all the links
inside. How can I do that with as little php as possible?
Thanks!
Wilhelm
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We are proud to announce the first stable release of the 1.17 series.
Selected changes since MediaWiki 1.16 that may be of interest:
* A new installer has been introduced. It has a wizard-style interface
which is translated into many languages. Many shortcomings in the old
installer were addressed with this rewrite. Note that it is no longer
required for the config directory to be made writable by the webserver.
Instead the generated LocalSettings.php file is offered as a download,
which you must then upload to the wiki's base directory.
* ResourceLoader, a new framework for delivering client-side resources
such as JavaScript and CSS, has been introduced. These resources are
now delivered through the new entry point script "load.php", instead of
as static files served directly by the web server. This allows
minification, compression and client-side caching to be used more
effectively, which should provide a net performance improvement for
most users.
* Category sorting has been improved.
* Sorting is now case insensitive.
* Sub-categories, pages and files can now be paged separately.
* When several pages are given the same sort key, they sort by their
names instead of randomly.
* The lowest supported version of PHP is now 5.2.3. If necessary, please
upgrade PHP prior to upgrading MediaWiki.
* Oracle Database support has been improved, and is now ready for beta
testing. If you work in an environment where Oracle is readily
available, and you can't get access to MySQL, this may be a useful
alternative for you. Please try it out and let us know if it works for
you. Oracle support is not yet recommended for use in production.
For more information about what's new in the MediaWiki 1.17 branch, see:
http://www.mediawiki.org/wiki/MediaWiki_1.17
Frequently asked questions about upgrading:
http://www.mediawiki.org/wiki/Manual:FAQ#Upgrading
Changes since 1.17.0rc1:
* Fixed syntax error in generated LocalSettings.php when a non-default
user rights profile is chosen.
* (bug 29399) Fixed PostgreSQL installation when the DB user for
installation is the same as the one for web access.
* (bug 29233) Fixed failover for DB slave servers. When a DB slave
went down, an error was immediately shown to the user, instead of
trying another slave. Was broken since 1.17 beta 1.
* (bug 29278) Fixed PHP fatal error when attempting to add text to a
page via a redirect.
* (bug 29408) Fixed uploads of files with MIME types that aren't
detected by MediaWiki.
Full release notes:
http://www.mediawiki.org/wiki/Release_notes/1.17
**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.17/mediawiki-1.17.0.tar.gz
Patch to previous version (1.17.0rc1):
http://download.wikimedia.org/mediawiki/1.17/mediawiki-1.17.0.patch.gz
GPG signatures:
http://download.wikimedia.org/mediawiki/1.17/mediawiki-1.17.0.tar.gz.sighttp://download.wikimedia.org/mediawiki/1.17/mediawiki-1.17.0.patch.gz.sig
Public keys:
https://secure.wikimedia.org/keys.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4BdgAACgkQgkA+Wfn4zXkHuACfRZ4ih2jCGLF2mpzn85iCifzk
vUcAnj8Unua4E4p0uyOeXh96Jqb14pkY
=E8Vn
-----END PGP SIGNATURE-----
I can't seem to get rid of the following errors for my users.
Strict Standards: Non-static method
AntiBot_GenericFormEncoding::onEditFilterMerged() cannot be called
statically in /var/www/elinux.org/includes/Hooks.php on line 129
Strict Standards: Non-static method
AntiBot_GenericFormEncoding::onEditFilterMerged() cannot be called
statically in /var/www/elinux.org/includes/Hooks.php on line 131
Strict Standards: Non-static method
AntiBot_GenericFormEncoding::onEditFilterMerged() cannot be called
statically in /var/www/elinux.org/includes/Hooks.php on line 133
Hooks.php:
129: // Run autoloader (workaround for call_user_func_array bug)
130 is_callable( $callback );
131
132 /* Call the hook. */
133 wfProfileIn( $func );
134 $retval = call_user_func_array( $callback, $hook_args );
135 wfProfileOut( $func );
What bug is this workaround referring to? I searched Bugzilla for
"call_user_func_array" but didn't find anything. Do I simply need to
Upgrade?
Thanks.
Im trying to upload a file via the API, called internally using fauxRequest.
Im trying a test just using the URL upload on the file http://upload.wikimedia.org/wikipedia/en/b/bc/Wiki.png
But I keep getting an error. -> uploaddisabled: Uploads are not enabled. Make sure $wgEnableUploads is set to true in LocalSettings.php and the PHP ini setting file_uploads is true
wgEnableUploads is set to true and I am able to upload files with the web interface. Im running MW 1.16
Thanks
Is there a way to increment the page counter through the API?
I have an external page that pulls content from the wiki. Im testing a CMS that uses mediawiki as the engine. And accessing pages through the API. But Id like to increment that page when it is accessed.
Any ideas?
First thing to check: are the URL paths correct? Right-click on one of those
names and see if it offers to view or copy the URL. Is it the path you
expect? If correct, are the files actually there?
It's not uncommon to accidentally forget to move them back into place during
upgrades!
-- brion
On Jun 24, 2011 6:04 AM, "Rick Phillips" <rphillips(a)idirect.net> wrote:
