@gizem.kurt will test and try to reproduce it. if there's a bug, we'll definitely refund it.
thank you we got your dbcontext file and respond you asap.
an update => https://support.abp.io/QA/Questions/3302#answer-ff39ae34-8f50-a8ca-9293-3a04da7a2cc0
We are stuck because of this one here https://support.abp.io/QA/Questions/3301/qgApoZ2OmDdJqiAoXp5L4ObZ82mStp54vqoB0A-is-not-a-valid-page-error . We got contractors to work with us for one week so there are like 3 man-weeks worth of changes that we can’t ship so super important to get this fixed (almost 1.5 weeks since discovered!!)
this problem has been addressed and we have fixed it. it's related to aspnet core razor pages base class change. we're testing the result to be sure it's working in 5.3.2. Therefore you'll get this fix with 5.3.2. And the planned date for 5.3.2 is July 5th, Tuesday 2022.
If you already switched to the latest ABP version 5.3.1 and see an issue, please report it under this topic. let's report only 5.3.1 problems not the old versions
Hello Albert,
So I went digging for my whole day yesterday into ABP and ABP commercial source code and I have found the issue :
The script that is responsible for setting the cookie is missing something :
function setLanguageToCookie(injector) { return () => { const sessionState = injector.get(SessionStateService); const document = injector.get(DOCUMENT); const cookieLanguageKey = injector.get(COOKIE_LANGUAGE_KEY); sessionState.getLanguage$().subscribe(language => { const cookieValue = encodeURIComponent(
c=${language}|uic=${language}); document.cookie =${cookieLanguageKey}=${cookieValue}; }); };If the path of the cookie is not specified then it is assigned to the path of the current page, which causes the problem in my case ; thus the fix (tested) is to change the line :
document.cookie =
${cookieLanguageKey}=${cookieValue};to
document.cookie =
${cookieLanguageKey}=${cookieValue};path=/;I did change manually the generated script (main.js) on the server to test but I do not know where I should do this change for a clean fix.
Could you tell me in which file I should do the change before compiling ?
Thanks
Thomas
is this from the Angular project?
you can temporarily disable it for a while. this will filter down the probable problems
thanks for your feedback. the generated code looks complex for the standard inputs. but this format is designed to support navigation properties (1-n, n-n). that's why it looks ugly. I created an internal issue (10906) to make an enhancement on this code.
@maliming will be your point of contact for this issue
then I'm closing the issue. you can always reopen
