How do I debug why Imageresizer isn't working? - imageresizer

I have installed Imageresizer in an existing EPiServer project, but when uring the queries on images I only get the original image.
I have tried this on an image that is present on the site:
http://localhost:15000/globalassets/image.jpg?width=100
But I just get image.jpg in full size.
I can access http://localhost:15000/resizer.debug and there is no errors besides:
1 Issues detected:
(Warning): To potentially see additional errors here, perform an image resize request.
I have checked everything here https://imageresizing.net/docs/v4/troubleshoot and my Web.config is as it should be.
I installed the plugin with the commands:
Install-Package ImageResizer.MVCWebConfig
Install-Package ImageResizer.Plugins.DiskCache
Install-Package ImageResizer.Plugins.PrettyGifs
according to this blog post: http://www.frederikvig.com/2013/01/add-powerful-image-resizing-cropping-and-manipulation-support-to-your-episerver-website/ and the official docs.
The plugin seems to be correctly installed as far as I can understand, it simply does not resize the images.
If I try to add .ashx I get a 404 page:
http://localhost:15000/globalassets/image.jpg.ashx?width=100
I don't know how I could investigate this further, any suggestions?

Not really sure why it did not work, but this plugin fixed it! I just installed it from NuGet and then it imageresizer worked as expected.
https://github.com/valdisiljuconoks/ImageResizer.Plugins.EPiServerBlobReader

Related

QGIS 3.22.5, 3.22.10, and 3.26.2 keep crashing when using GEOTIFFS

I'm uploading NAIP GEOTIFFS that I got from the USDA website. They are TIFFS with the coordinate system imbedded. They are loading correctly but the QGIS crashes when I try to get into the properties of the image layer. I would like to make some of them transparent. Originally this happened in version 3.22.5. Then I installed 3.22.10 and 3.26.2 and it still happens. Could it be related to my profile or plug-ins? Wonder if I should uninstall my plugins and then try. Uninstalling plug-ins would just be a pain.
Update-Took the plunge and unloaded all my plug-ins. This worked. I think I had some weird plug-ins that weren't working properly. So problem solved.

Adding AddRazorRuntimeCompilation() to the container in .NET CORE 6 will break the CSS footer

I create a brand new ASP.NET Core MVC project using VS 2022 and .NET Core 6.
VS will generate the base template and when I run it without touching any code, everything is fine.
So far so good.
Now I add the NuGet dependency Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation version 6.0.0.
In Program.cs file, I add a line
// Add services to the container.
builder.Services.AddControllersWithViews();
builder.Services.AddRazorPages().AddRazorRuntimeCompilation(); //Add this line of code
var app = builder.Build();
Rebuild the program and run it. Now I see the footer is not at the bottom of the page anymore.
Is it a bug or did I do something wrong here? Thanks.
I was struggling the same problem as well,
while trying the versions of Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation nuget package and found the solution with 5.0.13 version.
If you downgrade the package from 6.0.1 to 5.0.13, the problem goes away and footer will be on bottom again.
In Visual Studio 2022, there's an option for hot reload on file save. this fixed my issue without having the need to install Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation
What is happening is that when you enable runtime editing, the .NET Core built in bundle and minification is removed. If you look at shared/_layout.cshtml, there is a _layout.cshtml.css file. This is the runtime bundle/include you are missing. Since this is your core layout, move the contents from this file to your wwwroot/css/site.css file and the footer and other elements will render as before.
Is it your intention to actually use RazorPages? It looks like you just want to add runtime compilation to the standard MVC views.
If you intend to use controllers and views, just add:
builder.Services.AddControllersWithViews().AddRazorRuntimeCompilation();
But, I tried your code as well and in my environment, the footer is present in both cases, even if I downgrade Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation from version 6.0.1 to 6.0.0.
I think there's no need to add the runtime compilation since in the newest update/version hot-reload has been officially released.
PS. I am currently following an asp.net tutorial and I encountered this problem. Here's the link: https://youtu.be/hZ1DASYd9rk
I'm watching same video series as you do and i had the same error. I upgraded Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation to v6.0.11 and I don't get any error anymore I
Installing Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation version 5.0.17 Nugget Package cleared the error for me.
You may try to install any version from 5.0.0 - 5.0.17

Twitter-Bootstrap 3.3.7- Getting Started

I'm stumped. I cannot understand the getbootstrap.com Getting Started info. I'm running on Windows 7 Pro. I would like to use Pingendo - which I'm new to - to create my website.
I downloaded the distribution version bootstrap-3.3.7-dist.zip (pre-compiled) and unzipped it. Then I came to the MaxCDN code. Where do I put that code??
For the source code version, I see references to things I don't know about: Bower, npm, Composer, Grunt, Less, and SASS. All these appear to be Linux based tools - from the command lines shown. How does one accomplish the same thing under Windows without installing yet more tools? Do I even need to compile this code to use the greater features?
You can either add the downloaded bootstrap css and js files to your project and reference them or you can just use the cdn which is just the same files hosted on a server. You do now have to know about any of those to get started with Bootstrap. They are just additional ways to install it, and different preprocessors that you can leverage.

Installing dotnetnuke module install fails with 404

Im doing some dev work on a dnn module. I was able to build and install a package on my installation of DNN once. I made some changes and wanted to uninstall and reinstall it. Uninstalling went fine. Installing the module again failed by throwing a 404 on the install popup window as soon as i upload the new module zip. I dont see anything logged in the event viewer. Anyone know what can cause this?
Im running DNN 6.2.4
UPDATE: adding more info
the url its 404ing on is: "/Host/Extensions/tabid/36/ctl/Install/rtab/36/portalid/0/Default.aspx?popUp=true"
Im sure this is something unique to my module. I tried installing other modules and they worked fine.
Try hitting F12 in your browser to load the Developer console and see if you can find what the URL is that is 404'ng, that'll make tracking down the issue easier.
Update: Since it appears to be the old "max upload size" issue check out this video for how to fix that part
http://www.dotnetnuke.com/Resources/Video-Library/Viewer/Video/383/View/Details/How-to-increase-the-maximum-file-upload-size-in-DotNetNuke-6.aspx

Dojo version upgrade from 1.3 to 1.7.3

While changing the dojo version from 1.3 to 1.7.3, I simply replaced all my dojo 1.3 folder files with dojo 1.7.3. After rebuilding my web application, I am getting error hxrFailed at dojo.js, line no 15.
What is the wrong that I am facing here? Do I need to change any existing code. Is there any document to refer for all the required changes.
Please help me to get out from this issue.
Thanks,
Sridhar.ch
Lots changed and there are some lengthy tutorials to help you migrate. Check out the documentation tab on Dojo's website:
1.x to 2.0 migration guide:
http://dojotoolkit.org/reference-guide/1.8/releasenotes/migration-2.0.html
Updated buildsystem tutorial:
http://dojotoolkit.org/documentation/tutorials/1.8/build
In theory the current (1.8) build system is backward compatible until 2.0, but in practice I'm not sure it is 100% backward compatible because my 1.6 build profile didn't work with 1.7.x and up. I didn't try that hard to get it to work though.
I have gone through the same. the xhrFailed error occurred for me for multiple reasons. One of the reason was a missing a file in the define as below:
define(["something/was/missing/here"],function(){});.
Another cause for the same error occurred was when a folder in a path of a dependency was renamed but not updated in the application build profile. (This case only if your are doing custom builds).
See if that is the case!