• WordPress 7.0.4
• PHP 8.4
• WPForo 3.1.4
• wpForo - Blog Cross Posting - 3.1.6

Error/Warning:

PHP Warning: Attempt to read property "ID" on null in /nas/content/live/oursite/wp-content/plugins/wpforo-cross-posting/wpForoCrossPosting.php on line 893

----

I don't want to create a patch to handle the warning, but it is filling up the logs, and I'd like to get it cleared up.

----

Root cause: wpForoCrossPosting::postContent() is hooked to the_content at priority 9999 and does global $post; $postID = $post->ID; with no null check. the_content fires in some contexts without a populated $post global (REST rendering, admin-ajax, certain widget/feed paths), so it throws.

---- theoretical patch I could drop into mu-plugins----

I am experiencing a critical and reproducible problem with wpForo Cross Posting 3.1.6.

The important point is that the plugin was working correctly after a complete fresh installation.

Timeline

Yesterday I completely removed wpForo and the Cross Posting plugin, cleaned the related database data and installed everything again from scratch.

I then configured wpForo and Cross Posting again.

After the fresh installation and configuration, Cross Posting worked correctly.

Today I created WordPress articles and manually selected a wpForo forum for Cross Posting.

It worked correctly.

One WordPress article created one corresponding wpForo topic as expected.

However, later today, without changing the Cross Posting configuration, the exact same action suddenly started creating thousands of topics/posts.

I did not enable any additional Cross Posting rules or change the forum configuration immediately before the problem appeared.

Expected behavior

When I create a WordPress article and manually select a wpForo forum for Cross Posting:

1 WordPress article → 1 wpForo topic

Actual behavior

The plugin enters what appears to be a recursive/looping process:

WordPress article → wpForo topic/post → Cross Posting triggered again → another topic/post → Cross Posting triggered again → …

This can result in thousands of topics and posts being created from a single Cross Posting action.

This is extremely serious because one accidental Cross Posting action can generate tens of thousands of database records.

Important detail

The problem is not simply that Cross Posting stopped working after changing the wpForo page ID.

The complete timeline is:

• wpForo page ID was changed previously.
• Yesterday wpForo and Cross Posting were completely removed and freshly installed.
• The database was cleaned.
• Cross Posting was configured again.
• Cross Posting worked correctly after the fresh installation.
• Today it continued to work correctly initially.
• Later, without changing the configuration, it suddenly started creating thousands of duplicate topics/posts again.

Therefore, I suspect that something during the Cross Posting process is causing the plugin to lose or fail to recognize the relationship between the original WordPress post and the wpForo topic.

I would especially appreciate it if you could investigate whether Cross Posting 3.1.6 can enter a recursive loop when processing the cross-post relationship or when detecting an already-created topic.

Environment

• WordPress
• wpForo
• wpForo Cross Posting 3.1.6
• Elementor
• Manual Cross Posting from WordPress articles
• Fresh installation of wpForo and Cross Posting
• Problem occurs even after a clean installation

The fact that the exact same setup works correctly for several articles and then suddenly starts generating thousands of topics from one action is the most important part of this bug report.

I can provide database information, screenshots, plugin settings and details about the generated duplicate topics if required.

Thank you.

#2303788 <-- will work

#2303788 <-- will not work

Let me know if you need any more info.

Browser console shows this error in the reply/editor section: Permissions policy violation: unload is not allowed in this document.

Site URL: youngbarnacles.com
wpForo version: 3.1.4
Advanced Attachments version: 3.3.0

A user was accidentally deleted and later recreated with the same email address.

Example:

• Old user ID: 124
• New user ID: 654
• Same email address
• Same username

I updated all old comments in the wp_comments table so they now reference the new user_id.

I also verified that:

• comment_type = private
• comment_parent = 0
• comment_approved = 1
• course_id in wp_commentmeta is identical to newly created private comments.
• Old and new comments are otherwise identical.

Current behavior:

• All new private comments work correctly.
• All old private comments display:

"This content has been hidden from site admin."

This happens:

• while logged in as Administrator
• and even when logged in as the recreated user himself.

The comments are not lost.

In the WordPress backend I can edit them normally and see their full content.

There are no custom wpDiscuz database tables in my installation, only the standard wp_comments and wp_commentmeta tables.

Is there any additional metadata, cache, or internal mapping used by the Private Comments addon that may still reference the old user?

Or is there a repair/synchronization procedure for old private comments after a user has been recreated?

Thank you!

I would like to share a feature suggestion for your roadmap. Please understand this not as a demand, but as a constructive idea from a user who sees strong potential in the gVectors ecosystem.

Many websites that use wpForo also use WordPress posts, pages and wpDiscuz comments as part of the same community environment. From a user perspective, these are not completely separate content areas. They are all part of one website and one discussion space.

For that reason, I believe there could be great value in a universal search interface for:

• WordPress posts and pages
• wpForo topics and replies
• wpDiscuz comments
• gVectors AI / wpForo AI semantic search

