Updated documentation to reflect the final, working solution:
Key changes:
- Clarified the three-step pattern: Extract → Fallback → Use
- Documented why complex conditionals in t-set fail
- Explained why intermediate variables are the solution
- Added detailed Git commit history (df57233, 0a0cf5a, 8e5a4a3)
- Included QWeb rendering limitations and best practices
The solution uses Python's native 'or' operator with intermediate variables,
avoiding complex conditionals that QWeb can't parse reliably.
Pattern:
1. Extract value: display_price_value = price_info.get('price')
2. Apply fallbacks: display_price = display_price_value or product.list_price or 0.0
3. Use in template: t-attf-data-price="{{ display_price }}"
This approach is simple, reliable, and follows QWeb best practices.
Quick reference index for the website_sale_aplicoop template error fix:
- Links to detailed analysis (FIX_TEMPLATE_ERROR_SUMMARY.md)
- Links to best practices guide (QWEB_BEST_PRACTICES.md)
- One-page summary of problem, cause, and solution
- Quick reference cards for safe variable patterns
- Navigation structure for easy access to all fix-related docs
This file serves as the entry point for understanding the template fix
and accessing all related documentation in one place.
- FIX_TEMPLATE_ERROR_SUMMARY.md: Complete analysis of the website_sale_aplicoop template error and its resolution
* Root cause: QWeb parsing issues with 'or' operators in t-attf-* attributes
* Solution: Pre-compute safe variables using t-set before form element
* Verification: Template loads successfully, variables render correctly
* Git commits: df57233 (first attempt), 0a0cf5a (final fix)
- QWEB_BEST_PRACTICES.md: Comprehensive guide for QWeb template development
* Attribute expression best practices
* None/null safety patterns (3 patterns with examples)
* Variable computation patterns (3 patterns with examples)
* Common pitfalls and solutions
* Real-world examples (e-commerce, nested data, conditional styling)
* Summary table and validation tools
These documents provide immediate reference for QWeb issues and establish
standards for template development in Odoo 18 projects.
- Add LAZY_LOADING.md with complete technical documentation (600+ lines)
- Add LAZY_LOADING_QUICK_START.md for quick reference (5 min)
- Add LAZY_LOADING_DOCS_INDEX.md as navigation guide
- Add UPGRADE_INSTRUCTIONS_v18.0.1.3.0.md with step-by-step installation
- Create DOCUMENTATION.md as main documentation index
- Update README.md with lazy loading reference
- Update docs/README.md with new docs section
- Update website_sale_aplicoop/README.md with features and changelog
- Create website_sale_aplicoop/CHANGELOG.md with version history
Lazy Loading Implementation (v18.0.1.3.0):
- Reduces initial store load from 10-20s to 500-800ms (20x faster)
- Add pagination configuration to res_config_settings
- Add _get_products_paginated() method to group_order model
- Implement AJAX endpoint for product loading
- Create 'Load More' button in website templates
- Add JavaScript listener for lazy loading behavior
- Backward compatible: can be disabled in settings
Performance Improvements:
- Initial load: 500-800ms (vs 10-20s before)
- Subsequent pages: 200-400ms via AJAX
- DOM optimization: 20 products initial vs 1000+ before
- Configurable: enable/disable and items per page
Documentation Coverage:
- Technical architecture and design
- Installation and upgrade instructions
- Configuration options and best practices
- Troubleshooting and common issues
- Performance metrics and validation
- Rollback procedures
- Future improvements roadmap
- Create .github/copilot-instructions.md with global development guidelines
- Add comprehensive README.md at project root with quick start guide
- Create docs/ directory for technical documentation
- Move installation and linter docs to docs/
- Add docs/TRANSLATIONS.md with complete translation system guide
- Create README.md for OCA modified addons (product_origin, product_get_price_helper, product_main_seller)
- Document translation best practices (no _() in field definitions)
- Add references between all documentation files
- Clean up project root by moving technical docs to docs/
All documentation now properly references addon-specific READMEs for detailed architecture and implementation.
