debugging module metadata in OXID eShop

debugging module metadata in OXID eShop

While developing modules, there will be many situation when nothing works and you wonder, if your shop noticed the new updated metadata.php and why it was not able to find module’s templates or block files.
New developers will do the mistake and try to check cached entried in oxconfig table, but to prevent their success, oxid saves all settings as binary data. That makes retrieving settings from database outside of the shop framework almost impossible. (You need a particular key to decode values and some magic sql query to release the kraken)

Metadata inspection made easy

Dev-modules not only extends your OXID admin panel with a viewer for all the cached entries from metadata.php files, it also adds some basic checks for file paths and filesystem permissions to help you find currupted entries.

debugging module metadata in OXID eShop
class extensions
debugging module metadata in OXID eShop
custom classes
debugging module metadata in OXID eShop
templates
debugging module metadata in OXID eShop
template blocks
debugging module metadata in OXID eShop
module paths and events
debugging module metadata in OXID eShop
metadata per module
debugging module metadata in OXID eShop
search function
debugging module metadata in OXID eShop
file path check
debugging module metadata in OXID eShop
template blocks debugging

 

 

 

0.00 avg. rating (0% score) - 0 votes
0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *