Change how we load the plugin.

Since we now have code that should be available, both on the public blog
and in the admin section, we need to be more graular when loading the
various parts of the plugin.

We still try to avoid loading admin-only parts for the public blog, but
allways load the parts that we need in either case. Also avoid running
the db migrations when running unit tests, as the schema is copied over
from the dev environment it just caues problems.

Finally, don't hardcode unit tests to always be in_admin, but rather
determine that for each test.

1 files changed, 3 insertions, 8 deletions

diff --git a/includes/giglog_visitor_display.php b/includes/giglog_visitor_display.php
index 8177cb8..567bf41 100644
--- a/includes/giglog_visitor_display.php
+++ b/includes/giglog_visitor_display.php
@@ -1,13 +1,8 @@
 <?php declare(strict_types=1);
-function display_giglog()
+function display_giglog() : string
 {
-        require_once __DIR__ . '/admin/views/_concerts_table.php';
-		require_once __DIR__ . '/view-helpers/select_field.php';
-		require_once __DIR__ . '/venue.php';
-		require_once __DIR__ . '/concert.php';
-        $c = new GiglogAdmin_ConcertsTable();
-        $html = $c->render();
-		return ($html);
+    $c = new GiglogAdmin_ConcertsTable();
+    return $c->render();
 }
 
 add_shortcode('getconcerts', 'display_giglog');