Skip Navigation

[Resolved] Half of post disappears

This thread is resolved. Here is a description of the problem and solution.

Problem: I have a custom post type called "Activities" and I'm using Divi. When I check the Activity post on the front-end of the site, it appears to be cut off. Only half of the post appears.

Solution: Add some custom CSS that overrides the activity post height from Divi:

.single-activities .activities {
    height: inherit;
}
This support ticket is created 6 years, 6 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 3 replies, has 2 voices.

Last updated by Christian Cox 6 years, 6 months ago.

Assisted by: Christian Cox.

Author
Posts
#714448

Hello

I have a serious problem with one of my CPT content templates I've created in Toolset. I use the DIVI theme, everything is updated. The strange thing is that it worked without problem, and I moved on to other areas and I've just noticed today that the footer moved up and a big part of the post is missing in the browser: hidden link

Strangely it is there in the source view and I couldn't find any html anomalies. I even deleted that template and created a totally new template, without using Builder for it, only title and a field, and some lorem ipsum text, so you can see how it cuts the content in half...

This is a very similar content template, and works perfectly: hidden link

Please help me find quickly a solution for this... I also post the problem to Elegant Themes support too.

#718238
Screen Shot 2018-04-23 at 11.45.53 AM.png

WordPress automatically applies the class "activities" to this post, because this is the custom post type slug. Please look at the attached screenshot. You can see that I have disabled the "height" attribute on the "activities" class in the browser developer tools, and the post returns to full height. It appears that this height style is defined in your theme's style.css file. It's not something Toolset can control, but I can help you override it.

Go to wp-admin > Appearance > Customize > Additional CSS and paste the following code:

.single-activities .activities {
    height: inherit;
}

This should override your theme's height styles applied to the "activities" CSS class, but only on the single Activity pages. Other pages should not be affected.

#723658

Thank you Christian, you helped me out quickly as usual. Sorry to bother you with such a simple problem, it work just fine now.

But with the same CPT I found another problem which seems more complicated. And it's WPML related. I have a taxonomy archive to show the activity categories, but I used Divi Builder to create my layout and I created the taxonomy-activity-category.php where I inserted the layout as shortcode. The problem is that when switching languages the posts don't show in the other languages except the english. It seems the permalink does not translate. I translated the tanoxnomies and the taxonomy label.

This is the page that lists the categories: hidden link
When you switch the language you can see that the link of the categories has the same activity-category slug in the permalink in every language. I've consulted wpml help for this and it says it can't be translated: https://wpml.org/faq/translate-taxonomy-slugs-wpml/. That's okay, let's keep it in english, but it is still not working...

New threads created by Christian Cox and linked to this one are listed below:

https://toolset.com/forums/topic/taxonomy-archive-does-not-appear-in-secondary-languages/

#727962

I've split your question into another ticket, because it's our support policy to address one issue per ticket. Thanks!