Frequently Asked Questions
How do I instal SiteTree?
As for any other WordPress plugin, the easiest way is to use the administration area of WordPress itself:
- Go to the ‘Plugins’ screen through the main menu on the left.
- Click on the ‘Add New’ button at the top of the screen.
- Search for SiteTree.
- Click on ‘Install Now’ to instal the latest version available.
How do I upgrade from a previous version?
Just use the Automatic Update feature integrated into WordPress or manually replace the folder
sitetreethrough your FTP client or cPanel. The plugin will automatically manage the upgrade of your settings when first launched.
There is only one exception, SiteTree 1.0: before installing the current version, you must upgrade to SiteTree 1.3.3 in order to keep your preferences.
What do I need to use SiteTree?
All you need is a web hosting service running PHP 5.2.4 or later and at least WordPress 3.3. If your WordPress instal is older, the plugin will not activate. Instead, you should be prompted to upgrade to the latest version available.
Can I include custom content types in both my Sitemap and my Archive Page?
Right now, SiteTree supports only the content types built into WordPress: posts, pages, categories and tags. I have plans to implement automatic detection of custom content types but I don’t know when this feature will be actually added to the plugin.
I set all up but there is nothing in the Archive Page. What’s the matter?
First, you need to make sure the developer of the Theme you are using has not removed the filters applied to the
the_contentfilter hook. If you don’t want to dig into the source code of your Theme, just add the following lines of code at the beginning of the
functions.phpfile included in the Theme folder:
add_action( 'wp_footer', create_function( '', "echo 'Filter ';" . "echo ( has_filter( 'the_content', array( SiteTree::invoke(), 'append_sitemap' ) ) ? 'ON' : 'OFF' );" ));
Now, if Filter OFF shows up at the very end of the Archive Page, something in your Theme must be fixed.
Nevertheless, a conflict with another plugin cannot be excluded. In this case you may try to figure out which is the one is giving you troubles, temporarily deactivate it and ask a developer for help.