Project assets updater appears despite being disabled in settings

[Cheese]

Despite:

I am beginning to really hate keep seeing this!

I close it, I deploy, I see it again, I have customisations to files like server.js and middleware.js and made a Feature Request relating to allowing customisations of these files by the User:

Allow changes to Node middleware.js without prompting to overwrite the file if it is changed

Run in to an issue integrating i18 in to our Node Project. We need to make changes to middleware.js and this results in: [image] As I am totally useless as explaining this I've had my friend Opus explain it: Feature Request: Support for res.locals in templateView Middleware Summary When customising lib/core/middleware.js to add functionality (such as internationalization), Wappler flags the file as modified and prompts to replace it with the default version. This creates a maintenance burde…

I've now destroyed 132 monitors by slapping them upside the head every time I see this annoying dialogue! PLEASE can something be done about it?

This is enough to drive a man insane. It is like some repetitive annoying Cialis popup of a decade ago! No i don't want or need your damn blue pills!!

[Hyperbytes]

Maybe a linux thing, never see it on windows (except when you should)

[brad]

All good on a Mac as well. Just a thought @Cheese, you may have it turned off in the global settings but under the project tab it may be turned on? Not sure if there is a per project level setting for that. I am not at my computer but worth having a look.

[Cheese]

@Hyperbytes

Maybe a linux thing

[Cheese]

@brad

Not sure if there is a per project level setting for that

Maybe but I can't find it. I think it is due to the customisation of the files and the MD5/timestamp differing to that of the standard files. Thus I get the update dialogue.

[Cheese]

@Hyperbytes

never see it on windows

Have you made any changes to index.js, server.js, or middleware.js Brian?

[ben]

Actually, this is a valid point and the fix is simple: In middleware.js add res.locals in line 236 to read

res.render(template, Object.assign({}, res.locals, app.global.data, app.data, methods), async (err, html) => {

instead of

res.render(template, Object.assign({}, app.global.data, app.data, methods), async (err, html) => {

That fixes the problem

Sorry, I should have added that this change needs to be made by the Wappler Team, otherwise it will not stick.

[Cheese]

Will give that a go thank you Ben.

[ben]

Sorry Mr Cheese, us changing this will not stick

[Cheese]

@ben

Sorry, I should have added that this change needs to be made by the Wappler Team, otherwise it will not stick.

You're correct Ben. Needs Team attention, worth the try though, appreciated for the advice however.