by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 08 14:20
    depfu[bot] closed #104
  • Sep 08 14:20
    depfu[bot] commented #104
  • Sep 08 14:20
    depfu[bot] labeled #107
  • Sep 08 14:19
    depfu[bot] opened #107
  • Aug 24 11:31
    AnniMel commented #30
  • Aug 07 10:12
    tvdeyen closed #106
  • Aug 07 09:42
    tvdeyen synchronize #106
  • Aug 07 09:41
    tvdeyen synchronize #106
  • Aug 07 09:40
    tvdeyen review_requested #106
  • Aug 07 09:40
    tvdeyen opened #106
  • Jul 18 14:53
    depfu[bot] labeled #105
  • Jul 18 14:53
    depfu[bot] opened #105
  • Jul 15 09:26
    depfu[bot] synchronize #104
  • Jun 24 08:07
    depfu[bot] synchronize #104
  • Jun 24 08:07
    depfu[bot] edited #104
  • Jun 24 08:07
    tvdeyen commented #104
  • Jun 05 09:52
    depfu[bot] labeled #104
  • Jun 05 09:52
    depfu[bot] opened #104
  • May 27 09:46
    tvdeyen closed #102
  • May 27 09:22
    mamhoff edited #102
Thomas von Deyen
@tvdeyen
Dennis van der Vliet
@dennisvdvliet
That is very helpful. Excuse me for hitting you with so many questions without contributing a whole lot.

As a first contribution I would like to make some changes to how pictures are saved and processed.

  1. Add an option so a certain set of 'versions' of an image can be created when uploading.
  2. Do this in the background, using Active Job, so everyone can choose what processing backend they like to use.

Is this something that is of interest to you?

Dennis van der Vliet
@dennisvdvliet
The use case for this would be that if you store images on s3 or swift doing the inline processing is too slow. And also something that should not happen in the request cycle. This can be prevented by pre rendering these versions.
Dennis van der Vliet
@dennisvdvliet
An alternative to adding it to the main app would be to do like this plugin: https://github.com/magiclabs/alchemy-image_optim
Thomas von Deyen
@tvdeyen
  1. For the picture version thing: Please have a look at AlchemyCMS/alchemy_cms#879 This is the fundamental refactoring that would make this possible. Unfortunately we have limited time, to continue working on it. If you would take over, this would be great!
  1. AWS S3 image hosting support would be very great. There was a lot of discussion lately. Creating images upfront could be a solution, but is not suitable for all use cases. Alchemy has a image cropper widget, where editors can crop images inside the admin. That's why we render the images on demand. This is not working with S3 setups, unfortunately. Please keep this feature in mind, if you start to refactor ;)
Allie Reilly
@acreilly
@channel Does anyone know how I would go about seeding picture elements?
Joris van Rooij
@jorrizza
@acreilly You can create an EssencePicture, which in turn belongs_to Picture through #picture. This Picture has a Dragonfly accessor called image_file. You can use this accessor to store an image from disk in your seeds.
nodecraic
@webworkio
hey, if anyone has any remote remote , designer, DevOps or Sysadmin jobs they can post them at http://webwork.io
IngoAlbers
@IngoAlbers

Hey. I am creating a custom module for our resource, in which I want to be able to assign alchemy pictures from the library directly without essences, contents or elements. I still want to use the nice alchemy archive overlay, but this is tightly integrated with an element being available, for example:

def in_overlay?
  params[:element_id].present?
end

As I now have to decouple this by creating customized views and custom actions, I was wondering if there would be any interest for this feature? (being able to use alchemy pictures in the original overlay in a custom module in an easy way) or if something in this direction has already been done for the newer versions?
In the google group I found some similar requests without any real solution by for example just using essences in the end.

Thomas von Deyen
@tvdeyen
Hey. Indeed this is too tightly coupled. We would love to see a contribution that removes that hard depedency.
Ignacio Palacios
@NachoPal
Hi all
I deployed my project to my staging servers
and I forgot to change the staging environment configurations to avoid caching
So now I'm trying to flush the cache to see the new deployed changes
Alchemy uses default rails cache, right?
running: rake tmp:cache:clear RAILS_ENV=staging
unsuccessfully...
Am I missing something?
Ignacio Palacios
@NachoPal
Ok, was NGINX messing up caching the pages...
service nginx restartand problem was solve
Thomas von Deyen
@tvdeyen
Nice to hear that it works :) And yes, Alchemy uses the default Rails caching
Allie Reilly
@acreilly
Hi, for normal picture elements, not picture gallerys, how do I enabled the ability to crop an image and resize?
Thomas von Deyen
@tvdeyen
@acreilly either pass crop: true to el.render :image in your element view or (recommended) set it in your elements.yml as settings at your content definition.
Allie Reilly
@acreilly
thanks!
where can i find a list of all the settings available?
Thomas von Deyen
@tvdeyen
Everybode prefering Slack (as I do), please join http://slack.alchemy-cms.com
Dennis van der Vliet
@dennisvdvliet

I'm having some issues with the alchemy-devise gem. It complains that it "could not find compatible versions for gem 'alchemy_cms'".

alchemy-devise does indeed have a dependency on version 4.0.0 beta of alchemy_cms (https://github.com/AlchemyCMS/alchemy-devise/blob/master/alchemy-devise.gemspec)

Thomas von Deyen
@tvdeyen
@dennisvdvliet we changed version of the master branch, because we changed the roadmap. Sorry about that. Fix is coming right along.
Thomas von Deyen
@tvdeyen
@dennisvdvliet fix is live. Please update your bundle. Sorry for your inconvenience
Dennis van der Vliet
@dennisvdvliet
No worries thanks for the quick follow up
Martin Tomov
@mtomov

Hello : )

I've got a quick question about the elements in page_layouts.yml:

I've got about ~10 elements that I would like to add ~6-7-8 pages. As the YML format is a bit inflexible in extending arrays, is there some alchemy way of defining common elements across different page layouts, so that I won't repeat them everywhere?

Thomas von Deyen
@tvdeyen
Hi @mtomov would you please join our Slack channel? Gitter clients suck so much, that we switched back to Slack. Thanks
Martin Tomov
@mtomov
all right, will do. I've found this one to be rather nice, but I guess you've been using it for a bit more. Will switch, yes
Ignacio Palacios
@NachoPal
Hi, I'd like to join to the slack channel, but the link provided is giving an error
Ignacio Palacios
@NachoPal
Maybe in the meantime you can help me here with an issue
I'm trying to figure out what's the best way to be able to do a POST to an alchemy page which is usually handled by 'pages#show'
Ignacio Palacios
@NachoPal
I mean, I'd like to use another 'controller#action' for POST
I was doing that, adding the POST route to my app routes, and then, in my controller doing a redirect_to :back
the problem is Form input values get lost because of the redirect
in the case I do a validation and I want to render the form again because some field wasn't right
So I'd like to be able to render the view instead of redirecting
Ignacio Palacios
@NachoPal
What's the proper way of doing that using Alchemy?
Thomas von Deyen
@tvdeyen
Please have a look in how Alchemy does this in the MessagesController. In a nutshell you render the alchemy/pages#show template in your controller
And yes, we need to move away from the free heroku dyno for the slack singup page
Ignacio Palacios
@NachoPal
Thanks Thomas
Thomas von Deyen
@tvdeyen
Upgraded the heroku dyno. The Slack Signup should now work forever