Last modified: 2014-05-17 08:39:02 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 T63143, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 61143 - Vector skin needs non-collapsible bits
Vector skin needs non-collapsible bits
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
1.23.0
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 44881
  Show dependency treegraph
 
Reported: 2014-02-10 15:19 UTC by Mark A. Hershberger
Modified: 2014-05-17 08:39 UTC (History)
6 users (show)

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


Attachments

Description Mark A. Hershberger 2014-02-10 15:19:48 UTC
From https://www.mediawiki.org/wiki/Thread:Project:Support_desk/How_i_add_to_Adsense_in_Page/reply_%282%29

Noting the primary concern I'm reporting here with asterisks.  Other issues are other bugs.  The issue is primarily that it should be possible to specify some bits as non-collapsible.

  I want to bring this to the attention of whomever it may concern, this should
  also be a priority for all admins that use Google AdSense in their MediaWiki
  sites.

* The new default vector skin collapsible sidebar in 1.22+ prevents the
* extension from displaying advertisements.

  The latest version of the Google AdSense 2 extension has not been updated
  since 2012. It is not currently being maintained by any active developer.

  This is a concern for anyone looking to use this extension in a 1.22+ update.
  Updating MediaWiki may break AdSense functionary. This may result in lost ad
  revenue or possible suspension of AdSense accounts that are not displaying the
  ads properly.

  Please, I request anyone who could update the extension to work with new
  updates post an updated extension.
Comment 1 Nemo 2014-05-17 08:39:02 UTC
Problem solved by bug 39035.

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


Navigation
Links