Pulse (ELM5) Beta Release

A beta release of Pulse was made available earlier this week and we are now ready to make it more widely available. There are still some features we are adding, e.g. better pagination of long reports, more user options, but in terms of data collection, the module appears to be working well. Installing the beta will not jeopardize your data–each new release will retain your existing data. Get it here: Pulse - Store Statistics for Merchant 5
With us leaving for the Miva Merchant conference on Wednesday, updates are unlikely to be released during that time frame but we will be covering support.

p.s. Here are some of the forthcoming additions to Pulse:

- hide User Agents from general reports (so they don’t take up as much space). This will be optional though as many people get a buzz when the search bots show up

- truncate/wrap long referer* urls (need this in order to prevent long urls from bleeding)

- add pagination to long reports

These have already been partially implemented so we hope to have them available in the next update.

* Did you know that “Referer is a common misspelling of the word referrer. It is so common, in fact, that it made it into the official specification of HTTP – the communication protocol of the World Wide Web – and has therefore become the standard industry spelling when discussing HTTP referers.”?

Thanks Wikipedia.

Update 03/05/08: we’re back from the Miva Merchant conference and working on Pulse. Today we have added a product name field with sorting to the Product Stats, fixed a bug that arises when you are blocking IP addresses, and changed to Order Stats referer so that it picks up the initial referer–the site the visitor came from rather than the page that lead them to the checkout. (In hindsight, it’s obvious that’s what it should have been doing but these things sometimes get overlooked when you’re knee deep in the code!) There isn’t an update as yet as we also want to include a handful of other tweaks and fixes.

Hot off the presses, figuratively speaking, it’s Affiliate Manger - Login for 5.x!

Like it’s 4.x predecessor, the Affiliate Manager - Login module provides an interface that Affiliate Manager affiliates can use to view and/or modify (that bit is optional) their personal and referral data including hits, orders, payouts paid, and payout’s due. The layout and content of the pages are entirely configurable from within the module’s admin; the outer portions of the Merchant pages are maintained by Merchant “page templates”; and the main content is configured by the module’s own “templates and token”. The best of both worlds in that you can control things like the navigation bar, category tree, outer table, etc. in the same manner that you do with stock Merchant but you can control the main contents of the page from within the module’s main admin with our more robust, module specific, tokens.

Continue reading Hot off the presses, figuratively speaking, it’s Affiliate Manger - Login for 5.x!…

Update on Pulse

Well…we’d hoped to have this ready today but I have a shortened day–celebrating a belated Chinese New Year at my son’s (and wife’s) school. There are several cosmetic issues that need addressing but, more importantly, it hasn’t been tested extensively yet under the same condition that you will encounter when you install it, i.e. when the logs are still empty. So profuse apologies for the delay. Hopefully we can get some time over the weekend and have it ready for Monday.

Here are some screenshots so you know that it really does exist:

Product Flyout - AJAX has arrived!

The world of AJAX has arrived in module form to the world of Miva Merchant! We have just released a new 4.x module, Product Flyout, that allows you to mouse over products in your store and see a pop-up displaying the product name and description (think Netflix). Product Flyout requires our template modules and the OpenUI to work properly. Register Product Flyout as a Third Party Token, replace a token or two in your templates, and you will have dynamic pop-ups in your store!

The module is currently compatible with:

• (added 3/10/08) Storefront Template
• Category Page Templates
• Other Page Templates
• Product Page Templates (mainly for use in the related products template)
• Search Manager

The module is in beta and is selling at a discounted price of $40. After we test it out and work out the kinks, it will be priced at $49.95.

http://vikingcoders.com/go.mv?ID=LC_FLYOUT

We plan on releasing a 5.x version of this module as well. Be on the lookout for other AJAX modules over the coming weeks and months!

- Luis

Affiliate Manager 5 and Other Development Campaigns

I’m always surprises me at how quickly time passes (Thursday already!?). By now you’d think I would have adjusted my expectations. I had intended to post every few days but that didn’t last long.

The update of Affiliate Manager to compatibility with Merchant 5.x (although it’s a bit of a stretch to call it an upgrade given how much re-writing had to be done) has been done for a number of weeks now but the development of the module is still on going. It was my intent to add the ability to permit “product specific” payout configuration (i.e. the ability to, on an affiliate-by-affiliate basis, set different payouts for different products) to the initial release. However, I ran into some indecision on how best to implement it which slowed it down enough to get left out. I am still working on it but the indecision remains on how best to go about it. I polled a few developers who were looking for the features for their opinion on how they saw it as working but I never got a reply. So, I’ll lay out some possibilities and see if any one out there has an opinion (more specifically an opinion on how best to go about it….we all have opinions but not all are particularly relevant to this particular question).

