Sorry I meant 2.7.2 — the Form Builder release version that I tagged in the git commit above. It should have auto-released to the BigTree extensions repo.

It looks like that crash happens if you try to create a form without any fields in PHP 8.2+ — I'll push up a fix for that soon.

You can go to GitHub and hit the 4.5-devel branch here:
https://github.com/bigtreecms/BigTree-C … /4.5-devel

Use the "Code" dropdown and you can download a zip of the repository where you should be able to grab the core directory.

Haven't ran into this personally but I'll see if I can replicate it — I don't see any changes in 4.5.3 that would appear to affect using files from the file manager. Have you isolated it to that version bump exactly?

This is upgraded to 1.0.1 now which fixes some warnings and uses full PHP tags.

Very strange! Are your local and remote using different versions of PHP?

Did you run composer update on the server? You might not have the composer package for the Google Analytics API or your composer.json file might not be the latest one from BigTree 4.5.7.

Weird, I'm not able to replicate this. Is there a certain template that it always occurs on? I did push up a fix to 4.5-devel for BigTreeCMS::urlify so that it doesn't crash on a null value though.

Thanks Doon! Nothing deadly, just lots of downed trees.

Adding https:// to the static_root won't help the existing assets (you will want to update them in the database directly — that is the right course of action!) but I believe it should prevent future uploads from getting // by default but I could be wrong. It's been a long time since I last ran into the issue!

Hi Doon! Sorry for the late reply, I believe this is fixed in 4.5-devel (you'll have to re-save a page with corrupt title data) — there's quite a lot waiting in there for a 4.5.2 release, I should kick that out soon (maybe this weekend).

Events 1.2 will work fine with BigTree 4.5 but will have warnings / errors (possibly) in PHP 8. It could be manually updated to work with PHP 8, you'll just have to track down the errors and resolve them (they're usually just issues with skipping checks on non-existent arrays).

Events v2 has a fairly similar database structure as Events v1 with the exception of recurring events being handled very differently (through recurrence rules) so any events that are setup to be recurring will not be able to easily be migrated over without losing their recurrence. On the template side the event instances are returned as objects instead of arrays and fields in the database that are not in the default Events v2 schema for btx_events_events will be added to the AdditionalFields property array.

TinyMCE's cache is notoriously sticky. If clearing browser's cache doesn't work then it's likely a custom override somewhere that's telling BigTree to use a different version of TinyMCE.