easyio split domain with WOM causes conflicts
Closed this issue · 1 comments
nosilver4u commented
If a secondary Easy IO domain is configured in WOM, then Easy IO won't activate.
Also, it seems there are some notices introduced when you DO get it to activate.
nosilver4u commented
Even with several work-arounds, this is just completely busted at a very low level, and doesn't seem worth trying to sort.
Notably, for future reference, with the correct domains in place, and making sure Easy IO isn't rewriting S3 URLs, some of the local URLs have the wrong folder structure.