I’m back using Pinegrow after a sabbatical of several years and today I’m on 8.0 Remembering that changing outside of PG wasn’t always a good idea, I’ve been actively trying to do everything inside. Now sometimes the change is on the CSS grid visual aid, sometimes in the PG code editor on html or css and sometimes in the style panel, but always in a PG tool. And yet, I’m still getting a warning saying it was changed and do I want to reload.
I’m working on a Wordpress theme, using the WP theme builder.
Also, it seems that just loading a file in the code editor set the “changed” flag - a little * shows up before anything is changed.
Am I doing something the wrong way or is there a problem with PG itself?
While it’s not a dropbox or onedrive folder, when I closed everything down for the nigh yesterday, I found Sublime Text was open so that may may explain part of my issue - even though I’m pretty sure I didn’t change anything there, there might have been some indication that Pinegrow interpreted as a change. Sublime Text does monitor for changes. I’ll watch out today and try to test this to see if I can recreate the issue.
Regarding the screenshot, I’m not sure what you mean by “the open files in your interface”. Do you mean the project tab and the code editor panes?
Yes, I believe that as soon as I open, say, index.html in the code editor, I see the asterisk. Often, I open the code editor just to view the text (I’m not just “old school”, I’m “ancient school” - I used to debug looking at punched cards!) and the asterisk (*) appears.
I’ve found one thing that demonstrably causes this, and that’s a backup. Ironically, my 9am scheduled backup ran this morning and just afterwards, the pop-up appeared and asked whether I wanted to reload. Unfortunately, I thought the safe answer was yes, and that lost me an hour’s work. I was able to recreate this by making a couple of changes and manually running the back-up, and doing nothing else. That brought up the “reload?” screen as soon as I focussed on a new element.
So the take-aways here are: the true meaning of the reload is “Do you want to replace all of the changes recorded in Pinegrow but not saved with the unknown contents of the file in the project file?” and that many things can make Pinegrow ask this question (like a backup, OneDrive (and its like), or an external editor).
Thanks for finally disecting this, David. I think the Pinegrow team should make this process clearer for everyone, especially newbies and beginners whom they seem to be targeting. Some clear documentation and common examples would go a long way. I don’t know how many times I’ve lost work and couldn’t quite understand what was going on, and this includes when syncing with VS Code.
