[Support request] Undefined index: linkType

[David]

Hmm… nothing jumping out.
Are you able to push to a staging site and eliminate potential Plugin / Child Theme conflicts ?

[Josef]

I have no idea how to do that, so let’s say… no I am not able to.
Before the latest update (a few days ago) there were no error messages in the posts.

[David]

Few things we need to eliminate which means making some temporary changes and i was little concerned asking you to test if the site is live. But here they are:

Permalinks:

a) do they need rebuilding by clicking Save Changes in the Settings > Permalinks
b) is the custom structure causing an issue ? to test that switch to default and do step a above.

Child Theme:

Switch to parent theme temporarily to eliminate a child theme issue.

Plugin conflicts:

Temporarily disable all plugins aside from GP Premium to check for conflicts. This includes any caching.

[Josef]

1. I saved the permalink settings (did not help)
2. I changed to structure to default (did not help, so I changed it back to custom)
3. The child theme is absolutely necessary for the site, many pages built which that, so it should never be disabled.
4. I try to disable the plugins (except the contact form and stripe plugins, that should nothing to do with permalinks)

[Josef]

After disabling all plugins and enabling them one by one, I can confirm that it’s the GENERATEBLOCKS plugin that causes the error message. If I disable that plugin, there is no error message, however the design of the page falls apart, so I have to keep it enabled.

Generateblocks = Version 1.4.2

[David]

The GenerateBlocks plugin is required to build the Post Navigation Block Element, so disabling GenerateBlocks was the same as disabling the Block Element.

3. Is it possible to temporarily switch to parent ? It will at least identify if there is a conflict and if there is we can look at what code may be causing that.

[Josef]

Yes sure, just do that quickly and don’t leave it like that wehn you finished 😀

[David]

Would you mind just testing – by:
a) reenabling the Element
b) switching to the parent theme

Then check if the error is still there.
If the error persists then i need to do some head banging.

If the error goes away we can then login and look at the child theme.

is that ok?

[Josef]

Main theme active: https://prnt.sc/26wy6j4
Element activated.

Error is present.

[David]

Hmmm… i am gonna bat this over to Tom to see if he has any ideas on whats going on here.

[Tom]

Hi there,

Your Post Navigation Container blocks have settings set in them from GenerateBlocks Pro, but it doesn’t look like you have GenerateBlocks Pro on the site. This is causing the notices as the plugin is trying to use functionality that doesn’t exist.

I went ahead and removed those settings and updated the Element (hope you don’t mind, I have a backup in case). It seems to have fixed the issue. Can you confirm?

[Josef]

Hello,

Yes, thank you, the error message is gone.
However, I am confused about the Generate Blocks Pro.
I bought the premium version of the theme, which is Generatepress and GP Premium.
What is Generate Blocks Pro?
And how was this element set by that if I don’t have that?

[Tom]

Did you build the Element from scratch or did you import it from somewhere?

[Josef]

Originally it’s the default element that comes with the theme, I did not change it.
Then your colleague David told me to try to make a new one by selecting a template from the theme.
So this element came from the theme, it’s not custom made.

[Tom]

And then you customized the template? The look you have there isn’t one we have in our templates. Which template did you use from the plugin? I’ll review it and make sure it doesn’t have any GenerateBlocks Pro stuff in there.

Thanks!

[Author]

Posts