Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Clive Cooper 4 posts 25 karma points
    Jun 23, 2011 @ 13:20
    Clive Cooper
    0

    Universal Media Picker 1.5 with Amazon S3 missing data

    Our Picker has stoped loading the data correctly

     

    Before :-

          modes: [
    { type: "flash",
    src: "/jwplayer/player.swf",
    config: {
    file: "Rob.mp4",
    streamer: "rtmp://rtmp.cdn.dhelixc.com/cfx/st",
    provider: "rtmp"
    }
    },
    { type: "html5",
    config: {
    file: "http://cdn.dhelixc.com/Rob.mp4"
    }
    },
    { type: "download" }
    ]

    Now :-

          modes: [
    { type: "flash",
    src: "/jwplayer/player.swf",
    config: {
    file: "",
    streamer: "rtmp://rtmp./cfx/st",
    provider: "rtmp"
    }
    },
    { type: "html5",
    config: {
    file: "http://Rob.mp4"
    }
    },
    { type: "download" }
    ]

    all the settings in the data type have not been changed, has any one experienced this before

    or know of any updates that could have caused this problem

    Thanks

     

  • Morten Christensen 596 posts 2773 karma points admin hq c-trib
    Jun 23, 2011 @ 13:26
    Morten Christensen
    0

    Hi Clive,

    Did you also update to the latest version of the AWS A3 Picker?

    It looks like the CDN Domain is missing in the Now-snippet. Could you try and re-save the settings on the datatype and re-select + republish one of the videos to see if its updated correct?

    - Morten

  • Clive Cooper 4 posts 25 karma points
    Jun 24, 2011 @ 16:09
    Clive Cooper
    0

    Hi Morten

    I had to launch the site with a get around,

    but I'll give that a go, as we are using this combination on a number of our sites

    thanks

  • Jeavon Leopold 3010 posts 13225 karma points MVP 8x admin c-trib
    Jul 11, 2011 @ 10:40
    Jeavon Leopold
    0

    Hi Morten,

    I have just confirmed this also. On our development site and production site, the cname is not coming through using UMP 1.5 and S3 provider 1.2.

    I have resaved the data type and altered the cname and altered back again.

    Any thoughts?

    Regards,

    Jeavon

  • Morten Christensen 596 posts 2773 karma points admin hq c-trib
    Jul 12, 2011 @ 19:48
    Morten Christensen
    0

    Hi Jeavon,

    I sent you an email with updated assemblies.

    Let me know if it works.

    - Morten

  • Justin Spradlin 137 posts 345 karma points
    Jul 12, 2011 @ 20:32
    Justin Spradlin
    0

    I'd like to know if that works too. I think that my site was having the same issue after I upgraded recently to the latest UMP + S3 provider. 

  • Jeavon Leopold 3010 posts 13225 karma points MVP 8x admin c-trib
    Jul 12, 2011 @ 21:03
    Jeavon Leopold
    0

    Hi Justin,

    It does work! I'm sure Morten will release the updated v1.2.1 S3 provider shortly.

    Cheers,

    Jeavon

  • Morten Christensen 596 posts 2773 karma points admin hq c-trib
    Jul 12, 2011 @ 21:03
    Morten Christensen
    1

    Hi Justin,

    I believe the issue only occurs for some files, which results in missing cdn name. I have located and fixed the issue and will upload an updated package very soon.

    - Morten

  • Justin Spradlin 137 posts 345 karma points
    Jul 13, 2011 @ 01:35
    Justin Spradlin
    0

    Great! Thanks for the quick action! You rock.

  • Morten Christensen 596 posts 2773 karma points admin hq c-trib
    Aug 16, 2011 @ 18:22
    Morten Christensen
    0

    Hi Justin and Clive,

    I have uploaded version 1.3 of the S3 Provider, which fixes the CNAME issue.

    Sorry about the wait.

    - Morten

  • zoltrain 2 posts 22 karma points
    Aug 17, 2011 @ 17:15
    zoltrain
    0

    Hi Morten, 

    I've been getting the same  issue, but after downloading the new version it's fixed that problem. Though I'm getting a new issue though.

    When I upload a file using the S3 provider it will always upload to the root folder, even if I select a subfolder under the root.

    I also noticed you didn't package up the AWSSDK.dll in the new install, since you're using an older version of the AWSSDK(current release is 1.3.8, the one used for the S3 provider is 1.3.1) thought I'd let you know.

    Is there a place to get the source for this project? as I could write a patch for it if you're a bit busy.

    Cheers,

    Ryan

  • Justin Spradlin 137 posts 345 karma points
    Aug 21, 2011 @ 18:16
    Justin Spradlin
    0

    Hi Morten,

     

    Thanks for the update. That fixed the issue for me regarding the missing cdn name. However, I am also having the problem where all files are uploaded to the root of the bucket even when you specify a folder. It is not really a big deal, but I was going to make directory for images and videos to keep them seperate. Can you check and see if it is doing the same for you. 

    As far as updaing existing records to include the cdn, do you know of a quick way that I could "update" my exising documents that are missing the cdn. I had put a work around in my templates to add the cdn if it was missing as a short term fix. Now that that bug is gone, I have about 100 documents that clients uploaded and picked videos that don't have the cdn. Is there something I can do in the DB or via the API to quickly get all the documents and update them. 

    Thanks,

    Justin

  • Morten Christensen 596 posts 2773 karma points admin hq c-trib
    Aug 22, 2011 @ 14:59
    Morten Christensen
    0

    Hi Guys,

    Sorry about the updated package not working. It seems the merge of the AWS dll and my own dll has gone wrong.
    I'm working on a fix now.

    I will post back to this thread when its updated.

    - Morten

  • Morten Christensen 596 posts 2773 karma points admin hq c-trib
    Aug 22, 2011 @ 16:03
    Morten Christensen
    0

    AWS S3 Picker is now updated. Version is the same 1.3 as before.

    I dropped merging the dlls, and found an issue with the folder structure when no new foldername was entered. This has now been fixed, so the uploaded files doesn't end up in the root (unless uploaded to the root of course).

    Let me know if you encounter anything else.

    @Justin in order to update existing nodes I believe it would be sufficient to Republish the node (you might have to Save and Publish, but dont think its necessary). So if you create a script that loops through your nodes and publishes nodes with the AWS S3 Picker datatype on it you should be able to fix your existing properties.
    Let me know if you need help with that.

    - Morten

  • zoltrain 2 posts 22 karma points
    Sep 05, 2011 @ 10:56
    zoltrain
    0

    Hi Morten,

    Thanks a lot for the update, this has fixed the issue with the folders not being created/media not being saved to them correctly.

    Though I'm getting one particular error when viewing/selecting a value, it seems that the picker is formatting the URL to the image incorrectly when using the choose tab and using the S3 provider.

    It formats the image path as http://{bucketname}/{folderpath}/.s3.amazonaws.com/{folderpath}/{imagename}

    The folder path is written into the URL twice, an example of how it's being formatted is.

    http://testbucket.media/Test/.s3.amazonaws.com/Test/thumbnail.jpg

    Where Test is the folder inside my bucket, and thumbnail.jpg is the asset name. this is how the path is saved to the database which means at the moment all the image paths are being saved incorrectly and I have to use a helper function to correct them.

    - Ryan

  • Morten Christensen 596 posts 2773 karma points admin hq c-trib
    Sep 07, 2011 @ 19:54
    Morten Christensen
    0

    Hi Ryan,

    Did you try this both with and without a custom domain?

    - Morten

Please Sign in or register to post replies

Write your reply to:

Draft