If you're using a custom HTML loader in /custom/admin/layout/_html-field-loader.php then you'll likely need to update the TinyMCE init to use TinyMCE 6's selector structure.

You can compare the files in 4.4-devel and 4.5-devel to see what's changed in their init (and plugins):

https://github.com/bigtreecms/BigTree-C … loader.php
https://github.com/bigtreecms/BigTree-C … loader.php

Hi Rand,

I think you have the wrong BigTree! This is a forum for the content management system, not the board manufacturer

Glad you figured it out! I think BigTree 4.5 requires PHP 7.4 if you're using AWS dependencies. I'm not sure which part of Form Builder in particular is requiring PHP 7 though.

It should check on every load of the extensions page. What version of Form Builder are you currently on? Can you drop your manifest.json file from the extension in here? Thanks!

This seems like it is likely a file permissions issue. Are you using git for version control? If so, you likely do not want to be adding new templates in the live environment but rather want to setup a local environment from which you can commit your changes (which in this case would be in /custom/json-db/templates.json). You can check the file permissions by going to the Developer section and choosing Site Status. That will tell you if there are any directories that BigTree will need write access to that are not writable.

Accessing the database isn't something I can answer unfortunately as there could be many ways in which the database connection could be setup. In AWS you're likely either running AuroraDB or MySQL/MariaDB via RDS. The connections could be restricted to only intra-network connections in which case you'd need to have an EC2 instance as an SSH jumping off point to connect externally.

Yes, it will definitely be ready before then. I am hoping for the next few weeks with the end of August being the latest. PHP 8 introduced a lot of breaking changes (things like running "count" on an empty variable are now errors rather than warnings) so currently it does not run on PHP 8 or 8.1.

It's hard to say — mod_security throws a lot of rules at the wall and hopes it catches attacks (while causing a bunch of problems in the process). You'd have to check the security logs and find out what rule the search was triggering and then disable that specific rule.

Sorry I missed this post (got sent to spam). resource:// usually means it's referencing something in the bigtree_resources table but that's usually an ID (e.g. resource://15). I can't say I've seen a resource:// URI targeting the S3 path before so I'm not sure what's going on there. It's possible a misconfiguration with the environment.php file causing weird URIs.

Sorry, just realized this was never responded to! If the response is empty it's either:

cURL is failing (maybe some kind of SSL error connecting to Google's servers) or the response you're getting is not a valid JSON response. This could be incorrect reCAPTCHA keys or something of that sort or possibly that your IP is being banned by Google for whatever reason.

If I had to take a guess I'd say the filter function is crashing. It's run in an eval() statement so it will fail silently but the record could miss getting into the table.

What browser are you using to do the install? The example site files are in /core/example-site/ but you'll also need to import the database dump from /core/setup/example-site.sql

Hi Tushar,

Published Revisions will only ever show the currently published page (it doesn't show previously published revisions since that would be ALL the past revisions). If you aren't seeing a list of previous page states it's possible that for some reason there's a database error when inserting into the bigtree_page_revisions table (maybe a custom override somewhere or a missed SQL migration?).

I'd see if the table structure matches what a fresh BigTree install provides.