Error when saving API Query to production server with 3.9.8

[George]

Please restart Wappler with logging, reproduce the problem and attach the debug log. See:

How to report bugs together with the Wappler debug log

Updated for Wappler Version 1.1.0 and higher We have a built-in bug reporting in Wappler that auto post a topic in this forum together with the debug log. Starting from version 1.1.0 the logging isn’t available per default, so you need to restart Wappler with logging. You can do that by clicking on the Wappler’s tray icon (Windows right click) and then choose “Restart with Logging” Then reproduce your problem and choose to submit a bug report from the Wappler menu File / Submit error report ……

[George]

It seems like you are missing some global components.

Try restart or if the issue still persist, full reinstall from https://wappler.io/download/

[UKRiggers]

I always edit on the Dev (local) machine, then save to production.

report_2021-5-8_13-5-14.zip (318.6 KB)

[Teodor]

@UKRiggers

edit on the Dev (local) machine, then save to production

What do you mean by that? Can you explain this process a bit more detailed please?

[George]

Your report doesn’t include a debug log - have you restarted with logging first?

Otheriwse manually include the log files as stated in the article above

[UKRiggers]

I restarted using this

[UKRiggers]

I always work on my local desktop machine in front of me. When I am happy I change the Target to LIVE

and then with the single page open or API query highlighted, I then Ctrl-S or Save, which then saves to the Live Production Server.

[George]

Is it just on this target and just this action that you can’t save?

Or all server connect actions?

And what about regular pages?

Also could you locate the chrome_debug.log and add it here as well?

[Sorry_Duh]

Does the slide out action area function somewhat like the new tabs in Wappler 4 beta 6? if so the issue might be related to this I posted Wappler 4 Beta 6 Targets Getting Stuck

[UKRiggers]

It happens on all server connect actions.
And all regular pages.

Also, if I right-click the API to upload, nothing seems to happen…

chrome_debug Neil.zip (5.7 KB)

[Fred_K]

Reporting similar issue here:
chrome_debug.zip (4.0 KB) report_2021-5-8_15-55-20.zip (195.9 KB)

and this when saving on the AC side:

The saving does seem to work though.

[Teodor]

Just to confirm, it doesn’t work when an FTP target set as Development is selected?

[Fred_K]

Development yes. Target is remote / live.

[George]

Seems to FTP was broken due to some bad paths - we will issue a new update in a few minutes

[Pier]

Wappler Version : 3.9.8
Operating System : Mac OSX 20.4.0
Server Model: PHP
Database Type: MySQL
Hosting Type: Custom

I have a similar problem, after updating to wallpaper version 3.9.8.
When I try to upload any file to the remote server it gives me this error (see image).
There seems to be some problem when using the FTP server.

[George]

Fixed now in the just released Wappler 3.9.9

[UKRiggers]

Oooh! Wappler 3.9.9. We’re in danger of getting to Wappler 4.0 before 4.0 is released

[UKRiggers]

Working