My best guess is that the database connection is failing. Can you make sure that the connection parameters in /templates/config.php are correct?

I'm not really sure how to direct you -- Internal Server Errors are usually caused by htaccess files.  The mysql_query error may be caused by incorrect configuration information in your /templates/config.php (it might not be connecting to MySQL properly).

You can take two approaches to search in BigTree.  The first is the "search" method in the BigTreeModule class from which all module data classes are sub-classed:

http://www.bigtreecms.org/code-referenc … ule.search

You can just pass in the user's search term as the first parameter and the method will return anything in that module that contains those terms.

If you need to search Pages content instead of a module's content you'll want to use the BigTreeAdmin class's "searchPages" method.  For this method you'll want to pass in the first parameter as your user's search query and the second parameter as an array of fields to search (the default is only the navigation title).  To search the page's content, page title, and navigation title you'd want to the second parameter to be: array("nav_title","title","resources")

The other way that we commonly use is Google's Custom Search -- it leverages Google's index to provide really relevant search results and you can setup custom searches to only search a specific part of your site:
http://www.google.com/cse/

There's a good chance that following the 1and1 or GoDaddy .htaccess instructions will help with other shared hosting providers such as the one you listed. You'll want to modify the .htaccess files in your root directory and your /site/ directory the way they're described in the GoDaddy/1and1 instructions -- the internal server errors are definitely related to .htaccess.

This problem is currently fixed in the development branch on GitHub which you can download here:
https://github.com/bigtreecms/BigTree-C … evelopment

The issue should be fixed when beta 5 is released.  Keep in mind that the development branch may also have other issues, but we just tested it in a WAMP environment and those issues you encountered should be fixed.

Could you send us or post a screenshot of the warnings in the admin after the first failed installation?

We'll definitely address the notices problem in the installer, thanks for pointing that out!

This bug should be fixed in the 4.0 beta 2 release that is now available for download.

To setup a many-to-many field you'll want to create a table that relates one set of content to the other.  So let's say we have a btx_news table and a btx_categories table and we want to relate a news article to multiple categories.

We'll create a btx_news_categories table to tie them together.  Let's say it looks something like:

CREATE TABLE `btx_news_categories` (
  `news` int(11) unsigned NOT NULL,
  `category` int(11) unsigned NOT NULL
);

If we wanted to allow priority / sorting to the many-to-many relationship we could also add a "position" column that is also int(11).

Once this intermediary table is setup, edit the News module's form and click the "Many To Many" button in the header of the fields table.  It should add a blank row to table with Many To Many as the type.  You'll want to throw in a Title there, in this case "Categories" would be appropriate.

Next, click the Edit icon to pull up the options for the Many To Many field.  Choose "btx_news_categories" for the "Connecting Table" and the My ID and Other ID fields should now be filled with fields from that table.  In this instance we would choose "news" as My ID (since it relates to the table the form currently relates to) and "category" for Other ID.  For "Other Table" we would choose "btx_categories".  That should now populate "Other Descriptor" and "Sort By" with fields from btx_categories.  We'd choose whatever the title field in btx_categories was for "Other Descriptor" and probably use the same field for "Sort By" so it's easy to choose categories.

After that, save the field options and the form and you should now have a selector widget in your form that lets you choose categories to relate to the news item.  It'll populate the btx_news_categories table with the news item's ID and the category's ID for you to query against on the front end of your site.

Let me know if you have any questions!