# Overwriting code written outsid eof pinegrow is a scarey proposition

**URL:** <https://forum.pinegrow.com/t/overwriting-code-written-outsid-eof-pinegrow-is-a-scarey-proposition/7953>\
**Category:** Feature Request\
**Created:** [April 23, 2023, 4:15pm UTC](https://forum.pinegrow.com/t/overwriting-code-written-outsid-eof-pinegrow-is-a-scarey-proposition/7953 "2023-04-23T16:15:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![smgitner](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/smgitner/32/4615_2.png) [@smgitner](https://forum.pinegrow.com/u/smgitner)\
**Post date:** [April 23, 2023, 4:15pm UTC](https://forum.pinegrow.com/t/overwriting-code-written-outsid-eof-pinegrow-is-a-scarey-proposition/7953/1 "2023-04-23T16:15:50Z")

</div>

@matjaz

I think this is super important and should be added. I think this wording is confusing when exporting

> _" Do you want to overwrite the following files in folder **/Users/XXXX/Local Sites/mywebsite/app/public/wp-content/themes/mytheme/**?_
> 
> _It looks like these files were modified since you last exported them._

I think it should say something like the following:

_" Do you want to overwrite the following files in folder **/Users/XXXX/Local Sites/mywebsite/app/public/wp-content/themes/mytheme/**?_

_It looks like these files were modified in a separate code editor since you last exported them. Realize that by clicking the box you will overwrite all of the files._

**I think you should also add an ignore function like in GitHub that will ignore the files you coded separately in VScode. I think the ability to do VScode and Pinegrow is vital.**

i just find something like this to be scary. If you think about a week earlier I did the changes in VScode i then come back to compile in PG and I am thinking what did I do?

Or even a revisions comparison like in WordPress?

**strong text**

---

<div class="post-metadata">

**Author:** ![matjaz](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/matjaz/32/5_2.png) [@matjaz](https://forum.pinegrow.com/u/matjaz)\
**Post date:** [April 24, 2023, 5:11am UTC](https://forum.pinegrow.com/t/overwriting-code-written-outsid-eof-pinegrow-is-a-scarey-proposition/7953/2 "2023-04-24T05:11:14Z")

</div>

Have made the notice more clear:

It looks like these files were modified since you last exported them. Did you use a code editor to edit the files in the exported folder? **Exporting the files will overwrite any such changes.**

Note, it is best to keep all project files in the source folder (including any custom files) and then export them to the target project. Never edit files directly in the export folder.

---

<div class="post-metadata">

**Author:** ![smgitner](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/smgitner/32/4615_2.png) [@smgitner](https://forum.pinegrow.com/u/smgitner)\
**Post date:** [August 8, 2023, 5:37pm UTC](https://forum.pinegrow.com/t/overwriting-code-written-outsid-eof-pinegrow-is-a-scarey-proposition/7953/3 "2023-08-08T17:37:58Z")

</div>

sorry to bring this back but - I am a code guy at heart; I’ve spent the past few days trying to do ACF code in Pinegrow and find it just not the same. It’s super easy to use a plugin like Theme Code Pro and paste it into VScode and then, move on to the next order of business. I find PG not to play nice with vs code if you use both. PG keeps asking me to save files after they’ve been edited outside of PG. I know I have asked for better language with this in the past - but as the list gets longer, I can’t remember what i did with every file. I was wondering if there was some way to have pg ignore files that I adjusted directly in the exported file and then for it to stop asking me what to do.

---

<div class="post-metadata">

**Author:** ![MichelyWeb](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/michelyweb/32/6652_2.png) [@MichelyWeb](https://forum.pinegrow.com/u/MichelyWeb)\
**Post date:** [August 10, 2023, 3:57pm UTC](https://forum.pinegrow.com/t/overwriting-code-written-outsid-eof-pinegrow-is-a-scarey-proposition/7953/4 "2023-08-10T15:57:06Z")

</div>

Think of the process as a one-way street. PG =\> local WP =\> deployment.  
PG is the single source of truth for the Theme or Plugin you create with it.

> [@smgitner](#):
>
> I’ve spent the past few days trying to do ACF code in Pinegrow

What exactly is the problem doing that?  
I use require\_once() in the custom.php file to import files where I put code for ACF Post types or Field Groups inside my PG project.

Looks like that:

 ![CleanShot 2023-08-10 at 17.57.46@2x](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/d/d26c9cf4826b23a1d550f014aac979c6279eba31.png)  
 ![CleanShot 2023-08-10 at 17.58.34@2x](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/b/bef2ba8022bc7570a7badc431cd874f4200d3ce0.png)

In the Template Code you can write PHP Code like you want.

Would you please describe what’s not working when working with ACF code in Pinegrow?
