Images within partials do not render in editor

[mebeingken]

Wappler Version : 3.7.4
Operating System : mac
Server Model: node
Database Type:
Hosting Type: custom

Expected behavior

An image within a partial, should render properly in the editor and in the browser

Actual behavior

Images only render properly in the browser

How to reproduce

In the editor, an error is received that the image is not found, however in the browser the image renders properly.

[MH2ag]

I think it is necessary to set your links relative to site root. Try /assets/img/…

Building SPA pages with NodeJS

A single page application (SPA) is a web site/app that re-renders its content in response to navigation actions like clicking a link, without reloading the whole page. It consists of main template and different views, which are rendered in the main template. SPA for NodeJS It’s possible to build SPA pages and enable partial refresh thanks to NodeJS templating system. In our example we will show you a simple SPA page, containing of a main layout with navbar and two views, which will be loaded …

First screenshot.

[mebeingken]

Ya, that takes care of it.

I omitted a piece of this – the partial was created by the editor from a layout page.

In the layout page, the image selection sets:

assets/img/apple-icon.png (works both in the browser when attached to a content page, and in the editor)

And if you select the same image in a partial it sets:

../assets/img/apple-icon.png (works both in the browser and in the editor)

HOWEVER if you convert a section of content in a layout that includes an image, the original path (assets/img/apple-icon.png) works only in the browser and not the editor.

In other words, the partial should properly set the path, if it is in fact supposed to be different than when used in the layout.

[Teodor]

Ken, what’s the paths relative to option set to in your site settings?

[mebeingken]

The default, Document

[Teodor]

Well,
as the tutorial says:

@Teodor

Disclaimer: Before we begin, make sure your site links are set to Site Root Relative in the project settings in order to prevent issues when working in subfolders:

so, please set this to site root …

[mebeingken]

As always, the point is missed here. Since communication takes two, I’ll take half the blame.

I’m reporting a bug, not asking for a work-around or a solution. I do so in hopes of making the product better…period.

If Site Root is required when using partials, then I consider it a bug that Wappler does not prompt the user to change if not already set. If you feel the novice user will know to search the forum for a post about SPA, in order to learn that the editor allows for invalid settings, that’s up to you guys.

[George]

Actually having relative links in partials doesn’t make much sense, as partials can be included all over the place in different pages in different sub folders. So where is the relative link to then?

Maybe we should enforce site root relative links in partials always?

[Teodor]

This has been fixed in Wappler 3.7.7