puravida1976

Posted in the wrong plugin forum.

The latest mouseover code works with all up-to-date browsers

We will take a look. In order to prevent “breaking” existing users of our plugin, we will likely add a new option for the shortcode. Users will select [thumb] (for legacy support) or the new default of [stwthumb] to prevent conflicts in the future.

@jvandemerwe
No need to take it so personally. I was just pointing out that the “fix” likely was coincidence. It wasn’t a far stretch to assume that the account in our system that matched your username here were one and the same.

Glad it’s all working for you now, but I want to ensure that your observations do not unintentionally mislead and frustrate others. It’s better to isolate any real “bugs” if there are any. In this case, I don’t see anything wrong with Dan’s code, so I was pointing that out.

@jvandemerwe

Actually, no, it is still a coincidence.

I just took a look at your ShrinkTheWeb account and it has been disabled. If you try to login, you will see:

Disabled: Unsubscribed from ConstantContact

We disable accounts that unsubscribe from outage notifications and newsletters, because it causes more headaches for our support team when people are not aware of changes.

The reason it works normally but not when refreshing is because you have cached images locally which will show all the time. When you try to refresh them, our system blocks you because of the reason above.

Open a ticket with our support team and they will get you back up and running again.

@jvandemerwe

It was most likely coincidence that your change “fixed” your issue. There is no reason to send a user agent. As Dan mentioned, the main cause is that the IP/domain is not properly added to the “Allowed Referrers” list. This is your account security and must be set properly.

By default, a bad request sets a timer for up to 6 hours. If you managed to fix your “Allowed Referrers” and waited some time; then it probably just resolved itself. You could also delete the cache file no_response.jpg to kick off the service again.

Hi Justine007,

Websnapr is not as good as Thumbshots, which is already supported.

If you would like to review a reliable and high-quality service (our images are the highest quality of all the services), then please consider ShrinkTheWeb (https://www.shrinktheweb.com). I am the CEO and our support team can assist the developer to integrate, if the users of ODLinks would like to have support for our service added.

Best regards,

Brandon

Hello mark.b,

You can “sort of” do what you want with our advanced api and custom size pro feature. However, our service is not really focused on mobile devices and we do not currently support custom user agent strings (necessary for true mobile device rendering).

I believe that what you want would be better served by https://www.browserstack.com

Best regards,

Brandon

Considering this issue as resolved.

Consider adding support for ShrinkTheWeb (https://www.shrinktheweb.com)

More features and more powerful API. Reliable service, faster captures, and infinitely scalable.

By the way, WP-Portfolio is completely free and it supports our free account level. So unless you need something special (features or high usage), then you should be good to go…

Hello!

I wouldn’t mind helping you with formatting, but it is a bit beyond my current skill level in WP. Our plugin is more useful for use inside posts and for use by other plugins. It’s not really designed for portfolios, because there’s already some good plugins out there for that.

Check out WP-Portfolio and see if it meets your needs. I think you may be pleasantly surprised at how flexible that plugin is and it can run side-by-side with our plugin or it can be run by itself, depending upon your needs. That plugin might just save you a lot of time and headache. ??

Hello,

You would link like this:

<a href="https://somesite.com" target="_blank">[thumb]https://somesite.com[/thumb]</a>

Hope that helps!

We have pushed a release v2.2 that corrects this bug with the formbuilder code we rely on. Marking this issue as resolved.

Due to lack of response, we have launched a PHP 5.4 server and tested this change. The change to the formbuilder code we rely on works as expected, so we will be launching an update to our plugin shortly.