Thread

In EE1, the template I’m working with was doing this:

The following:

{path="member/{member_id}")

...is replacing __HERE__ below:

<a href="http://__HERE__">...</a>

(the code formatting was breaking it on the second “)

I was having trouble searching for what the equivalent might be in EE2.

Thanks in advance for any tips!

Jeff

OK more information:

Using MSM and Member Management, combined with the templates in Design > Themes > Member Profile Templates—viewing a member profile from site1 works properly, but attempting the same from site2 does not.

Works
http://site1.com/index.php/member/2

404 not found
http://site2.com/index.php/member/2

I’m hoping someone can help me figure out if there is an option/setting I need to change, or whether this might be an different issue?

Thanks!

Jeff

Addition/explanation: The original post was written when I wasn’t aware that the profile links were functioning properly from site1, and it was only site2 that they were returning page not found messages.

Hi Jeff,

Thanks for your question!

Have you enabled membership and registration on site 2 in the Control Panel?

These setting are distinct to each site and Membership is disabled by default. You must explicitly allow membership functionality on additional sites.

Let me know if you have any other questions!

Cheers,

Hi Dan,

Sorry for the delay! Technical issues. :-(

The Member Preferences configuration option “Allow New Member Registrations?” is “Yes”, on both site 1 and 2.

If this is not the setting, I guess I could use some direction to the correct one!

Cheers,

Jeff

Hey Jeff,

I too, apologize for the delays!

The only thing else I have tested out is with or without index.php

Are you using .htaccess in any way?

What version of ExpressionEngine and MSM are you using?

Cheers,

Hi Dan,

It does appear that the sites are using .htaccess in some manner, I’ll have to take a look at that.

EE v2.4.0, MSM v2.1.2

I’ll update this when I have additional information!

Cheers,

Jeff

Hi Dan,

Well, after poking at it on and off for a while, I finally figured out what was up. Apparently the migration from 1.6.4 to 2.4 resulted in an invalid member template being used.

Sooo when I saved the member settings page again I started getting an actual member template page (though the template itself still needs updating since it isn’t compatible).

Thanks for your help figuring this out!

Cheers,

Jeff

EDIT: The other issue that came up was that the entire theme was in a “profile_theme.php” file, which I ended up having to convert to individual files instead.

Hey Jeff!

Thanks for the follow up and I’m glad you were able to sort it out!

If you need anything else, please let us know!

Cheers,