WPIntell

Source evidence

Plugin using Shortcode – No Longer works

Redirect 404 to Homepage · support · 2024-09-05T12:51:00+00:00

complaintsentiment
mediumseverity
0.92relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 34 rows with source links

14.7% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
andyfarr unresolved
When ever I have the [Redirect 404 to Homepage] Plugin activated my plugin “SEATREG” no longer loads the floorplan. Instead it just opens the Homepage in its place. Is they a way to ignore certain Pages? The page I need help with: [ log in to see the link] Hi @andyfarr , That sounds like something might not be working correctly in the shortcode (is it this plugin ?). Which shortcode are you using in the page to display the floorplan? I’ll see if I can take a closer look at how that works and we may be able to get the page working. As background, this plugin uses WordPress’s core is_404() function to check whether to redirect to the homepage. If something redirects to the homepage, it means WordPress “thinks” it is missing or does not exist. So it may be important to fix that for best results. Looking at the page you’ve linked, the floorplan is linked via an iframe at https://www.edgevenue.co.uk/seatreg . However that page doesn’t seem to exist, so is a 404. Is that a page you created yourself? If not, it might be automatically generated by the SeatReg plugin, in which case it doesn’t seem to be working correctly. Sorry, I should have investigated further before posting my previous message. Looking at the code of the SeatReg plugin, it is hard-coded to link the floorplan shortcode to the home page url + the word “seatreg” (in the getRegistrationURL function). So it is something the plugin has created, rather than yourself. As such, you will need to contact the author of that plugin to ask why that page is returning a 404. Normally I would expect such a page to return a 200 code if it is used for publicly displayed information. Please feel free to link them to this page for reference. Let me know if any questions come up and I may be able to help. Thanks for the quick reply @pipdig !!! I copied a link to this thread and sent it to the other Dev of the conflicting Plugin SeatReg. Not sure what I can do on the matter. I hope they can find solution for myself soon. This reply was modified 1 year, 8 months ago by andyfarr .

Comments

4 shown
pipdig 2024-09-05T13:20:00+00:00

Hi @andyfarr , That sounds like something might not be working correctly in the shortcode (is it this plugin ?). Which shortcode are you using in the page to display the floorplan? I’ll see if I can take a closer look at how that works and we may be able to get the page working. As background, this plugin uses WordPress’s core is_404() function to check whether to redirect to the homepage. If something redirects to the homepage, it means WordPress “thinks” it is missing or does not exist. So it may be important to fix that for best results.

pipdig 2024-09-05T13:25:00+00:00

Looking at the page you’ve linked, the floorplan is linked via an iframe at https://www.edgevenue.co.uk/seatreg . However that page doesn’t seem to exist, so is a 404. Is that a page you created yourself? If not, it might be automatically generated by the SeatReg plugin, in which case it doesn’t seem to be working correctly.

pipdig 2024-09-05T13:29:00+00:00

Sorry, I should have investigated further before posting my previous message. Looking at the code of the SeatReg plugin, it is hard-coded to link the floorplan shortcode to the home page url + the word “seatreg” (in the getRegistrationURL function). So it is something the plugin has created, rather than yourself. As such, you will need to contact the author of that plugin to ask why that page is returning a 404. Normally I would expect such a page to return a 200 code if it is used for publicly displayed information. Please feel free to link them to this page for reference. Let me know if any questions come up and I may be able to help.

andyfarr 2024-09-05T15:57:00+00:00

Thanks for the quick reply @pipdig !!! I copied a link to this thread and sent it to the other Dev of the conflicting Plugin SeatReg. Not sure what I can do on the matter. I hope they can find solution for myself soon. This reply was modified 1 year, 8 months ago by andyfarr .