Vaultwiki for Xenforo

pegasus if you need any alpha/beta testers I'd love to help!

You know I've been watching the xF version since last year and I plan to be one of the first ones to buy it :)!
 
Mostly got Alerts and Likes setup today. Still have to figure out how to send the alert for quoted content.

This revealed a bug in VaultWiki general where content is not being quoted to begin with.
 
I ended up figuring out how to alert on quotes, and fixed the bug where the Quote button wasn't actually quoting anything. Since then alerts, Likes (of comments), News Feed integrations seem to all be working now (at least when using dummy data). It's still not possible to Like wiki pages themselves - that will be bundled with the Social Media/Sharing feature once we decide exactly how we're doing it.

Still need to figure out why search isn't showing any results. The data handlers look okay...
 
Aside from the handler always explicitly returning an empty array instead of the found results, quite a bit was missing for the search to work properly. Fixed it all, just have to finish converting the search-tab templates now (vB4 to XF template conversion).
 
Took a bit of trickiness to detect if the user is currently viewing forums or threads (including in add-ons), but that and a few short hours of errors later, forum and thread headers are working properly under XenForo now. I like that the insertion points are easier to find in XenForo - I wonder if the methodology could be ported over to vBulletin or not, but that's for another day when mods or custom styles lead to conflicts.
 
Took a bit of trickiness to detect if the user is currently viewing forums or threads (including in add-ons), but that and a few short hours of errors later, forum and thread headers are working properly under XenForo now. I like that the insertion points are easier to find in XenForo - I wonder if the methodology could be ported over to vBulletin or not, but that's for another day when mods or custom styles lead to conflicts.
Awesome ;D!
 
Have some XFCP classes that really ought to use traits, but I don't know of any current forum software that requires PHP 5.4 as a minimum.

Also, the fact that XenForo caches the classname after resolving means we can't use different classes for different situations as I initially thought. Specifically I'm talking about the BB-Code formatter. We wanted to extend the formatter directly since VaultWiki has a lot more output formats than standard, plain-text, and WYSIWYG. But we also didn't want to destroy any existing XenForo add-ons by breaking the resolveDynamicClass chain (we want custom BB-Codes to continue working). Instead we have to use one child class that uses "sideways" inheritance which is always really confusing for someone trying to read the source code.

While it would be easy to clear the classCache in XenForo_Application, we can't actually rewrite the resolveDynamicClass method to avoid classes being defined twice. And while it's perfectly feasible to rewrite a portion of resolveDynamicClass in our own code so that our class extends last and doesn't have the redefinition problem, this ends up limiting other developers who may want to extend on top of our class.

So providing public access to certain normally protected things (_tags, for one), then extending out sideways seems to be the most viable option.
 
One of the most important features of a wiki is the ability to compare changes that different users have made to the same wiki page, at the very least, for moderation purposes. Since there is not a function of XenForo yet that can handle comparing two strings like this, it meant that if we wanted a release prior to XenForo 1.2, we had to find another solution to handle the comparisons in the mean time.
 
vaporware
Capture.webp


Announcement was made in 2010
This thread in 2011
It's now 2013

All I see is this being bumped from time to time... Feels most like an advertizement at this point.

If this isn't vaporware, clearly the development isn't good or active (in my opinion). It shouldn't take 3 years and this thread shouldn't be bumped every so often to market a product that isn't real.

Looking for a (real working) Wiki?

Free: http://xenforo.com/community/resources/8wayrun-com-xencarta-wiki.98/
Paid: http://xenforo.com/community/resources/8wayrun-com-xencarta-wiki-pro.1690/

Not happy with those options?

Make a request here http://xenforo.com/community/forums/custom-service-development-requests.69/
 
I apologize if my contributions to this thread have bumped it to seem like an ongoing advertisement when it has not even been released. That was not the intent. XenForo customers have asked that we be more transparent about development progress on a XenForo version of VaultWiki, so we have tried to do that. In addition, I have tried to include in my own posts what the experience has been like coding under the XenForo framework. A lot of things have not been as simple as just extending the appropriate XFCP class, and I found myself searching for resources and tutorials that ended up not existing. My hopes are that by sharing the experience in detail, if another coder runs across the same programming conundrum in the future, they might get some ideas from the approaches I had taken.

Announcement was made in 2010
This thread in 2011
It's now 2013
A similar announcement was made for vBulletin 4 support months earlier than that (June 2010: https://www.vaultwiki.org/issues/1650/). Users of vBulletin 4 finally had their VaultWiki-4 release last month. Provided that development tasks like these (https://www.vaultwiki.org/issues/1931/) were actually completed when they were marked such, we might expect a pattern directly proportional:

VaultWiki 4 for vBulletin 4 was released 2 years 9 months after announcement.

If XenForo is also released 2 years 9 months after announcement, that's July 2013. But we have already stated earlier in the thread, based on work to-be-done, that the latest will be June 2013.
 
Announcement was made in 2010
This thread in 2011
It's now 2013

All I see is this being bumped from time to time... Feels most like an advertizement at this point.

If this isn't vaporware, clearly the development isn't good or active (in my opinion). It shouldn't take 3 years and this thread shouldn't be bumped every so often to market a product that isn't real.

Looking for a (real working) Wiki?

Free: http://xenforo.com/community/resources/8wayrun-com-xencarta-wiki.98/
Paid: http://xenforo.com/community/resources/8wayrun-com-xencarta-wiki-pro.1690/

Not happy with those options?

Make a request here http://xenforo.com/community/forums/custom-service-development-requests.69/
You don't seem to see the difference between XenCarta and VaultWiki. It's the first paragraph in the description of XenCarta!

"XenCarta is a "lite" wiki. It can be considered a page/content management system with wiki-like features such as diff comparisons, revision history and templates. However, it is a "lite" wiki because I have designed it to be as lite as possible; to eschew the many useless and bloated features you can find in most wiki software."

The people posting on here want a Wiki that has those 'bloated' features because they are absolutely essential when running a successful wiki!

I mean the logic that it's automatically vaporware because you can't find any activity can be applied to XenForo.... especially during the lawsuit.
 
Top Bottom