puravida1976

Hello. We keep our database cache updated to within 30-45 days. In this case, you want a quicker refresh, so we provide the ability to refresh requests manually. Here is an article on how to do that:

https://support.shrinktheweb.com/Knowledgebase/Article/View/11/0/

I noticed that you were using the WWW version of the domain in our database, so I refresh it for you. Cheers!

Nobody can afford to offer a completely free service for very long. ShrinkTheWeb offers a free service (up to certain limits) and has done so successfully since 2008. I’ve never even heard of Robothumb, which is saying a lot considering I stay on top of competitors that come and go. That is another one that will give you headaches in time. They just don’t spend the money necessary to provide a quality service.

Marking as resolved.

@grex22

After initial investigation, it doesn’t appear that we support any type of tooltip presently. Also, I did a search across all plugin files for “tooltip” and found no results. In other words, there is no mention in our code of the word “tooltip”, so it looks like what you are seeing is not coming from our plugin.

What have you done to troubleshoot?

On the “Web Design” page, I see a lot of screenshots. Did you get it working already?

The plugin (WP-Portfolio) doesn’t support columns currently. You would need to create two separate groups of websites (2 website groups) and then modify your template to have two columns. In one column, you would have the first website group and in the second column, you would put the shortcode for the second website group.

It may still not turn out how you want, because the images will stack into one column with the details on the right. Supporting multi-column grids has been requested before a few times and may go into our next revision of the plugin.

Try this:
In Portfolio Settings, click on the Force Table Upgrade button.

Hello,

I do not remember any of our developers using “tooltip” for any of the classes. Perhaps it slipped through as an after thought. I will review the code and make any necessary changes.

Hello 8milenj,

No need to upgrade unless you need PRO features or higher account limits. But what do you mean by fetching the images dynamically? Do you mean using the embedded method? It just became apparent a few months ago that our plugin does not support the embedded method, which is something we hope to add in the near future.

However, if you want to bypass the shortcode altogether and just use the copy/paste embedded method, I would not recommend that because you could not easily update all occurrences of the code if needed. You never know when something might change or requirements change. It would be bad if something changed to break your requests.

https://support.shrinktheweb.com/Knowledgebase/Article/View/112/0/data-from-stw-was-empty–outbound-curl-blocked

Hosting2go has whitelisted our IP, and now the plugin is working. Hopefully this will help others who run across the same issue! ??

@everyone
After much research and investigation, we have discovered that the web host has been blocking outbound curl requests, which our plugin relies on to work. We have requested that the web host whitelists our IP (which is not the best solution since our IP could change in the future).

Both issues will likely be resolved by this FAQ:

This is usually due to the plugin tables not being created properly. In Portfolio Settings, click on the Force Table Upgrade button.

Hi,

No, it didn’t work. At least no new ticket opened up for you. Sorry. I thought an email would do it. I guess you need to sign up for an account and open a ticket. You can just cancel the account once we’re done (to avoid receiving our newsletter and announcements).

Let me know if you have any trouble.

-Brandon

Sorry. Delayed by phone call. I tested this, using the same suggestion you posted above, and it worked fine. I could find no negative side effects. Since it only affected embedded method, the caching locally still worked as expected.

This means that I can consider to make the next release v1.39 include this change unless someone can find a reason why not to do so.