Guides & Documentation Site Back To Tiny Brick Store

Before You Purchase

Why don't you sell a version for 1.3?

We used to. However, the territory that comes with developing modules for Magneto is that the makers of Magento can update the source of their products whenever they like and we are subject to their changes. Much of the time, these changes help, rather than hurt our products. However, in the case of True Order Edit, a major change with 1.4.1.0 flatten of the sales tables (from EAV) and required a major refactoring. Instead of continuing to develop two versions of the module, development has stopped for the version developed on 1.3. We're looking into bridging the versions but don't have any updates at the moment. We do sometimes offer a 1.3-1.4.0 compatible version to customers who purchase the current version, but we don't recommend it. It's no longer supported, won't receive further development, lacks a custom shipping field, and has no ability to re-auth when the order total changes. If you still think you need a copy of this, purchase our current version and forward a copy of your purchase confirmation email to and we'll see if we can dig around in our archives to get you a copy.

My developer has done some modifications to Magento but most of them are minor. What do you mean by "this module will work in an unmodified Magento core"?

For a developer, modifying the core usually involves modifying any code inside the app/code/core folder of the Magento application. Magento is meant to be extended/overwritten...not altered. If a developer is making changes to your application by editing code app/code/core, they don't understand this difference and their changes will be erased if Magento is ever upgraded. That said, routine layout changes or extending core functions, rather than altering, should not cause conflicts. Also, even if core modifications are made, the module will likely work, unless the modified code influences caching. So, instead of trying to say which part of the stove isn't going to burn you, it's just typically better to say not to touch the stove at all. If you do, we'd like to not be responsible for any pain that came as a result.

Is it possible to test a module for a few days before ordering?

Unfortunately, we don't offer a free trial. Once we've released the code for implementation, we can't recall it, and prefer to avoid the possible issues surrounding that circumstance. In some cases we can issue you a development license for lightspeed, but it is subject to a few restrictions on the base URL of your development environment. Other products aren't available on a trial basis, but if you'd like to see the modules in action we do have demo servers. As always we do offer a 15-day grace period for returns. If things don't work out for any reason in that first 15 days, we'll give you a full refund. Note: You may be asked to allow access to your admin to ensure TinyBrick products have been completely removed.

Are updates / upgrades free of charge?

Ongoing updates are FREE for the life of the product, unless a major upgrade revision requires a major re-architecture of the module. To date, only True Edit Orders has required this once.

What are your payment options?

Currently, we only accept PayPal, although you can checkout using a credit cart without actually creating a PayPal account.

Do I have to pay twice for two domains? Is there anyway that I can purchase your plugin at a discount… Maybe 25% off… Not even a first time happy customer 10% off… Bulk discount pricing?

Modules are sold per domain, and are registered to 1 domain. We offer bulk discounts for the following volumes:

  • 2 = 20% off
  • 3 = 30% off
  • 4 = 40% off
  • 5+ = 50% off
  • The TinyBrick shopping cart will automatically apply these discounts. If you end up purchasing your licenses at separate times, please contact a representative to arrange the promotional discount. You may also want to check out our policy on development licenses.

Can I view or try these products out on a demo server?

Yes! Please use the demo servers to test out any scenarios you're curious about. Log in credentials are on the admin log in screen.

I notice your modules are priced per domain. How then do I test in my development environment without buying another license?

We strongly encourage dev environments, so we try to do everything we can to accommodate them while still protecting our licenses. So when you are purchasing your original license, purchase it for your ultimate live domain. Then for your dev domain, here are some options: Subdomains: Your domain license will automatically include unlimited sub-domains. (e.g. test.domain.com, beta.domain.com, etc.) Local Domains: Your domain license will automatically include local domains. (e.g. localhost, 127.0.0.1) Dev Domains: If needed, you can request a dev license for a domain or IP that is clearly for development. (e.g. testdomain.com, betadomain.com, devdomain.com, test.domain.com, 67.23.44.251, etc.) We suggest purchasing your initial license for your live domain, then emailing sales@tinybrick.com with your request for a dev domain. 98% of the time we can accommodate your development domain request free of charge.

Installation

I followed the basic installation instructions for my module, but it's not showing up. What's going on?

This is a very common bug in how Magento refreshes the admin view. After installing a new module you may be required to force a refresh the admin. Let's walk through how to do that:

  • In the admin panel, browse to System -> Configuration -> Advanced (In the advanced section at the bottom left)
  • On the left there should be an expandable panel. If not already expanded, expand it.
  • It should show a long list of modules. Near the end of the list, you should see one or more of modules labeled "TinyBrick_ModuleName". If you do not, then browse back to the top and click "Save Config".
  • After saving, browse to System -> Permissions -> Roles. Open the Administrator role (Since most people are logged in an administrator anyway.)
  • Don't edit anything in the role, and click "Save Role".
  • After save is complete, you may have to log out and back in, but most likely if you browse back to the long list of modules mentioned earlier, you should see the installed module.
  • There are a few other possible things to do to get the installed module to start showing up (like clearing all caches in System -> Cache Management, logging out and back in, or disabling and re-enabling the output of a module in that long list while saving in between changing state), but if these steps do not produce an output like you're looking for, then there is probably a larger issue like a module conflict or a step you missed during installation.

toc

Powered by Olark