(byebug) Refinery::Dragonfly.config.s3_datastore true (byebug) Refinery::Images.config.s3_datastore true (byebug) Refinery::Resources.config.s3_datastore true
Refinery::Dragonfly.s3_bucket_nameetc. The whole shebang.
All config values checkout.
(byebug) Refinery::Dragonfly.s3_datastore true (byebug) Refinery::Dragonfly.s3_bucket_name "helpcentre-dev" (byebug) Refinery::Dragonfly.s3_access_key_id "AKIAXXXXXXXXXXXXXXXXXXXXX" (byebug) Refinery::Dragonfly.s3_secret_access_key "19tuH6IXXXXXXXXXXXXXXXXXXXXXXXXXXGrq9dqP" (byebug) Refinery::Dragonfly.s3_region "eu-west-1"
# Refinery CMS # View the repo at this point: https://github.com/refinery/refinerycms/tree/81ed9917c0ed528bdcb0d91bbecf408d3c89706a gem "refinerycms", git: "https://github.com/refinery/refinerycms", ref: "81ed991" # Optionally, specify additional Refinery CMS Extensions here: gem 'refinerycms-acts-as-indexed', '~> 3.0' gem 'refinerycms-wymeditor', '~> 2.2' gem 'refinerycms-authentication-devise', git: "https://github.com/refinery/refinerycms-authentication-devise.git", ref: "4fbe542" gem 'refinerycms-videos', path: 'vendor/extensions'
HA! So, production links images as
/system/images/W1siZiIsIjIwM... where as the new local is using
So somewhere it is injecting the
refinery in the path locally, I guess I need to find a spot to override it?
W1siZis a base-64 encoded string telling dragonfly which image to get, and what processing (if any) to do on it. For instance I just decoded a string (using base64decode.org) from
[["f","2019/11/11/18/46/24/9941b2ff-e356-4d0a-8a6e-cf26bdb75d36/Plain.png"],["p","thumb","50%"]]. (I don't think using a geometry string of 50% is working. :frowning: )
@jbrodie My image paths in the page source (= src parameters in image tags) are
/system/refinery/images in both development and production. Images (from S3) are visible in both environments.
Just one wild thought: if you want to use S3 in development and production, do you also have the dragonfly-s3_data_store gem loaded for both environments?
@jussihirvi Yes, I have the gem exposed for all environments.
@anitagraham I am working on an instance I inherited from an older Rails 5.1 version, I am using the production DB restored locally with the buckets for S3 copied to a new dev version of the bucket. I was unaware of the encoding aspect of that so that is a little more insight. Thanks.
The only difference I can see is the pathing on them at this point. The new install, updated to Rails 5.2 is injecting an additional folder layer of refinery between the system and the images folder. I can only assume this would be some configuration somewhere that I can't seem to see.
config.dragonfly_url_format = "/system/images/:job/:basename.:ext"
@jussihirvi Thanks for all the time you have spent assisting me with this port. It seems that the previous developers did some strange things to make this work including using some videos plugin, which complicates things much more.
The amount man bastardization I was having to do to upgrade this to Rails 5.2 just isn't worth it. There are problems after problems for very little gain. We are going to leave it for now and do a fresh spin up on the current version of Refinery (which natively supports video now) and port in all our data to a new instance in the future. Atleast we have an answer now on this.
Thanks again to you and everyone that commented and helped out. I learned somethings on Refinery, and something about the crappy job the initial implementors did on our end.
Hello everyone! I, as some others, am having problems with images in Heroku.
I've been trying a few things but nothing seems to work. Does anyone knows how to fix the problem?
2020-02-14T03:56:29.526941+00:00 app[web.1]: I, [2020-02-14T03:56:29.526814 #4] INFO -- : [6b9b7602-3396-4ff2-83e5-972de0e45e2e] Started GET "/system/refinery/images/W1siZiIsIjIwMjAvMDIvMTQvNXkzNnhkOWsweV81OTk1NjI4OF82MTEyNTM4NzI3MDc1MTVfNTg2MjMwODg5NTQzODE1NzgwOF9uLmpwZyJdLFsicCIsInRodW1iIiwiMTQ5eDE0OSNjIl1d/59956288_611253872707515_5862308895438157808_n.jpg" for 18.104.22.168 at 2020-02-14 03:56:29 +0000
2020-02-14T03:56:29.527489+00:00 app[web.1]: W, [2020-02-14T03:56:29.527401 #4] WARN -- : [6b9b7602-3396-4ff2-83e5-972de0e45e2e] DRAGONFLY: uid 2020/02/14/5y36xd9k0y_59956288_611253872707515_5862308895438157808_n.jpg not found
2020-02-14T03:56:29.527604+00:00 app[web.1]: I, [2020-02-14T03:56:29.527517 #4] INFO -- : [6b9b7602-3396-4ff2-83e5-972de0e45e2e] DRAGONFLY: GET /system/refinery/images/W1siZiIsIjIwMjAvMDIvMTQvNXkzNnhkOWsweV81OTk1NjI4OF82MTEyNTM4NzI3MDc1MTVfNTg2MjMwODg5NTQzODE1NzgwOF9uLmpwZyJdLFsicCIsInRodW1iIiwiMTQ5eDE0OSNjIl1d/59956288_611253872707515_5862308895438157808_n.jpg 404
In my refinerycms 4.0.3 app, a logged-in refinery user can always access his own user page. This is necessary for example if they want to change their password.
However, on the user page, any user can also control their own plugin access. This rrenders the whole plugin access selection meaningless. Has this been fixed in newer versions?
I made a temporary hack where only a superuser can see and select plugin access permissions.