3

So here's the thing I never had the chance to get my hands on a Magento EE.

That said I still would like to make my extensions EE compatible.

Let's say we're dealing here with a normal CRUD module.

I'm looking for a canonical answer on how could I achieve that specially regarding FPC and indexing. (And more maybe ?)

6

I fear, that is way too broad for a canonical answer. At least you certainly cannot expect a checklist to follow without actually having to test your extensions in EE.

So get your hands on a copy and test:

  1. Full Page Cache. Turn it on and see if everything still works. Test with multiple sessions in parallel.

    To exclude blocks from the Full Page Cache, learn about hole punching with cache.xml:

  2. URL indexing. If you interact in any way with the URL index, you will need to rewrite that, because EE replaces the implementation completely. For example not all URLs are stored explicitly in the database anymore:

  3. Add to cart by SKU. If you do anything related to adding products to the cart, make sure that it also works with the "add to cart by SKU" form on the cart page.

  4. Password hashing. If you are dealing with customer passwords (for example, custom import), be aware that EE uses a different hashing algorithm.

This list is by no means complete, just first thoughts from my experience. Will update when more comes to mind.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.