ORM-based file upload package for php.

It does not seem common to implement __wakeup() privately. I've been having issues with the Stapler S3 storage adapter where this method can't be called because it's private.

Is there a reason S3ClientManager's wakeup method is private?

Getting this error when running composer update command. ??

{"error":{"type":"Symfony\Component\Debug\Exception\FatalErrorException","message":"syntax error, unexpected '['","file":"/home/damascu1/drccweb/vendor/codesleeve/stapler/src/Codesleeve/Stapler/StaplerServiceProvider.php","line":118}}{"error":{"type":"Symfony\Component\Debug\Exception\FatalErrorException","message":"syntax error, unexpected '['","file":"/home/damascu1/drccweb/vendor/codesleeve/stapler/src/Codesleeve/Stapler/StaplerServiceProvider.php","line":118}}Script php artisan clear-compiled handling the post-update-cmd event returned with an error

I just upgraded my app from L4 to L5 and encountered an issue when deleting a file from S3. An exception is thrown when validating the delete request to S3:

{"error":{"type":"InvalidArgumentException","message":"Found 1 error while validating the input provided
 for the DeleteObjects operation:\n[Delete] is missing and is a required parameter","file":"\/www
\/htdocs\/vendor\/aws\/aws-sdk-php\/src\/Api\/Validator.php","line":38}}

Which would seem very weird to me. I did check the message (see attachment) and as far as I can see, the [Delete] component is actually available. Any idea what this could be?

I'm using the following stack:

• L5.1
• laravel-Stapler 1.0.05
• stapler 1.0.06 aws/aws-sdk-php 3.4.0

Much appreciated

Hello,

I would like to know if there is an easy way to resize an image only if it is bigger than the size defined in the requested style. If the image is smaller, we just do not touch it.

Thank you for your help Regards,

The image quality of generated images isn't good as it should be so I decided to add a simple option, which allows you to set the quality of every single style with a simple @PERCENT postfix:

$this->hasAttachedFile('image', array(
    'styles' => array(
        'thumbnail' => '70x70@95',
    ),
));

This package is extremely useful, however still miss something. The Laravel possuim one function to create slugs, Str::slug() and I think it would be interesting to add this option to rename the images, that way it would be possible to follow a more defined pattern.

$this->hasAttachedFile('image', array(
    'styles' => array(
        'slug' => true,
    ),
));

In this case, something like Image Name_test.jpg would look like image-name-test.jpg

This PR fixes a condition where the file attachment would fail to save in the filesystem because the filesystem name was derived from the URL basename that was too long for the filesystem to support.

It also fixes a small issue where hash anchors in URLs would cause file extensions from pathinfo() to be incorrect

I'm running stapler with a S3 backend and since implementing stapler I've noticed considerable lag in my application. After running xhprof over my laravel app and digging my way down through the rabbit hole I found out that for every attachment->url() call stapler seems to do a S3->bucketExists() call. This seems to generate a guzzle request over the S3 API to check if the bucket exists. When doing this for say 50 images on a page this will result in a lot of curl requests and is really slowing the application down.

What is your opinion on this?

Im currently trying to incorporate a small gallery system into my application. Users can upload pictures to galleries and the pictures are getting resized to 3 different sizes for the thumbnail view, medium view and full view.

<?php

class Picture extends Eloquent {
    use \Codesleeve\Stapler\Stapler;

    protected $table = "user_pictures";


    public function __construct(array $attributes = array())
    {
        $this->hasAttachedFile('picture', [
            'styles' => [
                'full' => '512x512',
                'medium' => '256x256#',
                'thumb' => '96x96#',
            ],
            'url' => '/uploads/images/:attachment/:style/:id_partition/:filename',
            'keep_old_files' => true
        ]);

        parent::__construct($attributes);
    }

    public function user()
    {
        return $this->belongsTo('User');
    }

}

My upload part of my function looks like this:

$gallery = Gallery::find($id); // we get this through POST 
$file = Input::file('file');

$picture = new Picture;
$picture->picture = $file;

if ($gallery->pictures()->save($picture))
{
    return Response::json('success', 200);

} else {
    return Response::json('error', 400);
}

The image gets added to the database correctly and the uploads/ folder is 0777-chmodded as well. So no big deal there. However, the real problem I'm having is completely unclear to me:

{
  "error":
  {
    "type": "Imagine\\Exception\\RuntimeException",
    "message": "imagejpeg(.IMG_0014.JPG): failed to open stream: Permission denied",
    "file": "\/Users\/spaceemotion\/dev\/laravel\/vendor\/imagine\/imagine\/lib\/Imagine\/Gd\/Image.php",
    "line": 691
  }
}

The php-tmp folder is writable as well, I tested that through other applications.

Why do I still get a permission denied? What am I doing wrong?

What is the best method to store multiple files with a single record. I have a need to store an image, an mp3, and an mp4 file and associate them with a single record. I don't really need a one-many relationship since there will never be more than one of each type of file being stored. My implementation works great if I just select one file with my form, however, if I select more than one the save function errors out with this error:

Illuminate \ Database \ QueryException SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'title' cannot be null (SQL: insert into sermons (title, subtitle, speaker, desc, msgdate, updated_at, created_at) values (, , , , , 2014-01-14 23:46:08, 2014-01-14 23:46:08))

It's like it looses the reference to the instance of the newly created record. Here is the code from the function that handles adding a new record:

public function handleCreate()
{
    //handle create form submission
    $sermon = new Sermon;
    $sermon->title = Input::get('title');
    $sermon->subtitle = Input::get('subtitle');
    $sermon->speaker = Input::get('speaker');
    $sermon->desc = Input::get('desc');
    $sermon->msgdate = Input::get('msgdate');
    $sermon->imgfile = Input::file('imgfile');
    $sermon->mp3file = Input::file('mp3file');
    $sermon->mp4file = Input::file('mp4file');  
    $sermon->save();

    return Redirect::action('SermonsController@index');
}

I've looked for documentation on this but just cannot seem to find any. Any help would be greatly appreciated.

Hi

I think it would be a great addition to use Stapler as a single table, e.g managed_files. The table would include a morphTo relationship to have multiple model types create a relation to it. Other models would then need morphMany or morphOne.

The hereto described structure can be quite easily implemented, however pushing a file from a model to its managed_files relationship seems to be impossible at the moment..

A code example:

Let's say the managed_files table looks like this:

$table->increments('id');
$table->morphs('model');
$table->string('file_file_name')->nullable();
$table->integer('file_file_size')->nullable();
$table->string('file_content_type')->nullable();
$table->timestamp('file_updated_at')->nullable();

The ManagedFile model:

class ManagedFile extends Eloquent {
    public function model() {
        $this->morphTo();
    }
}

Another model, let's say User:

class User extends Eloquent {
    public function __construct() {
        $this->hasAttachedFile('avatar[file]');
    }
    public function avatar() {
        $this->morphOne('ManagedFile', 'model');
    }
}

No matter how I try to feed hasAttachedFile with the uploaded file data, it still tries to find the corresponding columns in the User table instead of in the related model table.

I don't know a lot about the internals of Stapler, but a quick suggestion may be to have hasAttachedFile support a parameter for setting a custom defined table and/or base column name.

This way the file can be called as $user->avatar->file->url() or if a custom getAttribute method or presenter has been set still as $user->avatar->url(). Moreover as the hasAttachedFile is still set in the related model (User), model specific configurations can still be set.

Note: the idea about using a single table originates from Drupal.

Hello. We are currently using https://github.com/CodeSleeve/stapler for image uploads.

But now we want to support uploading videos. This videos are processed by Cloudinary so basically we get 4 video URLs with different qualities.

We want to save these videos to S3.

Does https://github.com/CodeSleeve/stapler support this?

I have this problem that occasionally some original image files are not saved to AWS S3. Most of the time everything works fine and it's maybe one file in 10000, but it happens semi-regularly (we currently have millions of files in S3, as stapler attachments, so it has happened quite a few times). What's weird is that some image styles are uploaded, but not the original. And it's not always the same styles, sometimes only one or two, sometimes everything but the original. This all seems to happen completely silently, since I can not find anything in any logs regarding the files. I haven't found any pattern for this and I'm not sure how to further test this. There doesn't seem to be any pattern to it.

So this is as much a bug report as it is an open question for any ideas that could help me better track down this issue to get to the bottom of it?

A consideration for a future update might be to stop using Inflector pluralization on :attachment interpolation when creating the location for files. The Inflector package is routinely getting updates to how certain words are pluralized and when those updates are pulled into a project with Stapler, it can change Stapler's construction of file locations.

For example, a project with an attachment named "audio" was formerly stored in /audios/[id]/[style]/[filename], but in Inflector v1.3, the pluralization for "audio" was changed to "audio" (instead of "audios"), which resulted in Stapler expecting files to be located at /audio/[id]/[style]/[filename]; breaking the connection to those files.

It may be a better approach to interpolate :attachment with the attachment name as specified on the model, rather than pluralizing it. And/or allow for the plural form to be specified on the model.

Had said problem using laravel 5, stapler and laravel-stapler with S3 (outside EC2), and thought to report my 5c here in case it's a pain for someone else.

What resolved the issue for me was moving key & secret under a credentials array: From

's3_client_config' => [
    'key' => '',
    'secret' => '',
    'region' => '',
    'scheme' => 'http',
],

to

's3_client_config' => [
    'credentials' => [
        'key' => '',
        'secret' => '',
    ],
    'region' => '',
    'scheme' => 'http',
],

and changing Validator.php's validateS3Options() to validate the changed options instead. (Naturally, i also updated the config file values.)

This change is not backwards compatible with this package. This is due to the override of the getAttributes() model method. If the attribute values aren't strings, the query builder can't bind them properly and you get an "Object could not be converted to string" message.

This looks like it's been in the EloquentTrait for quite a long time, since https://github.com/CodeSleeve/stapler/pull/94/commits/86fd1db830a837c189384dad0f9c6eed325b3d8d. What does overriding that method actually provide though? Doesn't the accessor for the field still exist?

Edit: Sorry I didn't bring this issue up in the laravel stapler repo, but this is the repo that contains the EloquentTrait class