“There are no docs for this view” in Group’s Docs tab

Hmm. That is mysterious. I tested BP Docs with a TwentyTwenty-family theme, and everything worked as expected. Are you using the BP Legacy or BP Nouveau template pack?

What happens if you use the “why not create one” link to create a new doc?

Hello again,

I’m using the BP Legacy template pack.

If I select the “why not create one” button, the same thing will happen. I have already tried creating some test Docs without any luck.

I stumbled upon this thread and I’m not sure if it’s related to the problem I’m experiencing: https://www.ads-software.com/support/topic/docs-associated-to-a-group-are-not-listed/

We’re building a multilingual platform that allows users to select their preferred language and interact with it. The Docs library will adjust its language accordingly.

Unfortunately, the Groups cannot be translated or configured to allow language selection for each of them.

Check the screenshots below:

I can select a preferred language for every Doc: https://ibb.co/SdwYxZ7

However, I cannot select a preferred language for every Group: https://ibb.co/NxdgXpM

When I visit the Home tab of a Group (in every language), I can see activity related to Docs, but only the ones in English and not in any other language (because English is the main language of our platform!?): https://ibb.co/0VqCwzF

My assumption is that the Groups cannot display any content on the Docs tab due to the multilingual interface of our platform.

(Just to let you know, I encountered a similar issue with the Docs Tags, and I had to manually select a language for each of them.)

My question is whether it’s possible to select the language for each Group, so that the English Docs will be associated with the English Groups. Later, we would have to do the same for every language (French Docs with French Groups, Greek Docs with Greek Groups, etc.).

Thanks again.

Yes, the group association is managed by taxonomy terms, so it sounds like your multilingual setup is going to be complicated (if each term needs to be assigned to a language). I don’t know how you are handling the language setup, so can’t offer any help on the groups piece, but BuddyPress has many hooks and actions, so it’s likely something can be done.

Hi David,

Thanks for your assistance. I’m sorry for the late response, I was trying to solve the issue without any luck. However, I managed to figure out the source of the problem; it was Polylang.

I faced another problem while developing the multilingual platform. The Docs were only visible to the administrator and not to registered users.

When I deactivated the Polylang plugin, everything on the website ran smoothly, but as a result, I could not navigate in any other language. I am currently testing some translation plugins to make things work.

I am leaving this topic active for a couple of days in case I find the right solution for this issue with Polylang.

Thanks again.

Hi again,

I’ve made great progress in developing my multilingual platform and have managed to solve most of the issues I encountered by editing the taxonomies. However, I’m currently facing one last problem related to creating docs while using a different language interface.

Here’s the scenario: when I’m in the French interface, the link “/fr/docs/create/” doesn’t work at all, whereas the English link “/docs/create/” functions normally. It seems that the ability to create docs is limited to the English interface only.

To fix the previous issues I mentioned, I had to deactivate languages and translations for custom taxonomies from the Polylang plugin settings. Specifically, I deactivated the following taxonomies: bp_docs_access, bp_docs_comment_access, bp_docs_folder_in_user, and bp_docs_folder_in_group.

I am using the following plugins additionally to make things work: BP Docs Taxonomies, Buddypress group taxonomy, and BuddyPress Polylang. These plugins are essential for making my platform work smoothly.

It seems that there might be a conflict between the Polylang plugin and some of the plugins I’m using. This conflict might be affecting the ability to create docs in languages other than English.

So, I am going to reach out to the Polylang team directly in order to seek a solution to the problem. It seems that they would be the best resource to help me resolve this issue.

I appreciate your assistance and guidance in this matter.

Topic resolved