By the way: I myself are not especially interested in having the category displayed. If the custom post type would be displayed instead, that would be fine. But it doesn’t… there is just no category-div.

If I examine the code, the following line fails:

if ( $current_queried_term instanceof WP_Term ) {

So my custom post type post seems not to be instanceof WP_Term – do you know, what the problem could be?

Well, o course a custom post type can have a standard post category. As you see in the above code, it just works 🙂 I add the categories and the post types in the block in Visual Composer and everything would work fine – if the theme wouldn’t lock out custom post types by default.

If it wouldn’t, your users could display any custom post type in the Big grid easily with its associated category. But it’s your choice, of course. 🙂 For me, it makes everything much harder because I have to come up with a complicated solution for beeing update safe – if it it working at all… In the end it has to be done via JavaScript – thats a little dirty 😉

But what would be the problem for you to just display the category regardless which post_type the post has?

The problem is: changes in td_module.php cannot be done via child theme this they are not update safe.

I need to limit the categories which are being displayed as related, too! An option in the theme panel would be wunderful!

Hey, Bogdan,

that worked!

Thank you very much for the great support!

Regards,
Rolf

Hi!

I have the 6.5.1 installed but still don’t see the new accordion or tabs or tour in VC: https://dl.dropboxusercontent.com/u/2216407/Bildschirmfoto%202015-10-21%20um%2016.14.59.png

They are only listed under depreciated: https://dl.dropboxusercontent.com/u/2216407/Bildschirmfoto%202015-10-21%20um%2016.14.51.png

I have updated both the theme and the plugin.

Any further suggestions?

Hey, I contacted the author of FeedWordPress yesterday, too. He replied and his solution worked. I post it here for anyone who experiences the same problem:

Hi Rolf!

Thank you for getting in touch. I’m sorry to hear this has been a problem for you. I think that it should be easy to solve; at least, here’s something to try. Let me know if it works for you.

By default, FeedWordPress deliberately tries to protect syndicated posts from being altered by the formatting filters that are applied to locally-authored posts (I’m not positive this is the best default policy; but there are reasons in favor of it and reasons against). In any case, though, this behavior can be turned off by flipping a single setting in the FeedWordPress admin interface.

Here’s how. Log in to your WordPress Dashboard, and then go to FeedWordPress’s Posts & Links settings (Syndication > Posts & Links in the navigation bar on the right hand side of the WordPress admin interface). This should bring up a settings page with a number of panels of settings that control how syndicated posts appear on your website.

Next, scroll down through these settings until you find a panel labeled Formatting. The first setting on this panel should be called Formatting Filters. By default, unless you have altered this setting, it should read “Protect syndicated posts from formatting filters” in the drop-down menu. What you’ll want to do is to pull down the drop-down, and change this setting to “Expose syndicated posts to formatting filters”.

When you are done, scroll down to the bottom to find the blue Save Changes button. Mash that button, clear any page caches or browser caches you may need to clear to make sure you are looking at a fresh copy, and take a look at your website again to see if VC codes are now being applied to syndicated posts.

Note that if you are adding VC codes to syndicated posts by editing them in the WordPress post editor, that when you save changes to a syndicated post you will also need to click the checkbox in the post editor reading “Manual editing,” in order to ensure that the changes that you make won’t be overwritten by FeedWordPress during a later update.

Hope this all helps. Let me know if you have any questions, and let me know how this works for you.

Cheers,
-C

Hi Emil!

I tried and found that the problem seems to be with the plugin “FeedWordPress” (https://wordpress.org/plugins/feedwordpress/) which syndicated articles from RSS feeds. On posts created by the plugin and activated plugin, no VC content gets parsed. When deactivating the plugin, VC tags are parsed well. Also VC tags are parsed well on posts that where created by hand, even when the FeedWordPRess plugin is active.

Can you imagine, what the issue could be?

Regards,
Rolf

• This reply was modified 10 years by rk.

so luckily I don’t work here nor speak for them.

Well, I think tagdiv might be lucky ones, ‘course you don’t work there nor speak for them. 😉 Because I don’t like to be SHOUTED at in forums. And likewise most of the people I know don’t like that.

By the way: Most of the trouble might result out of the misleading “upgrade from 4 to 6” naming of the update script. The script works nicely, but you have to run it also when upgrading from 5 to 6. But for example the problem with the outdated VC-Data was very annoying. Maybe the script addressed that too. The best thing would have been to place the “run the update script!” message prominently on every admin page header. Maybe the guys an tagdiv can add that for people updating in the future…

Regards,
Rolf

Hey ChrisS,

this is nonsense. Also major version updates have to work without changing the whole site manually. You might not
benefit from new features without changing something, but the site must not be broken!

Also, there must be no obligation to delete and install something in a specific order, in order to get things working.

And it must not be necessary to switch the theme to the default one in order to upgrade the VC settings which otherwise are producing an error.

Sorry, but the code just has to take care of that stuff. In good programming.

Regards,
Rolf

I found the solution in a Forum:

– Change theme to default theme.
– see if Design Option under “VC” appears
– if so – just resave data and then change back to “Newspaper”.

I can’t see any reason why a new version of the theme should not be compatible to the old one. That’s very unprofessional, guys!

• This reply was modified 11 years by rk.

Hi Steven,

A little CSS magic will help you in any case. 🙂

Great, thanks! Is there already a list of the changes?

Regards,
Rolf