Jump to content


Member Since 09 Sep 2002
OFFLINE Last Active Apr 18 2017 12:10

Topics I've Started

The problem 7%

25 March 2017 - 11:06

The records showed that 70% of my sales were made on the first interview, 23% on the second, and 7% on the third or after.  But listen to this; 50% of my time was spent going after the 7%.


"So why bother with the 7%" I thought.  "Why not put all my time on first and second interviews?"  That decision alone increased the value of each call from $2.80 to $4.27


Taken from "How I Raised Myself From Failure To Success In Selling" by Frank Bettger.

ISBN: 9780671794378.

Highly recommended.  


The questions I pose to you;


1. Is there anywhere in your shop or business activity where you can free up time?

2. Would you feel comfortable telling potential customers that they are not wanted?

3. Would you feel comfortable telling existing customers that they are no longer welcome?


Devious Trick or Super Smart

07 March 2017 - 12:25

I just bought an item (actually from a shop running Magento I think, but that's unimportant) that
was the last one in stock.

As soon as I bought it and confirmed Paypal, I went back to the shop and looked at the product.

The product is now marked "OUT OF STOCK", and has a special price of approx 25% lower than
I paid, along with "let me know when this product is back in stock".

I've no doubt that people searching will see this, sign up and be notified when back in stock. But at that time I suspect the price will be the same as I paid or higher.

In other words, the special price is only on there to get people to sign up for notifications.


Devious Trick or Super Smart ?

Autofilling forms

13 February 2017 - 11:35

More reading:



Code changes:



Discussion is welcomed as to whether this should go into Core.

If yes, why?

If no, why?

Warning: Mailchimp Users, update asap

06 December 2016 - 11:40

Mailchimp are sunsetting their v2 API at the end of this month.

As of December 31, 2016 all previous versions of the MailChimp API will no longer be supported, but will continue to be operational. Documentation and support for the older APIs will no longer be available. As such, we can no longer guarantee the availability of these older endpoints after that date. Any integrations built on these APIs will continue to function, but we’re strongly encouraging all developers to move off of the older APIs before the end of 2016.

In english:
At some point in 2017 your v2 Mailchimp integration will just stop working.

Update your integration to v3 API, pronto.

If you have questions, I will do my best to answer as best I can.

Changing a shop into a showcase

31 October 2016 - 13:16

Whilst working on a little project a few days ago, I came across something that I feel needs attention...


Old osCommerce user upgrading to Responsive osC. Old 2.2 shop is used only as a showcase (or put another way, there is no "buying" or "checkout" or "create_account", buy buttons are removed and so on). All of this is that typical hard-coded half thought out bulldust hackjob coding that we all see in historical shops...


Shopowner still wants to use his new osC as a showcase, but also wants to easily change that into a full-on shop at some point in the near future.


How to do this with no core code changes, or very minimal core code changes?


My Idea:


1.  HT module to deny access to choosable pages.

Mostly if the person browsing the site cannot sign up or access checkout...he cannot check out.

HT module created.  Easy enough.


2.  Customise Navbar/Boxes to remove ones not needed (eg, shopping cart link, checkout link, cart box etc etc)

All of this is built in already and can be done from Admin.

No changes needed.


3.  Remove Buy Buttons from everywhere, site wide.

This bit was more difficult, as we have no easy way to target these buttons. In product_listing module (used in multiple pages;  categories, products_new, specials etc) this is an admin setting.  Set the buy button to zero and it disappears.  OK, easy.




We are left with buy buttons at:  product_info.php, new products for month modules, probably other places too.


Potential Solutions:


A.  Add the same setting as found at the product_listing into the other places.


B.  Add a custom .css class to all buy buttons, then target .css to remove all buttons.


If we go with "A", we then limit shopowners who want to use osC as a shop but only have buy button at product_info

If we go with "B", we then limit shopowners who want to have a buy button only at (say) produt_info and nowhere else


Both of these are nuclear solutions.  


I have one more thought, which I believe is a decent way to do things;


Go with "B", but also give each button a customised css selector, as so:


(eg) product_info.php


tep_draw_button(IMAGE_BUTTON_IN_CART, 'fa fa-shopping-cart', null, 'primary', null, 'btn-success btn-product-info btn-buy');


(eg) new products for month module


<a href="<?php echo tep_href_link($PHP_SELF, tep_get_all_get_params(array('action')) . 'action=buy_now&products_id=' . (int)$new_products['products_id']); ?>" class="btn btn-success btn-index btn-buy" role="button"><?php echo MODULE_CONTENT_NEW_PRODUCTS_BUTTON_BUY; ?></a>


You can plainly see the two new added .css calls;


btn-product-info btn-buy

btn-index btn-buy


Assume that we do this similar things with all buy buttons - they each get a selector for the page on which they are located and a btn-buy.


CSS Examples


Remove buy button on product_info.php

.btn-product-info.btn-buy { display: none; }


Remove buy button on index.php

.btn-index.btn-buy { display: none; }


Remove buy button on (nested) index.php

.btn-index-nested.btn-buy { display: none; }


Nuclear Option, remove all buy buttons

.btn-buy { display: none; }


and so on.  Of course, these are .css examples and so are "just" hiding the button away from site.  


Anyway, if you got this far...and you have comments of relevance... please post.