Coconut Tickets WordPress to Laravel Migration – part 3
Part 3 – Technical Migration
In the last 2 parts of
we explored the motivation behind taking the risk of migrating the successfully working Coconut Tickets platform from WordPress to Laravel and the strategy that was used. In this part we dive deeper into the technology and look at the big technical decisions that were taken. Identifying the boundaries between the Coconut Tickets plugin and WordPress itself was critical to making the migration technical decisions. Using a combination of knowledge of our software and performing text searches for common WordPress function names (mainly starting wp) we analysed the use of the WordPress API with our plugin. This is where the yearly subscription to PHP Storm really delivered because we could find WordPress functions, and then (using PHP Storm) track their usage across the classes of the plugin which is more valuable than a simple text search. We identified the following areas that use WordPress directly and would need to be re-developed to work with Laravel.
In the next post in this series we discuss how we migrated the WordPress plugins and theme.
Find out more about