Problem created by custom routing for react-router

  • Resolved Copernicus

    (@copernicus)


    3 years, 3 months ago

    We experienced an odd issue with, we believe, the newly-added feature of “Create custom routing for react-router based on slug of the reactpress page.” (which is listed as part of v1.3.2).

    We have our react app at (for example): ourdomain.com/reactapp
    and then we have another, non-react page at ourdomain.com/reactapp/subpage

    However, once we upgraded to v1.3.2 the page at ourdomain.com/reactapp/subpage was displaying the content of ourdomain.com/reactapp

    We rolled back to v1.3.0 and the issue was no longer occurring.

    We’ve only been assisting in connecting the WordPress site and the React app. We haven’t worked on the React itself, so I can’t say whether or not there’s something in the app that we could have done to avoid this issue with the latest version (v.1.3.2) of the plugin.

    Hope this helps someone else.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author rockiger

    (@rockiger)

    @copernicus Yeah, you are right. The routing feature doesn’t allow for subpages.

    Maybe I should make it optional. Thank you bringing this to my attention.

    Thread Starter Copernicus

    (@copernicus)

    @rockiger Making it optional would be great (otherwise we can never update!). And, it seems like it would be a fairly reasonable use case to have a need for non-React-based subpages (for other/future users of this plugin).

    Thanks again for your work & helpful support!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Problem created by custom routing for react-router’ is closed to new replies.