In earlier versions of the module, “product specific” payouts were sort of a hack (and that hack still works in 5.x). The merchant would set each product’s “cost” to a particular value, then configure each affiliate’s payout to be based on a % of the product’s cost and thereby achieving a variable payout for each affiliate. Of course that kept you from using the cost field for anything else, but it was a nice representative of that “bang a square peg into a round hole” mentality that typified the glory days of Merchant (ahhh, the memories).

In the 5.x version of the module I’d like to add this as a more particular option configurable on each product’s page in admin. The question is how far to take it; how many options are really going to be used? Currently, each affiliate can have their payouts configured as a percentage (of the price paid, product cost, list price, or “profit”), a “per purchase” payout, and/or a “per product” payout. And each of these can be configured separately depending on what “level” the a referral was. Do we need that many configurable options for the prdouct-specific payouts? Would it be safe to assume that product-specific configurations would be necessary only for “primary” affiliates (i.e. those directly responsible for the referral)?

I’m currently in the process of upgrading/re-writing the Affiliate Login module and hope to have that ready next week. After that will be a new module, Affiliate Design which will replace the “Affiiate store-settings” feature of Affiliate Manager 4.x. I’m not entirely certain how best to go about changing the Merchant 5.x templates but I’m sure I’ll get it worked out.

I have been pushed off the boat…it’s the Viking way

After months  of managing to find a millions reasons not to get my feet wet in the “blogosphere” my fellow Vikings have taken the “sink or swim” approach and pushed me off the boat.   I’m averse to death so here you have it, my first blog post.

Last year we attended the Rails Conference.  One of the speakers asked the crowd, a room of  maybe 1000 people, how many had blogs.  Very nearly 1/2 the crowd raised their hand.   I personally doubt that 500 people in that room really had something to say worth reading.  And I suspect the same can be said for most of what I  would really like to say (which is probably where all those other bloggers go wrong).  That said, I’m going to try to focus on what you might be interested in reading, mainly information on our modules and development (current and future).  Also feel free to make suggestions on subjects you’d like to hear me ramble on about.   At least that way I’m guaranteed at least one interested reader.

First up will likely be a discussion on the upgrade of Affiliate Manager to 5.x.

Michael Brock
a VikingCoder

Hyper Development Mode!

Hyper development..maybe not, but it does save a few clicks. Here’s how I use Miva Merchant with MySQL for local development:

I use Instant Rails (Ruby, Rails, Apache, and MySQL all bundled together–there are similar suites for php). What’s nice about this, and the php versions, is the inclusion of phpmyadmin, so you get an environment very much like a web server.

I also use a batch file to fire everything up at once, launching myself into a hyper-productive development mode…in theory. Here’s the batch file:

@echo off
start /d “C:\Program Files\EditPlus 2\” editplus.exe
start /d “C:\MIVAMia\BIN\” Mia.exe
start /d “C:\InstantRails” InstantRails.exe
start /d “C:\Program Files\Mozilla Firefox\” firefox.exe “http://vc3/merchant.mvc|http://127.0.0.1:8000/mysql/|http://vc3/admin.mvc?username=x&password=y”

That Firefox command opens three tabs–store, admin and phpmyadmin. There is an about:config setting you need to change in Firefox if you want those tabs to not overwrite your existing window. Don’t recall it offhand but it may resurface in my memory at some point.

Bret.

2008 …with a vengeance

So far I’ve done pretty well with the new year and haven’t yet signed a check, written a letter, or added code to a module with the wrong year. Dreamhost did. Badly. And it’s a nightmare for them, despite the forthright and somewhat amusing blog. Check out their Um, Whoops! here.

37signals, the Rails people, used this as an example of why it’s a good idea to not kowtow to “flexibility” when developing–don’t add a feature just in case someone needs it.

ELM5 Scheduled for release in the New Year

ELM5, now renamed Pulse will be released as a public beta in early January. The module has been rebuilt from the ground up to take advantage of the superior database power available when using mysql. As such, the module will not be available for mivasql stores–the overhead and limited functionality of dbase just does not make sense for a data intensive module like this. If you’re not sure which database you are using, click on Main in your admin and in the top right corner, you’ll see something like:

Production Release 3
Miva Merchant Engine v5.06
Database API: mysql

mysql is the magic word here. If you’re not using mysql, you may want to take advantage of the free Miva Merchant mysql conversion tool.
If you’ve used ELM Stats previously and there’s something you felt was missing from it that you’d like to see in the 5.x version, please let us know in the comments.

The Efficacy of “Click Here”

The Efficacy of “Click Here”, Site Redesigns, Getting Physical and Whatever Happened to Urchin? 

Click here for an interesting post on the power of using “click here”.

Inc.com has a good analysis of two sites that were modified to improve conversion rates. And here’s an account of a popular online store that has gone brick-and-mortar.

Arstechnica looks at what happened to Urchin after it was bought out by Google.