Well, if you click the Publish button this folder will be uploaded. In no other circumstances a random folder is auto uploaded.
Never clicked that button Teodor!! Have been around bit… Quite aware of what files are on my server and what should not be there.
We do not auto upload random folders Dave. Our scripts auto upload our own frameworks.
You either clicked upload or publish button - no other ways for this to happen.
I can assure you it is not me manually uploading these files (I am responsible for server uploads). No other program has automatic ftp access aside from Wappler. We use another ftp client outside of Wappler most of the time and we do not upload folders like the Pinegrow example so something is happening that maybe is not known about? Am not having a pop just letting you know Wappler IS uploading these items.
I’m going to blame Quantum Pollution. 
Dave, i already explained you what and when we check, update and upload and what are the two possible reasons for such a folder to be uploaded on your server.
Turning this topic into a chat room isn’t really helpful.
In what context? It’s a serious issue that we are being told we are imagining to some regard. Not the case Teodor. I tried to make light of a serious situation that is not being acknowledged. In what way is this turning it in to a chat room? What is a forum? Come on Teodor don’t get mad at me it’s really unfair mate. This is not a wind-up it is incredibly serious.
The only issue, if it can be called like that is that when a new version of app connect OR bootsrap 4 is added to Wappler, as soon as you save your page - we check the files timestamps and auto upload them to the server. These are the only files which will ever get auto uploaded.
In no circumstance, different than clicking publish or upload buttons Wappler will or is able to auto upload a random folder to your server.
This:
I really don’t have anything else to say on this topic.
A simple we will investigate would be nice. Being told this is not happening or it’s our fault is not helpful when we can see it is happening and we are not at fault.
And that is closure for me on this matter. We have raised it, it has been heard. Good enough for me.
1 Like
I think uploading anything automatically - without your knowledge or intention - can be problematic (and potentially disastrous in the case of Bootstrap for example). All that is being suggested/requested is giving more information and control about such automatic actions; it’s then for the developer to decide what to do about it (eg to update files, not to upload certain files or perhap be aware of things which might need checking).
1 Like
This whole workflow will change.
As George explained in a similar topic a while back:
I agree that sometimes you don’t want to have Wappler update your files to the latest version. We only update files to the latest version with minor updates, when Bootstrap 5 would come out we would add it as a new Framework and not automatic update your current Bootstrap 4. Minor updates should always be backward compatible, if not then we normally won’t auto update it.
As George already mentions, we want to change the way publishing works in Wappler. We try do this is small steps. At this moment the upload depends on the target you selected, it tries to keep the current selected target in sync with your development. So if you don’t want to have it upload to your server you could set the target to local, as that is where you are working then switch to the remote server only when you want to upload/sync to it.
1 Like
There is going to be, necessarily, a FIRST TIME for Wappler to initiate an FTP to the target folder of the online hosting server.
THAT is definitely when I have experienced Wappler uplooading EVERYTHING to the online server.
Every single folder & file — every Font file, CSS, every file that is loaded into the project folder after choosing one bootstrap style framework. All of the other bootstrap styles are also loaded. On first defining the remote target & checking the connection for the first time then I wanted to pick out just the pages that pertained to the application I wanted online.
Wappler sent everything Online.
I now try to pull out just the needed pages and supporting files into a whole separate project to try to prevent this - Experimenting with this.
A file & folder protection/exclude synch or upload management is needed.
Wappler does NOT upload EVERYTHING when you first create the FTP connection. It is NOT possible this to happen, unless you choose to sync or hit the Upload button!
There is no need to experiment - different project/app files MUST be in different projects in Wappler!
I find it very difficult to Export into a new Project folder using Wappler
I used good old Finder on Mac to do this over a number of steps.
Is there a tutorial on creating a new Project folder for the import of Just the Required pages to be uploaded?
I don’t understand what do you mean by "Export into a new Project folder " nor i understand what “Just the Required pages” are.
There is a project manager, where you can setup a new project, already explained in the docs:
I fail miserably every time I think I’m being clear here.
This follows in line with my previous comments inside this thread.
- I have pages & action steps, experimental pages, etc in Project 1
- Eventually I have assembled the working pages & components
- I have settled on the Frameworks & a specific Bootstrap theme.
- NOW I want to load up those pages that comprise the entire ONLINE Website or “App”
- According to “best practices” just mentioned in this theme I should have a CLEAN Project to use when I set my Online FTP target.
- I just want to carry over the pages (with associated connection, server actions files, bootstrap framework, etc) into a brand newly created Project Folder.
- As far as I see Wappler doesn’t provide for an Export to new Project managment tool — Open Existing Project is definitely not helpful.
- So, I have to pick and choose from Mac Finder & then tinker with the .wappler file.
My starting project1 folder has “junk files” as I tried different things.
Extraneous Actions folders & server action files.
But, I want to keep them to experiment with again later.
Now I just want the GOOD-Working pages in a new project folder so that the FTP upload is exactly what I need with no “junk”
I am not referring to OPEN NEW PROJECT option. Please check my link as it explains how to setup a new project, where you can add your files by copy-pasting.
I really get lost in your workflow … what is the logic behind:
What’s the point of doing this? Why not work directly on building pages? I really get lost in your explanations - if you just have some test files, which you don’t need - why not just delete them?
Are you sure you do understand what a Wappler project is, how the files are related and how/where you upload using the Upload button?
1 Like
Hey, I get lost, too!
I am LEARNING as I go.
Everyday I am having to run through tutorials & sometimes conflicting methods.
People say Wappler accomodates many different individual “FLOWS”
One popularly used Work Flow is called “Trial & ERROR”
I chose to try Wappler even though I have another tool that I have used for years that can create in 3 hours what it takes me Days to do with Wappler – NO JOKE-- Seriously.
But DMXZone has been years & years in development.
I bought maybe 40 DMXZone Pro extensions for Dreamweaver.
So, Wappler is not intuitive – it just is not.
Some important details are left unspoken of in the cracks.
It is a Brilliant, Magnificent Application - which is why I keep plugging away.
I spent the past 2 days documenting what Wappler does behind the scenes when I apply step-by-step developments to pages –
checking out the project folder changes – opening up and reading the files generated after this action step and that actions step
I have screen shot files, Wappler actions, code, open Xcode files, etc.
What you’ve built, Teodor, is proprietary to you & your logic.
I’m trying to explore Wappler so that I can easily crank out new pages & know what files I should be examining if something fails.
So, Teodor, thank you for your time & patience!
Today I continue in a fewer trials & errors mode . . .
