Thanks! I added these in to set the text on the article list and “see all results” button.
.td-search-wrap-mob .td_module_wrap .entry-title a {
color: #000000;
}
.td-search-wrap-mob .td_module_wrap:hover .entry-title a {
color: #ef0000;
}
.td-search-wrap-mob .td-post-date {
color: #000000;
opacity: 0.8;
}
.td-search-wrap-mob .result-msg a {
color: #ffffff;
background-color: #000000;
opacity: 0.8;
}
My problem is a combination of PHP 7.1.2 plus define(‘WP_DEBUG’, false); in wp-config.php.
The warning from the offset posts not being set causes the spinner to keep going. If I set it to 0, the spinner stops and it shows it is added.
Turning off WP_DEBUG doesn’t cause the problem.
See:
https://forum.tagdiv.com/topic/error-in-composer-page-and-post/#post-185283
Most people will never see the warning unless they have define(‘WP_DEBUG’, true); in wp-config and are using PHP 7.1.x.
I have a problem in Admin where I add any big grid and it just spins.
Actually, it’s a bug in the code for all of the Big Grid classes where the ‘limit’ in $atts array is not being set.
line 20: $atts[‘limit’] = self::POST_LIMIT;
The code should be using an isset function to check if the ‘limit’ is set and if not then set it to 0.
Workaround: In the settings for your Big Grid, enter 0 for the value “Offset posts” and the warning will go away.
Actually, it’s a bug in the code for all of the Big Grid classes where the ‘limit’ in $atts array is not being set.
line 20: $atts[‘limit’] = self::POST_LIMIT;
The code should be using an isset function to check if the ‘limit’ is set and if not then set it to 0.
Workaround: In the settings for your Big Grid, enter 0 for the value “Offset posts” and the warning will go away.
Actually, it’s a bug in the code for all of the Big Grid classes where the ‘limit’ in $atts array is not being set.
line 20: $atts[‘limit’] = self::POST_LIMIT;
The code should be using an isset function to check if the ‘limit’ is set and if not then set it to 0.
Workaround: In the settings for your Big Grid, enter 0 for the value “Offset posts” and the warning will go away.
Does that include any 7.1.x version or only 7.1.0?
Twitter username for the Twitter sharing button on posts is set under Theme panel >> Post settings >> sharing.
If this is blank is uses the General Settings site title. Which it should never do because it can cause someone on twitter to be spammed with notifications. The site title and twitter username is 2 different things and may not be the same. Twitter @ Names have no space, Word Press site titles have spaces.
So your site name could be “Buffalo Botox” but then the twitter share button will spam poor @Buffalo on twitter with notifications.
-
This reply was modified 9 years by
macksix.
Nevermind, I see if there are the top 5 posts showing above, that is where they show. I was not seeing that the top 5 were for that category, I thought is was the top five recent for all categories. My dumb! 😀
Thanks guys!
All better now.
Sorry, that is not what I mean. The last 5 recent posts in any category do not show. Even on test with demo data and setting, the 5 recent posts do not show. Please look at screenshots above. It is clear there are 7 posts in Economy but only the last 2 are shown when I view the Economy category.
The last 5 “latest” post in the category are not being shown. Why?
Every category is this way.
-
This reply was modified 9 years by
macksix.
Now that my head is not fuzzy, due to lack of sleep learning this theme and visual composer, I see it is filtering the last 5 posts and I have seen those sorts of setting in the theme. I need to find if there is some global filter set.
Are those normally called the Archives? I see that in the browser tab it is called “Economic Archives” so that is maybe why it does not show the 5 latest? Is an Archive supposed to be different than listing the posts in a category?
The URL is http://defiantamerica.com
If you look at the Economy category, there are only 2 posts showing out of 7.

As you can see, I have filtered the posts on Economy within the Dashboard and it shows all 7.

I also have cache turned off.