Here are some mockups of this banner design with some common campaigns:

Just circling back to review this. Close button is now 44px.

@Dzahn: That's correct!

Seems like the right thing so that we can move forward!

The goal is to be able to return to near realtime banner impression data within turnillo to achieve three purposes:

Just looping back in on this ticket @JAllemandou as to what is needed from us.

Really sorry for the delay in getting back to you. I really liked the survey icon.

Incrementing the Sitenotice_id seeming to work on ja.wiki

Similar SOPA site notice had to be removed from Portuguese wikipedia yesterday evening.

Fixed SOPA site notice displaying on ja.wiki

I've tagged the core platform team for a lack of owner for Sitenotice (note this is not CentralNotice)

Given that the protection reasons would only ever appear on meta wouldn't user language be better?

I'm not opposed to this but I want to be able to A/B test this change within programmatic banners prior to committing to it. (which I should be easily be able to do within a campaign)

I'm not intrinsically opposed to moving banners beneath the search bar but I ask this change be held off until January.

As expected this https://superset.wikimedia.org/r/14 query matches turnillo

@Tgr for the time being. Hardcode the translation for Hungary. I know its not ideal but it will suffice for now.

@Nuria - jrobell I think already has access to pivot and turnillo if I'm not mistaken.

This issue affected T194939 and in place of CentralNotice three seperate sitenotices will be used

Thursday would be best.

Would be happy to chat with you more about this over hangout if that that would be useful @Miriam ?

Situations where fallback would have either prevented disruption or ensured effective delivery of campaigns:

Is this really a priority?

Out of interest, where did this task originate? Between turnilo (pivot's successor), Superset and the usual Hive queries it seems like we are pretty covered for the time being in terms of our ability to review impression data. Concerned that this is coming at the expense of Clone Campaign (which seems to have stalled) and therefore preventing working on campaign fallback which with a switch to bundle style campaigns, is now becoming more mission critical a requirement.

Whats holding this up?

Any chance of this getting looked at any time soon?

Is there any possibility of this being prioritised?

ssh-rsa

So the 2-3 hours turnaround is certainly fulfilling the needs of A/B testing requirements and vastly improves the ability to verify a campaign setup. Reducing both from 2-3 days to 2-3 hours.

My current need access to stat1005 so that I can be able to get near real-time page views data for the target pages used in central-notice campaigns. This for two uses, firstly A/B testing and secondly verifying live campaigns.

The script is called from common.js but is stored in another subpage. I actually have move it since to prevent it being an issue which is how I discovered the other issues.

Update: A second wave of testing showed this isn't as board an issue as first thought.. Cookie seems to setting correctly for majority of browsers. Will follow up with donor and continue to debug.

Testing order:

The internet suggested including the following:

Are we distinguishing two-factor from two step?

Hey all,

I would love to use a banner for this functionality.

All the code that has been smoothed and improved on in conjuction with my work with Wiki Loves Monuments has been merged into this new banner:

I presume a centralnotice will be required for this?

As of 4439645ece32 (June 2016) no banners have been shown on any Special or Edit page.

Please test

Been working on this over the last week.

@Krinkle - I've pulled that banner. Will take a look at it.

The suppression was only partial because I was only targetting desktop with
the banner.

This should show the drop