The first version would not need to be a new search engine or a combined search index. A practical basic solution could simply provide one shared search interface with separate search targets.

For example:

Website | Forum | Comments | AI

Each mode could still use the native search system behind it:

• Website: native WordPress search
• Forum: native wpForo search
• Comments: wpDiscuz / WordPress comment search
• AI: existing gVectors AI / wpForo AI search

This would keep the solution lightweight, maintainable and transparent. The main improvement would be the unified user experience: one search entry point instead of several disconnected search interfaces.

A very useful basic implementation could include:

• shortcode support
• Gutenberg block
• Elementor widget
• PHP function or theme hook
• reusable opening buttons for header, forum, sidebar, etc.
• responsive layout
• accessibility and keyboard navigation

In other words, the feature would be most powerful if it were not limited to the wpForo area only, but could be placed anywhere in WordPress.

A more advanced version could become a central Search & AI Workspace for the whole website. On the first level, it could separate:

• AI Search
• Classic Search
  
  Then, under Classic Search, users could choose between:
  
  
• Website
• Forum
• Comments

The AI mode could keep the conversational or semantic experience, while the classic modes would continue to use the existing native search results. So this would still not require a fully merged search result page or a new relevance engine.

I also understand that your current AI/search solution uses a collapsible area, and I can see why you may want to keep that as the default interface. My suggestion would not require abandoning this approach. Ideally, the underlying search/AI component could be modular enough to be displayed either:

- in the existing collapsible wpForo-style area, or

- optionally inside a modal, overlay or custom theme container.

This would allow site owners to integrate the same central search interface into a global header search modal, above the forum, or through a sidebar button, while still relying on the official gVectors component.

In my case, I am considering building a small custom solution for this. But before doing so, I wanted to share the idea with you, because I believe many other WordPress + wpForo + wpDiscuz site owners could benefit from an officially maintained gVectors solution.

To summarize the roadmap idea:

1. Extend the wpForo/gVectors search interface so it can also search WordPress content and wpDiscuz comments.
2. Start with a simple target switcher that forwards searches to the native systems.
3. Make the component reusable across WordPress, not only inside wpForo.
4. Keep the current collapsible interface as a default option.
5. Add optional modal/overlay integration for site-wide search experiences.
6. Later, evolve this into a central Search & AI Workspace for the whole gVectors ecosystem.

I think this could significantly strengthen the connection between wpForo, wpDiscuz, WordPress content and your AI features.

Thank you for considering this suggestion. I would be very interested to hear whether something like this could fit into your future roadmap.

first of all, thank you for your ongoing work on wpForo and wpDiscuz. I am currently working on a website where WordPress content, wpForo discussions and wpDiscuz comments are meant to become part of one coherent community experience.

While planning the next steps, I noticed something that might also be relevant for other users: the existing widgets are useful individually, but they do not yet feel like one unified widget system. Especially when using WordPress posts, forum topics, forum replies and comments together in a sidebar or on a homepage, the visual and functional differences between the widgets become quite noticeable.

I would like to share this as a product suggestion, not as a demand. From my perspective, this could be a valuable roadmap idea for the wpForo/wpDiscuz ecosystem.

A possible basic version could be:

- modernized and visually unified widgets for wpForo and wpDiscuz

- consistent spacing, typography, metadata rows, icons and responsive behavior

- improved layout options for the wpDiscuz comment widget

- shared display options such as:

  - show/hide title

  - show/hide excerpt

  - show/hide author

  - show/hide date

  - show/hide avatar

  - show/hide comment/reply count

The existing sources could remain separate, for example:

- latest forum topics

- recent forum replies

- recent comments

- most commented posts

But all widgets would feel like parts of one consistent product design.

A more advanced version could be a real universal content widget for WordPress + wpForo + wpDiscuz.

The idea would be: one widget, multiple selectable sources, one consistent layout.

Possible sources could include:

- WordPress posts

- WordPress / wpDiscuz comments

- wpForo topics

- wpForo replies

- recommended posts

- recommended forum topics

Possible sorting options could include:

- latest

- most commented

- most replied

- most viewed

- recently active

- recommended (specified by the tag "recommended")

Possible layout modes could include:

- compact list

- list with excerpt

- list with avatar or image

This would not need to become a search engine, a shared index or a complex ranking system. The main value would be a maintainable and visually consistent content discovery component that helps website owners connect their blog, forum and comment activity in one coherent interface.

I believe this could make wpForo and wpDiscuz even more attractive, especially for websites where the blog, the forum and the comment section are meant to work together as one community environment.

In my own case, such a feature could avoid the need to develop a custom solution. But more importantly, I think many other users might benefit from a unified widget system as well.

Thank you for considering this idea.

• User A PMs User B
• Admin also receives a copy of the message.

How do I prevent also being sent a copy of the message.

For one, I don't need my inbox being clogged up with these, and two, while nothing is truly private, I really would prefer not to have my users' messages being seen/sent to my admin email address.

Thanks!