Last modified: 2013-03-15 02:45:10 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T48083, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46083 - viwiktionary has $wgLogo defined twice
viwiktionary has $wgLogo defined twice
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
wmf-deployment
All All
: Lowest trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
: shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-13 20:12 UTC by MZMcBride
Modified: 2013-03-15 02:45 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description MZMcBride 2013-03-13 20:12:10 UTC
From <https://noc.wikimedia.org/conf/InitialiseSettings.php.txt>:

---
	'viwiktionary'		=> '$stdlogo',
	'viwiktionary'		=> '//upload.wikimedia.org/wikipedia/commons/thumb/7/74/Wiktionary-logo-vi.svg/135px-Wiktionary-logo-vi.svg.png', // bug 43240
---

It looks like the logo for viwiktionary is set twice currently. This should be adjusted.
Comment 1 Sam Reed (reedy) 2013-03-13 22:39:51 UTC
(In reply to comment #0)
> From <https://noc.wikimedia.org/conf/InitialiseSettings.php.txt>:
> 
> ---
>     'viwiktionary'        => '$stdlogo',
>     'viwiktionary'        =>
> '//upload.wikimedia.org/wikipedia/commons/thumb/7/74/Wiktionary-logo-vi.svg/
> 135px-Wiktionary-logo-vi.svg.png',
> // bug 43240
> ---
> 
> It looks like the logo for viwiktionary is set twice currently. This should
> be
> adjusted.

Of course, the latter array key just overrides it.

https://gerrit.wikimedia.org/r/53692
Comment 2 MZMcBride 2013-03-14 01:02:26 UTC
(In reply to comment #1)
> Of course, the latter array key just overrides it.

I don't think "of course" and PHP are compatible. ;-)

Thanks for the quick fix, Reedy.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links