E
Edward
I've studied Portal, Report, whose whitepaper can tell the mechanism at the
first time, but Community is different.
I succeeded in localizing the page to chinese, but that experience didn't
make it clear to me, what's the mechanism of request handling?
browsers request for http://localhost/community/default.aspx , in fact it
doesn't return the true default.aspx content(because this file is designed
to one installtion error page, if installation failed, user got it)
I checked the file: web.config, there is something like:
<pagePaths>
<add key="basePage" value="/communityDefault.aspx" />
</pagePaths>
in my opinion, Community has some great feature over Portal and other kits,
however, drawbacks accompany of course.
I hope somebody will help me. thanks.
first time, but Community is different.
I succeeded in localizing the page to chinese, but that experience didn't
make it clear to me, what's the mechanism of request handling?
browsers request for http://localhost/community/default.aspx , in fact it
doesn't return the true default.aspx content(because this file is designed
to one installtion error page, if installation failed, user got it)
I checked the file: web.config, there is something like:
<pagePaths>
<add key="basePage" value="/communityDefault.aspx" />
</pagePaths>
in my opinion, Community has some great feature over Portal and other kits,
however, drawbacks accompany of course.
I hope somebody will help me. thanks.