-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CityInfo page not saving images #146
Comments
I've never tried to upload images to a local server. I've only done it after deploying. I think this bug could be limited to just local environments. Please note if the problem persists after you deploy. Thanks for filing the bug! |
It happens on Heroku as well. It happened there first, which is why I installed locally to see why. Thanks! This message was handcrafted by a big thumb pressing letters on a tiny keyboard.
|
Can you share your heroku instance? I'd be really curious to reproduce this. Thanks! On Mon, Feb 9, 2015 at 9:43 PM, John Crowley notifications@github.com
|
Can somebody please try to reproduce this and then write steps to reproduce? |
Is there a recommended size/resolution for these images? I am unable to get anything to show up at all. |
@rkcheung I found the CMS to be buggy. I'm currently working on a derivative of this project that doesn't rely on the CMS. Depending on how technical you are, you might want to fork https://github.com/gnv-org/gnv instead. If you want to stick to using the CMS, image size (file size) is definitely a factor, but the whole implementation was complicated by the Cloudinary integration, cache time, and the idea of using it as a user-friendly uploader and also a CDN---it's hard to do both things well at all times. |
@arena Thanks - I will try yours. |
Set up City72 on Heroku and development box (MacOSX10.10). CityInfo saves text, but not images. The database query shows null values for img_url and resident_image_url despite having set files for upload (see image). Happens on Heroku and localhost. Note: I changed email and client url.
The text was updated successfully, but these errors were encountered: