The FLBuilderModel::get_upload_dir() and FLBuilderModel::get_cache_dir() methods are used to get the paths for both reading and writing.
Each has it’s own filter that I imagine you could use to change the paths. Those are fl_builder_get_upload_dir and fl_builder_get_upload_dir.
For cropping photos, we’re letting WordPress handle writing to files via $editor->save( $cropped_path[‘path’] );. The $editor var is an editor instance returned from wp_get_image_editor().
For writing CSS/JS cache we’re just using file_put_contents.
I’m not really familiar with the S3 plugin, so I don’t really have any ideas as to what kind of integration could be done. Hopefully the above will point you guys in the right direction. Let me know how it goes!
You’re welcome! We’re always opening to adding hooks. When you say “post-save action hook” do you mean after the CSS/JS cache is saved? Do you have an idea as to what you would need that hook to make available to you to get this working?
I hope you don’t mind me chiming in but we too are planning on using this plugin, and hadn’t yet considered the cached assets URLs…
I’m just wondering whether you use the pro version of S3 offload? It seems like they might have added (in a new release) a way to only serve certain assets from Amazon. This is definitely a workaround, but you might be fine with just serving images/files from S3/CloudFront and JS/CSS from the web server.