Bug #1394

Properly Handle Intra-Domain Requests to Non-Elm Paths

Added by Pavan Rikhi 12 months ago. Updated 19 days ago.

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


Category:CheckoutSpent time:-
Target version:v0.11.0 - Pre-Migration Requirements
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.

Associated revisions

Revision 97b49481
Added by Pavan Rikhi 19 days ago

[#1394] Properly Handle Links to External Pages

Add a new Redirect route to the client for parsing URLs that resolve to
external services, such as the Wordpress blog at `/blog/`, the HHF
website at `/hhf/`, etc.

Modify the webpack configuration to proxy the Wordpress blog & the
newsletter pages.

Closes #1394


#1 Updated by Pavan Rikhi 4 months 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

#2 Updated by Pavan Rikhi 4 months ago

  • Target version changed from v0.7.0 - Misc Pages & UI to v1.00.00 - Deployment

#3 Updated by Pavan Rikhi 22 days ago

  • Target version changed from v1.00.00 - Deployment to v0.11.0 - Pre-Migration Requirements

#4 Updated by Pavan Rikhi 19 days ago

  • % Done changed from 0 to 100
  • Status changed from New to Closed

Also available in: Atom PDF