What type of environment is it failing on? You mention it works in production on Linux — are you running a development machine on Windows?

Does your web server show anything in the error logs? Do you see anything when you view source?

You're likely fine with leaving in the override for BigTreeModule since that class is strictly used for front end logic display which shouldn't change at all.

You can check for whether you're updating an existing entry by doing:

if (!empty($bigtree["existing_data"]["id"])) {
   // Updating something that already exists
}

You can’t open actions in a new tab by default. You would need to create a custom view entirely to do that.

That's a tricky one. On the one hand I agree the expected behavior from a rational standpoint would be that sub-pages would also expire if the parent page did. On the other hand, we'd have to do this via a cron task to make it efficient. When you archive a page at the time of archival it can set the archived state of all the descendant pages. Expired status on the other hand is checked on the database row at fetch time. We'd have to traverse the page tree for each page request to see if any ancestor page is expired which isn't ideal. Since this would be a core behavior change which might cause unexpected results for people that for whatever reason do depend on sub-pages being alive still I'm going to log it as something we'll try to add in BigTree 5.

Currently, there's no plans to add this into BigTree 5 but that's not to say that it won't be added -- it would be a great addition. It would require all field types to be able to diff the content and then provide output to a differential tracker. A lot of work to implement but something I'd love to see if the community contributed it.

The developer that originally built your site should be able to edit the form to re-add the crops if they are missing. If you’re looking to do it yourself, the developer documentation on this site will point you in the right direction.

My first guess if it's skipping crops entirely (and not throwing an errors) is that the configuration for the crops for that field got wiped. I'd also check the Developer -> Status panel to ensure that there's no directory permissions issues.

I'll try to make this happen in BigTree 5! We may be able to sneak it into a 4.4 release if 5 gets too delayed.

I don't believe there were any changes between 4.2 and 4.4 with how translation of staticroot functions but I could be wrong. Is $bigtree["config"]["static_root"] set in your environment.php file properly?

The /site/ folder is the web root of a BigTree project. If you want to insert HTML files that are outside the CMS, you can place them inside of that directory and they will not be routed through BigTree.

Developer documentation can be found here: https://www.bigtreecms.org/developers/d … tallation/

You can (and should) run a local development environment for making updates to BigTree but it isn't a "push" CMS where you have a local install that then updates the remote site — each environment is separate. BigTree 4.4 allows for git based workflows to pass configuration changes (e.g. Templates, Modules, Callouts, etc) via a git deployment which is what I'd recommend. How you can access the MySQL database and cPanel depends entirely on your hosting platform and not BigTree.

If you do not see the Developer tab (which is what you'd use to create new templates, modules, etc) then your user level is not high enough. You can adjust that in the bigtree_users table in the database (level 2 is a developer, level 1 is administrator, level 0 is normal user). Modules are usually custom to your implementation of BigTree (though it does look like you have some that are provided by Extensions such as Form Builder and Social Feed). There are no "plans" for BigTree as it's an open source platform and there is no official cloud hosted solution. It sounds like you need access to your host's MySQL and SFTP information which according to the footer of your website is likely https://www.fxdesigns.net/ — they'd also have more information about how they built the website.