Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Category selector is incompatible with .NET 8 #31

Open
Tim-Schmelter opened this issue Apr 5, 2024 · 3 comments
Open

Category selector is incompatible with .NET 8 #31

Tim-Schmelter opened this issue Apr 5, 2024 · 3 comments

Comments

@Tim-Schmelter
Copy link

Tim-Schmelter commented Apr 5, 2024

We upgraded our projects to .NET 8 but needed to go back to .NET 6 because the geta category selector is not compatible and we get errors in the console wherever we use it in the cms:

geta_errors

Edit: It seems that geta categoeries 1.1.1 even has issues with .NET 6, so we rolled back to 1.0.0. So maybe .NET 8 is not the problem but 1.1.1

@evest
Copy link

evest commented Apr 5, 2024

Strange, I have 1.1.1 running fine on .NET 8.
image

@Tim-Schmelter
Copy link
Author

I just noticed something: in my screenshot you can see that it seems that the 1.0.0 script was loaded even if we were using the 1.1.1 version(now we rolled back to 1.0.0). What we were doing wrong then?

@evest
Copy link

evest commented Apr 5, 2024

Yeah; I wondered as well, assumed the screenshot was from after rolling back.

It is also returned with the wrong content-type in your screenshot, which is even more strange.

Seem like a cache issue, what does the modules_protected\Geta.Optimizely.Categories\Geta.Optimizely.Categories.zip look like? Is it 1.1.1 inside after you have upgraded?

Is the new zipfile deployed, or does it pick the old one?

Does it work locally in a dev env.?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants