Thanks now that the problem is clear we can go solve it.
It is quite a huge change that we made in design view so something like this was expected.
Thanks now that the problem is clear we can go solve it.
It is quite a huge change that we made in design view so something like this was expected.
Iâm sure you are all on top of this, but yes, i too have this issue. It is only affecting the content pages, not the layout pages, and only in Design view. I can still view in browser as per normal.
Windows 10,
NodeJS
Docker target
This is now solved in Wappler 3.3.1
Awesome @George!
But now I have the âalmostâ same issue but for the server actions
This time this issue is affecting all pages (Layout and Content pages)
weird it works all fine here. Also for the server actions.
How is your project setup, and on what target are you on? What is the Web Server URL for it in the target project settings?
I tried Local and Remoite target, same problem, restarted Wappler, re-saved the files⌠same issue.
So you local âdevelopmentâ target is also giving you 404?
and it has just a http://localhost
as Web Server URL defined?
Yes, exactly, I can show you in live if you want.
@George I tried this:
Replace this code:
<dmx-serverconnect id="s_list_annonces_public" url="api/Annonces/GetListAnnonces" dmx-param:limit="10" dmx-param:offset="query.offset"></dmx-serverconnect>
By this one:
<dmx-serverconnect id="s_list_annonces_public" url="file:///C:/Users/gegee/Desktop/Wappler-FR-NodeJS/app/api/Annonces/GetListAnnonces" dmx-param:limit="10" dmx-param:offset="query.offset"></dmx-serverconnect>
And I no longer have the error mentionned, but itâs a temporary âlocalâ fix and it doesnât work on my remote server indeed
Actually file protocol shouldnât work at all.
We solved the https problem so it should be all fine.
Are you on Windows? I can send you a beta of the upcoming update so you can verify it is solved.
We found the last problematic case when your site was in a sub folder and will be fixed in the next update
Same as remote targets using HTTPS
Hey George, thank you for your message.
My website wasnât in a subfolder, are you talking about the server actions maybeâŚ?
And my website had the same issue using HTTP.
I hope it will be all fine so I will be able to continue my project
Thanks!
Looking at your screenshots, your website is actually in a subfolder and not directly in the public_html folder:
public_html/application
Hey @Teodor, yes, you are right, I forgot it, itâs due to cPanel not allowing adding the NodeJS project in public_html directlyâŚ
Thanks for the clarification!
Fixed in Wappler 3.3.2