This question was discussed about 2 years ago.
Do we have any feature built-in Mandrill since then to cater to the requirement mentioned in that link of displaying every email sent through Mandrill in browser by adding a "View In Browser" link? If not, then I am leaning towards implementing something similar to what #Muleskinner did (again mentioned in that link as one of the responses). Please let me know what you guys think about it?
Would strongly recommend using a full-featured templating service on top of mandrill (we use sendwithus. Services like that provide a templated URL that can power this sort of thing, and you won't have to worry about building and hosting the templates yourself.
Finally I have managed to implement the requirement mentioned above. Explanation below for anyone else looking for help on the same subject:
Mandrill still DOES NOT have any such feature out of the box. So we need to implement this on our own. What I am doing is immediately after sending every email through Mandrill, I call its Render method which gives the resultant parsed template in HTML with all customers' information and storing it in the system for future use.
Related
I'm currently trying to send emails from a Rails application and would like to check the open/click rates of these emails. (without using any web service) Is there a gem or plugin that I can use to help me find out? Or is it even possible to do this?
Take a look here:
http://www.codingforums.com/archive/index.php/t-122920.html
I think the first mentioned method, detecting how many times an image has been viewed would be the easiest. Then again, these are not exact solutions, but I think an exact solution would be sort of a security hole (i.e. sending an HTTP request to a foreign server once you open an email).
Varatis is correct, using image tracking is the most common way this is done, and it is the way that most web services provide you with analytics on the e-mails they send on your behalf. Here is another Stack Overflow question that includes an example of how you might do this in Rails.
I've been doing some programming off and on for my brother, who is a stock trader. I'm wondering if it is possible to receive a push notification when a site server adds a page. For example, the site smallcapfortunes.com frequently adds pages that are simple extensions off the main URL. For example, the site regularly adds pages under URLs such as /neca/, /stev/, etc.
Are there existing methods to execute this? Or is this something I need to write myself? Has anyone here written anything like that?
I know there are existing sites to track basic updates to a single page. In my research, though, I haven't found anything like this.
Please let me know if there are any other details I need to provide.
Generally you can only get a push notification if a specific website offers that service.
Some websites publish a structured (XML) site map. If the one you're interested in does that, you could pull that sitemap on a regular basis and look for differences.
you're most likely going to want to use http://scrapy.org/ to go through the site and find new /neca/ and /stev/ urls, etc, then just trigger the script every so often.
For an event in a couple of weeks I'd like to make an web page/app which display tweets from a specific user, a specific hashtag and all #reply's at the first user in 3 boxes on the screen.
However I've never tried this. I want to use either .NET (C#) or HTML/CSS/JS since I'm proficient in those. Are there any libraries/API's I can use? Or is there an readily available freeware/open-source app I can use?
Have you seen TweetSharp?
Use Twitter's profile and search widgets. Profile for the first box, a search of the hash tag for the second box, and a search of to:username for the third box.
I actually just posted this as an answer to another question:
I just updated a plugin to work with the Twitter 1.1 API. Unfortunately, per Twitter's urging, you will have to perform the actual request from server-side code. However, you can pass the response to the plugin and it will take care of the rest. I don't know what framework you are running, but I have already added sample code for making the request in C#, and will be adding sample code for PHP, shortly.
The plugin makes a call to statuses/user_timeline, but you will likely want to look at statuses/filter or statuses/search, instead. All you will have to do is add your desired parameters (hashtag, replies, etc.) to the server-side code and it should work (with the addition of your security keys and tokens, of course).
Good luck! :)
In JIRA it is possible to create new issues through a simple GET request: http://confluence.atlassian.com/display/JIRA/Creating+Issues+via+direct+HTML+links.
A simple example of such a link:
"http://jira.atlassian.com/secure/CreateIssueDetails!init.jspa?pid=10420&issuetype=3&summary=say+hello+world"
This would create a new issue in project with PID=1042 with summary "Say Hello world".
Is there Redmine plugin/api which allows for such a use case? The REST API is inconvenient for my use since I would like to allow users to create new issues (with pre filled data) through a link sent in email and I don't want to use JavaScript for the job (to send the REST json/xml data).
EDIT:
From what I see (http://www.redmine.org/projects/redmine/wiki/RedmineReceivingEmails) Redmine provides an email API for submitting issues, this would be a parital solution. I would be able to add a "mailto:" link which would pre fill the content of the message.
This solution requires additional emails so still I would prefer to have a post link solution.
I have implemented a basic plugin which fulfills my needs. You can find it at:
http://code.google.com/p/redmine-post-link-plugin/
You could also have a server-side script that actually sends the e-mail. There's no post link solution as far as I know.
You might want to look at the Redmine API for updating and creating issues.
http://www.redmine.org/projects/redmine/wiki/Rest_Issues
In Redmine2 there is oficial API for it.
Now that idselector has been upgraded to RPXNow and you can't "just use" the selector code, what is a good replacement?
I want to implement OpenId on a new website that I am using, but the users are going to be just dumb when it comes to logging in unless I provide an easy way for them to.
As a reference, I will be using .Net Open Id for the background in an ASP.Net MVC web application.
EDIT
After some cheap thought, what about using the rpxlib?
Jarrett Vance made a "version" of open-selector that is much more developer/designer friendly.
This selector is different because it does not hide the markup details in javascript. Therefore, you can easily add new providers or rearrange the existing ones without digging into the javascript. The login form will still work for normal OpenID logins if javascript is disabled
The best of all, is that it comes with documentation, demo, and lots of images both cropped and as raw .pdn files (paint.net)
Jarrett Vance's openid-selector can be found here
(source: jvance.com)
PS: I would suggest reading this article before implementing RPX.
Another one to consider is http://code.google.com/p/openid-realselector/ (which is a rewrite/update of http://code.google.com/p/openid-selector/)
I have done an implementation with RPXLib and RPXNow, and it is really pretty straight forward.
I wanted to minimize the amount of work done in the OpenId format, and the RxpLib definately helped with that one.
RpxNow also has a nice feature of telling me new users, number of logins per day, etc...
I've made Open-selector, which you just add to your site and switches the regular OpenID box into a provider list and a username text input.
The code is pretty simple (in case you need extra customization) and there is an inline mode so it doesn't alter your original layout.
I was using that one, but then I found a few people using a different one which made me investigate, and I found this OpenID selector. There aren't any instructions per se other than the demo.html, but it shouldn't be too hard to figure out. Just include the css and js, then call the javascript function with the right parameter.
Edit about rpx: I chose to stay away from rpx because I didn't want to have a 'central point of failure,' and a site that isn't my own that users would authenticate to/through. It seems kind of counter-intuitive being that I'm using openid, but if you consider that the openid provider that the user is using as part of the user, then it kind of makes sense.