campaignShareReport

[Pete]

It seems like the method campaignShareReport has stopped to apply the
theme colors and page title/logo. I haven't changed anything to my
code but it doesn't work anymore for some reason.

[jesse]

More than likely our designers have messed with it enough that you
need to rework the style sheet being used.


jesse

[Pete]

I'm not using a stylesheet. I'm just passing colors and a header text
or image file but none of that is used. This is a var_dump of what I
pass as opts for example:

array(7) {
["header_type"]=>
string(5) "image"
["header_data"]=>
string(40) "http://example.com/logo.jpg"
["secure"]=>
bool(false)
["password"]=>
string(0) ""
["to_email"]=>
string(0) ""
["theme"]=>
array(8) {
["bg_color"]=>
string(6) "9C8A79"
["header_color"]=>
string(6) "F7D0B6"
["current_tab"]=>
string(6) "F7D0B6"
["current_tab_text"]=>
string(6) "9C8A79"
["normal_tab"]=>
string(6) "F7D0B6"
["normal_tab_text"]=>
string(6) "9C8A79"
["hover_tab"]=>
string(6) "F19477"
["hover_tab_text"]=>
string(6) "9C8A79"
}
["css_url"]=>
string(0) ""
}

It used to work like that, but now it doesn't.

[Pete]

By "none of that is used" I mean "none of that shows up on the
report".

[jesse]

Ok, basically the same thing. I'm certain it has to do with this:

http://blog.mailchimp.com/vip-reports-get-easier-cobranding/

I'll have to poke around with what was changed that has broken that
method.


jesse

[Pete]

Still doesn't seem to work. Could you find something out about this
issue so far?

[jesse]

The changes I linked above are what broke this. The "theme" parameter
will no longer work in any fashion. I've reworked the method to work
with these changes, but they will require changes in your code. The
new options are here:

http://apidocs.mailchimp.com/rtfm/campaignsharereport.func.php

You *can* use a custom theme you setup in an account.


jesse

[cfcrain]

The secure opt is not working either. The url returned prompts for a
password when loaded in an iframe. I have clients like wtf mate why do
i need a password.

I checked the documentation and it only lists "to_email, company,
theme_id, css_url" as opts. The previous docs had opts for "secure,
header_data, theme"

Here's my payload:

POST /1.3/?output=php&method=campaignShareReport HTTP/1.0
Host: us2.api.mailchimp.com
User-Agent: MCAPI/1.3
Content-type: application/x-www-form-urlencoded
Content-length: 426
Connection: close

cid=4999b4756d&opts%5Bsecure%5D=0&opts%5Bheader_data%5D=Newsletter
+Report&opts%5Btheme%5D%5Bbg_color%5D=f0f0f0&opts%5Btheme%5D
%5Bheader_color%5D=000&opts%5Btheme%5D%5Bcurrent_tab%5D=fff&opts
%5Btheme%5D%5Bcurrent_tab_text%5D=000&opts%5Btheme%5D%5Bnormal_tab
%5D=a10000&opts%5Btheme%5D%5Bnormal_tab_text%5D=fff&opts%5Btheme%5D
%5Bhover_tab%5D=666&opts%5Btheme%5D%5Bhover_tab_text
%5D=fff&apikey={blah}

[jesse]

Right, the documentation is correct. The "secure" option was removed
as well.


jesse

[cfcrain]

So, is there any way to display those awesome mailchimp reports
seamlessly in an iframe without making the user put in the password?

If i use the secure_url it loads the overview page fine b/c the
password is in the $_GET, but it isn't in the get for the other links
(top right), so it prompts the user then to put in the password (which
they don't have).

Sorry if i sound frustrated. it's because i am, but not with you. i
just joined the "mailchimp-api-announce" group, but couldn't find
announcements about changes to the "campaignShareReport" method.

[Barry Carlyon]

You can sorta cheat.

If you send the use to http://(api key zone).admin.mailchimp.com/<url to report>

they only have to login once per session....

I think your users would prefer to login rather than magically getting reports in order to keep things secure...
Thats my opinion

--------------------------------

Barry Carlyon
Freelance Web Developer
Freelance Lighting/AV Engineer

http://barrycarlyon.co.uk

mobile: 07729 048 443
skype: barrycarlyon
email: ba...@barrycarlyon.co.uk
msn: ba...@barrycarlyon.co.uk

> --
> You received this message because you are subscribed to the Google Groups "MailChimp API Discuss" group.
> To post to this group, send email to mailchimp-...@googlegroups.com.
> To unsubscribe from this group, send email to mailchimp-api-di...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mailchimp-api-discuss?hl=en.
>

[cfcrain]

We have a complete integration of mailchimp in our in house CMS, that
includes reports. The user (our client) is already logged in to our
system, so asking for a password to view a report on a campaign that
they created is confusing for them. I could understand the need for a
passoword if the report is going out through email, but they've
already authenticated once through us. Does that make sense?

[Barry Carlyon]

Looks like you might have to grab all the data over api and rebuild the report locally.
Or I wonder if you can call the api function to send a report to a friend and process the email inside the system.

I've not checked what the api can do stat wise as in my integration we just push opens/clicks and send the user to mailchimp (with login) for the full report

--------------------------------

Barry Carlyon
Freelance Web Developer
Freelance Lighting/AV Engineer

http://barrycarlyon.co.uk

mobile: 07729 048 443
skype: barrycarlyon
email: ba...@barrycarlyon.co.uk
msn: ba...@barrycarlyon.co.uk

[cfcrain]

The api stat functions are quite verbose (=excellent), but rebuilding
the reports isn't a quick fix and will take some time. I would have
liked to have a heads up. Was this change documented anywhere?

[jesse]

Wow, what a mess. The secure_url should have worked on subsequent
pages - it does now, which should fix things.

The deal with the "secure" option was me following change sets
incorrectly and not realizing that major changes had been made to the
vip reports (aside from the cobranding theme stuff) that hadn't
actually gone out in our last release. That's why you'll currently see
that in the app you can still share a vip report with no password.
That option is being completely removed in our next release in a
couple of weeks. Since I've already fubar'd things and the change is
going to be mandatory soon anyway, I'm not adding the option to not
have a password back.

Now that that's all cleared up, I will do a post announcing the
changes.


jesse

[cfcrain]

The password for the secure_url is persistent throughout the entire
report now. Awzum.

Thanks jesse,
katie