Issue: XenForo Support

Quite annoying that XenForo has E_NOTICE turned on, have to go through and add a lot of isset()s.

Uninstaller written, and it's quite fantastically generic if I do say so (should work for all platforms without modification).

Just realized, XenForo is throwing E_NOTICE in default XenForo pages, so perhaps it's just not compatible with PHP 5.4? Or... yup, just disabled XenForo's Debug Mode and the errors are gone. Thank you for wasting my weekend, when I could've worried about these later, during a cleanup build.

XenForo's forum index now loads again, which means progress, if you're optimistic.

Installer (including auto-installer) now runs beautifully. Spent a lot of today tweaking that and getting some of the front-end UI functioning (mainly error reporting, like login errors and such).

Soon

Can finally create new areas via the Admin Panel. Will be using every other panel now and confirming that items can be created/saved under XenForo.

With the exception of the Style Manager, all panels are confirmed working for add/edit/delete. Will extend the Style Manager in a bit with a XenForo sub-class to fix the issues.

Style Manager ready. Time to start templating.

Faster to template if there are pages that need templating. Building the importer first. Importer should use the same 1-click functionality as in the installer, which should save a lot of time building a new system (just extend vw_CP_Progress_Controller and define the Steps).

Always dread attachments. It's the last part of the importer to make now...

Importer ready for testing. When attachments are stored in the file system, the source must either be on the same server as the import target, or the attachment directory must first be physically copied to a directory on the import target server and the import config setting for the attachment path should be overridden. Only VaultWiki 4 can transfer wiki attachments to another copy of VaultWiki 4 from different servers because it now allows API access to attachments (this does NOT include platform-level attachments on wiki comments). However, physically copying the attachments and updating the paths is still the ideal solution for transfers between private servers or HTTP password protected sites.

Had some problems alternating databases under Zend_Db due to lack of USE implementation, but a workaround was documented in a Zend bug report. Also the database instances were overwriting each other in vw_DB during import, causing the importer to crash during write access to the target database. Both issues are now solved.

Reduced redundancy between development updates across platforms. All platforms now execute from the same code base, rather than clones. Should have been doing this from the start, but it apparently wasn't working in our Windows staging environment, or nginx was having issues executing PHP files at the end of symlinks.

VaultWiki now loads again under vBulletin 4. Some vB4 templates now need to be updated to reflect certain changes applied for XenForo support, like the overlay JS updates.