ThanksHm, yeah I can see what you mean. Bit surprised by this as this is surely quite a large breaking change, quite a lot of things will use this hook. I'll need to look into how it's supposed to work now.
// Definir el shortcode para llamar a la función comments_template()
function comentarios_shortcode() {
ob_start();
comments_template();
return ob_get_clean();
}
add_shortcode('comentarios', 'comentarios_shortcode');
Hi, yes I would. Coming with sites with many WP native comments and looking to fill up the forums with activity and transaction to XF forums (with XF linked threads also embedded/functioning as comments on WP posts).That's not something the plugin would currently be looking to handle, it would need a full XF importer built as it would also need users, threads and forums to be handled too. Would you be interested in a standalone importer that did WP posts to threads, WP comments to posts, and imported users too?
1.2.3
1.2.4
- Fix for comment template from other plugins being unset
1.2.4
- Notice of failed Article Forum Connect Plus check
- Adds support for WordPress Application Passwords for API authentication
Fixes WordPress 6.4 incompatibility
API optimizations
Adds support for threads that are not viewable by guests
API key wizard updates
Changed connection check API URL to avoid clash with legacy API directory
Added error message output to connection check notice
I just pushed a minor update that changes the API call that's made to verify the connection - it used to call the baseHello. I've recently installed this on our WP site and am getting this error: "Failed to connect to your XenForo API. Check your credentials." Our website URL is exactly the same as it reads in the ACP > Setup > Options > Basic options. I have also made sure the API key is correct - it is a super user key and the scopes auth, node:read, thread:read, thread:write are all enabled. The key has also been copied exactly. Can you assist?
/api
endpoint, but we found on another site that a legacy API directory I think from an XF1 addon was getting in the way and that request hit the legacy code. I've changed the endpoint to api/index
which should avoid that.We use essential cookies to make this site work, and optional cookies to enhance your experience.