Dan,

I think this may be related to a bug that Ben found today, but if this isn't the case let me know -- if you've tagged everything possible to a Many to Many then the whole many to many disappears when you try to edit the item the next time around. This is due to the (ideal) behavior of the tagger not showing up if there's nothing available to tag. It's on our list for an RC3 fix that will hopefully roll out around the beginning of March.

As far as One to Many, that's actually a field type Ben whipped up earlier today — hopefully he can respond here. He can probably export it and post it for anyone to have. I'm not sure if we're going to make it a core field type in the future or not but it's a possibility in 4.1 (we're feature frozen now for 4.0).

It looks like there is a bug with photo gallery processing as a Setting. I'll be sure to get this fixed shortly and released with the RC3 update.

The admin bar should show up on the front end of the site when you are logged into the admin area. Is it not working for you?

Right now the timeline is internal to get the most stable 4.0 release we can -- we're going to be publishing release schedules and feature expectations when 4.0 goes live.  GitHub is definitely the best place for any bugs you find, thanks!

I think to accomplish what you're asking with the URL scheme you'd need to create a custom router.php in in /custom/.

You'd also want to override a few functions in the BigTreeCMS class so that when getLink or getNavByParent is called it throws the /en/ or /es/ into your URLs.

RC2 is modifying the router.php file quite a bit to simplify and enhance routed templates so I'll have to let you know where to modify that when it rolls out. Basically, you'd want to add something like:

if ($bigtree["path"][0] == "es") {
    define("USER_LANGUAGE","es");
    $bigtree["path"] = array_slice($bigtree["path"],1);
} else {
    define("USER_LANGUAGE","en");
}

That would make the routing work properly when it starts with /es/. You'd probably need to put it in the line that precedes the $cms->getNavId call (I'm not sure what line it's on in RC1, but I think it's only called once).

For extending the BigTreeCMS class to properly get your /es/ links when your user's language is currently spanish you'd want to do the following:

• Create a class in /custom/inc/required/ that extends BigTreeCMS

• Edit your /templates/config.php file to define "BIGTREE_CUSTOM_BASE_CLASS" to the name of the class you created (it should be set to false in the default config, switching it to your custom class will make the default $cms variable an instance of your custom class instead of BigTreeCMS).

It looks like the following functions would need to be extended:

• drawXMLSitemap (if you want /es/sitemap.xml to show a separate sitemap of /es/ links)

• getBreadcrumbByPage

• getInternalPageLink

• getLink

• getNavByParent

They would mostly need to be changed to draw "es/" after WWW_ROOT when returning links if USER_LANGUAGE was set to "es". I'd be happy to write the extension class if you're interested. This is something that's come up a few times so we may be adding it as a core feature in the 4.1 release.

That's awesome! Glad to see it's working well for you!

Let me know if you come up with any cool method for doing it more easily. It's not something I've needed to do before so I haven't thought about it all that much!

Try this query:

INSERT INTO bigtree_users (`email`,`password`,`level`,`permissions`,`alerts`,`daily_digest`,`change_password_hash`) VALUES ('tester@test.com','$P$BVrfuFkCBcoGcwRUehyW951OJGwcJf0','2','','','','');

It sounds like the user creation in the install process is failing for you but I've never seen that happen before.

If you manually add a record to the bigtree_users table with your email address, the "level" column set to 2, and $P$BVrfuFkCBcoGcwRUehyW951OJGwcJf0 as the password field you should be able to login with the password "test".

We're planning on adding some kind of interface to the audit trail in the admin area in the 4.1 release but there aren't any solid plans for what will be involved yet.  I'll add the request to build audit information-gathering into the BigTreeModule class in some way in 4.1 as well.  If there are any specific methods you're interested in let me know!

BigTree stores all links as relative in the database so that when you push the database to your live server they are correct, so there's really only three steps to going live from your local development server:

1. Copy your files over to your live server and setup write permissions for the web server on /cache/, /site/files/, /custom/inc/, /templates/callouts/, /templates/basic/, and /templates/routed/ -- If you miss any of the file permissions you can check in Developer under Site Status and it will give you a list of directories that need write permissions.

2. Copy your database over to your live server.

3. Edit your /templates/config.php file to adjust your database connection parameters and your domain, www_root, static_root, and admin_root.

After that you should be all set on your live server. Let me know if you have any questions!

Can you try deleting the /cache/module-class-list.btc file and see if that fixes the error?