update edit the user template budypress

rosadonna. ru/aktivnost/

Look down

Hi selenii,
have you enabled wpDiscuz for Pages?
Screenshot: https://screencast.com/t/C7iGrruyu

Also don’t forget remove caches before checking.

Yes I have enabled it.
Caches are removed

Ok, this is not a regular post or page, this comes from BuddyPress template file. It sees they don’t use the regular <?php comments_template() ?> function in activity template file. The only way to turn on wpDiscuz on buddyPress activity page is editing activity template file and changing its comment function to WordPress Theme standard <?php comments_template() ?> function.

More info: https://codex.www.ads-software.com/Plugin_API/Filter_Reference/comments_template

But befor I have update the wpdiscuz it was everybody ok.

I have sent it to you

Thank you for access data.
We did our best to make it compatible with BuddyPress Activity page, but unfortunately it could be solved. New wpDiscuz has more smart conditions to be loaded. For example, it checks if(comments_open($post)) using current page/post ID. But as far as we see for some reason BuddyPress return PostID = 0 for Activity page. Here is the screenshot on your website: https://screencast.com/t/WE9nxgnz

Also we found that BuddyPress prevent comments_template() from rendering in their functions, this is the most important part to allow wpDiscuz be loaded. For example in \buddypress\bp-core\bp-core-theme-compatibility.php file we see this comments:

* To prevent comments_template() from rendering, we set the 'is_page' and
* 'is_single' flags to false since that function looks at these conditionals
* before querying the database for comments and loading the comments template.

There may be a serious reasons why they don’t want this to happen, so I think the idea to load wpDiscuz on activity page can not be more important and it will not be a reason for BuddyPress do change their function logic.

We did everything from our side. I’m sorry but this problem can not be fixed in wpDiscuz code.

But you say that your plugin ist compatible with budypress. I think you must write it on the fron page, that any function do not compatible.
Thank you for your help.

wpDiscuz is compatible with BuddyPress. if it is not been loaded only on activity page it doesn’t mean wpDiscuz incompatible. We’ve written this on our description page:

Integration with User Profile Plugins
– BuddyPress – Avatar, Profile page

So all is correct, wpDiscuz supports BuddyPress avatars and Username Links to Profile page. This is the main point of profile plugin integration/ compatibility. The issue on activation page is specific page issue, nothing more.

But it shows me this old comment in any buddypress page. everywhere I have this code.

How about 99% of your content which are not BuddyPress pages? Does wpDiscuz work on Posts, Pages….? And doesn’t it show BuddyPress Avatar and Profile URL on those post page comments? If so then it’s integrated well. BuddyPress pages are specific pages with specific functions, those are not designed to have comments. Those are non-comment compatible pages.

Saying wpDiscuz is integrated with BuddyPress we mean it shows BuddyPress Profile data on comments. The main profile data are Avatar, DisplayName and Profile Page URL.

BuddyPress have a few pages for certain data displaying, those pages are not regular content types and are not designed for comments. By default all comments are closed on those pages, your case is specific, for some reason you’ve opened comments and because of it’s not a regular logic id has conflicts with comment plugins.

Ok, all pages are woking very well, but how can I make an other page template for buddypress as standart. Some pages I could edit from my admin panale but not all. For example the member page.

Hi selenii,
I’d be happy to help you in this question, but i really have no clue. I think all changes should be done before loading template. As far as we see BuddyPress creates current page object with some changed logic. The most important is PostID = 0, ‘is_page’ and ‘is_single’ conditions = false. This process are being done before loading the template. So I think it need to be changed in earlier/deeper stages.