All Low add-ons are now owned by EEHarbor. Read the blog post.

Support archive

Files are not synched back to EE

patte 18 Jan 2012 15:42 problem, complete

Hi,

saving as files is working fine. All my variables are now within the default_site folder on the servers file system. The file path has been set within my assets folder (/home/www/p12345/html/expressionengine/assets/variables/) and the folder has write permissions.

But changing any of these files with my text editor wont change anything within the database. The files are not been synched back to the database.

Any idea?

Thanks much for support!

patte

Replies

  1. Low 18 Jan 2012 17:12

    Hi Patte,

    If you edit the variable in the CP instead of the file, is the file updated?

    In order to debug this properly, I'll need SuperAdmin login credentials as well as FTP access. Could you provide me with that info? You can send it to hi at gotolow dot com.

  2. Low 20 Jan 2012 10:01

    To follow up, the issue was solved by setting the correct permissions to "the top expression engine folder".

  3. RichardMeredith 15 May 2012 11:09

    Hi Low, got the same here, just wanted to know what permissions should be set to the expression engine folder.

  4. Low 15 May 2012 11:18

    Hey Richard, take a look at the docs about the file path settings. Make sure to set the permissions of the folder to 755 at least. If that doesn't do it, set it to 777.

  5. RichardMeredith 15 May 2012 11:27

    Lovely thanks, thats done the trick.

  6. RichardMeredith 15 May 2012 11:29

    Does Low Variables only work with files already created.

    Say I create a file locally and upload to the correct folder, would it sync to low variables? (I'm thinking it won't)

  7. Low 15 May 2012 11:30

    No, I'm afraid LV won't create new variables based on files. You'll need to create them in the CP.

  8. RichardMeredith 15 May 2012 11:32

    No worries, wasn't sure.

    Thanks Low

  9. Nutmeg 4 Oct 2012 09:27

    So, to be clear whatever you do on your local box needs to be done again on the live (staging) server?

  10. Low 4 Oct 2012 09:31

    If you create new save-as-file vars on your local box, uploading the files only will not create the vars on the live/staging server, no. They have to exist there too, in order to sync.

  11. Nutmeg 4 Oct 2012 09:38

    Thanks Low, meanwhile I read this thread which has a workaround duplicating the entries.

    Current workflow = local box>svn>deploy>live server

  12. Low 4 Oct 2012 09:47

    Yeah, that workaround will work.

    To clarify, LV won't create new vars based on files because of it's main feature: variable types. All vars -- their values -- can be saved as files, but a variable's properties (label, notes, group, early parsing, type, per-type settings, etc) cannot be saved in the file itself. Just the name (which is the file name) and the value. You can't create a new var based on that info alone...

    wazungu 14 Dec 2012 20:21

    Low, consider the value of saving-as-files: to allow easier editing, and better management with version control and deployment.

    As much as I love Low Variables, having to create and manage them with a CP on *each instance* of a site (local/live) is, well, a real pain.

    Consider moving toward putting all the data in the files - why couldn't these properties be saved in a prefs-like format? I'm thinking about the way a Wordpress child theme works - all the metadata is in a header, in like a comments block. Metadata + code. It's been done before.

    As it stands, LV is half-in, half-out of the utility of a file-based workflow. Any reason (apart from your hard work! =) that it wouldn't work? Devs everywhere would love it, right?

    Low 17 Dec 2012 09:59

    I did consider this. I also considered the amount of support that would derive from allowing vars to be created from files and it being only a partial solution.

    For instance, I could create a new default (textarea) var for each new file. The var would be created with all the default values. But you can just wait for all the people asking to create a Matrix var or something. Which in that case would even require an action *outside* of LV, which isn't available now. My take: either do something so it works right, or don't do it at all. Half-baked solutions are a no-no in my book.

    Metadata in a file doesn't seem right to me. It will be confusing for most people and very error prone.

    The local/staging/live workflow is indeed a tricky issue, but not mine to solve with LV.