You can disregard that rule, it's to ensure PHP gets the proper modified headers when apache_request_headers() is unavailable: http://us3.php.net/manual/en/function.a … eaders.php
Sounds like IIS handles this properly: http://msdn.microsoft.com/en-us/library … 80%29.aspx

I have BigTree running a few sites on 1and1. For each site I set up a php.ini file with some custom values:

magic_quotes_gpc = Off
magic_quotes_runtime = Off
magic_quotes_sybase = Off

allow_url_fopen = ON

zlib.output_compression = On

memory_limit = 32M
upload_max_filesize = 32M
post_max_size = 32MI also set the document root to the /site/ directory through the hosting control panel to avoid needing a separate .htaccess file in the root directory. Otherwise, you may need to include '/site/' in the .htaccess files' rewrite rules:

RewriteRule ^(.*)$ /site/index.php?bigtree_htaccess_url=$1 [QSA,L]

You will definitely need some PHP knowledge to do anything in BigTree. Here are some resources to get you started there:

-Docs: http://us1.php.net/manual/en/
-Getting Started (tutorial): http://us1.php.net/manual/en/getting-started.php
-PHP Academy: https://phpacademy.org/videos
-Codecademy: http://www.codecademy.com/tracks/php
-Lynda.com: http://www.lynda.com/PHP-tutorials/Intr … 485-2.html

PHP Academy includes some PHP and MySQL tutorials. Codecademy is probably the most basic and a good place to start.

This should help get you started understanding Modules: http://www.bigtreecms.org/documentation … e/modules/
Then as you start building your module, you'll want to read up on the Geocoding field type: http://www.bigtreecms.org/documentation … geocoding/

Step-by-step, this would look like:

1. Create table for new your module
2. Build your new module in the BigTree developer section
3. Remember to add a new geocoding field when building your module's form
4. Enter some new markers with addresses
5. In your template, use the module to query for your new markers
6. Draw your new markers.

You should start by setting up a new table containing the "latitude" and "longitude" fields to control your module. You can then use the "Geocode" field type when building the module's form. BigTree will automatically update the proper fields on save.

To actually display the markers on a map you're going to want to check out the Google Maps Javascript API: https://developers.google.com/maps/docu … avascript/

I'm seeing it in Chrome myself, but if I zoom in or out it hides. Try zooming back to 100% and it should be reappear.

No, it shouldn't be. Are you on the newest 4.0 official release? Do you get a little hand when hovering over that empty area where it *should* be?

Just click the little blue icon next to the field when editing the form, you'll get a modal with all the field type options including image dimensions.

No special fields are required. Tags are actually a relational system. The "bigtree_tags" table stores the actual tag (as well as metaphone info and a generated route), while the "bigtree_tags_rel" table stores the relationship between the tag and an individual page or module item. A basic SQL join is used to find tagged pages or module items, but you could always write a custom query to find everything related to a specific tag. Check out these tag related functions in the docs to help get you started:

http://www.bigtreecms.org/code-referenc … CMS.getTag
http://www.bigtreecms.org/code-referenc … TagByRoute

http://www.bigtreecms.org/code-referenc … agsForPage
http://www.bigtreecms.org/code-referenc … agesByTags

http://www.bigtreecms.org/code-referenc … agsForItem
http://www.bigtreecms.org/code-referenc … atedByTags

LDAP implementation always seems to be pretty specific to the client, so I don't think we plan to support it out of the box right now. You are correct in that you can extend the BigTree admin class to add or override any internal functions as you see fit.

You'll need to enable tagging in the module. Head to the developer tab and edit the form for the blog posts. There should be a checkbox to enable tags.

I think there might be an issue with how your module form is set up. This indicates there isn't a default form setup since it's trying to include "p3.php." For some reason BigTree thinks the pending item id is a custom action. What does the URL throwing the error look like? Do you have a default form set up, along with an "add" and "edit" action?

I think you need to double check you MySQL login values in the config.php file. All errors stem from the first, where you are being denied access to the database.