31

TLDR; In general, my preference would normally be to use a snippet, unless I need the variable content to be user editable (eg site email), and to only use an embed when parse order issues or similar necessitate it. Here's why... Snippets: Snippets are frequently my first choice for implementing reusable code fragments in EE. They are parsed at a very ...


13

No direct experience doing this, but I'd take this approach initially: Each "tier" is a channel entry. You could include things like price, description, etc. here (perhaps this is also a "products" channel used by CartThrob or Store, used to "sell" the tier). Use an add-on such as Zoo Visitor or Profile:Edit to create members as channel entries, then use a ...


8

All three of these are used for enabling you to not repeat yourself when building sites, but they vary in functionality quite a lot. Global Variables Global Variables are used generally for storing pieces of content that might not be be part of an entry, for instance a contact form email address, a store address, etc. You can not use EE tags within a global ...


3

I've not seen or heard any chatter about this, but I definitely prefer to keep all directories and files which shouldn't be replaced during an EE upgrade in my /assets directory like this. If I can place /system below root I leave the system third_party directory there for better security. If I can't place /system below the root... Third party /system ...


3

It's really your choice here. I imagine that this framework is best for smaller addons. One point of access is always slightly frowned upon; because it creates a SPOF in your addon. Trust me, I totally get the code-install-test-uninstall-ad.nauseam development path of EE modules, I'm sick of it too. However, I've found, that paying more careful attention ...


3

I think we'd need a little more information on the content structure and how you want to output the data. Relationships are possible, but on first glance I'd probably look at using Tags for the colours. You could use categories for colours, then assign relevent products to each relevent category - that would allow you to browse by colour, or pull in a list ...


2

You could duplicate templates and alter their names but I'd only do that if there where only a handful of items. If you have more then is manageable by simple duplication then it warrants the creation of a dev server and work directly on the templates then transfer across to live once happy with new codebase. You can always backup the code by using git and ...


2

WYGWAM inserts images with {filedirX} in place of the actual path to the image. So changing the domain name (or replacing site2.com/somefolder with /somefolder for folders within File Manager should work without a hitch. Thanks @kristengrote.


2

Bluedreamer is right, using tags for your colors might work great. But if extra data needs to be stored along with your colors, then storing them as fully-fledged entries is probably better. * If you do need colors to be entries, you could just use the following set up: Create two Channels: "Products" and "Colors" Assuming a product has many colors: In ...


1

First you would need to to decide which integration method you would like to use probably either PHP, API or JS. With the data you want to collect you would probably be best to use the PHP or API integrations (PHP link or API link). From there you have a few options: Write an extension (my recommendation) Modify the index.php file to include the PHP script ...


1

There's always the Custom System Messages addon - http://devot-ee.com/add-ons/custom-system-messages - which allows you to run things like error messages through regular templates. That way EE upgrades don't affect the message text.


1

It seems to me that the best way may be to simply use Categories for both Regions and types of events. That's not native to the Calendar module, but seem like it wouldn't take much to filter by a category url title. That is the direction I would go. Two category groups -- Region and Type -- with Areas being subcategories for the Regions. You'd want to make ...


1

I've used P&T's Assets to create something similar to this. They wanted to display their current document repository on their website using the same folder structure. With the latest version of Assets, you can upload everything to the server via FTP, then use Assets to sync it with EE; you just create the file upload location as the parent folder of the ...


1

That's one of the limitations of native category handling in EE. You can grab it with some PHP but even easier is to use Low Seg2Cat which is to remedy this type of case. You can simple use {segment_n_category_name} to output the category name from the segment in the URL where it is displayed. So if you have a URL such as: mysite.com/products/category ...


1

Haven't done this myself, but did need a sort of multiple "groups" or member "tagging" kind of feature. The easiest way it seems to do this in EE is to expose Channel Categories as a Member field or something similar. There are two commercial add-ons I know of that do this: IntoEEtive's Member Categories and Addon Bakery's Member Categories. I chose to ...


Only top voted, non community-wiki answers of a minimum length are eligible