My {path:avatars} is still showing my default mamp localhost url (http://localhost:8888/ee/ ) after updating successfully all other system urls for site migration to a live online environment.

I have already changed the sitepaths in forum preferences.

Any ideas why this might be, or if anyone has done this, which settings might be overlooked?

Many thanks.

EE 1.63 forum 2.1 20080525

edit: apologies this was meant to be posted in technical support forum (wrong window open!)

Moderator’s note: Moved there.

OK this seems to be a problem with the avatar paths in membership preferences. apparently they are not updating when i enter the correct path.

As I try and update the server and url paths it goes to an error screen and: “The following path you submitted is not valid: [old path inserted here, NOT the new one]”

EE 1.6.3 Build:  20080421

I don’t know if this is a bug and should be moved to that subforum?

I got around the bug, (or my local server problem) by running once again ‘Utilities: Find and Replace’ to replace in ‘site preferences specifically’ the correct server path from localhost to live URL.

I came across the same problem after a migration; here’s a similar more detailed forum post:

http://expressionengine.com/forums/viewthread/60041/

Your solution seems like a hack though; perhaps this is a bug?  Editing membership paths should be possible ...

Hi Matt, Yes similar problem. Did you fix it, or use the same hack?

I used the same hack

...

Hm- I can’t replicate, but not totally sure I used the same steps.  Did run into an issue w/having to change permissions to save- wasn’t even using some of the stuff that required it- sigs or something.  But had to have a valid path/permission to save anything.  But once I did- all was well.

Can you lay it out in super detail so… hm.  This is going to be a bear to replicate.  I know- if I replace the paths to say- signature- via find/replace to something bad.  Then try to edit it back to the correct path- would that be a valid replication?

Robin - I’m having the same problem today after switching things over from dev directory to live directory.  The only pathnames I can’t seem to update from the Admin are the paths in “Membership Preferences.”  I’ve made sure the server directories are writeable (777).

No matter what order I try to update the paths, EE ships the errors message “The following path you submitted is not valid:”...

I used the Utilities: Find/Replace technique.  Worked fine, but… this seems to be a buggie.

carvingCode - 12 June 2008 02:02 PM

The only pathnames I can’t seem to update from the Admin are the paths in “Membership Preferences.”  I’ve made sure the server directories are writeable (777).

No matter what order I try to update the paths, EE ships the errors message “The following path you submitted is not valid:”...

I think you need to change all of them at the same time. EE submits all of them to the db, and if only one of them is invalid, that would trigger the error.

Ingmar Greil - 12 June 2008 02:33 PM

carvingCode - 12 June 2008 02:02 PM

The only pathnames I can’t seem to update from the Admin are the paths in “Membership Preferences.”  I’ve made sure the server directories are writeable (777).

No matter what order I try to update the paths, EE ships the errors message “The following path you submitted is not valid:”...

I think you need to change all of them at the same time. EE submits all of them to the db, and if only one of them is invalid, that would trigger the error.

I don’t have a setup to test this with anymore but if carvingCode or someone does, would be great to have someone verify this so we can call it resolved!

Ingmar Greil - 12 June 2008 02:33 PM

I think you need to change all of them at the same time. EE submits all of them to the db, and if only one of them is invalid, that would trigger the error.

There’s no way, from Admin, to change all at once.  There’s only access to one at a time.

OK, I must have been thinking about something else, then. Sorry for the confusion, I have had something like this happen to me.

carvingCode - 12 June 2008 08:12 PM

Ingmar Greil - 12 June 2008 02:33 PM

I think you need to change all of them at the same time. EE submits all of them to the db, and if only one of them is invalid, that would trigger the error.

There’s no way, from Admin, to change all at once.  There’s only access to one at a time.

Actually, it turns out the settings under Member Preferences > Avatar Preferences, Member Preferences > Member Photo Preferences, etc., can be modified all at once by changing each one and *not* clicking the update button, but instead clicking the next settings button on the left menu and updating the other paths first - and *then* clicking the update button.  Since the menu settings are revealed via Javascript, you can switch through the menu settings (specific to Member Preferences) and they will retain your changes within the session / on the page until you click update to save to db.

I haven’t been able to replicate my previous environment that was causing problems to test this, but I have verified that settings under other menu sections within Member Preferences are retained w/o clicking the update button, so if indeed Ingmar’s hypothesis that all paths must be changed at once then this would be the way to do it.

>>
Actually, it turns out the settings under Member Preferences > Avatar Preferences, Member Preferences > Member Photo Preferences, etc., can be modified all at once by changing each one and *not* clicking the update button, but instead clicking the next settings button on the left menu and updating the other paths first - and *then* clicking the update button.
<<

Ah, yes.  That’s right.  Will try to remember this if ever I need to make these types of changes in the future.

Thanks!

The important thing, I suppose, is: Did this work, then? I cannot really test it, because I keep the same structure on all servers.