Bug #1394

Properly Handle Intra-Domain Requests to Non-Elm Paths

Added by Pavan Rikhi 8 months ago. Updated 10 days ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:Pavan Rikhi% Done:


Category:CheckoutSpent time:-
Target version:v0.7.0 - Misc Pages & UI
Easy Pickings:


E.g., anything to /blog/.* should use Browser.Navigation.log instead of Routing.newUrl since everything under that path is our wordpress site.

I think /gardenplanner/ need this as well. Should check out the apache config & redirects to make sure that's all.


#1 Updated by Pavan Rikhi 10 days ago

Should I redirect to new sites, or simply call load and handle that in nginx?

/seedracks/ -> seedracks.southernexposure.com
/gardenplanner/ -> gardenplanner.southernexposure.com
/newsletter/ -> use load
/blog/ -> use load
/hff/ -> heritageharvestfestival.com

Also available in: Atom PDF