Unanswered

Register function does not work after deployment from dev to test environment

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hi!

We deployed our portal from development to test environment with the XRM toolbox (portal record mover) the styling looks fine and all webfiles pages etc are embedded, yet if we click on "register" tab it throws following error (german)

Any suggestions how to fix this?

THANKS

Categories:

Power Apps portals

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Christian Leverenz 1,214 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Anonymous ,
we had also issues on that and they were related to a diffrent portal default,base,callitwhatever language. It was somehow no route to the selected locale on the registration page available (if i remember correctly, it happened already a while ago)
So, may be comparing the languagesettings on both environments might help.
Hope my memories aren't too wrong,
Christian

PS may be you toggle the dev-errors switch in the portal settings. Then you will get the "yellow screen of death" 🙂 with more informations what actually went wrong.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hey @chleverenz

Thanks for the reply!
Could you elaborate on where I should first check the language settings within the portal management?

Thanks!

Was this reply helpful? Yes No
Christian Leverenz 1,214 on at

Like
a
(0)

Report
Copy link

Link copied!

@Anonymous
you can see the languagesettings for the websites in the website itself:
so, just make sure, that your default languages match in both systems. The supported languages could be a problem as well, but at first the default language can be a problem.
A little bit background: portals generate for every webpage a localized page. So, one page is the root (and determines the route to the page) and the localized version have, well, the localizations. So if you support 3 languages and create a webpage, there should be 4 entries for webpages: one root and 3 localizations.
When the localization does not exist for a specific language, you receive a 404. I do not know what happens with the build-in pages like profile.aspx, when the path to the localization is missing. Never tried to create that situation 🙂
Hope it helps and points in the right direction,
Christian

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

@chleverenz!

Thanks! So the default portal language on our dev portal is english and on the test portal the default language is german..

Was this reply helpful? Yes No
Christian Leverenz 1,214 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Anonymous ,
and could you change the default language? (i never tried, would be curious to know whether it works) or did you add english as a language in the targetsystem (and did this help?) ?
Kind regards,
Christian

Was this reply helpful? Yes No