Hi, I recently updated to version 1.6.2 and now when clicking on the forum page on my website, I'm just met with:
Oops! The page you requested was not found!
I've been through every troubleshooting checklist I can find in the support threads and just exhausted every option including uninstalling/reinstalling but nothing has worked so far. Any ideas?
Hi, I recently updated to version 1.6.2 and now when clicking on the forum page on my website, I'm just met with:
404Oops! The page you requested was not found!
I've been through every troubleshooting checklist I can find in the support threads and just exhausted every option including uninstalling/reinstalling but nothing has worked so far. Any ideas?
same issue for me, when i add any attchment in post "error 404" occurs.
after changing media attachment setting issue resolved.
Settings>Features>Insert Forum Attachments to Media Library to "NO".
I don;t think they are related. And I don't think this option has any relation to 404. When you change an option you also delete all caches so I think your issue was the cache, and after deleting the cache problem is fixed.
Please deactivate and activate wpForo again. Then navigate to Dashboard > Forums > Settings > general tab, make sure the base URL is correct and click on [Update options] button. Then navigate to Dashboard >Settings > Permalinks admin page, and make sure you use WordPress permalinks, update those too.
Thank you for your reply. I've just run through that list and all seems to be in order but still seeing the error. Any other suggestions?
- Could you please explain why it redirects to /communityforum/ page when I call /community/ ? Have you setup any redirection rules?
- What is the forum page slug/url?
- What is the Forum base URL in Dashboard > Forums > Settings Page?
- Why your website contains "~" in URL? Could you please test it on real website?
@robert
I tried changing the Base URL to see if the issue was the standard 'community' URL. It currently matches the page URL, so that shouldn't be an issue. It didn't work as the standard 'community' URL either.
The forum slug is 'communityforum', as is the base URL in the Forums dashboard.
The website is a temporary URL while I wait to transfer the domain over. The previous version of wpforo worked perfectly on my website until updated to 1.6.2 and then this error started.
Please deactivate this version, delete it and install the previous 1.6.1 version. I need to see how it works. This will not affect any data, so do not worry.
This version works! There must be a compatibility issue between my site and version 1.6.2. How strange!
This version works! There must be a compatibility issue between my site and version 1.6.2. How strange!
Actually Disable this and try again:
<!--Generated by Endurance Page Cache-->
Also as Robert said something is very wrong in your setup, the base forum url and their navigation.
I'm not sure how to disable that. The previous version works with no problem?
I'm not sure how to disable that. The previous version works with no problem?
Ask your hosting provider how to disable. If it is a plugin IN your Wordpress disable/remove it.
Also install it to a real domain and check. This url (temp) is a bit strange and could cause some problems.
Thank you for your help. I will be moving the site to a real domain as soon as it is available to transfer to my host. I'm a bit new to all this website business so thank you for your patience and explanations. For now it seems to be working again 🙂
Thank you for your help. I will be moving the site to a real domain as soon as it is available to transfer to my host. I'm a bit new to all this website business so thank you for your patience and explanations. For now it seems to be working again 🙂
There is plenty of information how to disable Endurance cache (are you on BlueHost ?). Just google it.
Also this
http://box5848.temp.domains/~asevxfan/community/
http://box5848.temp.domains/~asevxfan/communityforum/generaldiscussion/
clearly show some settings error of your base url.
Thank you. I was in the middle of switching everything back over to the 'community' slug/base URL. That should all be in working order now.