search

mcrider / azimuth

Azimuth is a simple, elegant, and fast CMS built using meteor.js.
232 stars 54 forks source link

Asset uploading not persistent in app #80

Closed mwcrowley closed 10 years ago

mwcrowley commented 10 years ago

Using the new 0.8.0 build I have been trying out the new asset uploading system. The images do upload and are visible/usable on my barebones site until Meteor is restarted (the pointers are held in the MongoDB in the cfs.assets.filerecord database. On the file side they are stored in _tempstore in the CFS folder).

When the database is restarted the record of the image does not disappear (it still is displayed on the assets page) but the image itself is missing as well as in any page that it is embedded on. The pointer in the DB is still present and so is the file in the _tempstore folder however the src on the on the page is pointing to Assests folder which does not exist.

I've tried my my best to pin down the issue but haven't had any luck, seems like it's something to do with the asset handling set-up.

screen shot 2014-03-31 at 5 51 01 pm

mcrider commented 10 years ago

Not sure if you're using azimuth from git, but I had better results when setting an absolute path to the CFS uploads directory (in server_init.js). I'm still struggling with this behavior...

jindrichbartek commented 10 years ago

I have same problem, but I'm using meteor 0.7.2, azimuth 0.2.0, collectionFS 0.3.7. and cfs-public-folder 0.0.3. And for deployment meteor.com. After every (re)deployment I lost access to my uploaded files (Though I can see them in assets page, but just filenames, without actual data)

mcrider: Can you give example of how to set absolute path in server_init.js?

mcrider commented 10 years ago

Things should now be working better if you do a mrt update. @jindrichbartek I'm not sure how well CFS works on meteor.com's servers, I've read that there may be issues.