ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Agile Records error after updating

September 30, 2012 7:07pm

Subscribe [1]
  • #1 / Sep 30, 2012 7:07pm

    Goughy

    4 posts

    I have just updated from 2.3.1 to 2.5.3 with my “Agile Records” test configuration.

    Now when I click “Register” or “Log In” or “Your Home” in the Hello box on any of the Agile Records pages, I get the following error message:

    “URI beginning with string /member/ forbidden.”

    Any suggestions?

  • #2 / Oct 01, 2012 5:19pm

    Dan Decker

    7338 posts

    Hi Goughy,

    Have you made any changes to the member profile trigger word? Do you have any add-ons installed that change membership behavior?

    There shouldn’t be anything changed in Agile Records between these versions.

    Cheers,

  • #3 / Oct 01, 2012 5:26pm

    Goughy

    4 posts

    Hi Dan,

    No changes that I can recall and no add ons. It’s a basic install and it’s been a while since I worked on it. I’ve tried the same update locally on my own system and it works fine.

    I’ll reinstall from scratch on the system that’s giving me the problem and take it from there.

    Thanks for your help.

  • #4 / Oct 03, 2012 12:38pm

    Dan Decker

    7338 posts

    Hi Goughy,

    My pleasure!

    I’ll leave this open in case you need to bounce back in.

    Cheers,

  • #5 / Oct 03, 2012 12:47pm

    Goughy

    4 posts

    Thanks - I got to the bottom of the problem.

    My hosting service had implemented a block on URI’s with /member/ strings.

    I had actually changed my Profile Triggering Word but I had not made the necessary changes to the templates to take account of the new word. It took me some time to find all the instances of /member/ and it probably would have been better if this had been a global variable somewhere that I could have changed just once!

    Anyway, it was a valuable learning experience and the problem is now resolved.

  • #6 / Oct 04, 2012 12:12pm

    Dan Decker

    7338 posts

    Goughy,

    Oh, excellent!

    I’m glad you were able to sort out the cause.

    Thanks for the feedback and information!

    If you need anything else, please let us know.

    Cheers,

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases