Packages not showing in backoffice after deployment to srerver

Questions
,
1

Hi, we have several packages running on our localhost including Umbraco Forms and Skybrud.Umbraco.Redirects.

When we run:
dotnet publish --configuration Release

The dlls get generated and everything looks fine. When we deploy the publish directory to the server, none of the packages work. They show as installed, but they don’t show in the backoffice.

Any ideas?

2

It sounds like there might be an issue with how the packages are being deployed. Here are a few things to check:

  1. Ensure the packages are in the correct folder: Make sure the DLLs for Umbraco Forms and Skybrud.Umbraco.Redirects are in the bin folder on the server after deployment. Sometimes the deployment process might miss copying certain files over.

  2. Check for any errors: Look at the server logs to see if any errors are being thrown that could prevent the packages from loading correctly.

  3. Check your Umbraco version: Make sure the version of Umbraco on the server is compatible with the versions of the packages you’re using.

  4. Reinstall the packages: Sometimes the packages might not get fully initialized during deployment. You can try reinstalling them via the Umbraco backoffice.

  5. Verify the permissions: Ensure that the user running the app on the server has the appropriate permissions to load and access the required files.

Give those a shot, and let me know if anything looks off!

4

If you’re missing the package in the backoffice, it means at the very least that Umbraco didn’t find the umbraco-package.json file. That file is what determines what is present in the ‘packages’ section of Umbraco. So my guess is that the App_Plugin files are not copied over correctly.

7

My apologies if not related in the slightest, but I am still on version 13+ so far, and I’ve noticed that deploying via Visual Studio sometimes (seems like most of the time) doesn’t include all of the files in the App_Plugins folder. I also checked they are set to copy content.

8

If your app_plugin files aren’t ones automatically included.. eg static assets not in the wwwroot folder (css/js/html/ images…)

then I believe you need to add the copyToOutputDirectory

eg

<Content Include="App_Plugins\SM.BlockPreviews\BlockElement_embed.html">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    </Content>

If you do a dotnet publish --configuration Release then you should be able to see what is going to be included in bin\Release\net8.0

also you can specify an output directory…
dotnet publish --configuration Release --output ../../PublishedSite

and a environment name if needed to test correct appsettings.. (short param names too)

dotnet publish -c Release -o ../../PublishedSite -p:EnvironmentName=Live

you can even run that published site locally with (replace www with your project name)

dotnet www.dll --urls=https://localhost:44589/ --configuration Release --environment Live
or
.\www.exe urls=https://localhost:44589 --environment Live --configuraton Release

1 Like