- ABP Framework version: v8.0.4
- UI Type: MVC
- Database System: EF Core (SQLServer)
- Tiered (for MVC) or Auth Server Separated (for Angular): no
Since upgrading to 8.0.4, when I create a solution either through CLI or Suite, in the front end web site, the "flyouts" for setting the theme (System, Light, Semi-Dark, Dark) and Container Width do not function (though the icon is displayed). The Language icon isn't displayed at all. If I log in, the Administrator menu shows an available drop-down but it doesn't work.
A solution I created with abp suite 8.0.3 just before I upgraded to 8.0.4 works fine.
I get the same results using the CLI or Suite. The cli command is as follows which will also give the specifics of the solution I'm trying to create: abp new test9 -t app-pro -u mvc -d ef --theme leptonx --dbms sqlserver --connection-string "Server=localhost;Database=abpTest9;Trusted_Connection=True;TrustServerCertificate=True" -csf
I also tried reverting to version 8.0.3 by using the following command: abp new test6 -t app-pro -u mvc -d ef --version 8.0.3 --theme leptonx --dbms sqlserver --connection-string "Server=localhost;Database=abpTest6;Trusted_Connection=True;TrustServerCertificate=True" -csf This doesn't work either.
After creating the solutions, I did at some point run "abp install-libs" but that didn't seem to have any effect.
What are my next steps to debug and fix this issue?
I appreciate any help you can provide.
6 Answer(s)
-
0
Hello,
I am checking your case, at my end for both 8.0.3 and 8.0.4 application is running fine. I just want confirmation on - When you are running 8.0.3 application that time your CLI and ABP suite both should be of version 8.0.3 and while running 8.0.4 application your CLI and ABP suite both should be of version 8.0.4. or Please check in incognito mode once and try to clean browser cache.
thanks
-
0
I created and ran the project with the command you gave and I did not encounter any errors. Are you getting an error in the console? If you get an error, please share.
-
0
Hello,
Please share steps to reporduce the issue.
Thank you.
-
0
Hello, I have run a new test (test10). The CLI version is 8.0.4. The resulting solution has the same issue that my previous tests had.
My "yarn" section looks different than yours and I'm suspecting there is something in there that is causing the issue. I'm posting the command line output from the test here.
There are three yarn warnings I've been ignoring. ➤ YN0007: │ es5-ext@npm:0.10.63 must be built because it never has been before or the last one failed ➤ YN0007: │ @fortawesome/fontawesome-free@npm:5.15.4 must be built because it never has been before or the last one failed ➤ YN0007: │ preact@npm:8.2.9 must be built because it never has been before or the last one failed Thanks for helping me with this. Blessings
-
0
Also, when comparing the new solution to the one that is working (from a few weeks ago using 8.0.3), I see in the test10.Web project under wwwroot\libs that the directory is empty. As a test, I copied all the contents from the working wwwroot\libs directory to my new solution and it appears to have resolved the issue.
So, why do the new builds not successfully create this folder? Did I miss something in the yarn warnings?
-
0
A coworker pointed out that I have yarn 4.1.0 while you are using yarn 1.22.21.
I changed my yarn version and now things are working as designed.
I'm marking this as closed.
Thanks for your help.
