Best Of

you want to set this to false.

@Adrian

I raised this as an issue on Github a while ago:

https://github.com/vanilla/vanilla/issues/7262
https://github.com/vanilla/vanilla/issues/7263

I can confirm that the issue is still the same in 2.6.3, and that it is still not possible to enable applications.

@createsean

Go to the dashboard and enable any plugin, and the Vanilla plugin should automatically enable.

A few bits of info you may find helpful:

• Vanilla operates in UTC.
• We already set date_default_timezone_set('UTC'); in environment.php (which runs at the start of every request) so I'm wondering if you're really using 2.6 and why setting it a second time in a class file makes a difference.
• Generally, if I'm recalling correctly, we do time conversions during the MySQL connection. Note that MySQL can exist on its own timezone separate from the server.
• Being 1 hour off usually indicates a daylight saving time issue.

I also started with MyBB! But you have to understand that extending Vanillas functionality is always done by adding files, not by changing existing ones.

Create a plugin in the plugin folder and only work with the files in this folder.

In Vanillas source code you find many "fireEvent" calls and whenever you see something like that, you can get control!

The file which is building a discussion is here https://github.com/vanilla/vanilla/blob/release/2.6/applications/vanilla/views/discussion/index.php

And in there, this part is most interesting:

$this->fireEvent('AfterPageTitle');
// Write the initial discussion.
if ($this->data('Page') == 1) {
    include $this->fetchViewLocation('discussion', 'discussion');
    echo '</div>'; // close discussion wrap
    $this->fireEvent('AfterDiscussion');
} else {
    echo '</div>'; // close discussion wrap
}

If you have created your own plugin, add this method to it:

public function discussionController_afterPageTitle_handler($sender) {
    echo '<h1>test</h1>';
}

It might help you understand what is happening (after you have read the developer documentation)

After that, think about the code above:
"If this is page one, print out discussion, if not print a closing div".

Your method now should check the same and if this is page one, you do not have to do anything, but if this is not page one, you should take the above actions.

A few hints on that:

• $this is passed to your method as first element and is refenced with the word $sender by convention
• if you want to fetViewLocation from a plugin, you need to use it like that: include $sender->fetchViewLocation('discussion', 'discussions', 'vanilla')
• you shouldn't echo that closing div, because that will be done by the if clause from above anyway
• don't forget to fire the AfterDiscussion event. Otherwise some additions made by other plugins will not work on the discussions that are printed out by you. You can emit that event like that $sender->fireAs('DiscussionController')->fireEvent(AfterDiscussion');

Do the same for the Tagging plugin: delete it and delete the cache afterwards.

I forgot about the import process. The structure file that I asked you to change is used for the Vanilla installation process. So changing it without doing anything else is useless. By visiting /utility/structure you force a reload of that structure file and after that your table GDN_Category will allow NULL in column CountComments.

And based on the above this is what is happening: The column CountComments of the table GDN_Category should be updated. It holds the information how many comments the discussions of the given category alltogether has. Therefor it updates the field with the sum of the field CountComments of the table GDN_Discussion for each category.
"Take the sum of GDN_Discussion.CountComments per Category and update GDN_Category.CountComments for all categories"

I guess the problem is that you either have empty categories or that the field CountComments in the table GDN_Discussion already shows NULL values.

But whatever it is: when you change the database structure so that it accepts NULL values for this columns and the problem shouldn't show up any more.
Instead of changing the structure file you could edit the databse directly, if you know how to do it. I would advise to make "0" the default value for GDN_Category.CountComments and GDN_Discussion.CountComments and allow NULL values.
After the import process you should do three things:
1. recreate the old structure file
2. visit yourforum/utility/structure again (to restore the database structure)
3. visit yourforum.com/dba/counts which is another helper which amongst other counts, also looks at the Category.CountComments column