Thread

I updated an ExpressionEngine 2.6.1 site to 2.7.0, as well as from 2.1.3 to 2.7.0. The updates went without errors and everything works well. But when I try syncing files from my file upload directory to my database it refuses to sync all the files in there.

From the 169 files in the upload directory only about 90 - 140 get synced after numerous processes. Even with 12 files in my upload directory only 9 got synced.

On one site I had MSM 2.1.6 installed so I figured it had something to do with that, but also without MSM it does not work properly.

I get no errors whatsoever, and since syncing your upload directories is almost mandatory after an update I’m very curious what makes this occur. At this point I’m refusing to update any sites to EE 2.7.0 until this gets cleared up.

Maybe it’s something on my side because I haven’t seen anything posted about this since the 2.7.0 release.

So I hope someone can clear this up for me.

I’m also experiencing this issue with a 2.7.0 site; I have 122 image files in a directory (each between 750kb to 1mb) - when I run a file sync it completes suspiciously quickly, and only handles about 30 of the 122 images (and a seemingly arbitrary selection at that - it doesn’t seem to be governed by filesize or filename). I thought it might be a memory issue, but it doesn’t seem to be as some of the images that get handled are amongst the largest. All have 666 permissions. When I run it again, the same thing happens, and the final report says 122 images handled, 0 errors.

Same issue also (my related thread here including some of the things I’ve tried http://ellislab.com/forums/viewthread/237812/)

Bh

Same issue here. Upgraded to 2.7 (from 1.72!) today.

Yep - same issue for me too on a local copy of my site - http://ellislab.com/forums/viewthread/237807/

I’ve just upgraded from 2.1.3 to 2.7.0.

No suggestions I’m afraid. If no fix is available, all you can really do is manually re-upload all the files it hasn’t synchronised through the file manager again.

I just tried to submit a bug report to get this fixed, but I think if I don’t pay $49 a month I can’t inform EllisLab of a bug in the software? So I’m not sure where this leaves us.

Luckily they’re active on the forums also, so if this post gets enough attention I’m sure they’ll look into it. If not somebody else with a support plan posts this as a bug.

We’re having this issue too, but on a larger scale, we have 4000 images in our image bank and only 1300 are synching, it really isn’t an option to manually add them, any idea when this bug will be fixed?

I’m also having this issue, manual upload of all the files is a no go due the volume involved, any one got close the figuring this one out. Syncing multiple times does not work for me.

I even tried rolling back all the related files still no luck guessing the change is hidden in what would appear to be an un-related file.

I just tried to submit a bug report to get this fixed, but I think if I don’t pay $49 a month I can’t inform EllisLab of a bug in the software? So I’m not sure where this leaves us.

That’s not the case. If you are logged in, just click the “Help / Bugs” link in the top right. Then click “bug tracker” in the right menu and then click the bright green “new bug” button.

You don’t need a support subscription to report bugs.

Bug reported here: https://support.ellislab.com/bugs/detail/19710

I just tried to submit a bug report to get this fixed, but I think if I don’t pay $49 a month I can’t inform EllisLab of a bug in the software? So I’m not sure where this leaves us.

That’s not the case. If you are logged in, just click the “Help / Bugs” link in the top right. Then click “bug tracker” in the right menu and then click the bright green “new bug” button.

You don’t need a support subscription to report bugs.

Thanks Jeremy - I’d missed the green button as well. Must get my eyesite sorted. 😊

Bug reported here: https://support.ellislab.com/bugs/detail/19710

Just to let people know if they’re not aware, a fix for the file synchronisation issue has already been posted to the bug tracking issue for it linked above. I’ve just tested it on a local test site I have set up and it’s worked for me. Hopefully it’ll sort everyone else out who has had the same problem as well.