Roxy Fileman fails to add correct url while adding images for example to the welcome page. I am able to upload the image but when i click on preview it fails to fine it on the server due to the wrong url. Its using /images/uploaded/iusa_75x75.73366068_6pn0.jpeg which ties into my shopping cart as myshop.com/images/uploaded/iusa_75x75.73366068_6pn0.jpeg when in fact my shop is at myshop.com/shop4 , if i manually add the correct url to the source code of the welcome page as in myshop.com/shop4/images/uploaded/iusa_75x75.73366068_6pn0.jpeg BINGO , that works. I would hate to have to always go back into source code and have to add this. Where is this controlled so i can change it or does this have to be changed by your team. Thank you
Actually i am not adding the domain just adding /shop4 (<p><img src="shop4/images/uploaded/iusa_75x75.73366068_6pn0.jpeg" alt="" /></p>)
Roxy Fileman fails to add correct url while adding images for example to the welcome page. I am able to upload the image but when i click on preview it fails to fine it on the server due to the wrong url. Its using /images/uploaded/iusa_75x75.73366068_6pn0.jpeg which ties into my shopping cart as myshop.com/images/uploaded/iusa_75x75.73366068_6pn0.jpeg when in fact my shop is at myshop.com/shop4 , if i manually add the correct url to the source code of the welcome page as in myshop.com/shop4/images/uploaded/iusa_75x75.73366068_6pn0.jpeg BINGO , that works. I would hate to have to always go back into source code and have to add this. Where is this controlled so i can change it or does this have to be changed by your team. Thank you
Actually i am not adding the domain just adding /shop4 (<p><img src="shop4/images/uploaded/iusa_75x75.73366068_6pn0.jpeg" alt="" /></p>)
Also on v4.30 it works find and i dont have to add nothing in source code.
We've released a new version - 4.40.2. This is a minor release that is fully compatible with the previous versions (4.40.0 and 4.40.1). So all third-party plugins for 4.40 work for all minor versions (4.40.0-4.40.2).
The full list of changes in the new version is available in release notes.
Not sure if this is something with Nop 4.40 or .NET Core 5 in general, but now when we publish our project it is almost 2GB (up from ~0.5GB), and is now too large to be uploaded to AWS Elastic Beanstalk. I'm not overly familiar with runtimes but it appears somehow related to SkiaSharp (and/or SkiaSharp.NativeAssets.Linux.NoDependencies) in the Nop.Services project causing many additional results to be published in the Presentation/Plugins/<plugin>/runtime folder. Previously in 4.30 those runtime folders only had 3 or 4 "win" folders; they now have those win folders, as well as osx and several linux builds, and comparing the two directories with Winmerge shows a HUGE size difference between 4.30 and 4.40 runtime directories.
Can anyone advice on how to resolve this? I'm not sure if it's a "bug" with 4.40, or something we can configure to prevent from happening. For what it's worth we use the AWS Toolkit in Visual Studio to publish to EB.
Edit: 1. The max size allowed by EB is just over 0.5GB from what I understand, so we were close to, but under, the limit previously. Now with 4.40 we are quadruple what's allowed. 2. The issue is not limited to only our plugins; the Nop plugins that come with the default solution also have the new additional runtimes output. 3. This is appears to be only one issue where a lot of excess files are being output causing the resulting project to be too large to upload; however there are other differences in other directories (I'm still looking into) causing the project output to be too large. Has anyone else run into issues with 4.40 and deploying to AWS EB?
I tried that and I still see all of the excess runtimes output, even though I set Target Runtime to win-x64. The runtimes folder contains the following:
I deleted the SkiaSharp.NativeAssets.Linux.NoDependencies from the Nop.Services dependencies list and the project rebuilt fine, and now publishes much smaller - but still takes up 1.2GB, still too big for AWS EB. Is nobody else having this issue? Each plugin folder in Presentation/Nop.Web/Plugins is taking up WAY more space than it did previously.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
