Copied to clipboard

Flag this post as spam?

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


  • Rasmus Pedersen 3 posts 74 karma points
    Sep 12, 2017 @ 14:35
    Rasmus Pedersen
    1

    Reupload of image

    Hey Backend Devs!

    We, TeaSolutions, recently discovered your package and currently testing how we can use it for our projects. The current project I'm working on, we tend to use the re-upload function often, so we don't have to select it in content if we change the image. enter image description here

    The problem we bumped into was, if the image is already compressed and you reupload a new one, you won't be able to compress the new image. It will say the Image is already compressed. Is that something you have thought about or experienced from other users?

    Our intend of the package is, that our customers will be able to use it themselves without it being a big task to change images.

    Another thing us devs talked about was the list of Optimized Images. Since we have projects with 1000+ images, the list easily gets a mess and doesn't seem that helpful to the customer. Have you had any further thoughts about this list? Could it be an idea to make it optional?

  • Backend Devs 61 posts 484 karma points
    Sep 13, 2017 @ 07:22
    Backend Devs
    0

    Hi, Rasmus and TeaSolutions team!

    We are delighted that you are planning use Tinifier in your projects and ready to help you!

    I created a new bug "Reupload of image" in the tracker. We will fix it in a next release.

    List of optimized images is in discussion right now. We already faced on with a messy problem. We have different approaches how to resolve it:

    1. Top X most tinified images.
    2. Recent Y tinified images
    3. Remove this feature at all
    4. Make it optional (show/hide option in the settings tab)

    What do you think about it?

  • Rasmus Pedersen 3 posts 74 karma points
    Sep 14, 2017 @ 06:33
    Rasmus Pedersen
    0

    Hey again,

    Thanks for the quick answer!

    From our point of view option 3 or 4 is what speaks to us the most. Though others could find it useful, so making it optional sounds like a good idea.

    If there should be anything else you want to ask us, feel free to ask and we will do our best to help.

    Waiting excitingly for next release

  • Backend Devs 61 posts 484 karma points
    Sep 14, 2017 @ 10:20
    Backend Devs
    0

    Hi,

    We are planning to release 1.3 version between 28 - 30 September and include show/hide "list of images" panel

    Thank you!

    Most decisions are not binary, and there are usually better answers waiting to be found if you do the analysis and involve the right people.

    James Dimon

  • Nik 495 posts 1905 karma points
    Sep 14, 2017 @ 11:12
    Nik
    1

    I'm not currently using Tinify (although I am currently looking into its implementation in a couple of existing projects).

    Just a thought on the list, what would be more useful would be a list of unoptimized images, so people can see what is still waiting to be optimised. Then the ability to export a list of optimized images based on a date range (i.e. when they were optimized) or on a %saving (so you could get the number of images that saved you the most etc).

    If you have a list of unoptimized images you can then queue them for optimisation, or bulk process them (assuming you have api requests left).

    The lists could be better as a dashboard view as well, as opposed to the left hand tree view. So switch the left hand tree view to be Settings / Stats / Images.

    Cheers, :-)

  • Backend Devs 61 posts 484 karma points
    Sep 15, 2017 @ 07:30
    Backend Devs
    0

    Hi,

    We decided to make an optional tree on the left panel with a single node "the most tinified images". In future, it can be easily extensible with other nodes like "unoptimised images".

    Export feature for each of this nodes is a cool idea. Right now we don't have enough resources to include it in 1.3 version, but the project is open-source so feel free to fork it. All required information we store in the DB.

    Regards

  • Backend Devs 61 posts 484 karma points
    Oct 10, 2017 @ 12:45
    Backend Devs
    0

    Hey,

    We released a new version where we resolved next issues:

    • show/hide left panel
    • re-upload issue
    • re-upload + optimize on upload setting crazy issue

    Also, we added support for Azure Blob Storage, read more about current (1.3) version on our blog.

  • Rasmus Pedersen 3 posts 74 karma points
    Oct 11, 2017 @ 09:05
    Rasmus Pedersen
    0

    Cool stuff. Will see if I find time to test it out.

    When do you plan to go out of beta?

  • Backend Devs 61 posts 484 karma points
    Oct 11, 2017 @ 10:52
    Backend Devs
    0

    We are waiting for feedbacks from Azure based websites and still have some minor issues. After it, we go out of beta. I assume it will be on Tuesday next week.

  • Backend Devs 61 posts 484 karma points
    Oct 17, 2017 @ 13:14
    Backend Devs
    0

    We have gone out of the beta!

  • Camilla Jeppesen 1 post 71 karma points
    25 days ago
    Camilla Jeppesen
    0

    Hello!

    Just installed package v. 1.3.2.

    I still have this problem. I experience it when I use "Remove file" and then reupload. The image is not Tinified then - so I used the "Tinify" option from the "Action"-dropdown.

    A red bar then appers with the text: "Tinifier Oops: Sorry, but at the same time you can only tinify only one image". I'm not trying to upload/Tinify any other image.

    It's also a problem if I just use the "Choose File".

  • Backend Devs 61 posts 484 karma points
    7 hours ago
    Backend Devs
    0

    Hi,

    Possibly it occurs because DB messed up during upgrades. You can click "stop tinifying" and try again. I believe the error occurs only with already uploaded images. If it doesn't help try to clean up Tinifier* tables in the DB.

    enter image description here

Please Sign in or register to post replies

Write your reply to:

Draft