Multiple issues upgrading to v6

[NoelDeMartin]

Hi there,

Yesterday I upgraded my website to v6, and I faced multiple issues. I wonder if I'm doing something wrong, or what. In case you want to look at the code, my site is open source and all the content is there in markdown files: https://github.com/noeldemartin/noeldemartin.com (and you can see all the changes I did during the upgrade in this diff).

None of these errors happened in v5, so it has to be related to this update.

1. Critical Issue: Out of Memory with Antlers

A bunch of pages in my website are now broken, because I didn't manage to get them working with antlers :/. In particular, when I enable antlers for this blog post I get the following error:

Symfony\Component\ErrorHandler\Error\FatalError
Allowed memory size of 134217728 bytes exhausted (tried to allocate 10485760 bytes)
error source: vendor/statamic/cms/src/View/Antlers/Language/Analyzers/TagPairAnalyzer.php:368

Because of this, I have disabled antlers in my blog posts for now.

2. Medium Issue: Antlers @ escaping

After the upgrade, I had many issues like this one:

Incomplete arguments for @close directive Line 12 char 35. Exception thrown while parsing an Antlers enabled field [content]

The thing is that @close is not a directive. I've even had this issue with @vinnl, so I'm sure this isn't a directive. What's even more disconcerting, is that it doesn't always fail :/. For example, in this other blog post, I get the error above because I'm including a Vue code snippet. However, that blog post includes many code snippets, and for some reason only some of them throw this error. I could keep the @close in others without a problem 🤷.

3. Medium Issue: Invalid migration file

I'm not sure when it happened, but after upgrading I had a migration called 2026_02_08_103105_drop_origin_on_global_set_variables.php which threw an error (basically, because the table global_set_variables doesn't exist in my database).

It is possible that I am running an uncommon setup, because I have most the content in markdown files, except the users in an .sqlite database. Still, I didn't create this migration for sure, so whichever script is creating it could have looked at the previous migrations to see if this one was necessary.

I was able to solve this by removing this migration file.

4. Minor Issue: GD extension required

I suppose this was always required, but I was able to use v5 without having this so I wonder why it's failing now.

[NoelDeMartin]

In case somebody else stumbles upon these issues, I got some help in the Discord server so I'm going to mark this as solved.

Here's how I worked around them:

1. I simply upgraded the memory limit with ini_set('memory_limit', '512M') 😅. I'm still not sure what changed in v6 that made this happen, but this seems to work for now. I also realized I wasn't using static caching, so I enabled it with the "half" strategy and I don't this should be much of an issue anymore (unless I write even longer blog posts!!).

2. I still have no idea why this happens in some places and not others, or what changed in v6. But I worked around it by urlencoding the @ character in urls, and using the noparse tag elsewhere. I opened a follow-up issue because I still think something like this should be mentioned in the upgrade guide.

3. & 4. I still have no idea what caused those, but I already solved these by removing the invalid migration and installing the GD extension.

[duncanmcclean]

Not sure about the Antlers issue - I'll leave them for someone else.

Medium Issue: Invalid migration file

Do you have the Eloquent Driver installed? If so, which repositories do you have enabled? php please support:details will tell you.

Minor Issue: GD extension required

Glide uses GD by default, but you can also use ImageMagick or libvips, depending on which extensions are installed on your server.

GD/ImageMagick were "required" with Glide in v5 so not sure how this became an issue with the v6 upgrade. Were you running into errors?

[NoelDeMartin]

Do you have the Eloquent Driver installed?

I do, but I'm only using the database for users, for everything else I'm using files. Here's the output of the support:details command:

Environment
Application Name: Noel De Martin
Laravel Version: 12.50.0
PHP Version: 8.5.0
Composer Version: 2.8.12
Environment: local
Debug Mode: ENABLED
URL: localhost:8000
Maintenance Mode: OFF
Timezone: Europe/Madrid
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: null
Cache: file
Database: sqlite
Logs: single
Mail: log
Queue: sync
Session: file

Storage

Statamic
Addons: 1
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.2.4 Solo

Statamic Addons
statamic/eloquent-driver: 5.1.1

Statamic Eloquent Driver
Addon Settings: file
Asset Containers: file
Assets: file
Blueprints: file
Collection Trees: file
Collections: file
Entries: file
Fieldsets: file
Form Submissions: file
Forms: file
Global Sets: file
Global Variables: file
Navigation Trees: file
Navigations: file
Revisions: file
Sites: file
Taxonomies: file
Terms: file
Tokens: file

GD/ImageMagick were "required" with Glide in v5 so not sure how this became an issue with the v6 upgrade. Were you running into errors?

Yeah, I don't know how this became an issue only now :/. I don't use any of the Statamic image manipulation helpers, I just add .jpg and .png files to my public folder, so I don't do any image manipulation. But I guess this is required by these dependencies. I just thought I'd mention it because they could have been added as a required dependency, whilst they were optional before? I don't know, you can look at the diff on the composer.json if you want. I don't think I added or removed any image-related dependencies: NoelDeMartin/noeldemartin.com@6519525

[duncanmcclean]

I do, but I'm only using the database for users, for everything else I'm using files. Here's the output of the support:details command:

Okay, thanks!

You actually don't need the Eloquent Driver for eloquent users, that part is in core. I'll take a look into why the migration was published though. 🙂