Site publish may not be accurate?

To ensure you get the best experience, this website uses cookies.

Learn More

Site publish may not be accurate?

viewed
465

posted

Anne

Title

Body

I am sorry to bother you again. Regarding the disappearance of the Admin link in the navbar and the impossibility of logging off, I am thinking I will try removing all files from the server, and then republishing the backup I used last time. It does not seem that any files were removed, but only some new ones added. Though the update to .net8.0 has been accomplished, since the dlls are the same name as the .net6.0 dlls, I wonder if they ever transferred over, or if they were skipped. (see screenshot) The popup about buying the newsletter solution is still in view randomly, too, though I did buy the plugin. (I just saw it). Though I had put the 8.0 license files in my licensefiles directory, they did not publish over. I had to delete the 6.0 files from the licensefiles directory that is on the server, and then the 8.0 files were successfully published. Also, for example, I did not retain a scripts folder and a vendor folder with a script in my recent version, yet it was not removed from the server and has caused many log errors. Also, I cannnot reach the comments settings. So, would you agree I need to remove the entire directory that is on the server, and republish my current solution in VS 2022? I am going to copy and paste an error message from the log that I see in the control panel. Also, I will attach a screenshot of the server files of dlls that have older dates that I would expect. Please let me know your advice. Thank you.

==
An unhandled exception has occurred while executing the request.
System.InvalidOperationException: Unable to resolve service for type 'cloudscribe.TalkAbout.Web.Services.CommentService' while attempting to activate 'cloudscribe.TalkAbout.Web.Controllers.TalkController'.
at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.ThrowHelperUnableToResolveService(Type type, Type requiredBy)
at lambda_method947(Closure, IServiceProvider, Object[])
at Microsoft.AspNetCore.Mvc.Controllers.ControllerFactoryProvider.<>c__DisplayClass6_0.<CreateControllerFactory>g__CreateController|0(ControllerContext controllerContext)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
at cloudscribe.Core.Web.Middleware.EnforceSiteRulesMiddleware.Invoke(HttpContext context, SiteContext currentSite, IOptions`1 multiTenantOptionsAccessor, IUserContextResolver userResolver, IAccountService accountService)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.StatusCodePagesMiddleware.Invoke(HttpContext context)
at cloudscribe.Multitenancy.Internal.TenantPipelineMiddleware`1.Invoke(HttpContext context)
at cloudscribe.Multitenancy.Internal.TenantResolutionMiddleware`1.Invoke(HttpContext context, ITenantResolver`1 tenantResolver)
at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddlewareImpl.<Invoke>g__Awaited|10_0(ExceptionHandlerMiddlewareImpl middleware, HttpContext context, Task task)

Preview

add a comment

Site publish may not be accurate?

Answers

Tags