XEN DEVELOPMENT is a developer's resource for new developers wanting to build XenForo 2 add-ons. Experienced developers are also welcome to share their experienes and knowledge. This site is not affiliated with XenForo or a replacement for the official XenForo developer forums.
I'm combining both so that the migration is easier. XenWord uses a post meta called thread_id whereas XPress uses their own table. It's unfortunate so without XenWord installed then all of the thread linking disappears.
An addon for documentation was started yesterday and most of today was spent working on it. The frame is starting to take shape. It isn't tied to a database table, yet. This is similar to getting off the couch and preparing to run a marathon. The race hasn't really begun.
This release is compatible with Theme House XPress. Added two options to the widget.
(1) Show Post Categories
(2) Option to Show Display Name versus XenForo username
I had to remove the files from the previous release then run uninstall in the Admin CP. Next, these files were uploaded...
The 3.5.2 code is in the legacy folder and hasn’t been changed. It was simply incorporated into XenWord Pro 2018.
With that said, I haven’t tried it. I believe the legacy is namespaced and that’s where I’d start looking.
Are those paths absolute or relative?
Look at line 9 of HTF_KotomiHeader.php
( 28 ) 2018.07.13 - July 13, 2018
Moved user role checks into conditional
Bug Fix: \src\Admin\Thread.php line 89
Bug Fix: \src\Includes\Widgets\Threads\Thread.php Prefix conditional
Bug Fix: \src\Includes\Authors\Link.php Added check for object vs single post
Released XenLate 1.0.0 for showing WordPress blog posts. I was able to take a resource thread ID, add it to a new WordPress post and tie the resource and thread together. A "Discuss in Our Community" button links to the resource.
This is my first attempt at creating a XenForo 2 addon. It is a XenForo widget which will pull the latest posts or pages from a WordPress installation. This addon should not require a bridge but the authors of the blog posts ID and user_id should match.
Set the absolute path