Cater for non-permalinks URLs eg https://example.com/?p=39

[bobbingwide]

Initially I didn't think it was necessary to support requests for a particular post ID but I discovered that it's necessary to detect when parameters are being passed to the URL since this affects the processing.

The requirement is to detect query params to deal with them differently

URL	Means
https://example.com/	display the home page
https://example.com/?p=39	display the post with post ID 39

Example scenario

• website: denisethatcher.com
• uses: WooCommerce
• if we deactivate WooCommerce on the home page then the link changes from https://denisethatcher.com/product/denise-thatcher-invades-britain/ to https://denisethatcher.com/?p=39
• Visiting this link leads to a 404

Aside: The [add_to_cart] shortcode doesn't work either but that's a separate issue to be addressed.

Possible workaround

• Register the product Custom Post Type using oik-types

Possible solution

• Add support for query parm detection. If the query parm is p=nn or page=nnn or even preview=nnn then don't treat this is a request for the home URL but find the URL using the ID.

[bobbingwide]

Aside: The [add_to_cart] shortcode doesn't work either but that's a separate issue to be addressed.

Additionally; the output from the shortcode had been disabled; hidden by CSS, 8 years ago. Don't ask me why!

[bobbingwide]

There's also a problem when the request is like https://ebps.co.uk/?post_type=tribe_events
This gets treated as https://ebps.co.uk/
Workaround: Change the URL to https://ebps.co.uk/events

Other menu items may not be processed due to taxonomies not being registered either.
Workaround

[bobbingwide]

The logic also causes a major problem with requests such as:

https://example.com/?wc-ajax=update_order_review
https://example.com/?wc-ajax=checkout

This is a major problem with WooCommerce sites, if you unload WooCommerce on the home URL.

• It prevents WooCommerce from responding to these requests.
• They're supposed to return some JSON.
• When WooCommerce is deactivated the result returned to the browser is the HTML for the home page.
• This isn't expected by WooCommerce's checkout.js
• It never enables the Place order button.

Workaround

• Don't deactivate WooCommerce on the home page.