Jason

Hi Josh,

Apologies for the confusion, you can now update to Alyeska v3.1.17. There was about a 30-hour delay in the files being published on ThemeForest after the layout builder update went up to ww.wp.xz.cn.

http://themeblvd.com/changelog/?theme=alyeska

I also just verified that ThemeForest does have the correct version and everything went up about 36 hours ago. So you should be downloading v3.1.17 if you go to your Downloads dashboard at ThemeForest.net.

Please in the future go through proper support channel when asking for help. You’ll just log in to ThemeForest.net with the account which purchased the theme and that has valid support license, and then click “Contact Author” here:

https://themeforest.net/item/alyeska-responsive-wordpress-theme/164366/support

Hello,

The version of Jump Start you’re using was published almost four years ago. And although Jump Start v1 isn’t supported any longer (as of 2015 since the release of Jump Start 2.0), releases are still being made to Jump Start customers to keep things working for those that haven’t found time to update, which has now been over two years since the deprecation.

So if you’re going to keep using Jump Start v1, you must update it to the latest available patched version, which you can get by logging into wpjumpstart.com with the account you purchased the theme with and hold a valid license with. This will be Jump Start v1.2.15.

http://themeblvd.com/themes/

• This reply was modified 8 years, 4 months ago by Jason.

Please see here: http://docs.themeblvd.com/article/62-saving-large-amounts-of-data

Hello,

Nope, sorry unfortunately it cannot. This honestly is just because so many of the things that make the layout builder work are in the Theme Blvd theme framework, itself. The layout builder plugin adds the admin interface, extending tools already present in Theme Blvd framework. And then all actual elements outputted and styled on the frontend are part of the theme framework, as well.

Hi,

Here’s how to get support for your Theme Blvd products:

http://news.themeblvd.com/2016/05/31/important-theme-blvd-support-announcement/

Hi,

Is it possible to get just thumbnails on the main portfolio page or is that an extra added paid feature? My portfolio gallery appears as the larger screen shots.

This plugin, by itself, doesn’t really do anything other than just setup a custom post type and associated taxonomies. It is up to the theme to style how that looks on the frontend.

So to answer your question, yes, in our paid themes like Jump Start, Denali, and Gnar, we extend the use of this plugin to have galleries with thumbnails, but it’s not any kind of extended feature of the plugin you can get; it just depends on how you setup your specific theme.

I also wanted to see if there was a way to change the word /items/ to /portfolio/ in the URL. I do not see a setting for that or I completely missed it.

You’d have to filter where the taxonomy is registered, from your own plugin or theme. You can see in the plugin where all this is filterable:

https://github.com/themeblvd/portfolios/blob/master/tb-portfolios.php#L155

Hi,

The Tweeple plugin itself doesn’t come with any kind of styling. It’s just outputting a standard unordered list, which you can style from your own CSS, or often will simply take on the styling of the current theme and look fine.

In your case, the overflow would just have to do with your box holding the tweets (and this would be the same no matter what was in the box, whether it was tweets or some other random content).

In general with CSS, if you have a container that you’ve given a fixed height, and you want the content to scroll, you’d use the overflow CSS property.

http://www.w3schools.com/cssref/pr_pos_overflow.asp

div {
	overflow: scroll;
	width: 500px;
	height: 100px;
}

I should add that I’ve looked several times at this, and I’m not sure how the Tweeple plugin itself could ever pass 0 when setting the transient.

But in the last update posted to Tweeple a few days ago, I added a filter that allows you to manually filter the caching time, as it’s getting passed from Tweeple to WordPress’s set_transient().

https://github.com/themeblvd/Tweeple/blob/master/inc/class-tweeple-feed.php#L270

So, in theory the following code could be added to your child theme’s functions.php (or your own plugin, or wherever you want), to ensure that the Tweeple plugin is never passing 0, which is what causes the never expiring transient.

function my_cache_time() {
	return 7200; // Manually force cache time for all feeds
}
add_filter('tweeple_cache_time', 'my_cache_time');

You can give that a try on your sites and monitor several days, and see if anything changes. If nothing changes, then it suggests a bigger issue with setting WordPress transients in general and your server possibly? And if it does solve your problem, then it could point more towards the issue existing in the Tweeple plugin, itself.