Field metas missing after upgrade.

What version did you upgrade from and to? And what sort of field type is {fontDesignerName}?

Hi @Robin,

Thanks for the reply and I hope that you’re having a good day

So I’d upgraded from v2.5.5 to v3.5.16, it went well in the process and unfortunately, I didn’t notice that the sub-domain http://famira.firstascentstaging.com/typefounders/catalog/ is not working well, there are few sub-domain aside from /typefounders and they look okay.

So in the http://famira.firstascentstaging.com/typefounders/catalog page, you’ll notice the variables are just displayed in the site and to other site pages.

FYI: here’s the live old version that I’ve upgraded to 3.5.16, http://www.kombinat-typefounders.com/catalog.

Thanks

That’s weird!

I guess my first thought is, if you’re going to keep upgrading (and I would unless there’s a really good reason not to), I’d probably push on through and get on v5 and take another look at it.

It may be an issue that upgrading resolves.

If not, I’d start by simplifying. Get the very simplest template you can and see if it breaks. Something ike

{exp:channel:entries entry_id="5"}
{title}:


{FontDesignerName}something {/FontDesignerName}

{/exp:channel:entries}

There may be an issue with a conditional. I’d wonder if perhaps there’s something going on with the case in the custom field name- can’t really see it, but might be possible. Anyway, simplifying would be my first step just to eliminate a bunch of possibilities. But only after upgrading.

nvm, I got it fixed, it’s something related to the custom Channels, from external extension called Playa, I have to manually add those Channel and modify affected Content, weird enough though that it works on other Domain, anyway, thanks for the time.

Unfortunately, I got a new problem, below.

Error
Something has gone wrong and this URL cannot be processed at this time.

I assume this is related to the module used, condition or syntax.

My bet would be a conditional. If you have debug set to 1 or 2 in the config and are logged in on the frontend as a superadmin, it should give you a bit more detail.

If that doesn’t help, what I always do is simplify until I can spot it. But it’s about got to be a conditional.

And I’m not sure how difficult it would be to re-run the upgrade to v3, but given any choice in the matter, I’d move from playa fields to native relationships. You can use this importer when on the latest version of 2 and it will create copies of the data in native relationship and grid fields.