Recent content by jgaulard

  1. jgaulard

    Guest Redirect

    @AndyB - Is this addon updated for the latest version? Also, it'd be awesome if there was a redirect option for "attachments" as well. So instead of having them serve 403 pages for guests, they'd be redirected to some other page, such as the login page.
  2. jgaulard

    XF 2.3 Upgrade Error: Requested Resource Does Not Allow Request Data With POST Requests

    It appears that changing the values for ModSecurity worked. I've now updated one of my websites. The only issue I've found so far is that my logo has shrunken. Thank you for all of your help. Jay
  3. jgaulard

    XF 2.3 Upgrade Error: Requested Resource Does Not Allow Request Data With POST Requests

    Thank you for this. I took a look at the error logs and I found this: [Fri Sep 06 16:34:29.503332 2024] [:error] [pid 3804716:tid 3804748] [client 172.70.569.5:53016] [client 292.70.187.5] ModSecurity: Request body no files data length is larger than the configured limit (131072).. Deny with...
  4. jgaulard

    XF 2.3 Upgrade Error: Requested Resource Does Not Allow Request Data With POST Requests

    Hi, I changed the php variables and I am encountering the same issue. Here are my server variables: Any more advice? Thank you.
  5. jgaulard

    XF 2.3 Upgrade Error: Requested Resource Does Not Allow Request Data With POST Requests

    Thanks very much. I'll have my host look into changing these settings. I'm running a VPS, so they'll need to do it globally.
  6. jgaulard

    XF 2.3 Upgrade Error: Requested Resource Does Not Allow Request Data With POST Requests

    Hi there - I attempted to upgrade from version 2.2.16 once again from the control panel with this latest version (2.3.3) and I am receiving the same message on an otherwise blank page: ---------------------------------- Request Entity Too Large The requested resource does not allow request data...
  7. jgaulard

    XF 2.3 Upgrade Error: Requested Resource Does Not Allow Request Data With POST Requests

    Hi there - I attempted to upgrade once again from the control panel with this latest version and I am receiving the same message: ---------------------------------- Request Entity Too Large The requested resource does not allow request data with POST requests, or the amount of data provided in...
  8. jgaulard

    XF 2.1 remove all thoses useless 301 redirect

    It's my suspicion that if you simply leave the 301 redirects alone and not have anything link to them, Google will slow crawling to them and ultimately drop their crawling of them altogether over time. So basically, once you stop linking to them, there's nothing more you'll need to do. Let me...
  9. jgaulard

    XF 2.3 Upgrade Error: Requested Resource Does Not Allow Request Data With POST Requests

    Hi, I am attempting to update from 2.2.16 to 2.3.2 from the control panel. I am receiving this error directly after pressing the upgrade button: The requested resource does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit...
  10. jgaulard

    More Google frustration

    Check your "Latest Activity" page under "What's New." That's generally where the /posts/ URLs come from. That page and also emails that are sent to members, but Google wouldn't know about them. If you scroll down the Latest Activity page and roll over each and every URL in each post, you'll see...
  11. jgaulard

    XF 2.0 Stop Google indexing member profiles

    Perfect. Just remove the robots.txt block.
  12. jgaulard

    XF 2.0 Stop Google indexing member profiles

    Hi - If your goal is to have all member profile pages removed from Google's index and to never see them returned in Google's search results in any way, then yes, you are correct. Remove the block from robots.txt. There is nothing more you need to do. You don't need to add noindex to any...
  13. jgaulard

    XF 2.0 Stop Google indexing member profiles

    Hi - I'm not sure what you mean. If you leave the pages unblocked, Google will crawl them to see that they should not be indexed. If you block them, Google won't be able to crawl them to see the 403 response code.
Back
Top Bottom