By Dinocanid
Getting Started
So you’ve just installed Mysidia Adoptables 1.3.6, now what? Already at your disposal you’ll find some built-in features and very basic starter themes.
The first thing you’ll want to do is access the Admin Control Panel (Admin CP or ACP) to take a quick look at everything the script has to offer. If you’re making a very basic collectables website and not much else, this is probably all you’re going to need. There’s even settings you can turn on/off for click-based leveling (think dragcave). But what if you want something bigger, more unique?
Adding a Theme (A new coat of paint)
Right out of the box, Mysidia lets you add themes and allows users to switch between whatever themes you have installed. A theme is, more or less, your site’s template and what makes it look pretty. There are about two ways to install a theme:
1. Navigate to “Themes->Add/Install New Theme” in the ACP and fill out the info there.
2. Navigate to your cPanel file manager and enter the templates folder. Make a new folder with your theme’s name and upload all these files:
1. Header.tpl
2. Template.tpl
3. Style.css
4. Any addition files your theme might need to work properly
That’s how you add a theme, but what about creating one?
[Tutorial] Creating a Theme
This tutorial won’t go over the basics of HTML and CSS, so you’ll have to search through the internet for that. What it will cover though is how to apply that knowledge to creating a theme.
Pages and Controllers
(A big ol’ switcheroo)
After spending several weeks trying to wrap my head around 1.3.6, one of the most notable changes is how pages are set up. In this version, page controllers have moved and classes are no longer called classes. This causes some confusing mixups for developers coming from 1.3.4. Here’s the equivalents laid out:
* adoptcontroller.php (1.3.6) = adopt.php (1.3.4), located in the root (usually public_html) folder.
* class_adoptable.php (1.3.4) = adoptable.php (1.3.6), located in “…/root/model/domainmodel”.
* Classes from 1.3.4 have also basically been scattered all over the place. We’ll cover each one as we go along.
$document->add
(Something happened here…)
For…some reason, this command is now modular. Things that used to be built-in now have to be included manually. Who knows why, but that’s how things are now.
If, for example, you wanted to use:
$document->add(new Comment(“”));
Then you would have to add:
use Resource\GUI\Document\Comment
…at the top of the file. Again, exactly why it was broken up like this is beyond me.